George 🌊 (@TheOnlyGamo) header
George 🌊 (@TheOnlyGamo) profile picture

RWAs are inevitable | Team @DuskFoundation

Joined October 2021
Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)Photo by George 🌊 (@TheOnlyGamo)
Waitlist is now open for Dusk's regulated RWA trading platform. Sign up to enter a raffle for $500 in RWAs πŸ‘‡
Dusk Trade waitlist is now open. Our regulated RWA trading platform, built with NPEX, a licensed exchange with €300M AUM, bringing tokenized assets and funds on-chain. Sign up for a chance to win up to $500 in RWAs πŸ‘‡
1
9
41
1,657
George 🌊 retweeted
Dusk Web Wallet v2 is now live on mainnet. Send, stake and bridge your dusk-network:native in one redesigned app, with .dusk names and liquid staking built in. Open Web Wallet v2 ↓
2
18
2
60
4,264
George 🌊 retweeted
Your savings aren't public. Your rent isn't public. With Dusk, your onchain balance remains private. See how privacy works across dusk-network:native ↓
4
8
1
46
3,308
George 🌊 retweeted
Tokenization shouldn't stop at the token. Many tokenized securities still rely on the same custody, registry and settlement processes offchain. The token is new, and the intermediaries are the same. With native issuance, the asset itself is created onchain. Dusk can carry the whole lifecycle on one chain: β†’ Issuance β†’ Trading β†’ Settlement β†’ Corporate actions That's the difference between a tokenized asset and an onchain market. See the full lifecycle on Dusk ↓
7
13
2
61
3,610
George 🌊 retweeted
Public or private blockchain? Why not both. $DUSK is a public blockchain with private, auditable transactions.
6
17
1
68
3,411
George 🌊 retweeted
Dusk is speaking at @HouseofChimera's Privacy Stack MEGASPACE, alongside @near_intents, @0G_labs, @Dashpay & more. πŸ—“οΈ Mon, Nov 16 ⏰1-4:40 PM UTC Set a reminder ↓
HOC & Frens MEGASPACE: The Privacy Stack πŸ”’ πŸ”Ή 20 teams. 3.5 hours. One stack. πŸ”Έ @near_intents, @0G_labs, @Dashpay & more, supported by @aelo_xyz πŸ—“ Mon, Nov 16 ⏰ 1-4:40 PM UTC Drop your questions below. We'll get them asked live! Set a reminder πŸ‘‡ teapawt.net/i/spaces/1KoXKAzlgXKXB…
19
66
2,864
George 🌊 retweeted
Dusk Web Wallet v2 is now on testnet. A full redesign for sending, staking and bridging DUSK, with .dusk names and liquid staking. Try Web Wallet v2 ↓
7
16
3
76
4,489
George 🌊 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,776
George 🌊 retweeted
W3sper, Dusk's wallet and transaction SDK, now has Python and Go ports. @HeinDauven built them as an experiment for teams whose stack runs on Python or Go rather than JavaScript or Rust. Both run Dusk's own wallet-core for cryptography, the same module the JavaScript SDK uses. Both ports support: β†’ Offline transaction signing β†’ Public and private transfers β†’ Staking and contract deployment β†’ GraphQL queries and network events Try them out ↓
Building tools for Dusk usually means you have to use either JavaScript or Rust. Need Python or Go for your stack? I ported W3sper, Dusk's wallet and transaction SDK, to both as an experiment. If you're a builder, try them on testnet and tell me what breaks. PRs welcome: github.com/HDauven/w3sper.py github.com/HDauven/w3sper.go
7
18
2
78
3,979
George 🌊 retweeted
Introducing T-Minus 90, a program that takes three dApps from idea to mainnet on Dusk in 90 days. Our CTO @HeinDauven, creator of Dusk Domains, and @tminus_dusk, creator of @sozu_dusk, launched it and mentor each team from the first contract onward. Selected builders get: β†’ Help with deployment costs β†’ A weekly call with both mentors β†’ A Claude Team seat for 3 months β†’ Product reviews and a security review before launch In return, each project is developed in public with an open-source repo. It needs a working proof of concept on testnet by December 1 and a mainnet launch by February 1. Builders keep full ownership, and no equity is taken. Distribution counts most, so applications should show who will use the dApp and why. ZK, privacy, AI and agentic use cases are a plus. Applications close October 30. Apply below ↓
8
15
2
87
4,402
George 🌊 retweeted
Dusk is sponsoring @binance Pick, powered by @predictdotfun. β†’ Earn Scores through eligible dusk-network:native trading β†’ Use them to make virtual predictions β†’ Compete for a share of 1,000,000 USDC Explore the campaign ↓
Binance Pick Week 1 ends soon and Earnings Season is live. Predict with Scores, climb the leaderboards and share 1,000,000 USDC. Join: app.binance.com/uni-qr/proph… Powered by @predictdotfun Sponsored by $ACE $DUSK $SXT T&Cs apply. Not available in all regions.
7
27
3
87
6,544
George 🌊 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,882
George 🌊 retweeted
Fun fact: .dusk names made ~30k dusk-network:native (~$3,400) in revenue on day one. 1 day -> ahead of ~80% of protocols on DefiLlama 7 days -> ahead of ~2 in 3 Pretty crazy, and that's out of 1,300+ listed protocols. A lot of adoption room still left for crypto dApps.
Nothing beats seeing a side project get real users. Thanks to everyone who registered a name, listed one or helped test Dusk Domains before launch. Great first day πŸ’ͺ Wallet support is up next!
4
17
58
1,103
Registered my .dusk address name on dusk.domains Did you get yours yet?
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
1
5
21
327
George 🌊 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,837
George 🌊 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,009
George 🌊 retweeted
Our CTO @HeinDauven released Multicall, a read-only contract that batches up to 256 contract calls into a single query, all executed against the same block. β†’ 250 balance reads in 90 ms, down from 8.9 s β†’ Node CPU per call cut from 1,328 Β΅s to 113 Β΅s β†’ Throughput up from 1,869 to 11,082 reads/s β†’ Pages with mixed block heights down from up to 94% to 0 Useful for any dApp frontend, backend or client library making many view calls at once, such as token balances, metadata and config. Check out the repo to learn more ↓
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
10
18
1
90
4,318
Trillions are coming onchain. Privately. $DUSK
Trillions are coming onchain. Privately. $DUSK
10
36
618
George 🌊 retweeted
Which financial app would you like to see a private onchain version of?
We just shipped 10 releases of Dusk's core cryptography. Here's the simple version of what each piece does and what just got better. β†’ Proofs (PLONK) The engine that lets you prove something is true without revealing the details. It's how Dusk keeps transactions private and still verifiable. Creating and checking proofs is now roughly 2x faster. β†’ Hashing (Poseidon) A digital fingerprint for data. Same input, same fingerprint, and you can't reverse it. Inside a proof, it now does the same job with about a third less work. β†’ Merkle trees A way to prove one item is part of a huge list without showing the list. Those proofs now take a third less work, and the trees reject bad input. β†’ Encryption (ElGamal + SAFE) What locks private data so only the right people can read it. Decrypting an encrypted number inside a proof now takes up to 84% less work. β†’ Signatures (Schnorr + BLS) How the network knows a message really came from you. Multisig now has protection against key tricks, and checking a signature inside a proof takes 14% less work. β†’ Curves The math the whole stack is built on. Both foundation libraries were upgraded and now reject bad input. Full breakdown in the thread ↓
8
21
2
85
5,005