Settlements can be handled for transfers, but that does not mean the lifecycle can be self-driven. @Dusk The figures posted on the official website—2.1억+ DUSK staked, ~10 seconds SBA deterministic finality, NPEX confirming a €300 million issuance size, and XSC compressing the eligible investor whitelist into the Zedger Sparse Merkle-Segment Trie root—prove that the "day-one issuance" can run. They do not prove that the "third-year follow-on issuance" can run.
Look at follow-on issuance step by step: which slot does the snapshot day bind to? Under which shareholder register in XSC do we compute the privileged subscription rights' shielded balance? For those who abstain, do their shares return to the pool or get cancelled, and who signs to trigger that? On the cash side, do we use Quantoz’s EURQ or the fiat channel? Is paying money and delivering shares atomically settled within the same SBA round? The whitepaper v3 provides the cryptographic foundation for Phoenix/Zedger/Rusk VM, but the corporate action state machine is left blank—XSC’s standard only says that "lifecycle management" is programmable; it doesn’t finish writing the issuance/matching functions for the issuer.
So in calm market conditions, everyone transfers the poster about "€300 million RWA on-chain." After the poster exchange at the meeting, the issuer’s lawyer speaks up: in the ZK environment, how do we measure the next round's discounted pricing, M&A share-for-share conversion, and liquidation preference? If the answer is infrastructure, it’s solvable; if it’s just a display case. The first year of the display case has press releases; the second year, the budget table first gets cut—cut while X is still rotating the initial issuance script; forwarding it won’t save the TCO.
#dusk The identity that should be recognized is the "environment in which an event can be deterministically executed," not the "event itself." The environment provides: ~10s finality, delivery-versus-payment readiness, and selective disclosure of the view key to the AFM. But who has authority, what the proportions are, what happens to abstentions—those still have to be encoded by the issuer into XSC extensions, bound with a Citadel eIDAS identity, and settled via DuskDS using EURQ. Without filling this layer in, a native issuance is only half a system: you can demo the pricing, but you can’t demo liquidation in year eight.
I’m using follow-on issuance as a litmus test, not nitpicking. A half-built system can fool the comment sections in a bull market, but it won’t fool NPEX’s legal team. Until legal signs off, $DUSK won’t allocate you subscription rights—it only guarantees that if someone someday writes the rights-allocation into XSC, that execution won’t be rolled back.
Look at follow-on issuance step by step: which slot does the snapshot day bind to? Under which shareholder register in XSC do we compute the privileged subscription rights' shielded balance? For those who abstain, do their shares return to the pool or get cancelled, and who signs to trigger that? On the cash side, do we use Quantoz’s EURQ or the fiat channel? Is paying money and delivering shares atomically settled within the same SBA round? The whitepaper v3 provides the cryptographic foundation for Phoenix/Zedger/Rusk VM, but the corporate action state machine is left blank—XSC’s standard only says that "lifecycle management" is programmable; it doesn’t finish writing the issuance/matching functions for the issuer.
So in calm market conditions, everyone transfers the poster about "€300 million RWA on-chain." After the poster exchange at the meeting, the issuer’s lawyer speaks up: in the ZK environment, how do we measure the next round's discounted pricing, M&A share-for-share conversion, and liquidation preference? If the answer is infrastructure, it’s solvable; if it’s just a display case. The first year of the display case has press releases; the second year, the budget table first gets cut—cut while X is still rotating the initial issuance script; forwarding it won’t save the TCO.
#dusk The identity that should be recognized is the "environment in which an event can be deterministically executed," not the "event itself." The environment provides: ~10s finality, delivery-versus-payment readiness, and selective disclosure of the view key to the AFM. But who has authority, what the proportions are, what happens to abstentions—those still have to be encoded by the issuer into XSC extensions, bound with a Citadel eIDAS identity, and settled via DuskDS using EURQ. Without filling this layer in, a native issuance is only half a system: you can demo the pricing, but you can’t demo liquidation in year eight.
I’m using follow-on issuance as a litmus test, not nitpicking. A half-built system can fool the comment sections in a bull market, but it won’t fool NPEX’s legal team. Until legal signs off, $DUSK won’t allocate you subscription rights—it only guarantees that if someone someday writes the rights-allocation into XSC, that execution won’t be rolled back.