We're happy to share what we've built recently for the Moltiverse @monad
Agents don’t just execute tasks anymore. They start businesses. They raise funding. They hire other agents. Agents to agent transactions are here.
$100 in Kimi credits are available for the the first devs to:
- QRT this thread and tell us what you shipped for the Moltiverse this week and
- Tag @monad_dev for visibility
Good luck 🦞
final minutes vibe coding before deadline of @ETHGlobal Hack-money Hackathon
we’re building a marketplace for openclaw agents to buy and sell services using x402, match investors with agents to bootstrap capital needed for operations (compute and credits), custom skills to interact with the platform, and policy enforcement for agents to interact with whitelisted actions, and rewarding those agents that have higher reputation scores.
🤞🏻hopefully we can share it when things are done!
I just read a blog by Chris Dzombak who shipped 12 projects using Claude Code in just a small amount of time,
His secret isn't anything fancy,
It was just as simple as changing a single CLAUDE .md file with some rules like:
- prefer making small changes that compile and pass tests
- standard workflow of understand -> testing -> implementation -> refactor -> commit
- maximum 3 attempts per issue, then stop
- decision frameworks and much more
instead of treating AI as a code generator, it gives it a software engineer's mindset, most importantly, it still enforces manual review being necessary and human's are ultimately responsible.
(i attached a link to his blog with markdown below)
One wrong abi.encode and your calldata’s just expensive garbage.
Was cooking @polystream_xyz v1, ran into a classic Solidity nuance:
abi.encode() vs abi.encodePacked() when building calldata in bytes.
Here’s what I learned 👇
@jalldoes Great point on showing the uint256 vs uint8 difference
uint256 stays 32B in both encodings, while uint8 is only 1B in abi.encodePacked (32B in abi.encode).
For the abi.encodePacked example though, the 123 (0x7b) and 5 (0x05) are missing
• abi.encode() → padded per ABI spec, type-safe, decodable
• abi.encodePacked() → tightly packed, cheaper, collision risk
This matters a lot when protocols expect specific calldata bytes — get it wrong, and your low-level call() just reverts.
Happy to share some milestones that we’ve achieved so far!
- 50 beta testers!
- 140+ wallets created
- 500+ transactions initiated
- Users paid 0 gas!
So what’s next?
Just tested posting on Red Note for the first time to explore product-market fit.
Framed a relatable money scenario — something most people would resonate with.
Got 8k+ views & 60+ comments overnight.
Relatability > features.
Listening > building.