Hiring guide
How to choose a BNB Chain development company in 2026
How to choose a BNB Chain development company in 2026: BSC or opBNB, the hard fork schedule through Jenner and what to request in each proposal.

Two quotes for building on BNB Smart Chain (BSC) can describe the same product and leave out different parts of its maintenance. The difference rarely lies in the initial contract, which a team with Solidity experience can write without having worked on the network before, because BSC is EVM-compatible. It appears later, when the network upgrades and someone has to check that the product still works and that its nodes or network access services run the right client version.
This year, the schedule is explicit. BSC scheduled the Osaka/Mendel (April 28) and Pasteur (August 25) hard forks through mandatory client releases, and has set Jenner for December 8, 2026, bringing a compliant asset standard that is still a draft. A useful proposal separates what gets built now from what will need reviewing at each upgrade, and that is the criterion of this guide. Metlabs publishes it and provides BNB Chain development services, so it has a commercial interest in the engagement: that is why it does not compare agencies but describes what a proposal should cover and presents ours against the same criteria. Network information was checked on November 8, 2026 in BNB Chain's documentation and its published client releases.
BNB Smart Chain in 2026: a network that upgrades on a schedule
BNB Chain spans several networks. BSC is the main EVM-compatible chain; opBNB is a layer 2 built on it with the OP Stack; and BNB Beacon Chain, formerly Binance Chain, was shut down for good on November 19, 2024. A BSC proposal does not by itself cover opBNB integration, and one that still describes Beacon Chain as a live network relies on a context that no longer exists. Our BNB Chain technology page explains the architecture of each component.
What sets BSC apart is how often its protocol changes. The BSC client releases show that each hard fork ships in a release that is mandatory for every mainnet node operator, with a fixed date and time: Jenner, the next one, activates on December 8, 2026 at 02:30 UTC. For whoever commissions a product, that cadence turns maintenance into a scheduled task: upgrading or verifying nodes and network access providers, rerunning product tests against the new version and checking whether any change affects its contracts.
Jenner also brings two changes that affect product design. BEP-702 proposes CAS20, an asset and stablecoin standard implemented as a precompiled contract of the network itself, with separate roles to mint, burn, seize balances and pause, and transfer policies based on address lists; token creation is enabled by an administrator appointed through governance, and the document is still listed as a draft. BEP-703, the Payment Lane, reserves 5% of each block's gas by default for eligible BNB transfers and for payment contracts on a governance-managed list. Neither is active today: they are options to assess once activated, not features a provider can promise.
| Hard fork | Activation date | Status at Nov 8, 2026 | What the proposal should cover |
|---|---|---|---|
| Fermi | Jan 14, 2026 | Active | The application's confirmation rule measured against current block times |
| Osaka/Mendel | Apr 28, 2026 | Active | Client version run by the nodes or the network access provider |
| Pasteur | Aug 25, 2026 | Active | Product tests rerun against that version |
| Jenner | Dec 8, 2026, 02:30 UTC | Scheduled in v1.8.2; BEP-702 in draft and BEP-703 | Tests before activation and a written decision on CAS20 and the Payment Lane |
What to check in a BSC offer before signing
The first check is currency. An offer that still describes BNB Beacon Chain as a live network, or that does not distinguish BSC from opBNB, relies on a map of the network that predates November 2024. That alone says nothing about the team's work, but it does require asking in writing which network the proposal covers, which external services it needs and how upgrades will be handled after delivery.
The second is who reviews the code. Having the same provider develop and audit the contracts simplifies coordination, but it is not an independent review when the product holds third-party funds, because the team is reviewing its own design. The proposal can include both functions as long as it keeps them apart and states which contract version is reviewed and who fixes the findings.
The third concerns DeFi products built from a protocol already running on the network. An offer that takes that protocol as a model should clarify who wrote the starting code and under which license it is reused, and which part of the economic model it delivers beyond the software: the parameters, who can change them and what happens if an integration it depends on becomes unavailable.
Metlabs: payments, tokens and business integration on BSC
Metlabs is a blockchain development studio with offices in A Coruña and Madrid, Spain, that develops Solidity contracts for BSC together with the application, backend and reconciliation with the client's systems, for companies that need an onchain payment or issuance reflected in their processes. Our in-house technical team connects product definition, architecture, smart contracts, backend and interface; the proposal identifies the components, people and responsibilities required for the chosen network.

Product decisions and integration scope
At Metlabs, we start with the user journey and the rules the product has to enforce. Our blockchain development service connects functional requirements with contracts, interfaces and integrations, and on BSC it adds an item worth writing down from the outset: what gets reviewed at each hard fork and who reviews it.
A hypothetical example: an e-commerce platform wants to accept stablecoin payments on BSC. Demonstrating a transfer is not enough to accept the work: tests cover the wrong network, a rejected approval, insufficient funds and reconciliation between the contract event and the order. With Jenner scheduled, the proposal adds an explicit decision: whether the payment contract will be designed to qualify for the Payment Lane list once it is active, which depends on BNB Chain governance rather than the provider, or whether the product will work the same without it.
Administrative permissions, repository access, deployment and handover to the maintenance team also need agreement. Where there is an external security review, the scope identifies the contract and version reviewed and who fixes the findings. For a token with minting or pause powers, custody of those keys matters as much as the code.
This approach fits engagements spanning an application and its business systems. A limited change to an existing contract is quoted for that specific scope. To compare our offer, the functional brief and acceptance criteria need to be the same ones the other candidates receive.
What to include in the Metlabs proposal
- A contract and role specification on BSC, separate from any opBNB integration.
- A payment journey linked to the order, with network, asset and amount checks.
- Insufficient balance, rejected approval and reconciliation tests that can be rerun after each hard fork.
- Code handover, deployment procedure, custody of administrative permissions and a review schedule for network upgrades.
The work follows the phases described in our blockchain development service: discovery, architecture and design, iterative development, and validation before release. We agree on the first journey to build and its acceptance criteria at the start, so progress can be checked against a working delivery. External audits, specialist integrations and ongoing support are scoped in the proposal.
To discuss the scope with Metlabs, share the asset or process, its users, existing systems and the operations the first release must support. This gives the team a basis for identifying dependencies and preparing a proposal you can compare with those of other providers.
Scope, delivery and maintenance: what to separate on BSC
The comparison works when every candidate receives the same use case and separates initial development, maintenance and recurring services. Price differences only become meaningful once deliverables and exclusions are written down, and our general guide to choosing a blockchain development company adds how to assess the team that signs them.
- Network and dependencies: BSC, opBNB or another ecosystem network, assets used and external services required.
- Permissions and handover: key custody, administrative powers, repository and deployment procedure.
- Acceptance: user operations and failure scenarios passed by contracts, interface and backend together.
- Network upgrades: who follows BSC client releases, how hard forks are tested and what happens if one affects the contracts.
What decides a BNB Chain proposal: who follows the hard forks after delivery
Contracts and applications are common ground for any BSC offer, because EVM compatibility lets a team with Solidity experience write the code without having worked on the network before. The difference with the largest effect on total cost appears after launch. With four hard forks in 2026 (Fermi in January, Osaka/Mendel in April and Pasteur in August, already active, and Jenner scheduled for December), a BSC product needs someone who reads each release, decides whether it affects its contracts or infrastructure and reruns the tests before the activation date.
That follow-up cannot be assumed unless it is written down with an owner and a scope; in the Metlabs proposal it is an explicit deliverable, and it is the first thing to look for in any other. The same applies to CAS20 and the Payment Lane: a quote that builds them in before activation is selling a hypothesis, and one that ignores them leaves the client without a plan for when they arrive.
On BNB Chain, the date of the next hard fork makes a good test: a serious quote says what the team will do with the product on December 8 and at the upgrade after that.
Frequently asked questions
Got a blockchain project in mind?
From idea to product, strategy and technology must move forward together.




