Team keeps shipping 🔥 Qevie Batch Import is live. Upload a CSV and Qevie turns rows into policy checked QUSDC execution. `name.qie` recipients are resolved. Duplicates are flagged. Invalid rows are blocked. Valid rows are composed into the right rail: batch pay, request, link, or subscription. Then Autopilot checks AgentPolicy limits, routes through smart accounts, uses Qevie Paymaster for gas abstraction, and writes receipts back to Passport. CSV in. Policy checks. UserOps out. All on @qieblockchain Mainnet Try it: qevie.xyz

A chain where agentic activity is routine. While Celo’s ~593k AA wallets seem modest vs. Base (~13.4M), the real story is usage: Celo clocks 20.67 ops/wallet (from 12.3M UserOps), outperforming Base (17.1) and Ethereum (4.7). Wallets here are built for high-frequency action, not just holding assets. Whether it's automated AI agents or real users onboarded via MiniPay, they are constantly transacting. For builders, this means you are deploying into a live economic loop where autonomous agents and real users actively consume liquidity, ensuring your dApp taps into continuous, onchain velocity.

Without bundlers, UserOperations never reach the chain. Bundlers package and submit UserOps, making the entire ERC-4337 flow possible. Learn more about Skandha Bundler 👇 etherspot.io/skandha/

to a special contract called the EntryPoint. The UserOp lifecycle works as follows: 1. The user creates and signs a UserOp containing the desired action, gas limits, nonce, and signature. 2. A bundler collects UserOps from a mempool and groups them into a bundle.⬇️

Qevie is officially live on @qieblockchain Mainnet. An agent native QUSDC execution layer built on ERC-4337 smart accounts, scoped session keys, Qevie Paymaster, QIE Domain Resolver, AgentPolicyManager, ReceiptRegistry, and Passport. Users can send, request, batch, create links, set recurring flows, or simply issue agent commands. Autopilot maps intent to the right payment rail, checks policy constraints, resolves `name.qie` recipients, submits UserOps, and records execution receipts. Policy defines the boundary: - QUSDC-only execution - allowed recipients - per-tx / daily / weekly caps - expiry - gas behavior - guardian revocation Execution is automated only where the smart account allows it. Try it: qevie.xyz OPEN TO FEEDBACKS AND SUGGESTIONS!

ERC-4337がようやくFinalになった！🎉 EthereumのAccount Abstractionをめぐって、かなり長く議論と開発が続いてきた規格だけど、ついにEIP側でもFinalのステータスに確定した形。 ポイントは、単に「ウォレットが便利になる」というレベルじゃなくて、EOA前提の体験からSmart Contract Account前提の体験へ寄せやすくなるところ。仕様としては、コンセンサス層を変えずに、UserOperation、bundler、EntryPoint、paymasterみたいな上位レイヤーの仕組みを組み合わせて実現する設計になっている。 特にpaymasterが絡むと、ガス代の支払いをアプリ側で肩代わりしたり、ユーザーに見せる手順をかなり減らせる余地がある。関連するエコシステム側の投稿では、すでに10億件以上のUserOps、5900万以上のアカウント、1200万ドル超のpaymaster volumeという数字も出ていた。 もちろんFinalになったから、明日いきなり全部のウォレットUXが変わるわけではない。ただ、オンチェーンアプリを「秘密鍵とガスを理解している人だけのもの」から一段広げる基盤としては、かなりデカい。 AIエージェントがオンチェーン操作を自然に扱うワークフローや、Web2っぽいアプリ体験とも相性が良さそう。

ERC-4337 is finally final🪩 1 Billion UserOps 59 Million Accounts $12 Million in Paymaster Volume The next billion users shouldn’t need to know what a wallet is 🥂

Just as promised we’ve officially pushed Qevie beyond a simple QUSDC payment app. The stack now runs as an account abstraction payment layer on @qieblockchain Mainnet; smart accounts, Qevie Paymaster, Voltaire UserOps, payment links, QR flows, subscriptions, receipts, Passport and SDK rails are all wired into one flow. The core layer is now live in build: Qevie Autopilot A scoped session-key agent loop where Watcher tracks due obligations, Reputation Oracle reads Passport/ReceiptRegistry history, Strategist composes payment intents, Guardian validates policy boundaries, and Executor submits UserOps through the smart account....

Hedera Sponsored Transactions are now live in production. Gasless txns with one-line config, fund a wallet, whitelist contracts, set gasPrice to 0. No bundlers, relayers, or UserOps needed.

finally ready to show my app on @arc Testnet: Circle Dev Wallets Modular Passkey Wallets real USDC transfers gasless UserOps AI-moderated chat rewards for good vibes penalties for toxic messages try it here: vibecheck-arc.vercel.app/

⚡ @Quicknode × @hedera がスポンサー付きトランザクションをローンチ — 「ガスレスUX」を実現 QuickNodeとHederaは、スポンサー付きトランザクションを正式にローンチし、アプリがユーザーの代わりにガス料金を支払えるようにしました。 Hederaのネイティブなマルチペイマスターアーキテクチャ上に構築されたこのシステムは、Web3における最大のオンボーディングの摩擦点の一つを排除します： 👉 ウォレット設定 ガス承認ポップアップ。 👥 ユーザーは今、以下ができるようになりました： • HBARを保有せずにトランザクションを実行 • ガスプロンプトを完全に回避 • ブリッジングや残高のトップアップなしでアプリを利用 バンドラーを必要とし、EntryPointコントラクトやUserOpsを要するERC-4337アカウント抽象化モデルとは異なり、HederaはスポンサーシップをJSON-RPCリレーに直接統合することで、よりシンプルなアーキテクチャを実現しています。 🛠 主な機能： • 資金のあるHBARウォレットからのガススポンサーシップ • コントラクトごとのホワイトリスト登録 • 支出上限 • @BitGo カストディ統合 • シンプルな1行統合 • メインネット テストネット対応 これは、Hederaのマルチペイマスターリレー機能をHiero JSON-RPC Relay v0.75で初めて本番環境に展開するもので、現在QuickNodeによってライブ運用されています。 「ブロックチェーンを一般ユーザーから見えなくする」

⚡ @Quicknode × @hedera Launch Sponsored Transactions — Enabling a “Gasless UX” QuickNode and Hedera have officially launched Sponsored Transactions, allowing apps to pay gas fees on behalf of users. Built on Hedera’s native multi-paymaster architecture, the system removes one of the biggest onboarding friction points in Web3: 👉 wallet setup gas approval popups. 👥 Users can now: • transact without holding HBAR • avoid gas prompts entirely • use apps without bridging or topping up balances Unlike ERC-4337 account abstraction models requiring bundlers, EntryPoint contracts, and UserOps, Hedera integrates sponsorship directly into its JSON-RPC relay for a simpler architecture. 🛠 Key features: • gas sponsorship from funded HBAR wallets • per-contract whitelisting • spending caps • @BitGo custody integration • simple one-line integration • mainnet testnet support This marks the first production deployment of Hedera’s multi-paymaster relay feature in Hiero JSON-RPC Relay v0.75, now operated live by QuickNode. “Making blockchain invisible to mainstream users”

NEW: Gasless transactions on @hedera, live on Quicknode. Fund a wallet, whitelist your contracts, set gasPrice to 0. What you skip: ✗ Bundler ✗ Custom relayer ✗ Off-chain signer ✗ EntryPoint contract ✗ UserOps pipeline Read more ↓ blog.quicknode.com/quicknode…

The mistake is fading what’s actually happening with AI agents onchain right now just because the coins aren’t moving. – LLMs got good enough at tool use and planning – ERC-4337 already processed 1B UserOps across 57M smart accounts – EIP-7702 pushed smart account behavior directly into the existing EOA base and already crossed 18M live smart accounts with 146M authorizations. – AA made wallets programmable – intent systems let users say what they want instead of manually choosing every route – solver networks already look like proto-agent markets hiding in plain sight. The stack is there for agents to autonomously think, hold money, sign txs, pay APIs, bridge capital, route liquidity, and settle globally in seconds. The catalyst now is execution: intent → solver → simulation → smart account → settlement. Funny how DeFi protocols like @CoWSwap, @Uniswap, @EnsoBuild, and #NEAR Intents all starting to become proto-machine markets competing to fulfill objectives for autonomous capital. Agents optimize for latency, fill quality, cost, and reliability. So the value probably accrues harder to execution markets than flashy consumer frontends. Same thing happened in tradfi where HFT firms captured more edge than broker UI. Another thing I realized is agents need stablecoins way more than they need governance coins. – Base processed 50M x402 txs – Olas agents crossed 5.2M txs and 3.4M agent-to-agent requests – @virtuals_io claims 18k agents and $470M agent GDP Realize this completely changed how I look at the market AI agent coins might not be the layer that captures value just because they print revenue or buybacks. The layer capturing value could be the infra onboarding billions of autonomous transactions.

► Where Account Abstraction Actually Failed Last cycle, I used to expect account abstraction was the tech that could onboard the next billion users. Yet, I still just open rawdog EOAs everyday and click confirm like nothing changed. Looking at it cleanly, AA didn’t actually fail technically. By May 2026: – 62M smart accounts deployed – 2.4B cumulative UserOps – $180M gas sponsored by paymasters – 14M EIP-7702 delegations since Pectra Problem is users never cared. AA became middleware for developers instead of a real consumer narrative. Most users didn’t even know they were using it. Farcaster, games, embedded wallets, Polymarket quietly deployed smart accounts underneath while users just clicked buttons. There was never really a hyped AA narrative moment because better wallet UX is probably not a strong enough driver for behavior. The tech also started abstracting the abstraction itself with stuff like ERC-4337, ERC-6900, ERC-7579, EIP-7702, native AA, paymasters… Honestly, L2s accidentally reduced part of AA’s value prop too. When tx fees already cost fractions of a cent, ppl stopped caring as much about gas abstraction. Too early for humans, but AI agents might be the thing that finally forces it to matter tho. AA primitives by chance are basically the exact stack AI agents need to exist safely onchain. An AI economy running millions of autonomous microtransactions per day probably cannot exist on EOAs at all. The machine economy is accidentally reviving the entire AA thesis. – Active smart accounts going higher since agents started executing onchain – 100M x402 transactions happened within ~7 months – AWS launched AgentCore Payments – Coinbase pushing Agentic Wallets hard – @privy, @zerodev_app, @turnkeyhq, @pimlicoHQ pivoting toward agent infra now – @safe went from DAO multisig infra to AI-agent treasury tooling Unlike many crypto innovations, AA projects were always hard to drive speculative demand around. So AA got less retail attention and lived in the shadow of more tangible narratives.

Day 39 of Smart Contract Security⚔️ Been building a full ERC-4337 smart contract wallet from scratch. Here's what that actually looks like. 🔐 No protocol changes. Just UserOps, Bundlers, and an EntryPoint coordinating off-chain intent with on-chain validation. The `PackedUserOperation` struct is the heart of it — and `validateUserOp` is where your account defines what "authorized" means. Added ECDSA signature verification, locked `validateUserOp` to EntryPoint-only access, implemented `execute` for arbitrary contract calls, and built full Foundry tests that sign real UserOps with `vm.sign` and verify them against a mock EntryPoint. Also contrasted with zkSync's native AA — same concept, Bootloader replaces EntryPoint, but the execution model is architecturally different. Private keys are a single point of failure. Programmable accounts are the fix. 🛡️

Under the hood we run a post-quantum smart-wallet stack on a custom @arbitrum Orbit L3, Stylus contracts, wallet-sdk relayer dashboard, and a agent that drives real UserOps, so agentic means measurable, traceable flows, not vibes.