Why is my shielding address the same for ETH, DOGE, and ADA?

[kitkat]

I was also under the impression the shielding address changes every few hours but when I checked back in after 12+ hours the address had not changed.

[Mike_Wagner]

Improvement of ETH/ERC20 shielding design

You’ll note that the shielding flow in the app has been updated for better UX and security. In this topic, I’d like to explain the historical shielding process for ETH/ERC20 tokens: what the original design and drawbacks were, the new improvements, and what we’re ultimately working towards. Additionally, we believe that an exploit was carried out last week that took advantage of a user who had a timed out shield request under the original design. This post will provide contextual information ab…

[App v4.7.0] Shielding & Un-Shielding ERC20 & BEP20 PRV

As recently announced, Incognito app users can now withdrawal PRV off the Incognito chain and onto the Ethereum network (ERC20) or Binance Smart Chain (BSC). If you missed the announcement and want to learn how it works check out this link: Let’s learn how to Shield and Un-Shield PRV to/from the Incognito network. Shielding PRV Step 1 - From the app home screen: tap on Assets > Shield my crypto > Search for Privacy (PRV) (see figure 1 - Privacy (PRV) asset selection). [List_Shield_Tokens (1…

Introduction to a trustless non-custodial Bitcoin bridge

Hi everyone, Portal comes back. As mentioned in the previous post, we are building the Incognito’s trustless non-custodial bridge v4 (portal v4), and it’s available on the Testnet environment. We are planning to deploy it on Mainnet in a few days. Portal v4 will replace the centralized bridge for Bitcoin (BTC). In other words, after Portal v4 release, users can shield/unshield Bitcoin through the trustless non-custodial bridge instead of the current centralized bridge. We summarize the improve…

[Shipped] Incognito’s trustless non-custodians bridge V4

Problem: As you know, we finished the design and implementation of Incognito’s trustless bridge for public tokens (BTC and BNB) that allow users to shield public tokens decentralized, aka Portal v2 (with Incognito vault) and Portal v3 (with Ethereum smart contract vault). See detail: [Shipped] Incognito's trustless bridge V3 with Ethereum bond contract However, there are some problems with our current design. First, the logic of the shielding and unshielding processes is quite complicated. S…

[kitkat]

Hey Mike, thanks for your response. If I’m reading this correctly, what I’m experiencing is expected behavior?

[Mike_Wagner]

Yes most (perhaps all?) asset shielding addresses are no longer rotating. They are non-expiring and unique to each Incognito address.

The first goal in the redesign was to move away from temporary dev team controlled intermediary addresses. I do believe a future goal remains to add user controlled OTA to the shielding flow.

[kitkat]

Is it expected for my wallet addresses to be the same for different coins? My assumption is they would be different but I’ve been wrong before. My address was different for BTC but the same for the others I’m using.

[kitkat]

@Jared any ideas as to why the shielding addresses are the same for different coins?

[KingOfCrypto]

This is not a strange occurrence dear @kitkat . That’s how it is in all other exchange even Binance.

The reason I can ascribe to this, is that BCS, Polygon, and others uses a fork of Ethereum Blockchain, so this made the wallet address to be the same. If you’re using MetaMask you will understand this. The caution all of us need is just that we shouldn’t make a mistake of sending fund that is meant for BEP20 to ERC20, just because the address is the same. You will lose the money!

I use the same address on my ERC20, BEP20 and Polygon!