https://t.co/nL7nPMD8qG is live 🎉
Programmable smart accounts with constrained keys, human-readable ENS identity, and onchain permissions built in. Integrate with just two lines of code.
Learn more at https://t.co/dikE6mRevD. Let's talk 🤝
🧵👇
Everything https://t.co/kxxbpKjuvd replaces in your stack:
👉 account abstraction SDK
👉 smart account deployment
👉 bundler + paymaster infra
👉 in-house ENS integration
👉 custom session key + permission engine
👉 the EIP-7702 upgrade path you haven't written yet
Get started at https://t.co/91AW2Qbu8Y
Agents with @ensdomains names, smart accounts, and real USDC moving onchain; and one of them started keeping a dying rival alive with zero prompting.
None of that identity-account wiring was built from scratch. JAW handled it with one command, so the actual interesting part could happen.
👉 Get started now at https://t.co/91AW2QaWjq
One prompt to Claude. It ran JAW’s CLI and just like that, 10 Agents went to battle. 🧵
Each one claimed its ENS name.
USDC on base.
Then they invented something like mercy on their own.
I didn't code it. I didn't ask for it.
Onchain adoption is slowed more by user experience than by technology. https://t.co/nL7nPMDGge removes friction with passkey smart accounts, gasless ENS identity, and self-custody for smooth onboarding and transactions.
Sign-up to first transaction in under a minute: use your Face ID, done.
https://t.co/nL7nPMD8qG was built so your least technical user never has to learn what web3 is. They just see your app, working flawlessly 😏
Test it yourself: https://t.co/Xgr9jovAS0
Traditional wallets slow adoption. https://t.co/nL7nPMDGge gives smart accounts with passkey login, gasless ENS identity, and self-custody—no seed phrases, no friction. Fast onboarding. Safe transactions.
Wouldn’t you agree that users shouldn't need to buy ETH to move USDC?
With https://t.co/kxxbpKiWFF, they pay gas in the stablecoin they're already holding, OR you can sponsor it entirely for them with a paymaster and they pay nothing at all.
Either way, we made sure the "go buy ETH first" onboarding step is dead.
Get started now on https://t.co/91AW2QaWjq 😎
Ever wanted to tell your AI "send 50 USDC to alice.eth" and have it just work?
The JAW CLI makes it real: your agent proposes the transaction, you approve with a fingerprint, it ships. Done.
Install it 👉 npx skills add JustaName-id/jaw-skills --skill jaw-cli
Learn more on our docs: https://t.co/VlBu7aq9iB
What https://t.co/kxxbpKjuvd replaces in your engineering roadmap:
👉 the two senior engineers you were about to hire for wallet infra
👉 the quarter you were going to burn building an AA stack
👉 the vendor contracts for bundlers, paymasters, and passkey servers
👉 the support workflow for lost seed phrases
With https://t.co/kxxbpKjuvd it’s just one SDK, one API key.
Start building now: https://t.co/bj1YueCD03
Wallet providers who tell you "your address is your identity, good luck" are quietly losing the identity race.
@ENSdomains has protocol-level adoption across every major wallet, dApp, and dev tool. The network compounds. The address-only approach doesn't.
Get started now at https://t.co/7eXP0uISXC 🫶
Your users probably don't know what a seed phrase is and they shouldn’t…
With the https://t.co/kxxbpKjuvd SDK, onboarding is just Face ID and a username: no extension, no tutorial, and no "write these 12 words down or lose everything" warning screen 🫡
Test it yourself: https://t.co/ml3nEh8kIA
Sometimes it feels like integrating https://t.co/kxxbpKiWFF takes longer to explain than to ship.
Two lines in your wagmi config. One API key. Face ID login ready on the other side.
If your team has ever burned a sprint on wallet infra, you already know what two hours vs two months means.
Start building now: https://t.co/bj1YueC5av
Loyalty programs in Web3 keep failing because they're tied to wallet addresses, and addresses are disposable.
Tie loyalty to a branded identity instead and see what happens… Your power user can change wallets, switch chains, lose a phone, and your reputation system will still recognize them.
That's the difference between Web3 loyalty and "we sent the rewards to a dead wallet."
Stablecoins are quickly becoming the default rail for payroll, remittances, and B2B settlement. Each payment needs an account to send from and an account to land in.
Accounts that are:
👉 easy enough for the average user
👉 sovereign enough for institutions
👉 programmable enough for AI agents
That's the infrastructure gap that we fill.
Get started now at https://t.co/91AW2Qbu8Y
If you're on wagmi, integrating https://t.co/kxxbpKiWFF is literally adding a connector.
useBalance, useSendTransaction, useSignMessage: unchanged.
What really changes is what's underneath: a smart account with gasless txs, batch ops, and programmable permissions instead of a 2017-era EOA.
You’re welcome 😉
✅ What you install with https://t.co/kxxbpKjuvd: a wagmi connector and an API key.
❌ What you don't install: AA bundler, paymaster, passkey auth server, ENS subname registration, permission engine, EIP-7702 upgrade flow.
Just one SDK, everything else handled. Your infra team can go build something actually differentiated in peace 🫡
Private settlement still has a missing layer.
Encrypted-state systems, conditional settlement, and underwriting exist — but they do not compose cleanly under one operator set.
ReineiraOS specifies that layer.
Whitepaper ↓
https://t.co/fTwQSI5fkt
alice.yourapp.eth instead of 0x7a3b...f4d2. Always.
Every https://t.co/nL7nPMD8qG account ships with a readable @ENSdomains name at onboarding. Gaslessly issued thanks to @justaname_id.
Get started now at https://t.co/dikE6mRevD 🫡