Adding the BEP 20 tokens to the opBNB bridge requires your tokens to be verified on both BSC and opBNB. Follow the steps as below.

1. Deploy your token`s smart contract to the BSC(Testnet/Mainnet).
2. Verify your smart contract with BSCScan or BSCTrace explorer.
3. Deploy your L2 contract to the opBNB.
4. Verify your L2 contract with opBNBScan or BSCScan(opBNB).

To ensure compatibility with the BSC network, the L2 BEP 20 token must adhere to one of two interfaces, which are either the legacy IL2StandardERC20 interface (only if the bridged layer is L2) or the new IOptimismMintableERC20 interface. Both interfaces are available in the @eth-optimism/contracts package, along with a reference implementation of the L2StandardERC20 contract that is based on the OpenZeppelin ERC20 contract.

For example:

// SPDX-License-Identifier: MIT
pragma solidity >=0.5.16 <0.9.0;

import { L2StandardERC20 } from "@eth-optimism/contracts/standards/L2StandardERC20.sol";

contract L2CustomBEP20 is L2StandardERC20 {
constructor(
address _l2Bridge,
address _l1Token
)


L2StandardERC20(_l2Bridge, _l1Token, "USDC on testnet", "USDC")
{
}

function decimals() public pure override returns (uint8) {
   return 18;
}

}

Please make sure your decimal setting of the L2 contract is the same as the L1 contract decimal settings.

Warning: The standard bridge does not support certain ERC-20 configurations:

• Fee on transfer tokens
• Tokens that modify balances without emitting a Transfer event

You need to create a PR to the repo to add your token into the list of our bridged token list, and at the same time upload your token icon to the git repository.

First, append your token information to the list.

Then, create a folder with your token symbol and upload your token icon file. The icon file should be a 48x48 png file with a size no larger than 300kb.

mkdir YOUR_TOKEN_SYMBOL