💡 A collection of experimental prototypes exploring decentralized transaction infrastructure, peer-to-peer architecture, and core network flows—built to rethink how interoperable systems (inspired by Beckn) can function without centralized aggregators.
🌐 Peer-to-peer transaction layer without cloud-based aggregators.
- Leverages ICE, STUN, and UDP hole punching to enable direct buyer-seller communication across NATs.
- Deployable proxy agent to handle STUN + proxy Beckn app traffic.
- Simulates registry-level changes to support peer URLs via STUN.
Tech Stack: Java, STUN, ICE, Docker, HTTP/3, UDP
Goal: NAT traversal without cloud infra.
🔄 Minimal reference implementation of a decentralized routing gateway.
- Lightweight gateway that forwards discovery/search/order messages.
- Simulates multi-node network behavior without centralized routing.
- Useful to mimic mesh-style routing or limited-scope registries.
Tech Stack: Python or Node.js
Goal: Simulate message routing across minimal infrastructure.
🗂️ Registry emulation service to mock participant registration.
- Emulates a Beckn-style registry for internal/local testing.
- Lets you register BAP/BPP endpoints without actual infra.
- Ideal for simulating fallback flows, failovers, or port-based STUN entries.
Tech Stack: Python (FastAPI)
Goal: Quick setup for local registry + testing flows.
🧪 End-to-end transaction flow simulation (Search → Select → Order).
- Mocks full transaction life cycle with hardcoded participants.
- Includes order fulfillment, cancellation, and updates.
- Useful to test conformance to transaction flow structure.
Tech Stack: Python or JavaScript
Goal: Simulate flows across mocked BAP/BPP for learning or debugging.
🔐 Prototype focusing on securing transaction payloads and signatures.
- Integrates payload signing, encryption (JWE/JWS).
- Can be used to simulate signing keys and message tampering detection.
- Extendable to support Zero Trust or federated identity experiments.
Tech Stack: Node.js / Python + cryptographic libraries
Goal: Explore core security & auth layers of open transaction protocols.
| Component | Technologies |
|---|---|
| Networking | ICE, STUN, HTTP/3, UDP |
| Languages | Java, Python, Node.js |
| Containers | Docker |
| Validation | Pydantic, FastAPI, JSON Schema |
| Infra Mocking | Lightweight Registry/Gateway setups |
git clone https://github.com/Archi-shaw/corenet.git
cd corenetEach folder contains its own README.md or instructions for setup.
Ideas for protocol enhancement, better routing, or identity flows? Open an issue or drop a PR — experiments welcome!
enerate individual README.md files for each project folder (STUNAgent, MockRegistry, etc.) too? I can help standardize each sub-project’s documentation.