ZeroDev

The programmable account platform for better onchain products. An @Offchain company.

[ZeroDev @ZeroDev]

ZeroDev Wallet is here.

It completes the ZeroDev platform by giving teams one place to build, launch, and scale programmable accounts.

Embedded wallets. Smart accounts. Gasless transactions. Recovery. Session keys. Automation.

Better onchain products, shipped faster.

[ZeroDev @ZeroDev]

@grid_arena Enter the Grid 🫡

[ZeroDev @ZeroDev]

Every @grid_arena account is now powered by ZeroDev.

Built on ZeroDev Kernel smart accounts, traders get instant biometric passkeys, sponsored gas, and sub-second transactions.

No seed phrases. Zero popups. Just pure execution.

[Grid @grid_arena]

Zeroing in.

Every Grid account is now a @ZeroDev smart account, on your own address.

Buy a stock. Start an Earn pair. Put Cash into a vault on any chain.

One tap. No gas.

[ZeroDev @ZeroDev]

we love building smart wallet infra for tokenization

[Arbitrum @arbitrum]

we love tokenization

[ZeroDev @ZeroDev]

@OpportunityDeFi Welcome to ZeroDev 🫡

[ZeroDev @ZeroDev]

Onchain options just got simpler with @OpportunityDeFi, powered by ZeroDev.

[Opportunity @OpportunityDeFi]

Opportunity × @zerodev

A simpler way into onchain options.

We're bringing ZeroDev-powered smart wallets to @OpportunityDeFi, making it easier to get started.

Explore the testnet: https://t.co/FpwaZP90bc

[ZeroDev @ZeroDev]

@arbitrum @Offchain let's go!

[Arbitrum @arbitrum]

Cross River is bringing its tokenized lending platform to Arbitrum One.

> Arbitrum One will provide the rails at launch to tokenize and service loans on Cross River’s platform
> @ZeroDev’s embedded wallet solution will power the customer experience
> Architected by @Offchain’s Enterprise Services team

By making lending programmable, @crossriverbank is laying the groundwork for easier loan transfers and new financing opportunities in the future.

[Ed Felten @EdFelten]

Cross River is building with @Offchain Enterprise Services

Very excited to support their business as one of the biggest banking as a service companies out there.

Our team will be working very closely with theirs for the build out of a proprietary tokenization engine, all with settlement to @Arbitrum and wallet infra powered by @ZeroDev

The programmable economy is growing, and Offchain promises to be at the center of it.

[ZeroDev @ZeroDev]

@GillesGade @HongKongFinTech @Offchain bullish

[ZeroDev @ZeroDev]

@crossriverbank @HongKongFinTech @GillesGade @Offchain let's cook

[ZeroDev @ZeroDev]

@Offchain @crossriverbank @arbitrum ready 🫡

[ZeroDev @ZeroDev]

Cross River selected ZeroDev to power the customer experience for its tokenized lending platform.

Built by @Offchain's Enterprise Services, our embedded wallet solution will be integrated into @crossriverbank's tokenization platform on @Arbitrum One.

A huge moment for smart wallets in institutional finance.

[Offchain @Offchain]

We’re partnering with @crossriverbank to integrate tokenization directly into its lending platform.

@Offchain Enterprise Services brings dedicated engineering together with @Arbitrum One and @ZeroDev wallet infrastructure in a single delivery.

https://t.co/p7DhE66j5T

[Derek Chiang | Ethlabs @decentrek]

Quick notes on 7702 to dispel fud and keep your funds safe.

First thing first -- 7702 itself isn't broken. Don't panic if you are using a wallet that supports 7702 (MetaMask, Uniswap, Ambire, etc.).

To recap, 7702 is an account abstraction EIP that allows an EOA to sign a special message, called a "7702 authorization," that would insert a smart contract into the account, which enables the account to do powerful things like transaction batching, e.g. doing "approve" and "transfer" in one transaction so you can swap on Uniswap with one click.

But unfortunately the same feature also allows a hacker to efficiently move all your tokens in one single transaction. In the Binance hack, the hacker moved ETH, USDT, and 62 other tokens in one transaction, whereas without 7702 they'd have had to send one transaction per token. In this particular case, many of those transactions would've failed because Binance was still using the hacked wallet for withdrawals, so all transactions sent by the hacker would've had to compete with the legit transactions for nonces. So using 7702 did help the hacker steal as much funds as possible, as quickly as possible. Ouch!

However, in order for the hacker to use 7702, they must have either 1) had access to the private key, or 2) tricked Binance into signing a 7702 authorization. The latter is very unlikely, as it's hard to imagine Binance being so incompetent as to expose an endpoint for signing 7702 authorizations or (even worse) for signing raw messages which the hacker could've repurposed for 7702 authorizations. But I can't rule that out until the official postmortem.

What does all this mean for you?

- If you are a wallet developer, do NOT, under any circumstances, expose a way for third parties to request 7702 authorizations. This is just handing your users a giant footgun to shoot themselves with. No wallets I know of do this, so don't worry if you are a user.

- If you are a user, use a well-known wallet. 7702 does let wallet developers screw up in more ways than before, so use only well-known wallets whose developers' competence you can trust.

- If you are a company (e.g. an exchange) operating hot wallets, do NOT, under any circumstances, expose an endpoint (even if it's an internal endpoint) for signing 7702 authorizations or raw messages.

As a contributor to AA, I feel partially responsible for hacks like this, since by increasing the power of accounts, we've indeed also empowered hackers (not unlike how any new technology empowers both the good guys and the bad guys). That said, it's important to note that 7702 was only a transitional EIP, and "endgame AA" such as Frame Transactions (EIP-8141) would allow wallet owners to set up their wallets much more securely. For example, if Frame Transactions were available today, Binance could've:

- Set up their wallets as multisig contracts only (not EOAs).

- Set up "post conditions" for their `transfer()` functions, so that even if the multisig got hacked, the contract itself would perform sanity checks such as "no transfers of more than 1000 ETH without additional signers."

In short, the endgame of Ethereum UX is one with both optimal security and optimal UX, and users never have to trade off between the two. But we still have a long way to go until we get there. Back to work!

[ZeroDev @ZeroDev]

Lots of people are blaming EIP-7702 for recent hacks.

7702 isn't the cause of the attacks. Attacks are caused by compromised apps, leaked keys, or a bad signature request. Every 7702 delegation needs the owner’s signature.

Always protect your keys and always watch what you sign.

[ZeroDev @ZeroDev]

ICYMI: ZeroDev Earn is now live across Ethereum, Arbitrum, Base, Robinhood Chain, Hyperliquid and more

DeFi teams can give users a simple way to discover and access yield opportunities across chains

All in one flow, from vault selection to deposit tracking

Try out the demo here or tag a team that should check it out:

https://t.co/RWT4lgU8bN

[ZeroDev @ZeroDev]

@shaddoteth Ethereum, Arbitrum, Base, Hyperliquid, BNB and more :)

Find all the chains supported here:

https://t.co/Td08FmAD4G

[ZeroDev @ZeroDev]

ZeroDev Earn is here.

Cross-chain yield across supported assets, routes, and opportunities through one integration.

No new ZeroDev Earn transaction-level fee at launch; existing API and SRA pricing still apply.

https://t.co/JfLYIzq3vq

[ZeroDev @ZeroDev]

At launch: selected Aave and Morpho opportunities.

Try the demo, then read the quickstart.

https://t.co/CCrxUnUPse

[ZeroDev @ZeroDev]

Users start with a supported asset on the chain where they already hold it. They don't need the right asset on the right chain first.

ZeroDev Earn is built on Smart Routing Address, which launched in September.