Awesome. This is great.
2 Likes
any update?
1 Like
I’m working on an update and hope to have it posted tomorrow.
8 Likes
Update: I wanted to provide a few updates and highlight some important information regarding the introduction of TEX Addresses.
-
Kris and Daira have updated ZIP 320 to reflect the TEX Address option. It is currently in draft status, but we anticipate it will be approved by ZIP editors and published by the end of the month.
-
Binance has received a copy of the draft ZIP specification and is in the process of reviewing it.
-
As it currently stands, only Binance will generate TEX Addresses. Other exchanges and third-party wallets need to implement parsing code to ensure smooth interaction with Binance and avoid transaction failures.
-
Pacu and I have started reaching out to wallet developers and exchanges to implement this change. We are starting with wallets that support shielded transactions, including Zingo, NightHawk, Edge, and Unstoppable.
-
As Hanh mentioned above, YWallet has already implemented support for TEX Addresses.
-
ECC will integrate support for TEX Addresses into Zashi. If it’s not included in Zashi 1.0, it will be added in a subsequent release soon after.
-
ECC’s mobile wallet SDKs will also be updated to support TEX Addresses, with the release scheduled by the end of March.
I’ll continue providing periodic updates as things progress and new information becomes available.
22 Likes
So, does it mean that Binance hasn’t approved it yet? There is still a chance that it will be delisted, right?
No, Binance has approved it. They just haven’t done the integration work yet, and the ZIP outlines how to implement the change.
11 Likes
thanks for the update @aquietinvestor
did you get to know when the will remove the “monitoring” tag?
1 Like
Unfortunately, Binance has not provided a timeline for removing the “monitoring” tag. As I understand, they usually update the monitoring list at the end of every quarter. It is likely that the tag will remain until support for TEX addresses is implemented, which will likely occur in the second quarter.
3 Likes
Why did the hanh of YWallet complete support for TEX three weeks ago, but ECC has not been completed yet?
1 Like
Actually TEX support has been added to the zcash_address crate for all clients of rust crates will have access to that feature.
Daira and Kris have been fully involved on the outreach and communications to partners and supporting the task that @aquietinvestor and myself are carrying out.
In terms of ECC SDK’s I guess that’s an @andrea question.
What I can do is repeat information that’s been shared in LCWG. As they have stated in the Light Client Working Group, ECC engineers have been focused on Orchard Support and tasks needed for Zashi’s launch among others. TEX Support APIs are ready for partners to start adopting and a subsequent feature complete release will be release somewhere in April after Zashi is released.
Currently, Binance is not showing TEX addresses to their customers so we are still on track.
15 Likes
@aquietinvestor any updates from binance about the monitoring tag?
2 Likes
Hi @elkouaris. Here’s the latest update I have regarding the monitoring tag:
3 Likes
The Binance has released fresh “Monitoring” adjustments.
A number of assets have been added to it, but they did not exclude anything from the list this quarter. So $ZEC and company are still “under monitoring”:
2 Likes
The answer is that we have been fully immersed in releasing the Zashi wallet. We have everything in place for ZIP 320 support with the exception of properly handling the gap limit for the interstitial transparent addresses in wallet recovery (the single-use-only transparent addresses that are deshielded to before sending to the Binance address.)
The way that the ECC SDK support for ZIP-320 addresses works is that, when you enter a TEX address as the recipient, the wallet automatically creates two linked transactions: one to deshield to an ephemeral transparent address, and a second zero-conf fully transparent transaction that spends the deshielded funds to send them to the eventual recipient.
Handling it this way, and ensuring that the ephemeral address is only ever used once, means that there is no privacy leak greater than what would exist for any normal Z->T transaction. However, since it’s possible for funds to be sent to those ephemeral addresses, the wallet must be able to track them and ensure that they are discovered in wallet recovery. Also, we have to make sure that the rules around creation of those ephemeral addresses are such that they are truly one-time-use only, and that the BIP 44 indices used for their derivation are never reused, even if the user has multiple wallets with the same seed.
13 Likes
Is there still a risk of delisting now？
yes.
2 sort.
There is no imminent risk of Binance delisting Zcash. However, future developments are unpredictable, and new circumstances could potentially influence their decision. Currently, there is no indication that such a change is likely to occur.
8 Likes
any update?
@pacu and I are actively engaging with wallet and exchange partners. We still anticipate the implementation of TEX addresses in the second quarter.
8 Likes
Binance just rejected a deposit from my zashi today. I need help. I lost one zcash . They are giving me 32 days to answer to my appeal. Ridiculous. That’s absurd
3 Likes