sharing my thoughts and build income

Joined June 2025
submitted TasteCase for the @Qloo agentic hackathon ai recs look right until you test different people. tastecase uses qloo to rank restaurants per profile, explain why, and turn ranking differences into reusable regression tests live: tastecase.vercel.app
currently working on something on @Qloo on Devin I don't own a Mac but currently using this on devin cloud. using devin cloud + fusion ( fable 5.1/gbt-6.1 sol/opus 5.5 together with any executor ) has to be the most efficient way to ship rn love this workflow rn
18
10
29
515
🛠️ Retium Testnet Maintenance & Upgrades We're currently working on upgrades to the Retium testnet network. During this time, please expect temporary service interruptions and a possible network reset. We'll keep the community updated on our progress and let everyone know once the upgrades are complete and the testnet is back to normal operation. Thanks for your patience and support!
19
27
6
70
1,961
One stablecoin. Many chains. RTD is heading multichain. Same RTD, same one to one reserve, wherever you hold it. Coming soon 👀
28
31
21
101
4,943
Two keys. One transaction. Most wallet drains start with a single stolen key. On Retium, 2FA lives in the protocol itself. Your phone becomes a second signing key, and every protected action is still verified by the network. Security by design, not as an extra.
26
23
10
80
2,327
My landlord said I haven’t paid rent. I said I transferred the money. My bank app said, “Something went wrong.” Now my landlord wants his money, I’m showing screenshots, and my bank app has suddenly developed amnesia This is where @GenLayer gets interesting Genlayer Intelligent Contracts can use AI to interpret information and evaluate things that aren’t always as simple as a yes-or-no answer. With the right evidence sources and rules, a developer could build a system to assess a payment dispute and determine whether the available evidence supports the claim Imagine having a system that can actually examine the evidence instead of just watching me and my landlord argue all day I’m not saying GenLayer will pay my rent for me, but if it can help settle this argument fairly, my landlord and I might finally sleep peacefully @VGtheWinner, you should check out genlayer too. i think you’ll find its approach to intelligent contracts interesting portal.genlayer.foundation/?…
1
1
7
146
. @grvt_io 's stable funding perps are due in november, and the detail i keep coming back to is once-daily funding funding is the recurring cost of holding a perp. with a single payment each day, someone holding stocks, fx, commodities or indices for a few days can work out the carrying cost ahead of time. that's my read of the design, and it only counts if it plays out that way in practice pair that with zero trading fees and the cost side of a position gets a lot simpler to reason about the target is 1,000+ markets by december 2026. it's a target, so i'll be checking how many are live in november and how they actually trade grvt finished the buyback first. this is the next dated item on the list
🤝 Paid partnership
11
3
1
19
577
Building on @RetiumChain? Here is how to verify your deployed smart contract retium verify <contract-id> <file.wasm> <contract-id> is the ID of your deployed contract <file.wasm> is the compiled WASM file on your computer Example: retium verify c16837bf... target/wasm32-unknown-unknown/release/hello_counter.wasm Replace c16837bf... with your actual contract ID How it works when a contract is deployed, Retium records a BLAKE3 hash of its WASM code. The CLI compares that hash with the hash of your local file Match means the deployed code matches your file. A mismatch means the code is different, so treat it as unknown until you investigate Tip: use the same Rust toolchain, commit your Cargo.lock, and keep your build settings consistent to help reproduce the exact WASM file Official docs: docs.retium.org/developers/v…
1
1
7
118
The latest update to Whisk.Exchange is ready, bringing some new benefits for Retium community contributors.
46
27
26
96
5,909
After reading Albert Castellana’s post, 𝐏𝐞𝐫𝐦𝐢𝐬𝐬𝐢𝐨𝐧 𝐢𝐬𝐧’𝐭 𝐚 𝐯𝐞𝐫𝐝𝐢𝐜𝐭, I was struck by the gap between proving that an agent was authorized to act and proving that it acted correctly. PACT can show which permission and scope an agent used, while Internet Court is designed to connect contracts, escrow, evidence, and dispute resolution for agent-to-agent commerce. 𝐌𝐲 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧 𝐟𝐨𝐫 𝐀𝐥𝐛𝐞𝐫𝐭: @kstellana @GenLayer If an agent stays within its permissions but still delivers the wrong outcome such as buying the wrong product, booking the wrong airport, or providing unusable data how should GenLayer distinguish between a failure of execution, a failure to understand human intent, and a failure of the merchant to deliver? Could future Intelligent Contracts require agents to convert vague user intent into explicit, testable acceptance criteria before payment is released, while still allowing a human to appeal when the evidence is ambiguous? 𝐖𝐡𝐲 𝐈’𝐦 𝐂𝐮𝐫𝐢𝐨𝐮𝐬 Permission records and signed receipts can prove that an agent was allowed to perform an action, but they do not necessarily prove that the result matched the user’s actual intent. That makes intent interpretation and outcome verification just as important as authorization in an agentic economy. This question is also relevant to Internet Court because GenLayer’s dispute resolution role is to evaluate evidence, interpret natural language obligations, and reach machine speed judgments through decentralized AI validator consensus. The answer could help clarify whether intelligent contracts will mainly resolve disputes after something goes wrong or whether they can prevent ambiguity before the transaction begins.
11
10
1
22
324
i just completed my @GenLayer airdrop registration, and the process went smoothly from start to finish what excites me most about genlayer is how intelligent contracts combine ai with blockchain to handle tasks that go beyond traditional smart contract logic it’s exciting to see this technology already in action and explore what it makes possible
GEN Airdrop Registration is open. You've been building GenLayer with us since the start. Now it's time to register. Open until Monday, October 26. airdrop.genlayer.com
3
68
been thinking about what happens when an AI agent pays another agent to do a job, but things don't go as planned say a coding agent hires another agent to review a smart contract. payment is funded, but the review never gets delivered what happens to the money ? this is one of the problems @termix_ai is trying to address with AACP ERC-8183 defines a job lifecycle with escrow and expiration handling, so a funded job doesn't have to leave the client's money stuck forever but what if the agent delivers incomplete work ? or both sides disagree on whether the job was done properly ? that's where reputation and dispute resolution become important. AACP's broader design accounts for these, although not every part of the dispute system is live yet i think this is an important part of building an agent economy getting agents to transact is one thing. figuring out what happens when things go wrong is another and for agent to agent commerce to work at scale, we need to think about both
🤝 Paid partnership
One of the more interesting parts of @termix_ai is that you don’t necessarily need to build a brand new agent just to use AACP you can give an existing coding agent the TermiX skill and suddenly its operating surface becomes much bigger think about a coding agent that can already: → write code → inspect repositories → run tests → use tools → and make decisions around a task now add TermiX that same agent can potentially: • discover services • find other agents • publish or respond to requests • receive offers • fund jobs • deliver work • handle marketplace messages • settle transactions through AACP that changes the role of the agent Before: TASK → TOOLS → OUTPUT with an economic layer: TASK → TOOLS → NEED EXTERNAL HELP → FIND AGENT → PAY → RECEIVE WORK → CONTINUE a developer doesn’t know how to do everything personally we hire specialists, buy services, delegate work and keep moving. agents should eventually be able to do the same this is why the @termix_ai skill is probably one of the parts I’m most interested in testing If I can plug it into an agent I already use and watch that agent independently interact with the marketplace, then AACP stops being something I only understand from documentation It becomes something I can actually put inside my existing agent workflow
25
10
1
36
725
most NFTs have traits that rarely do anything beyond defining how they look just submitted chogmog for Chogathon i built Chogmog, a browser game where those traits become actual game mechanics. chogs power chain-reaction machines, and changing a single part can change how the entire machine plays out anyone can build and play without a wallet, while holders can turn their chogs into reusable parts for others to create with play chogmog: chogmog.vercel.app confused ? watch the demo below @ChogNFT
14
8
24
367
Wole retweeted
Building on Retium? Here’s a useful SDK tip 👇 Before deploying your smart contract, run a dry run first The @RetiumChain CLI supports: retium deploy <contract.wasm> --dry-run This runs every check the chain runs on a deploy and shows the contract ID before you spend anything It gives you a chance to catch problems before you submit the real deployment transaction One more thing: if your contract has an init function, run it immediately after deployment and check the owner. Retium docs warn that until init has run once, anyone may call it Build carefully, test before deploying, and verify what goes onchain Official docs: docs.retium.org/developers
Built for devs and builders. A new Layer 1. A new virtual machine. A whole new playground. The Retium SDK is out. Rust smart contracts are ready. Happy hacking! docs.retium.org
1
3
5
90
Building on Retium? Here’s a useful SDK tip 👇 Before deploying your smart contract, run a dry run first The @RetiumChain CLI supports: retium deploy <contract.wasm> --dry-run This runs every check the chain runs on a deploy and shows the contract ID before you spend anything It gives you a chance to catch problems before you submit the real deployment transaction One more thing: if your contract has an init function, run it immediately after deployment and check the owner. Retium docs warn that until init has run once, anyone may call it Build carefully, test before deploying, and verify what goes onchain Official docs: docs.retium.org/developers
Built for devs and builders. A new Layer 1. A new virtual machine. A whole new playground. The Retium SDK is out. Rust smart contracts are ready. Happy hacking! docs.retium.org
1
3
5
90
just did a lil 3D game with minimax m3.1 flash it took about 30 mins costs $0 ( used an api key from openrouter ) , it's free till month end so you can check it out to be honest, it didn't really do well and the first try crashed how did it do ?
23
6
38
780
Ethereum has a huge existing ecosystem to upgrade, which makes its move to post-quantum security a long process QMS took a different approach by building post-quantum security into its consensus and finality layers from day one, while keeping Ethereum-compatible signatures in the execution layer for now The difference is starting with core security already in place instead of having to retrofit it later #QMS1002
1
1
5
76
Blockchain has come a long way, but scalability, unpredictable fees, and inefficient execution remain major challenges. I believe @RetiumChain is taking a different approach to solving these problems. Here's why I'm paying attention. 1/5 🧵 👇 @Nicholas_Ozz @BithiX7
6
2
7
80
A smart contract shouldn’t be able to run forever or consume unlimited resources @RetiumChain places a limit of 100 million instructions per transaction through its fuel system If a contract runs out of fuel, execution stops and its changes are rolled back This helps keep contract execution bounded instead of allowing one transaction to consume unlimited resources Small technical details like this matter when building blockchain infrastructure Source: docs.retium.org/whitepaper/i…
Retium SDK is out Developers can now use the SDK and CLI to create accounts, send transactions and deploy smart contracts on @RetiumChain testnet Here’s how to get started 👇 1️⃣ INSTALL THE SDK git clone github.com/Retium-Org/retium… cd retium-sdk cargo install --locked --path crates/retium-sdk rustup target add wasm32-unknown-unknown 2️⃣ CREATE YOUR ACCOUNT retium key new my-wallet.sk --show-seed Keep your seed private and offline 3️⃣ FUND YOUR ACCOUNT Visit retium.money to claim test RTD, then use it to get RTM for testing 4️⃣ GET AN API KEY Connect your wallet at retium.net/api-keys and create an API key for transaction requests 5️⃣ BUILD AND DEPLOY Write a smart contract, compile it to WASM, run a deployment dry run, then deploy it using the CLI 6️⃣ TEST AND VERIFY Call your contract methods, query its state and verify the deployed code Retium supports WASM smart contracts, giving developers the option to explore languages beyond Rust Remember, this is a public testnet, so tokens have no real-world value and network resets may clear your data Docs: docs.retium.org/developers SDK: github.com/Retium-Org/retium… Developers, what are you building on Retium?
1
7
126
opus 5.5 and gpt-6 astra both scoring 100% on devin’s sregym-lite benchmark is pretty wild deven really put the top models in the world right now to the test on debugging and these two came out on top lol argon in d mud <3
Introducing Devin Oncall: Devin automatically investigates alerts and bugs, helping your team diagnose and resolve production incidents. Devin Oncall already handles thousands of alerts every day for some of the world’s largest companies. Let it become your SRE today.
12
4
20
553
Wole retweeted
Retium SDK is out Developers can now use the SDK and CLI to create accounts, send transactions and deploy smart contracts on @RetiumChain testnet Here’s how to get started 👇 1️⃣ INSTALL THE SDK git clone github.com/Retium-Org/retium… cd retium-sdk cargo install --locked --path crates/retium-sdk rustup target add wasm32-unknown-unknown 2️⃣ CREATE YOUR ACCOUNT retium key new my-wallet.sk --show-seed Keep your seed private and offline 3️⃣ FUND YOUR ACCOUNT Visit retium.money to claim test RTD, then use it to get RTM for testing 4️⃣ GET AN API KEY Connect your wallet at retium.net/api-keys and create an API key for transaction requests 5️⃣ BUILD AND DEPLOY Write a smart contract, compile it to WASM, run a deployment dry run, then deploy it using the CLI 6️⃣ TEST AND VERIFY Call your contract methods, query its state and verify the deployed code Retium supports WASM smart contracts, giving developers the option to explore languages beyond Rust Remember, this is a public testnet, so tokens have no real-world value and network resets may clear your data Docs: docs.retium.org/developers SDK: github.com/Retium-Org/retium… Developers, what are you building on Retium?
Built for devs and builders. A new Layer 1. A new virtual machine. A whole new playground. The Retium SDK is out. Rust smart contracts are ready. Happy hacking! docs.retium.org
6
4
1
20
528