Pinned
Biconomy
8,050 posts
Biconomy
@biconomy
Build the Web3 apps of the future!
Single click DeFi for agents, wallets, dapps.
- Biconomy reposted
8 months ago, we launched HyperSignals. Since then, we’ve grown to 2,000+ daily active users and built a highly loyal community. But behind the scenes, we realized the market was moving much faster than anyone anticipated. 🧵
- Biconomy repostedWe spent months building a better way to pick trades. Then we watched our own users. Nobody needed another pick. They needed someone to run the whole thing.
- Biconomy repostedPeople can hold the same asset for completely different reasons. One trusts the technicals. The other trusts the earnings and P/E. Another watches macro. Another reads options flow. So we let you pick. You tell the copilot what to lean on. Charts, fundamentals, macro,
Replying to @biconomy8/ Start to finish: you sign once. The origin batch unwinds the lending position and opens an intent. A solver bridges the funds. The destination batch waits for them to land, reads the real amount, and supplies it to the farm. One signature kicked off a two-chain script, and- Replying to @biconomy7/ Stack them and it's one flow. One ERC-7964 signature authorizes the plan. ERC-8211 encodes each chain's steps with live values and conditions. The Open Intents Framework moves the liquidity in the middle, and the destination batch waits for it before continuing.
- Replying to @biconomy6/ So instead of hardcoding "supply 487 USDC," each step resolves its value live: "supply whatever just arrived." Steps also carry their own conditions and can wait. The destination batch gates on "have the funds landed?" and a relayer only submits once that's true. No glue
- Replying to @biconomy5/ Wall three: even with a signature and a bridge, you still can't write the script. You don't know exactly how much you'll unwind until it runs. How much you supply depends on what the bridge delivers. And the supply step can't fire until the funds actually arrive. This is the
- Replying to @biconomy4/ Wall two: cross-chain liquidity is fragmented. That's what the Open Intents Framework is for. openintents.xyz An open-source, solver-agnostic standard that lets the leading EVM solvers compete to fill your order. You sign an intent, your funds lock on the origin
- Replying to @biconomy3/ Wall one: a normal EVM signature only authorizes execution on a single chain. Your action spans two. ERC-7964: cross-chain signatures. eips.ethereum.org/EIPS/eip-7964 Encode every call across every chain into one EIP-712 object, sign the array once, and that single signature
- Replying to @biconomy2/ Say you want to unwind a lending position on one EVM chain, bridge the funds with the Open Intents Framework, and supply them to a yield farm on another EVM chain. One clean intent in your head. The moment you sit down to encode it, you hit three walls.
- 1/ We're really excited about OIF! ERC-8211, the account-centric execution standard built by Biconomy and the @ethereumfndn Improve UX team, pairs with the Open Intents Framework and ERC-7964 signatures to let developers encode, and users run, arbitrarily complex cross-chainThe Open Intents Framework is designed as shared infrastructure for intents. A modular, open framework that the ecosystem can build intents on, together. Today, it takes its next step: adoption at scale.
- Replying to @biconomy9/ ERC-8211 is one of the most important ergonomics-shaped standards on Ethereum since 4337. The Smart Batching SDK is what makes it real for product teams today. Feel free to check out the deep dive in our blog
