#dusk
Quick question nobody asks about crypto custody: who actually holds the keys?
Not the marketing answer.
The real one.
Most of the time it's a third-party custodian's servers, running software you don't control and can't fully audit.
Fine for a personal wallet.
Not fine for a regulated exchange with a legal duty to control its own infrastructure.
That's the real problem NPEX had.
Not "is custody secure," but can they use it without handing control of their stack to a SaaS provider they don't operate.
The answer was Cordial Systems. Self-hosted custody, meaning NPEX runs it themselves instead of trusting someone else's servers. Cordial's already worked with Figure, which has put over $20 billion in private credit onchain. Not an unproven vendor. Dusk Vault sits on top as the actual custody product NPEX uses day to day, and NPEX isn't just integrating it either. They're a client running their own infrastructure on it.
I keep coming back to why self-hosted matters so much. A regulated venue can't just say "trust our custody provider." Regulators ask who controls the keys, who can be subpoenaed, whose failure takes the assets down with it. A third-party SaaS nobody's heard of is a real problem. "We run it ourselves" is a very different conversation.
It also answers something people treat as separate. Everyone talks about privacy and compliance like that's the whole story. Custody is the unglamorous third leg nobody brings up until something breaks, and then it's the only thing anyone's asking about.
Honestly still working out where I land on this. Self-custody sounds great until an institution is holding billions in client assets and something breaks at 2am. Does self-hosted custody actually reduce risk for a regulated venue, or does it just move the risk somewhere less visible?
$DUSK @Dusk
Quick question nobody asks about crypto custody: who actually holds the keys?
Not the marketing answer.
The real one.
Most of the time it's a third-party custodian's servers, running software you don't control and can't fully audit.
Fine for a personal wallet.
Not fine for a regulated exchange with a legal duty to control its own infrastructure.
That's the real problem NPEX had.
Not "is custody secure," but can they use it without handing control of their stack to a SaaS provider they don't operate.
The answer was Cordial Systems. Self-hosted custody, meaning NPEX runs it themselves instead of trusting someone else's servers. Cordial's already worked with Figure, which has put over $20 billion in private credit onchain. Not an unproven vendor. Dusk Vault sits on top as the actual custody product NPEX uses day to day, and NPEX isn't just integrating it either. They're a client running their own infrastructure on it.
I keep coming back to why self-hosted matters so much. A regulated venue can't just say "trust our custody provider." Regulators ask who controls the keys, who can be subpoenaed, whose failure takes the assets down with it. A third-party SaaS nobody's heard of is a real problem. "We run it ourselves" is a very different conversation.
It also answers something people treat as separate. Everyone talks about privacy and compliance like that's the whole story. Custody is the unglamorous third leg nobody brings up until something breaks, and then it's the only thing anyone's asking about.
Honestly still working out where I land on this. Self-custody sounds great until an institution is holding billions in client assets and something breaks at 2am. Does self-hosted custody actually reduce risk for a regulated venue, or does it just move the risk somewhere less visible?
$DUSK @Dusk