How 2-5-foundation/vane_web3 works
Project type and purpose
• This is a Rust-based, full-stack “sovereign custodian” for Web3 users (“vane_web3”), acting as a local safety layer around any wallet to confirm addresses, simulate transactions, verify ownership, then route transactions to blockchains.
• It comprises multiple Rust crates (app, node, db, db-wasm, primitives, tests) plus a minimal JS/TS front-end MVP (vane_web3_mvp).
File structure
• Top-level crates:
• app: binary that kicks off the MainServiceWorker
• node: core workers (P2P, RPC, Telemetry, TxProcessing, Cryptography)
• db: local storage via Prisma + native code
• db-wasm: same DB logic compiled to WASM for browser/WASI targets
• primitives: shared data structures
• integration-test: end-to-end tests
• scripts: DB codegen (Prisma)
• vane_web3_mvp: front-end (Node.js + Bun) to drive the core wasm in browsers
• Config files: Cargo.toml, Dockerfile, .env, .dockerignore
README for additional insights
• Technical components = workers inside the MainServiceWorker orchestrator:
1. DbWorker
2. P2PWorker
3. TxProcessingWorker
4. RpcWorker
5. TelemetryWorker
6. MainServiceWorker
7. Remote Db (Airtable) peer discovery
Elements
• Labels: name each crate/worker and external system
• External networks in a third (e.g., clouds for P2P & blockchains)
Detailed capture of essential architectural elements
• Link TxProcessingWorker to “Blockchain JSON-RPC endpoints” cloud.
• Link RpcWorker bidirectionally to “Front-end client (JS/WASM)”.
• Link TelemetryWorker back to the Local DB.