Calling on CW devs to come build on our new chain, @dangoXchg !
It will take you no time to become productive in our CW-inspired VM, ‘grug’.
You will be able to compose with state-of-the-art defi primitives: CLOB, our unified margin account, lending, vaults…
We have plans to bring on liquidity, including private raise, ICO, yield farming…
I will **personally** assist you on technical and non-technical matters. Our social media will promote your app relentlessly. Our frontend will feature your app in prominent positions.
It takes great commitment to bet on an early stage ecosystem like us, but imo, it’s worth it! I like to think about Jupiter and Jito—they bet on Solana when it was at lowest, but now they’ve been rewarded handsomely. This could be you!
At @Permissionless Hackathon IV organized by @cracked_labs, we challenged builders to create powerful applications around token distribution and real-world assets — all while leveraging the @ForteProtocol Rules Engine.
🥇 1st Place: Echoverse (@saifonblock)
A privacy-preserving reward platform that uses ZK proofs and TEEs to distribute real rewards to real users — with Forte handling compliance under the hood. Powered by @BNBCHAIN and @Ethereum
🥈 2nd Place: Daivest (@CyberAdair)
An AI-powered portfolio manager that enforces user-specific risk policies directly on-chain, using smart accounts and Forte’s Rules Engine for trade validation.
Big thanks to @cracked_labs for organizing a great event and a massive congratulations to the winners — and to every team that leveraged our Rules Engine infrastructure . 💪
Why risc-v over wasm for Ethereum contracts?
If the argument is that there is more risc-v zkVMs than wasm ones, then that's the wrong way to look at it.
WASM actually has a lot of nice properties that EOF is trying to add, which risc-v doesn't have (e.g. it doesn't have jumps and is easier to analyze statically).
The ability to prove properties about contract code and lower to machine code while preserving gas accounting are the key properties. This actually has been done in wasm by ewasm couple of years ago (surprised that VB didn't mention this in the post).
ZK-friendliness between risc-v and wasm shouldn't be the deciding factor (and it is a toss-up based on what I found when I deep dived this ~2years ago).
@brane_trix@Deploydon cw-orchestrator supports unit (mock), integration (test-tube), live, and interchain testing, all in Rust.
There's no better alternative
https://t.co/ki5FeVwJyZ
@noahsaso Mike @mikedotexe did some work on this at AwesomWasm
https://t.co/g3bmGiPvVk
https://t.co/Y106mSDium
Issue being that serializing and deserializing the messages to search for keys can be quite expensive.
〰️Introducing WAVS—the Next-Gen AVS Builder〰️
Build AVSs in minutes, not months. Focus on the core logic of your service. Let WAVS handle the rest.
For full-stack, multichain decentralized applications. Where off-chain compute meets on-chain verification.
Start building with WAVS—a WASM-based runtime for off-chain services.
check out this write up discussing why we at @DA0_DA0 prefer Polytone as a cross-chain account solution and why ICA is insufficient
we strongly advise against creating ICAs for DAOs !
https://t.co/ldQkPqLqZx
Excited to share what we’ve been up to these past few months @AbstractSDK !
Async apps are the future, and one of the best ways we can bring new institutions onchain, today.
Check it out 👇
Chain-Abstracted Asynchronous Application Architectures by @CyberAdair from @AbstractSDK.
Explore how hub & spoke, mesh, and intent-based architectures will shape the next generation of decentralized apps.
Full video below 👇🧵
The solution to "multisig confirmation hack" problem is human-readable transactions.
You need to have a trusted user interface i.e. your hardware wallet to be able to decode and tell you want the transaction is doing, instead of hashes, domains and other crap.
Some advanced blockchains built correctly ground up like @radixdlt have this feature already today. Also most Cosmos transactions are quite human readable.
https://t.co/0D0ggMEiQE
i really cannot process how wallet devs accepted that having 3 gas parameters, multiple roundtrips, and a fee estimation flow which involves users configuring dummy signature values is an acceptable developer or user experience
ZKNY 🎆
Amazing start of 2025 for @union_build on new years day: fully working state-lenses running on testnet-9!
Recursive state and consensus proofs take message passing to the next level.