avatar
Hein Dauven
947 Twitter followers
Follow
Core Developer @DuskFoundation 🌙🦀🐧#EdHead #ZKP #RWA #Bitcoin
Posts
avatar
Hein Dauven
01-29
I'm donating @ForgeAtDusk to @DuskFoundation so it can be officially maintained by the foundation. We've released v0.2 today. huge thanks to @mocellione for adding data‑drivers (rkyv<=>JSON translation) + trait support. ⚒️ Building Dusk WASM contracts used to mean repeating the same interface in multiple places (exports, wrappers, off‑chain encoding/decoding). That duplication causes drift, bugs and slows development down. Dusk Forge changes this: your contract module is the single source of truth. #[contract] auto‑generates the WASM exports + a JSON schema (functions + events), so you focus on business logic, not glue code. New in v0.2: a generated data‑driver WASM that translates JSON <=> rkyv for inputs/outputs/events (great for wallets, explorers, tooling), plus trait exposure so reusable patterns don't need hand‑wired exports. If you're building on Dusk, give it a spin + tell us what you need next. Repo: github.com/dusk-network/forge…. Issues/PRs welcome, let's make Dusk smart contracts feel as straightforward as Rust code. $DUSK #Rust #WASM
DUSK
4.52%
avatar
Hein Dauven
01-09
ERC20-like tokens on $DUSK are now in draft. DRC20 is public and open for community contribution. Big thanks to builders helping shape the standard: @sozu_dusk @tminus_dusk @pieswap_dusk @neotamandua A shared baseline makes tokens easier to integrate (wallets, explorers, tooling), safer to implement and faster to ship without everyone reinventing the wheel. And with DuskEVM coming up, having a clear token standard matters even more for bridging between EVM <-> DS.
Dusk Forge
@ForgeAtDusk
01-09
A DRC20 proposal is now public: a minimal fungible token reference for $DUSK @DuskFoundation. Built as a clean starting point for ecosystem tokens. We’re evolving it in the open with a collective of OSS builders on Dusk. RFCs, issues & PRs welcome: https://github.com/Dusk-Forge/drc20-reference…
DUSK
4.52%
avatar
Hein Dauven
11-16
The argument Canton uses confuses "can someone send a bogus message?" with "can that message have any effect?". Every bank website, FIX gateway or API on the planet is bombarded with unauthorized requests. Compliance is about what executes and settles, not whether packets can be sent. If you use the internet as an analogy, your data packets will traverse any router it thinks is the quickest path. Inevitably, this can mean it hits sanctioned jurisdictions or routers owned by bad actors. No regulator treats that as you "using a terrorist's infrastructure" in any meaningful legal sense, the network fabric is neutral. A base layer blockchain is the same. Neutrality at the base layer (transport/mempool/consensus), with access control and policy enforced at the application/contract layer. This is entirely compatible with the "appropriate systems, policies, procedures, and controls" language you quoted. The fact that unauthorized calls can appear in the mempool is a red herring.
-- END --