Part 2 RFC: Implementation Roadmap
- Dominant language
- C#
- Stars
- 8k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
I'm working on Part 2. So I thought I'd share a bit of the roadmap. I'm aiming on publishing sometime in the next week but still have a few hurdles and could use your expertise.
Hop on to [our Slack](https://join.slack.com/t/nyc-crypto/shared_invite/enQtMjcwNTMxMzA3MjMzLWI5OWMwYTZkMmQ2MGJjNjcxYjVkOWM0MWJiNTQ4NWVhNmM5MzVmMzM2OTM1NjQ5MWM0OGNjZWJhZDdmMTk1OWE) if you wanna get involved.
- [x] **Basic Contract (P2P Protocol)**
- Endpoints:
- `get_chain`, `post_transactions`, `get_nodes`, `post_block`, ...
- [x] **Heartbeat Loop**
- Ported to `aiohttp` over Flask
- `asyncio` allows us to have an event loop for introspection (and pinging other nodes)
- [ ] **Transaction Verification**
- Using [Python NaCl](https://github.com/pyca/pynacl) to generate a public/private signing key pair: `private.key`, `public.key` which should be generated before runtime.
- Would still appreciate thoughts on this method
- [ ] **NAT (Opening ports on Router, like uTorrent/Transmission/Bitcoin Wallet): uPNP, NAT-PMP, PCP...**
- Attempting to open a port on the router at runtime using one of these protocols
- Bogged down on this one, poor python library support unsure how to proceed for now
- Would appreciate help on this one
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.