Incognito - Binance Smart Chain bridge

A bridge from Binance Smart Chain (BSC for short) to Incognito is one of the most desired features now.

BSC supports bridges to 35 other blockchains, which means that if Incognito has a bridge to BSC, it would have a bridge to those 35 blockchain networks as well. Additionally, people have been bridging their crypto assets to BSC enormously according to BSC’s token tracker in order to experience Defi dApps in a faster and cheaper way as compared to its counterpart (a.k.a Ethereum) so imagine if Incognito offers a method to bring anonymity possibility to 1% of BSC’s users who actually care about privacy, it would be a huge leap of the project in new user acquisition as well as processing volume.

How will the Incognito - BSC bridge solve problems for users?

The current Incognito users benefit from the bridge on cheap and stable shielding / unshielding fees. For example, At the time of writing:

  • A direct shielding from Ethereum to Incognito costs ~$1.66 (gas used by shielding transaction: 41,000, gas price: 15 gwei, eth price: $2,700). The cost is even more expensive for unshielding that would be ~$10.2 (gas used by shielding transaction: 253,000, gas price: 15 gwei, eth price: $2,700).

  • A shielding from BSC to Incognito will only cost ~$0.15 (gas used by shielding transaction: 77,000, gas price: 5 gwei, BNB price: $400), similarly for the unshielding which will cost ~$0.3 (gas used by shielding transaction: 145,000, gas price: 5 gwei, BNB price: $400). Of course, the shielding & unshielding costs will have to include network fees in BNB to convert ETH into wrapped ETH and wrapped ETH back to ETH through Binance’s bridge.

For the new users, the expensive fees would also be a big barrier to onboarding. These users likely want to try out with a small shielding / unshielding to learn how the system works prior to having more confidence with larger ones. So giving those a try through the BSC bridge will help overcome the dilemma.

Also, for BSC’s Defi dApps users who actually care about privacy, the Incognito - BSC bridge is introducing pBSC, an extension of BSC that has a similar approach to the pEthereum but with much cheaper fees. This enables privacy-protecting BSC transactions and privacy-protecting decentralized applications like Pancake Swap or Pancake Bunny.

Typical flow

The following illustrates the flow of coins that happens over public chains, Binance Smart Chain, and Incognito chain.

As illustrated in the typical flow above, to be able to shield coins from public networks like Bitcoin, Ethereum, etc, you need to:

Step 1: convert public coins to wrapped coins on Binance Smart chain first. This could be done through the Binance bridge. Please have a look at Binance bridge user guide in case you aren’t familiar with it.

Step 2: Once having the wrapped coins in your personal wallets (e.g. MetaMask or Trust Wallet), you will be able to shield the wrapped coins to private coins as you used to do with ETH/ERC20 tokens decentralized shielding.

Step 3: You can transfer the shielded wrapped coins privately or swap anonymously over the Incognito network.

Step 4: The unshielding experience for the shielded wrapped coins from Incognito to Binance Smart Chain would be similar to what you’ve done with ETH/ERC20 tokens before.

Step 5: To convert wrapped coins from BSC back to public coins on a public network, you can use Binance bridge again.

Technical designs

Because BSC is EVM-compatible, it launched with support for the rich universe of Ethereum tools and DApps. In theory, this makes it easy for us to port Incognito - Ethereum bridge to Incognito - BSC bridge. It’s just a matter of tweaking a couple of settings and the technical designs for the proposal would be the same as here (the bridge) and here (the pEthereum).

The code will be completely open source for both protocol and wallet app.


Thank you to the team!!! BSC bridge is everything! We will be ahead of the whole planet!
And let’s say goodbye to Vitalik:)

1 Like


Yes yes yes yes yes yes yes.


@duc What do you anticipate the workflow will be like for US-based users?* I believe US users are barred from legally transacting with the Binance Bridge.

*Asking for a ** cough ** friend.

An example – a hypothetical US user could trade pUSDT-ERC20 for pUSDT-BSC on Incognito. However they would not be able to unshield that pUSDT-BSC to the cheaper BSC network. They could certainly trade the pUSDT-BSC for another pAsset they can unshield such as BTC, LTC, XMR, etc. But they could not unshield to the public BSC network.

It is not the intent of this proposal to offer an alternative BSC workflow away from the Binance Bridge.

  • The (US restricted) Binance Bridge is still a critical component of the anticipated shielding/unshielding workflow, correct?

  • A pBSC based token could still be acquired and traded by a US user, as long as that asset stays within the Incognito network? (Or a public BSC network becomes available to US users.)


I don’t get why US users cannot Binance Smart Chain. It is decentralized (ignoring some debates) like Ethereum, EOS, or some other chains. How can they ban BSC apps? Or do they just ban URL of Binance Bridge? Could you give some details?

Since I don’t understand the problem exactly, I may provide a non-sense link but will try :joy: For example, doesn’t the method in solve US citizens’ problem?

Legally? No. Technically? Sure. But the technical howto wasn’t the issue I posed.

Accessing the Binance Bridge is geo-restricted by Binance for US residents (and a few other jurisdictions). Any workflow for a US user which uses the Binance Bridge is not legally compliant. A Google search will yield a number of workarounds for that geo-restriction – successfully circumventing a geo-restriction does not magically make that transaction legally compliant.


I believe it’s important for US residents to understand that accessing the Binance Bridge is a violation of Binance’s TOS. However small, it would not be without some potential risk. It only takes one DNS leak to expose a US IP, and potentially lock an otherwise unrelated – but signed in on the same session – account which momentarily pings from an unmasked, unsupported IP. It’s very unlikely any legally uncompliant user would be at risk for action from a JHA, but in the future – who knows? Some of the more prominent 2017 BCC YT shills are quite recently facing legal consequences.


As I see, Binance thinks BSC may create legal problems for Binance itself and US users. OK but why? I don’t understand this part. Binance can use other domains for BSC but it does not use. Do they think this will not solve the problem? If so, this means that US users cannot use other bridged networks such as Polygon/Matic, xDai but as I know US users can use them. If US users can use them, why can’t they use BSC? Is it just because of pinging some domain names containing “binance” word? I’m a little bit confused :shushing_face:

1 Like

If US residents use the service – no matter the service’s physical location – the service would fall under FinCEN’s jursidiction. This is exactly what tripped up Arthur Hayes & BitMEX. HQing BitMEX in Seychelles does not insulate BitMEX from compliance with US securities regulations when US residents are allowed to use the service.

Binance has banned US residents from the .com exchange so the exchange can operate without having to comply with US securities regulations. Because the Binance Bridge is operated as an extension of the .com exchange (I know the URI is .org but it’s still part of the .com exchange), Binance still does not want US residents using the service. Again this is to limit exposure to potential US oversight on the .com exchange.

The .us exchange is setup and operated 100% independently from the .com exchange so that it can comply with US regulations without affecting the main .com exchange. The name and a few technologies are licensed from to the independent company – BAM – that operates the .us exchange. It is that compliance which limits the type of assets that can be offered to US residents. All of the assets that are available on the .com exchange but not available on the .us exchange are generally assets that do or may fail the Howey test for securities; or tokens are offered as part of an ICO or any number of other reasons that run afoul of US securities, KYC, AML, etc rules.

These are legal limitations. It’s not a technical matter of access. It’s a legal matter of access.


Ok, I understand these but my confusion is on BSC vs other chains. I think I’m stuck language barrier since English is not my native :slight_smile: So let me go through an example. Let’s say that a cross-chain token that fully complies with US laws is created. Different amounts of its supply are on three chains (BSC, Ethereum, Polygon/Matic).

US users can trade/transfer it on ^^^ since it has no owner (i.e. decentralized)

  • Ethereum :white_check_mark:
  • Polygon/Matic :white_check_mark:
  • BSC :no_entry_sign:

If someone or I build another “decentralized” bridge that does not use any Binance entities, will BSC be legal for US users in “my sample case”? If the answer is no, what makes BSC different from the other chains for the token fully complied with US laws?


Correct. It’s not a problem with Binance Smart Chain. It’s a problem with the Binance owned & operated Binance Bridge. US residents can’t use it. US residents can use the BSC network. But not the Binance owned & operated Binance Bridge.


Imma drop this off right here –

Sorry for the late reply and thanks for pointing out the problem. I was searching around for the past few days (I guess you did as well) to figure out an alternative workflow away from Binance bridge…

So the point here is that somehow a US resident can take binance-peg tokens (e.g. wrapped ETH) not through Binance bridge. I think there are two potential solutions (in an example of ETH):

  1. Using Trust Wallet to swap ETH (Ethereum network) -> BNB (Binance chain) -> BNB (BSC) -> Binance-peg Ethereum token (BSC). After that, a US resident can shield the wrapped ETH right from Trust Wallet through the Incognito - BSC bridge to take advantage of cheaper fees. The workflow is the same for unshielding.

  2. Incognito app will offer a seamless way to do all the steps above behind the scene in order to make the UX better but I’m not sure whether Binance bridge has exposed API for the integration or not (need to dive deeper in this). Another thing I don’t quite like about this is that it may make us repeat the centralization workflow that against our direction (decentralization-focused)

What is your thought of Trust Wallet workaround?

Absolutely, there is no restriction within the Incognito network.

The non-VPN workarounds I have found so far are:

  1. Trust Wallet (website)
  2. Binance Chain Wallet (extension, tutorial, academy, YT tutorial)

Both workarounds provide BEP2 <==> BEP20 exchanges without touching the Binance Bridge.

I haven’t tested either method however. I personally have additional roadblocks to acquiring BNB in the first place, lol.

1 Like