Lately I’ve been wondering how position limits even work once everything moves on-chain.
In traditional markets one legal identity usually means a limited set of accounts. You can’t just open twenty new ones and pretend the 5% cap still holds. On public chains it’s the opposite. Addresses are cheap. Splitting holdings becomes the default move for anyone trying to stay under a threshold.
That mismatch is what made me look closer at Dusk. The part that stood out wasn’t the privacy angle. It was the idea of binding identity to accounts in a way that actually survives corporate actions, mergers, or LEI changes. If an identity changes, the old account has to be retired properly instead of just getting abandoned for a fresh address. That feels closer to a registry than the usual free-for-all.
For capital allocation this matters. If limits can be enforced at the contract level instead of sitting in some issuer spreadsheet, the risk of sudden over-limit events drops. That could make larger tickets feel safer. The realistic downside is clear though. If the identity layer turns rigid or the proofs become a bottleneck, liquidity and participation suffer. People will still look for workarounds.
One lesson I’ve taken from past cycles: rules written only in documents are advice. Advice doesn’t stop anyone. Enforcement that can fail in real time does.
Would you accept position limits that only live in a prospectus, or do they need to be something the contract itself can reject?
$DUSK #dusk @Dusk
In traditional markets one legal identity usually means a limited set of accounts. You can’t just open twenty new ones and pretend the 5% cap still holds. On public chains it’s the opposite. Addresses are cheap. Splitting holdings becomes the default move for anyone trying to stay under a threshold.
That mismatch is what made me look closer at Dusk. The part that stood out wasn’t the privacy angle. It was the idea of binding identity to accounts in a way that actually survives corporate actions, mergers, or LEI changes. If an identity changes, the old account has to be retired properly instead of just getting abandoned for a fresh address. That feels closer to a registry than the usual free-for-all.
For capital allocation this matters. If limits can be enforced at the contract level instead of sitting in some issuer spreadsheet, the risk of sudden over-limit events drops. That could make larger tickets feel safer. The realistic downside is clear though. If the identity layer turns rigid or the proofs become a bottleneck, liquidity and participation suffer. People will still look for workarounds.
One lesson I’ve taken from past cycles: rules written only in documents are advice. Advice doesn’t stop anyone. Enforcement that can fail in real time does.
Would you accept position limits that only live in a prospectus, or do they need to be something the contract itself can reject?
$DUSK #dusk @Dusk