# build a dApp on BNB Smart Chain (BSC)

- Chain-scoped: bsc (https://composewith.eth/chains/bsc)

> BNB Smart Chain is a high-throughput, low-fee EVM L1 with deep retail distribution. The credible building blocks are the chain-agnostic infrastructure that has verified BSC deployments — account abstraction, oracles, indexing, multisig, and automation — composed the same way as on any EVM chain.

## Recommended stack

- **Biconomy** (transactions_and_paymasters) — readiness 79/100, difficulty medium — Smart accounts, bundlers, and paymasters on BSC for gasless onboarding so users don't need BNB to start.
- **Pyth Network** (oracle_and_price_data) — readiness 82/100, difficulty medium — Pull-based price feeds are live on BNB Chain for DeFi, perps, and pricing logic.
- **The Graph** (indexing_and_data) — readiness 80/100, difficulty medium — Index BSC contract events with subgraphs instead of hand-rolling an indexer; BNB Mainnet is supported.
- **Safe** (supporting_protocol) — readiness 80/100, difficulty low — Multisig treasury and admin controls for protocol operations on BSC.
- **Gelato** (automation) — readiness 79/100, difficulty medium — Scheduled and event-driven execution (keepers, limit orders) on BNB Chain.

## Considered and excluded

- ens — ENS naming is Ethereum-mainnet centric and is not a native BSC identity layer; resolve names cross-chain only if you specifically need ENS.

## Risks

- BSC's security and decentralization assumptions differ from Ethereum and major L2s; weigh this for high-value or trust-minimized use cases.
- Liquidity and tooling skew toward BSC-native protocols (e.g. PancakeSwap); a protocol being EVM-compatible does not guarantee a live BSC deployment, so verify contract addresses per chain.

## Next steps

- Point your deployment and RPC at BNB Smart Chain (chain id 56) and confirm each dependency's BSC contract addresses.
- Wire gasless onboarding with a BSC paymaster so first-time users transact without holding BNB.
- Index the contracts you ship with a BSC subgraph before building dashboards or activity feeds.

## What the agent receives

```json
{
  "intent": "I want to build and ship an app on BNB Smart Chain (BSC)",
  "matched_intent": "build-on-bnb-smart-chain",
  "recommended_stack": [
    {
      "slug": "biconomy",
      "name": "Biconomy",
      "role": "transactions_and_paymasters",
      "readiness_score": 79,
      "integration_difficulty": "medium",
      "reason": "Smart accounts, bundlers, and paymasters on BSC for gasless onboarding so users don't need BNB to start."
    },
    {
      "slug": "pyth",
      "name": "Pyth Network",
      "role": "oracle_and_price_data",
      "readiness_score": 82,
      "integration_difficulty": "medium",
      "reason": "Pull-based price feeds are live on BNB Chain for DeFi, perps, and pricing logic."
    },
    {
      "slug": "the-graph",
      "name": "The Graph",
      "role": "indexing_and_data",
      "readiness_score": 80,
      "integration_difficulty": "medium",
      "reason": "Index BSC contract events with subgraphs instead of hand-rolling an indexer; BNB Mainnet is supported."
    },
    {
      "slug": "safe",
      "name": "Safe",
      "role": "supporting_protocol",
      "readiness_score": 80,
      "integration_difficulty": "low",
      "reason": "Multisig treasury and admin controls for protocol operations on BSC."
    },
    {
      "slug": "gelato",
      "name": "Gelato",
      "role": "automation",
      "readiness_score": 79,
      "integration_difficulty": "medium",
      "reason": "Scheduled and event-driven execution (keepers, limit orders) on BNB Chain."
    }
  ],
  "excluded_candidates": [
    {
      "slug": "ens",
      "reason": "ENS naming is Ethereum-mainnet centric and is not a native BSC identity layer; resolve names cross-chain only if you specifically need ENS."
    }
  ],
  "risks": [
    "BSC's security and decentralization assumptions differ from Ethereum and major L2s; weigh this for high-value or trust-minimized use cases.",
    "Liquidity and tooling skew toward BSC-native protocols (e.g. PancakeSwap); a protocol being EVM-compatible does not guarantee a live BSC deployment, so verify contract addresses per chain."
  ],
  "next_steps": [
    "Point your deployment and RPC at BNB Smart Chain (chain id 56) and confirm each dependency's BSC contract addresses.",
    "Wire gasless onboarding with a BSC paymaster so first-time users transact without holding BNB.",
    "Index the contracts you ship with a BSC subgraph before building dashboards or activity feeds."
  ],
  "generated_with": "composewith.eth",
  "registry_version": "2026.06.10-8752c9d"
}
```

---
Canonical: https://composewith.eth/intents/build-on-bnb-smart-chain