Biconomy

About Biconomy (BICO)

What Is Biconomy (BICO)?

Biconomy is account abstraction and chain abstraction infrastructure for EVM networks. Its purpose is to remove the parts of using a blockchain application that have nothing to do with what the user is trying to do: holding the right gas token on the right chain, signing a separate transaction for every step, and manually bridging funds before an action can execute.

BICO is the project's token. It is an ERC-20 deployed on Ethereum with a further deployment on Arbitrum, and Biconomy describes the Biconomy Network as a proof-of-stake orchestration layer in which holders stake BICO and delegate it to node operators. Biconomy is infrastructure rather than a blockchain of its own, which is the single most important thing to understand about it.

Official sources:

• Biconomy
• Biconomy Documentation
• Biconomy Staking
• Biconomy on GitHub

Who Founded Biconomy? (History)

Biconomy was founded in March 2019 by Ahmed Al-Balaghi, Aniket Jindal, and Sachin Tomar. Its first product was a multi-chain relayer that let applications sponsor gas for users through meta-transactions, at a time when account abstraction had no standard and every implementation was bespoke.

The company raised roughly 22 million dollars in total, including a 9 million dollar round in July 2021 led by Mechanism Capital and DACM with participation from Coinbase Ventures, CoinFund, True Ventures, and others. The BICO token launched in late 2021.

The product line has changed substantially since. Hyphen, Biconomy's cross-chain liquidity bridge launched in 2021, was decommissioned on December 31, 2024. In November 2024 Biconomy acquired Klaster and used that work to build its Modular Execution Environment. The current stack centers on ERC-7579 modular smart accounts, EIP-7702, and cross-chain intent execution rather than the original relayer. Repositories including the SDK and the composable batching contracts were receiving commits into September 2026.

How Biconomy Works

1. Nexus smart accounts Nexus is Biconomy's smart account implementation, compliant with ERC-7579. Instead of a fixed wallet contract it is a small core with pluggable modules: validation modules that define how a transaction is authorized, including ECDSA keys and passkeys, execution modules for batching and automation, and fallback handlers for extended behavior. Third-party modules can be installed on an existing account without redeploying it.

2. Composable batch execution Ordinary batching submits several calls together. Biconomy's composable batching lets a later call consume the output of an earlier one, so a sequence such as swap and then deposit the exact amount received becomes a single atomic operation rather than two transactions with a guess in between.

3. Modular Execution Environment MEE is the orchestration layer. A user signs one intent, and MEE turns it into a coordinated plan of transactions that may span several chains, handling dependencies between steps, sourcing gas from whichever chain the user has funds on, and settling the result. Biconomy calls the resulting unit a supertransaction.

4. EIP-7702 and EOA support With EIP-7702, an ordinary externally owned account can temporarily adopt smart contract code, so smart account features become available without migrating to a new address. The stack supports both smart accounts and EOAs.

5. Smart Sessions Sessions grant scoped, revocable permission to an agent, bot, or automated system, constrained to specific contracts, specific functions, and spending limits. This is the primitive that lets automated strategies and AI agents act for a user without holding that user's keys.

Key Ecosystem Components

• Nexus, the ERC-7579 modular smart account
• The Modular Execution Environment and its supertransaction model
• The Supertransaction API, a REST interface with a quote step and an execute step
• AbstractJS, the TypeScript SDK for encoding calls and managing accounts
• Smart Sessions for delegated, permission-scoped execution
• Gas sponsorship infrastructure, descended from the original relayer product

BICO Token Utility

BICO is an ERC-20 with 18 decimals and a total supply of 1,000,000,000 tokens. A live read of the Ethereum token contract confirms the symbol, the 18 decimal places, and a total supply of exactly one billion whole units. A second deployment exists on Arbitrum.

The documented role of the token is staking and delegation. Biconomy's official staking interface describes the Biconomy Network as a proof-of-stake orchestration layer where holders stake BICO and delegate it to node operators, receiving a share of rewards. BICO has also historically been described as the network's governance token.

One honest caveat belongs here. Biconomy's current developer documentation describes the product stack, the smart account, the SDK, and the execution APIs without stating that BICO is required to create an account, call the API, use gas sponsorship, or execute through MEE. Token demand therefore rests on the staking and network fee design rather than on a hard technical requirement inside the developer workflow. Anyone evaluating BICO should read the current network documentation directly rather than assuming product usage translates into token usage.

What Makes Biconomy Unique?

Biconomy's strongest differentiator is that it treats multi-chain execution as a single signed intent rather than a sequence the user has to assemble. Most account abstraction stacks stop at making one chain easier. MEE composes across chains, including sourcing gas from a chain the user already holds funds on, which removes the most common reason a transaction fails for a non-expert user.

The second is standards positioning. By building on ERC-7579 modules and EIP-7702 rather than a proprietary wallet contract, Biconomy's accounts can adopt third-party modules and stay aligned with Ethereum's account abstraction direction rather than diverging from it.

How Biconomy Differs from Similar Infrastructure

Against bundler and paymaster providers whose scope ends at ERC-4337 user operations on a single chain, Biconomy adds an orchestration layer spanning chains that supports dependent steps within one execution.

Against general purpose bridges and messaging protocols, Biconomy is not primarily moving value between chains for its own sake. Bridging is one step inside an execution plan, and its own standalone bridge was retired at the end of 2024.

Against smart contract wallets aimed at end users, Biconomy sells to developers. Its output is an SDK, an API, and contracts that other applications embed, so most people who benefit from it will never know they used it.

Use Cases of Biconomy

• Onboarding users into applications without requiring them to hold a gas token first
• One-signature flows that swap, bridge, and deposit across chains as a single operation
• Passkey and social login authentication in place of seed phrase management
• Delegated, spending-limited permissions for automated strategies and AI agents
• Sponsored transactions where an application pays gas on behalf of its users

How Biconomy Is Secured

Because Biconomy is infrastructure rather than a chain, its security profile has several distinct parts. The smart account contracts and the modules installed into them are the primary on-chain risk surface, and modular accounts add a specific hazard: an account is only as safe as the least trustworthy module a user installs. The execution layer must faithfully carry out signed intents, and a user's protection there is that the signature commits to the plan. Session keys are constrained by contract-level limits, so an over-broad session scope is a user configuration risk rather than a protocol failure. Staking and delegation add validator-style operator risk on the network side. Treat module installation and session scoping with the same care you would apply to token approvals.

Risks and Considerations

• Token utility risk, since the developer-facing product does not require BICO to function
• Smart account and module risk, where a malicious or buggy module can compromise an account
• Session key risk if permissions are scoped too broadly or left active too long
• Product churn, demonstrated by the retirement of the Hyphen bridge and the shift away from the original relayer model
• Competitive pressure, because account abstraction infrastructure is a crowded category and EIP-7702 lowers the barrier for wallets to implement similar features natively
• Dependence on standards still evolving, including the module and delegation specifications the stack builds on

Why Biconomy Matters

Biconomy matters because the friction it targets is the friction that keeps ordinary users out of on-chain applications. Gas tokens, chain selection, and multi-step approvals are not features users want; they are implementation details leaking into the interface. Biconomy has been working on that problem since 2019 and has rebuilt its stack twice to stay aligned with where Ethereum's account abstraction standards actually went, which is a better indicator of durability than any single product launch.

Where Can You Buy Biconomy (BICO)?

BICO is listed on centralized exchanges and trades on decentralized venues on Ethereum and Arbitrum. Availability, pairs, and supported networks vary by exchange and jurisdiction, so confirm which network a platform uses before withdrawing.

Major Centralized Exchanges (CEX)

BICO is often available on:

• Binance
• Coinbase
• KuCoin
• OKX
• Gate

Pairs are commonly quoted against USDT and USD where supported.

Storage Options After Purchase

After purchase, BICO can be stored:

• On an exchange, where the exchange controls the keys
• In any EVM compatible non-custodial wallet
• In a hardware wallet paired with an EVM wallet interface

BICO exists on more than one network. Confirm whether you are handling the Ethereum or the Arbitrum deployment before sending, because withdrawing on the wrong network is a common and usually unrecoverable mistake.

Related Coins

You can compare BICO with related ecosystems on Coinrithm:

• Ethereum (ETH)
• Arbitrum (ARB)
• Optimism (OP)
• LayerZero (ZRO)
• Across Protocol (ACX)