Chris Gale retweeted
Who honestly looks a chart like this and thinks "yea I think its a good time to finally buy now"
$LITE
The future of agent set ups - lightweight wrappers around existing harnesses running on your own infra.
It has access to your full dev env and can improve itself recursively. it's also so easy to build when you're set up for it.
Introducing the worlds first video player offering micro streamed rewards. Live on @tempo. Streams video and on-chain currencies.
Brands can reward PathUSD to viewers every few seconds.
Attention is rewarded.
Videos are shared. Referrals are rewarded.
Try it here video-rewards.com/widget/193
Check it out @dwr
90% video completion rates happen when viewers have skin in the game.
ViewFi Stream now enables brands and companies to offer users with real-time #PathUSD rewards — micro-payments streamed to wallets every 10 seconds.
The future of attention is compensated.
stream.viewfi.io - try and earn today (testnet tokens for demo purposes)
Built on @tempo
Direct video stream - video-rewards.com/widget/190
Whitepaper - app.viewfi.io/docs/whitepape…
Running Karpathy's autoresearch on my Mac Mini with a local Qwen 3.5 as the researcher agent.
It proposes experiments, trains a GPT from scratch, evaluates, keeps or discards, repeats.
No cloud.
No API costs.
Just silicon thinking while I sleep 💪
Once you have seen this, it changed everything.
My agent now manages my crypto wallet. Simples.
#AgenticAI #openclaw
The agentic payment wars are starting.
x402 (Coinbase/Solana) wants to rebuild the internet with HTTP 402.
lobster.cash just gives your agent a credit card.
One works at Instacart checkout right now.
But one will scale to open whole new business models #nanopayments
Just submitted @Fabricbloc_ to the @artemis Agentic Commerce Map
The twist? Our #openclaw did it autonomously.
No MetaMask popup. No human clicking "confirm."
$1 USDC paid via x402 — signed, submitted, done.
This is what agentic payments look like. 🤖💸
agenticpayments.artemisanaly…
Suggestions:
1. Better errors — "Missing accepted field" not "No matching requirements"
2. Server-side SDK that works with any signer
3. Payload examples in docs
4. Validation endpoint to test before paying
Pain point #2: Header confusion
v1 uses X-PAYMENT
v2 uses PAYMENT-SIGNATURE
Found this by grep-ing through source code, not documentation.
Pain point #1: The `accepted` field
x402 v2 requires your payment payload to include an `accepted` field matching the server's requirements.
Not in the docs. Error message? "No matching payment requirements"
Took my agent time reading node_modules to find this.
What worked beautifully:
✅ EIP-3009 (gasless for sender)
✅ CDP Server Wallet signing
✅ The 402 → payment → retry flow
The protocol design is solid. The DX needs work.
This is wild.
Qwen 3.5 running fully local on an iPhone 17 in AIRPLANE mode... 🤯
No subscription. Nothing leaves your device.
AI subscriptions just became optional.
The new Qwen 3.5 by @Alibaba_Qwen running on-device on iPhone 17 Pro.
Qwen 3.5 beats models 4 times its size, has strong visual understanding, and can toggle reasoning on or off.
The 2B 6-bit model here is running with MLX optimized for Apple Silicon.
Today I launched V2 of my mission control using #OpenClaw
It has 10 agents running 3 companies. Generating revenue. Running development, marketing and outbound sales.
Every day I get 10% more productive. V3 has some big updates which will save me hours.











