Onchain Transaction Orchestration
Make any transaction gasless and bridgeless in minutes
Orby's onchain transaction orchestration enables wallets, exchanges, platforms, and agents to offer one-click transactions, gas abstraction and chain abstraction. Furthermore, Orby enables all this functionality on dapps.
Orby x One-click Transactions
Token approvals are a relic of poor EVM design. Over the last few years, the ecosystem has made numerous attempts to eliminate them, partly because they represent a significant avenue for hacks. Batch transactions using 7702 are the most recent attempt to eliminate token approvals. However, there is one big issue: dapps need to support smart accounts via EIP-5792 for wallets to enable one-click transactions, and most dapps do not support smart accounts. Even with 7702 enabled, users are still stuck with the "approve token + execute transaction" flow. With Orby, wallets/exchanges/etc can enable one-click transactions and eliminate token approvals regardless of whether dapps support smart accounts or whether 7702 or 4337 is enabled.
Orby x Gas Abstraction
Gas is one of the most significant friction points for crypto users. Worst of all, it appears at the most inconvenient moment, when users attempt to execute a transaction. Unfortunately, just like one-click transactions, dapps need to support smart accounts for users to utilize gas abstraction, even if the account in question is a smart account itself. This poses a considerable barrier since most dApps do not support smart accounts. With Orby, wallets/exchanges/etc can enable gas abstraction for any dApp or onchain interaction. More importantly, this is not limited to smart accounts but extends to EOAs, regardless of whether they are 7702-enabled.
Orby x Chain Abstraction
Orby virtually unifies accounts across one or multiple chains, allowing them to be used as a single entity. Orby handles everything needed for these accounts to work as one, namely:
The virtual unification of the account states and balances across chains.
Communicating unified data/balances to apps to be used for transactions.
Generating and orchestrating the execution of all the operations a set of accounts needs to complete a transaction. This includes gas abstraction for both EOAs and AAs.
Most importantly, Orby requires no changes to existing infrastructure and is forward and backward-compatible. Orby can be added or removed from any wallet, app, or agent in minutes, just as you would a proxy. Furthermore, it works with any account configuration:
It works for EOA wallets regardless of whether they are browser extensions, mobile, or embedded.
It does the same for SCA/AA wallets.
It works if you want to use EIP 7702. It works if you do not want to use EIP 7702.
It works if you want to use pre-confirmation systems, regardless of whether they are token-wrapping-based resource locks, such as Compact or module-based ones.
It works even if you want to merge EOAs and SCAs on the same chain to create hybrid/companion accounts.
Last updated