nexus-divachain - Action Report¶
Project: /home/user/Projects/nexus-divachain Created: 2026-02-20
Project Directory Reorganization (2026-02-20 08:06)¶
What: Reorganized nexus-divachain project files into ~/Projects/nexus-divachain/ with standard subdirectories.
Why: Files were spread across ~/Projects/nexus-node/, ~/Documents/, ~/backups/.
How: Moved files with mv, created symlinks at old paths for backward compatibility.
Files moved: - ~/Projects/nexus-node/divachain/ -> src/ (symlink back) - ~/Projects/nexus-node/Dockerfile.dev -> configs/ - ~/Projects/nexus-node/nexus-devnet.yml -> configs/ - ~/Documents/NEXUS_DIVA_PARTNERSHIP_PROPOSAL.md -> docs/ (symlink back) - ~/Documents/NEXUS_NODE_DISCOVERY_SKETCH.md -> docs/ (symlink back) - ~/backups/divachain_devnet_genesis_backup/ -> backups/devnet_genesis/
Backup: ~/backups/pre-reorg-20260220.tar.gz (41MB)
DIVA Chain Integration Design - Multi-Chain I2P-Native Seeding Layer (2026-02-20 14:24)¶
What: Designed DIVA chain integration as the anonymous seeding and discovery backbone for the full NeXuS stack.
Why: Need a decentralized node registry with zero clearnet exposure. Existing solutions require central servers or expose metadata. DIVA chain is I2P-native and battle-tested (successor to Konrad's original chain which was deanonymized reproducibly).
How: DIVA is multi-chain, born inside I2P, never touches clearnet. Node bootstrap: I2P tunnels build (10-30 min) then node reads chain for peer list, cipher manifests (IPFS hashes), profile hashes, relay pool membership. Node announces itself with only master pubkey + cryptographic proof of work - no name, no IP, no identity. Ephemeral rotating API tokens (3-10 min). Native XMR/BTC bridge built in. Two-layer key architecture: cold master key (Ed25519) signs rotating hot session keys (BIP32-derived). Contacts look up master pubkey, chain returns current session key signed by master. Balances sweep through XMR ring sigs before session wallet burns.
Files: docs/action_report.md, ROADMAP.md (nexus-phantom)
Dependencies: I2P (SAM protocol), IPFS, Monero
Proved PUT /tx works on develop-deno devnet (2026-03-01 02:48)¶
What: Fired up the local DIVA Chain devnet and proved PUT /tx accepts and processes transactions. Why: Core blocker for NeXuS integration — needed to confirm transaction submission works before the March 2026 Konrad meeting. How: Debugged a chain of issues in the develop-deno branch. Fixed 3 schema bugs (votes→proofs rename was incomplete), cleared stale LevelDB LOCK files, and got the node fully booting. Successfully submitted nexus:test and nexus:node:register transactions — both returned HTTP 204. TX commit requires quorum (multiple nodes voting) so pending in single-node devnet, but submission pipeline is confirmed working. Files: configs/nexus-devnet.yml (stop_grace_period 30s), divachain src/schema/* (3 bug fixes). Dependencies: Podman, podman-compose, nexus-i2p-net, localhost/nexus-diva-dev:latest image.