spending the week of aug 24 in Belgrade with @_JAW_id for @belgradebw@ethbelgrade 🇷🇸
if you're building anything onchain, let's meet ) who's gonna be there?
JAW runs on 13 mainnets today. Need one that isn't live yet? We onboard chains on request, so ours don't cap your roadmap.
Get started 👇 https://t.co/dikE6mRMlb
erc-20 approvals aren't getting fixed, they're getting bypassed. with erc-7715 the limit lives in the account instead of the token. x per month, expiry, revocable onchain, that's how subscriptions work in @_JAW_id today. We support @base check us out.
https://t.co/aTS6j3c6CW
Identity becomes valuable the moment it changes financial outcomes.
Better borrowing rates are just one example. Next come payments, AI agents and everything that depends on programmable trust.
this is exactly why we're building @_JAW_id
JAW is live on @soneium 🎉
Building on Soneium? Now you can easily drop in self-custodial wallets with Face ID or fingerprint, ENS identity, and programmable permissions.
Put your focus on your product, and let us handle the rest.
your user is mid-checkout 👉 they click connect 👉 a popup opens 👉 they lose it 👉 behind a tab 👉 they give up 👉 you lose them ☠️
we've seen this kill more onboarding flows than any bug ever did.
JAW stays inside your app: no separate window, no interruption, no users lost.
Get started: https://t.co/91AW2Qbu8Y
Most wallets ask users to sign a transaction they can't actually read. JAW uses clear signing throughout: every request surfaces what is being approved in plain language, not a hex string. When an AI agent is the signer, that same standard applies. The user set the rules, the system shows what it's doing, and the private key never moves.
https://t.co/Pj0Tldl2vo
The reason JAW doesn't use seed phrases isn't just UX. It's architecture. A passkey is a P256 key pair generated on the device, stored in the secure enclave, and never transmitted. There's no server-side secret to steal, no phrase to phish, and no recovery flow that requires trusting a third party. That's what we mean when we say the account belongs to the user.
https://t.co/91AW2Qbu8Y
standards the @_JAW_ID stack uses under the hood:
ERC-4337, EIP-7702, EIP-3668, EIP-5792, ERC-7677, a variation of ERC-7715, ERC-7828, ERC-7811, ERC-7871, EIP-712, ERC-1271, ERC-191, ERC-7739, ERC-7730, ERC-7201, ERC-7528, EIP-1193, EIP-3326, EIP-4361 and ERC-8213
credit to the authors of every one of these
Asking a user to hold ETH just to pay for gas is the kind of friction that kills the first session. JAW's managed ERC-20 paymaster lets your app sponsor gas entirely or let users pay fees in stablecoins, without you having to wire up a bundler or manage a paymaster contract yourself.
👉 EIP-5792 atomic batching means multiple operations go through in a single user action.
Get started at https://t.co/kYZIfBlHrI
The wallet and the passkeys are identical whether JAW renders as an iframe or a popup. Only the carrier changes. This means no tradeoff between UX and security: the embedded dialog is just the popup, delivered inline.
👇
https://t.co/dikE6mRMlb
JAW now renders inline by default.
❌ No popup window.
❌ No extra tab.
✅ The sign-in and transaction dialog appears as a bottom drawer on mobile, as a centered dialog on desktop, or right inside your app.
On Chrome, Edge, and Brave it works with zero setup. On Safari and Firefox you get an automatic pop-up fallback.
To enable the embedded dialog on those browsers too, message us on Telegram, and we'll add your domain to the allow-list 👇
https://t.co/GkuIhJglMF
We've got news from the JustaName team:
We've made the call to consolidate our work into JAW. Sunsetting products is never fun, and throwing away work you're proud of is even worse. But we'd rather do one thing exceptionally than six things adequately.
What this means in practice:
Staying live:
👉 Subname issuance APIs and SDKs.
👉 Existing integrations keep working; no actions needed.
Winding down over the coming weeks:
👉 ENSvolution,
👉 JustVerified,
👉 JustaName plugin,
👉 The playground and the app.
JustaName doesn't disappear, though; it becomes the identity stack inside JAW, where ENS-native identity meets passkey accounts and programmable permissions. That's the bet we're making with full focus now.
Our conviction in ENS remains unchanged. It's baked into every JAW account by default.
X activity moves to @_JAW_ID from here on. Come say hi!
Two new things in JAW
🔎 See exactly which assets will move before you sign, with every balance change simulated upfront
🤝 @RobinhoodCrypto chain is now supported
The screenshot below shows both in action 👇
We're not pretending migrating off any wallet is zero effort. What we can say is this one is a connector swap, not a rebuild, because both wallets expose the same developer surface.
Read more 👇 https://t.co/Efeucwcq5f