#dusk $DUSK
Every RWA chain claims compliance built in. What actually made me stop was one specific line in Dusk's market infrastructure docs: transfer controls exist as a distinct, enforced step Enforce who can hold or transfer separate from onboarding and separate from settlement. Most chains blur those into one thing: if you have tokens, you can move them.
So I wanted to check what that separation actually means for NPEX going onchain.
Documented: Dusk's architecture splits the regulated-asset lifecycle into stages issuer setup, investor onboarding (wallet binding to verified participants), transfer controls, trading/distribution, and settlement with deterministic finality. Each stage is a checkpoint, not just a UI step. Zedger runs this natively on DuskDS Hedger brings a similar model to DuskEVM using homomorphic encryption plus ZK proofs so balances stay encrypted while remaining auditable.
Why it matters: a public ledger can prove a transaction happened. It can't, by itself, prove the recipient was eligible to receive that asset. That eligibility check is what separates Tokenized from regulated. NPEX bringing its ~€300M+ AUM onchain is the first real test of whether that enforcement layer runs live, not just in docs.
What I can't confirm from public material: whether NPEX's current onchain activity actually routes through wallet binding and transfer control logic at the contract level, or whether that enforcement still happens off-chain today with the blockchain acting mainly as a settlement and record layer for now. Dusk's docs describe the design; they don't show me NPEX's live configuration.
Genuinely curious has anyone seen a transaction (or rejected transaction) from the NPEX deployment that shows transfer-control logic actually blocking an ineligible holder onchain rather than at the brokerage layer?
@Dusk_Foundation $DUSK #dusk
Every RWA chain claims compliance built in. What actually made me stop was one specific line in Dusk's market infrastructure docs: transfer controls exist as a distinct, enforced step Enforce who can hold or transfer separate from onboarding and separate from settlement. Most chains blur those into one thing: if you have tokens, you can move them.
So I wanted to check what that separation actually means for NPEX going onchain.
Documented: Dusk's architecture splits the regulated-asset lifecycle into stages issuer setup, investor onboarding (wallet binding to verified participants), transfer controls, trading/distribution, and settlement with deterministic finality. Each stage is a checkpoint, not just a UI step. Zedger runs this natively on DuskDS Hedger brings a similar model to DuskEVM using homomorphic encryption plus ZK proofs so balances stay encrypted while remaining auditable.
Why it matters: a public ledger can prove a transaction happened. It can't, by itself, prove the recipient was eligible to receive that asset. That eligibility check is what separates Tokenized from regulated. NPEX bringing its ~€300M+ AUM onchain is the first real test of whether that enforcement layer runs live, not just in docs.
What I can't confirm from public material: whether NPEX's current onchain activity actually routes through wallet binding and transfer control logic at the contract level, or whether that enforcement still happens off-chain today with the blockchain acting mainly as a settlement and record layer for now. Dusk's docs describe the design; they don't show me NPEX's live configuration.
Genuinely curious has anyone seen a transaction (or rejected transaction) from the NPEX deployment that shows transfer-control logic actually blocking an ineligible holder onchain rather than at the brokerage layer?
@Dusk_Foundation $DUSK #dusk