mafintosh / mafintosh/peer-wire-protocol
Question about how the contract works.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 47
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Hey friend. I have a P2P wire protocol question.
I have been building my own implementation. I have been simulating responses from other P2P programs and I can’t get passed the handshake. I get a handshake:
bufferSize!: 68
Protocol type: BitTorrent protocol
infoHash: aff8bda8adebdab34e1af9ac648bd93c13ed6344
peerId: 2d4c54313030302d764874743153546a4d583043
Then I try sending a handshake back or a interested or any other code...
Do you have any advice?
Thanks,
Connor.
(Also, is there a better place to contact you?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report identifies the P2P handshake and interested message exchange as the relevant entry points, but names no files or tests. Start by tracing the handshake response in this JavaScript/Node.js protocol implementation and comparing the simulated exchange with protocol expectations; done means a peer completes the handshake and accepts a subsequent message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100