Binaconomy is a gas abstraction stack for BNB Chain. It helps applications create smart accounts, sponsor gas for approved actions, and manage that flow through a backend, web app, SDK, and CLI.
The default local stack is pre-submission: it deploys contracts and exercises auth/credits, but it only performs a real eth_sendUserOperation flow when a bundler is configured.
New wallets need gas before they can do anything. That creates onboarding friction, forces manual funding, and makes automation harder.
Binaconomy provides:
- deterministic smart-account creation
- backend-managed gas credits
- voucher-based paymaster sponsorship
- a shared flow exposed through the web app, SDK, and CLI
- onboard a new user without asking them to hold BNB first
- sponsor a limited wallet action, such as a first swap, claim, or account setup step
- let an operator team manage credits, approvals, and operation visibility from one place
- allow scripts and AI agents to trigger the same flow through the SDK or CLI
- Web app: the reference product UI for sign-in, wallets, credits, and activity
- SDK: the main TypeScript integration surface for apps, services, and AI agents
- CLI: a simple command-line interface for operators, scripts, and autonomous agents
The SDK and CLI exist so external tools, bots, and AI agents can use Binaconomy without driving the web UI.
flowchart LR
WEB["Web App"] --> SDK["SDK"]
CLI["CLI"] --> SDK
SDK --> API["Backend API"]
API --> DB["Drizzle + Postgres/Neon"]
SDK --> BUNDLER["Bundler"]
BUNDLER --> ENTRY["EntryPoint"]
ENTRY --> ACCOUNT["Smart Account"]
ENTRY --> PAYMASTER["Paymaster"]
ACCOUNT --> TARGET["Target Contract"]
More detail: System Architecture
See User Flow for the step-by-step path from wallet authentication to sponsored execution and audit review.
flowchart LR
A["Sign with Wallet"] --> B["Get Session"]
B --> C["Add / Check Credits"]
C --> D["Request Voucher"]
D --> E["Build UserOperation"]
E --> F["Submit on BNB Chain"]
F --> G["Review Status"]
See Dependencies.
| Contract | Address |
|---|---|
| EntryPoint (v0.7) | 0x0000000071727De22E5E9d8BAf0edAc6f37da032 |
| CreditToken | 0x2B63fbd13eb84D8F531c0431f1436A76Ac8ce370 |
| Paymaster | 0xC31cEdB849d0955221A4811E39b7fb39f941E9AB |
| Smart Account Factory | 0x9d3e8C914C077813cAA818EdC164B43fd5Ad5819 |
| CreditSale | 0x3a8ce47526b3733bf32AA0f7B20c279dE79D31Fb |
See Roadmap.
- Use issues for bugs, architecture questions, and feature requests.
- Use pull requests with a clear change summary, test evidence, and impacted package list.
- For contract changes, include
forge testoutput and call out any security-sensitive behavior changes.