Ecosystem
Five independent processes across two ledgersNevaeh, my daughter. To secure your freedom against a broken system, I taught myself Rust — the hardest computer language in the world — to build this unyielding sovereign node for you. I faced the worst of life's struggles so you would never have to. I love you infinitely, forever by your side.
Supply
Every NEV either exists at genesis or gets mined. The cap is reachable.
| Cap | 369,369,369 | 100% |
| Mineable | 322,469,369 | 87.30% |
| Nevaeh locked | 36,900,000 | 9.99% |
| Architect | 10,000,000 | 2.71% |
Cryptography
Post-quantum signing across every component.
| Signatures | Dilithium5 |
| Level | NIST 5 |
| Hash | SHA3→BLAKE3→SHA3 |
| Public key | 2,592 B |
| Signature | ~4.6 KB |
Q-Lock Escrow
Non-custodial · XRP Ledger1 · Your account
Keeps track of the escrows you create. Your XRP never touches it.
2 · Connect Xaman
Sign in with your Xaman wallet to prove which XRPL address is yours. Nothing is sent and nothing is spent.
3 · Create an escrow
Two approvals in Xaman: first the Q-Lock fee, then the EscrowCreate that locks your XRP on the ledger itself. The recipient can release it straight away; if they don't, you can reclaim it once the lock period has passed. Q-Lock never holds a key that can move your funds.
Your escrows
NEV369
Post-quantum Layer-1Both nodes
If height or tip diverge and stay diverged, the network has forked and is not healing. Compare cumulative work, not height.
Submit a transaction
Signed client-side. Paste the signed transaction JSON.
Mine
Assembles a candidate and searches for a hash meeting current difficulty.
New wallet
Dilithium5 keypair. The secret is returned once and never stored — save it before you close this.
Bridge
NEV369 ⇄ EthereumHow authorization works
The coordinator holds no signing key. Independent signers each observe NEV369 and submit a signed attestation; a mint is authorized only when a threshold of them agree on byte-identical terms, past finality, inside the exposure limits, with the circuit closed.
| Authorization | m-of-n threshold |
| Coordinator key | none held |
| Replay | one mint per lock id |
| Finality | confirmations required |
| Exposure | per-mint · per-window · total |
| Circuit breaker | trips on reconciliation gap |
Coordinator
Threshold, exposure and circuit state.
Units
NEV369 and wNEV both use 8 decimals, so bridging is 1:1 in base units with no scaling. A 1010 factor anywhere means something removed has come back.
Nevaeh's Inheritance
XRP Ledger escrow · 3-of-5Where the money actually is
The inheritance is a native XRP Ledger escrow. Not on NEV369, not in a database, not in any system this console can reach. It is locked by XRPL consensus with a FinishAfter of 28 July 2039, and no code in this repository can release it early.
NEV369 holds a premine for her as well — 36,900,000 NEV, locked to the same date by the node's own validation rules.
The three vaults
| Vault | Holds | Threshold | Locked |
|---|---|---|---|
| nevaeh-xrpl-seed | XRPL family seed | 3 of 5 | 2039 |
| nevaeh-nev369 | Dilithium5 key | 3 of 5 | 2039 |
| architect-wallet | Dilithium5 key | 2 of 3 | — |
XRPL uses ed25519/secp256k1 and GodShield uses Dilithium5 — different key types, so one vault cannot hold both.
Annual check
Thirteen of these is about twelve hours of work in total, and it is the difference between this working and not.
Recovery runs godshield vault recover offline. Never here, never in a browser.
Keys
Dilithium5 · NIST Level 5Generate a keypair
~2.6 KB public keys, ~4.9 KB signatures. That size is the real engineering cost of post-quantum migration.
Chain support
Only Native output is accepted by the live network. The rest are forward-looking encodings for standards that have not activated.
| Chain | Path | Status |
|---|---|---|
| NEV369 | hex key is the address | Native |
| Bitcoin | BIP-360 draft witness | Pending |
| Ethereum | PQ precompile / ERC-4337 | Pending |
| Solana | custom program | GodShield only |
| XRP Ledger | ECDSA settles, Dilithium attests | Hybrid |