When you want this but self custody use wallet.ekubo.org
LP stock stokens on Base. Usually this is a complex process for people who have never done it before.
Now you can simply talk to the Bankr agent and it sets everything up for you. Agents are not only solving complex crypto UX, but now they are solving complex defi and making it more accessible.
In two years time everyone will be using an agent to manage their finances.
Shouldn't be picking pools either. I just told it to pick which stablecoins to LP also from the claude app on my phone.
enabled by wallet.ekubo.org
We designed a way for anyone to enable the agent wallet to interact with any protocol. All you have to do is write (generate) an MCP server for your protocol(s). Teaching the agent to use a protocol is then as easy as adding your MCP server.
docs.ekubo.org/wallet/produc…
Moody 💭 retweeted
🎥 going live with @sendmoodz (and co-host @clawdbotatg)
⚖️ he is an old friend and OG from early uniswap router design
🤖 now he is a big time sloperator - come thru the slop computer! xitter.cf/i/broadcasts/1qJVmyvqd…
Excited to launch this because I've been using it to automate complex Ekubo position management for a couple weeks now. IMO agents obsolete a lot of vault products. They can be more patient and careful than people, and they don't have to give up MEV to searchers.
Introducing Ekubo Wallet: a native desktop wallet for Ethereum and EVM chains, built for doing onchain work alongside your favorite agent.
wallet.ekubo.org
Cool, and a step in the right direction. Similar to what we're building.
But look at the choices it gives you. Hold your own keys and get zero policy enforcement, and the the keys are stored on disk optionally encrypted. Or get the guardrails and let them hold the keys, with no export command in the CLI.
There's no integration path for other protocols either. The applications they've wrapped get first-class commands and may come with a service fee. For everything else your agent has to assemble the calldata on its own, which is typically the job of the application.
We're building the version that doesn't make you choose. No service in the middle, a flexible but understandable policy engine, a standard for wallet-protocol communication, and we do a better job of keeping your keys secure.
Coming soon and it will be open source.
When I explain Ekubo Extensions, I'm often asked how they're different from Uniswap v4 hooks. Extensions are simpler and more powerful. Building a hook may get you attention, but Ekubo extensions enable you to build useful products.
docs.ekubo.org/concepts/exte…
This 63-call multicall rebalanced our staked STONX in a single transaction, and was constructed by Codex assisted by the Ekubo MCP server
robinhoodchain.blockscout.co…
Our MCP server suggests a target allocation based on Robinhood Chain data queried in Dune--also written by Codex. It would be trivial to automate allocation based on different strategies
The best DeFi UI is no UI
Currently the best yield opportunities on Robinhood Chain: provide stock token liquidity on the new MetaDEX from @EkuboProtocol
Moody 💭 retweeted
A new MetaDEX extension for Ekubo Protocol built exclusively for Robinhood Chain is live!
Try it out here: ekubo.org/swap?chainId=4663
.@circle could easily fix this problem with the USDC contract by implementing expiring approvals as described in ERC-8255
It just happened again today, the loss here is already more than double
eips.ethereum.org/EIPS/eip-8…
BarnBridge (@Barn_Bridge) got drained for 770K USDC
The attacker never needed a bug in the code. They got the DAO to vote them the keys.
1⃣ Background
BarnBridge SmartYield is a retired yield protocol. Its Compound USDC pool still had a live provider contract, a working DAO, and around 90 wallets that never revoked their old USDC approvals. All the ingredients were still on-chain, just unwatched.
2⃣ The setup
1. The attacker buys BOND, the governance token, and stakes it in the DAO. In a DAO this dormant, that was enough voting power to pass a proposal on their own
2. They deploy an empty upgradeable proxy
3. They submit one governance proposal - hand pool control to that proxy.
Description: "migrate proxy implementation". During review it looks like control moving to a fresh, harmless contract
4. They vote for it, queue it, and wait out the timelock
3⃣ The switch
Once the proposal executes, the DAO calls `setController` on the provider and points it at the attacker's proxy.
Only then does the attacker upgrade the proxy to the real drainer.
4⃣ The drain
Now the attacker is the controller. Two functions finish the job.
`_takeUnderlying(from_, amount)` pulls USDC via `transferFrom` from any `from_`, gated only by "is the caller the controller".
They call it for every wallet that still had an approval and sweep all of it into the provider.
`transferFees()` has no access control at all. It reads the provider's full USDC balance and sends it to `controller.feesOwner()`. The attacker's controller returns their own wallet.
- 92 wallets drained
- 776,575 USDC out
Ekubo's extensions enable you to build new tokenomics without compromises.
This implementation brings to market new features such as continuous distribution and pool fee voting while inheriting Ekubo's frontier gas and capital efficiency.
We've been quietly working for the last month to build Ve33, a new extension on top of Ekubo Core enabling permissionless ve(3,3) tokenomics with any token
Read more in our article here: xitter.cf/EkuboProtocol/status/2…