RWADaily (@Onchain_Assets) profile picture
Joined August 2021
Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)Photo by RWADaily (@Onchain_Assets)
RWADaily retweeted
The goal is NOT to put intermediaries onchain. It's to make them unnecessary and ensure the value flows back to those operating the network. STOP tokenizing intermediaries.
“The whole idea behind @DuskFoundation is to remove intermediaries and return earnings to the people operating the network. Whether it's settlement, issuance or trading. Value creation flows back to participants.” ~ Hein Dauven - CTO of the Dusk blockchain
2
9
1
41
935
RWADaily retweeted
Private KYC. On a public chain, an investor allowlist is a public list of wallets. With Citadel, a provider verifies your eligibility and issues a private credential. No personal data goes onchain. See how it works ↓
3
15
1
62
3,545
RWADaily retweeted
been exploring @DuskFoundation and the thing that stands out is how much sits on one settlement layer. duskvm runs native contracts, duskevm runs plain solidity, and the base chain handles both public and shielded balances, which is a lot of surface to learn from docs alone. built an mcp server that lets claude do the exploring with you. ask it for the top provisioners on mainnet, what a transaction actually did, a contract’s abi, a duskevm receipt or how to deploy something, and it answers from the live chain and the docs. wallets live in it too, each with its own password, and it can send DUSK on any network. nothing goes out blind. you see the network, recipient and fee first, and the password is what releases the transfer. adding more features like staking, shielding/unshielding, contract interaction, bridging soon repo: github.com/Intellihackz/dusk… cc: @opendusk_org , @nocturne_stds
2
16
1
65
1,049
RWADaily retweeted
The Dusk Web Wallet and Explorer got an upgrade. A new design across both apps makes sending, staking and looking up transactions simpler, with .dusk names built in. What's new ↓
3
18
2
68
4,417
RWADaily retweeted
Selective disclosure is how financial markets move onchain. Issuers, exchanges and custodians need positions, counterparties and client data kept private. On Dusk: → transactions stay private → auditors see only what's required → investors prove eligibility and reveal nothing else Regulated finance has always run this way. Now it can run onchain.
7
15
2
74
3,516
RWADaily retweeted
The Dusk Explorer got an upgrade. A clearer view of every account, transaction and block on Dusk, redesigned with simplicity in mind. Now live ↓
7
14
1
76
4,342
RWADaily retweeted
The era of public portfolios is ending. dusk-network:native
5
12
3
57
5,491
RWADaily retweeted
Dusk shipped a lot in October, from faster ZK proofs to .dusk names for wallet addresses. Here's what's new: → 10 cryptography releases → Phoenix privacy releases → Dusk Domains on mainnet → W3sper for Python and Go → Multicall for batched reads Get all the details ↓
7
20
3
87
6,835
RWADaily retweeted
DuskEVM is not just another EVM L2. With Hedger, apps on DuskEVM get privacy: → confidential balances and transfers → selective disclosure for compliance The EVM tooling you know, settled on Dusk. $DUSK
4
22
2
85
4,288
RWADaily retweeted
Corporate treasury is coming onchain. A recent @AFME_EU report maps how Europe's corporates can use DLT to move cash, collateral and funding faster, starting with cross-border payments and intraday liquidity. What changes for treasurers, and why those flows need privacy ↓
10
17
3
78
4,773
RWADaily retweeted
T-Minus 90 is a builder program for Dusk that @tminus_dusk and I are running together. Over 90 days, we help 3 builders take a dApp from idea to mainnet. We've both shipped on Dusk. Tminus built @sozu_dusk, I built Dusk Domains. So the mentoring comes from people who've been through it, from the first contract to the mainnet deploy. The deal You get a Claude Team seat for 3 months, a weekly call with both of us, product reviews along the way and a security review before you go live. You also get shoutouts from my X account, help with the mainnet deployment costs and a private Discord with the other builders. In return, you build in public, with an open-source repo and a short weekly update. Your proof of concept needs to work on testnet by December 1st. If it doesn't, your seat goes to the next person on the waitlist. The dApp needs to be live on mainnet by February 1st. You fully own what you build. We don't take equity. Who we're looking for What matters most to us is distribution. Who is going to use your dApp and why will they use it? ZK and privacy, AI or agentic use cases are a plus, but the proof of concept on testnet needs to work first. The ZK or AI parts can come later. Applying takes about 5 minutes. If you're not picked, you're on the waitlist. Timeline Oct 23, 2026 applications open Oct 30, 2026 applications close Nov 1, 2026 3 builders picked, kickoff, Discord opens Dec 1, 2026 testnet PoC check Feb 1, 2027 mainnet launch, then a retro Apply below 👇
15
29
5
74
5,244
Do I even dare saying this looks decent?
3
4
12
339
RWADaily retweeted
We've upgraded private transfers on Dusk. The latest Phoenix releases brings stronger user protection, with more efficient proof generation. Here's the simple version of what's improved ↓ → Finding your funds (ownership checks) Phoenix represents private funds as records called notes. Your wallet checks which ones belong to you. Each check now uses 36% less CPU time, so the same processing time can handle about 156 checks instead of 100. → Reading private amounts (note validation) Your wallet decrypts a note to read its amount. Phoenix checks that the recovered amount is consistent with the note, rejecting mismatches. This helps prevent inconsistent payment data from being accepted. → Checking private transfers (zero-knowledge proofs) A proof lets the network verify that a transfer follows the rules without seeing its private details. The updated proofs reject malformed keys and attempts to use the same note twice in one transfer. → Protecting the sender (sender encryption) Phoenix uses random values to help hide sender data. The updated proofs reject values that could reveal a sender's key or make transfers linkable to the same sender. → Protecting key data (secret handling) Phoenix now clears key's secret data from memory when discarded. It also hides secret key material and private proof inputs from debug output, reducing exposure when developers troubleshoot software. These go live with Dusk's next network upgrade.
Privacy is getting a major upgrade on Dusk with the latest Phoenix releases. Less processing work for your wallet to identify private funds, with 36% less CPU time per ownership check. See what's improved ↓
9
25
3
96
4,881
RWADaily retweeted
Dusk Domains is live on mainnet. Give your long wallet address a memorable .dusk name. → Register from 10 dusk-network:native a year → Buy and sell names on the marketplace Get yours today at dusk.domains
Dusk Domains is live on Dusk mainnet. One readable .dusk name for your Dusk address, from 10 DUSK a year. dusk.domains
6
16
3
83
6,888
RWADaily retweeted
Dusk Domains is live on Dusk mainnet. One readable .dusk name for your Dusk address, from 10 DUSK a year. dusk.domains
3
24
5
63
5,887
RWADaily retweeted
Privacy is getting a major upgrade on Dusk with the latest Phoenix releases. Less processing work for your wallet to identify private funds, with 36% less CPU time per ownership check. See what's improved ↓
5
23
4
90
7,836
RWADaily retweeted
Building Dusk Domains taught me a lot about dApp development on dusk-network:native. Along the way I found a number of things to fix and improve that will pay off for everyone building on it. The first one is live now in the form of a contract called Multicall, deployed on mainnet and testnet. A dApp page needs a lot of values from the chain, like balances, token info and settings. Normally every value is its own query to a node, sent one after another. That's slow, and new blocks can land in between, so the answers don't always line up. Multicall packs up to 256 contract reads into one query. The node runs them back to back against the same block and sends back one reply. Reading 250 balances on mainnet: 8.9 s one query at a time -> 90 ms in one batch. Any dApp or backend on Dusk can use it today. Read-only, immutable and MIT licensed: github.com/HDauven/dusk-mult… Mainnet and testnet contract ID: 93de287b7d349d678a0038fe7772e8960e1a84a1b5da2d0b1f62f532616ce1d4
9
22
4
74
4,006
RWADaily retweeted
Trillions are coming onchain. Privately. $DUSK
12
32
6
137
9,578
Regulated markets want two things at once: privacy from the market, transparency for the regulator. That's what dusk-network:native was built for. Zero knowledge and compliance at the protocol level. Not sexy. Just what real adoption looks like.
6
24
455
RWADaily retweeted
Europe wants bigger onchain markets. On 9 October, the EU Council backed changes that would allow more financial activity under the DLT Pilot Regime. Currently, the DLT Pilot Regime lets authorised operators test blockchain-based trading and settlement under regulatory supervision. Expanding it is part of a wider push to make it easier to invest across Europe and fund businesses. The opportunity is in connecting the steps that make a market work. When trading, ownership records and payments sit in separate systems, operators have to keep matching them up. Consider what happens when a bond changes hands. The buyer needs to meet its eligibility rules. Ownership and payment need to transfer. The issuer needs to know who should receive the next interest payment. Dusk provides infrastructure for connecting those steps onchain. → Securities issued natively onchain creates the bond directly onchain, with an ownership record that can support transfers and interest payments. → Citadel helps investors prove they qualify to buy the bond without publishing personal details onchain. → Delivery versus payment is a requirement that the security and payment transfers complete together, or neither complete, when both assets are onchain. For issuers, that can mean fewer records to reconcile after a sale, with ownership changes reflected in the next interest payment.
11
28
6
115
5,591