Scale without vault sprawl
Unique addresses derive from one seed, so onboarding ten thousand customers does not mean ten thousand key ceremonies or ten thousand fees.
Wallet-as-a-Service (WaaS)
Generate unique deposit addresses programmatically from a single MPC vault seed. Attribute deposits per customer, keep full recoverability, ship wallet features in weeks — and never create a vault per user again.
Unique addresses derive from one seed, so onboarding ten thousand customers does not mean ten thousand key ceremonies or ten thousand fees.
No vault-creation delay in the deposit path. Addresses are issued on demand at API latency, so checkout never waits on cryptography.
Create, query and manage addresses and balances through the wallet engine APIs, with role-based access scoped per key.
What you can build
curl -X POST \
https://api.nodus-360.com/v1/vaults/vlt_8f21/addresses \
-H 'Authorization: Bearer $NODUS_KEY' \
-d '{ "chain": "ethereum", "count": 250,
"label": "customer_batch_apr" }'Key ownership models
Three models, all with BIP39 disaster recovery. In none of them does Nodus360 or io.finnet hold key material — which is usually the difference between launching a wallet and becoming a custodian.
Model A
Omnibus model. Your team holds every share; end users never touch cryptography.
Model B
Non-custodial product model. Shares live on user devices; you provide the interface, not the liability.
Model C
Threshold split between you and your user, so neither side can move funds alone.