Push Chain has successfully completed its security audit with @hackenclub. By the numbers: - Zero critical-severity findings were identified - 300 hours of audit work - 3 smart contracts and full chain audit completed - $100,000 bug bounty launching soon

Let me repeat: "The number of agents will keep growing"

𝟭 𝗠𝗶𝗻𝘂𝘁𝗲 𝘄𝗶𝘁𝗵 𝗣𝘂𝘀𝗵 ⚡ — 𝗪𝗲𝗲𝗸 𝟰𝟴 Heads-down build week. Here's where things stand 👇 🔧 𝗥𝗲𝗮𝗱-𝘀𝘁𝗮𝘁𝗲 𝗦𝗗𝗞 We're wrapping up the SDK that lets apps read state directly. ✅ 𝗘𝗥𝗖-𝟴𝟭𝟴𝟯 The first implementation is done, with hooks. - Every Job ID is now tied to a Mandate ID - One AGW, one job, enforced right in the hook Next up: letting existing mandates be modified. 🔬 𝗥&𝗗: 𝗔𝗴𝗲𝗻𝘁 𝗝𝗼𝗯 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 Two design proposals are being explored side by side. We're also building more hooks for different job types. ⏭️ 𝗔𝗚𝗪 𝗦𝗗𝗞 Kicks off this weekend or early next week. 𝗪𝗲𝗲𝗸𝗲𝗻𝗱 𝗩𝗶𝗯𝗲𝘀 🍩 → agents don't take weekends off, but the humans are trying.

𝗣𝘂𝘀𝗵 𝗣𝘂𝗹𝘀𝗲 🫀 — 𝗣𝘂𝗹𝘀𝗲 𝟰𝟳 Read State is live in the Docs Playground ⚡ One batch. Three reads: → Ethereum price feed → Solana token balance → Public API Hit run ▶️ push.org/docs/chain/build/re…

if you want to protect your onchain agents from getting hacked. follow this secure runtime stack and study the 5 most destructive types of agent hacks shared below.

WE ARE ABOUT TO WITNESS AN ERA OF HYPERPARABOLIC AGENTIC ACTIVITY ONCHAIN. THE SIGNS ARE VISIBLE. GET READY.

If you think AI agents are as loyal as a golden retriever, you need to read this ↓↓

"Yes, you can always trust AI" 🔊🔊

𝟭 𝗠𝗶𝗻𝘂𝘁𝗲 𝘄𝗶𝘁𝗵 𝗣𝘂𝘀𝗵 ⚡ — 𝗪𝗲𝗲𝗸 𝟰𝟳 📖 𝗥𝗲𝗮𝗱 𝗦𝘁𝗮𝘁𝗲 Live on testnet. A contract on Push Chain can now read state from a contract on any supported chain. 🧩 𝗪𝗮𝗹𝗹𝗲𝘁 & 𝗦𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 - Wallet v1 architecture is finalized. - SDK work has started on the feature set that talks to it. 🔐 𝗔𝘂𝗱𝗶𝘁 Bug bounty is complete and closed. 🧱 𝗡𝗲𝘅𝘁 Preliminary architecture for 8183 is finalized. 𝗪𝗲𝗲𝗸𝗲𝗻𝗱 𝗩𝗶𝗯𝗲𝘀 🍩: reading state, not the room.

TL;DR: 1. Give every agent its own identity, wallet, and audit trail. 2. Treat every website, API, and agent message as hostile input. 3. Lock memory writes with source, trust level, and expiry. 4. Always assume the agent will fail at some point so place effective measures to contain the blast radius. Read rest of the tips here:

POV: a malicious prompt bear-hugging my perfectly innocent agent to trick it into draining its wallet.

how not to get hacked while interacting with suspicious crypto apps. ft. @ChatGPT

if you still think onchain agents are riskier to use especially while performing heavy economic activities the fix is already out btw:

𝟭 𝗠𝗶𝗻𝘂𝘁𝗲 𝘄𝗶𝘁𝗵 𝗣𝘂𝘀𝗵 ⚡ — 𝗪𝗲𝗲𝗸 𝟰𝟲 🔐 𝗔𝘂𝗱𝗶𝘁 - All reported issues are fixed. Final reports are in and we're verifying them now. - Audited deployments go out next week. 🧩 𝗪𝗮𝗹𝗹𝗲𝘁 & 𝗦𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 - New wallet contracts and flow are live on testnet. - Next: finalizing contract parameters, then evaluation and hook design. This is the logic that decides when a payment gets released. - Marketplace research is done and in review. 📖 𝗥𝗲𝗮𝗱 𝗦𝘁𝗮𝘁𝗲 SDK v1 changes are ready and going into review. 𝗪𝗲𝗲𝗸𝗲𝗻𝗱 𝗩𝗶𝗯𝗲𝘀 🍩 → rate limited until Monday.

Here's a slightly different outlook on answering "which chain will have the highest agentic activity” What if we stop measuring them using a single scalar metric (eg: txns performed, value locked ) and measure them based on multiple vectors that account for their execution intensities as well. the current landscape looks somewhat like this:

pick one chain that will have the highest agentic activity by 2028

ragebait or no-ragebait?