Zooko, this thread has turned into a question of if we should ever get rid of Taddrs. We all agree a lot of things need to happen for that to work.
So to assume good faith, can you answer this question ?
Zooko, this thread has turned into a question of if we should ever get rid of Taddrs. We all agree a lot of things need to happen for that to work.
So to assume good faith, can you answer this question ?
Yes, nobody (afaik) (who wants Zcash to genuinely succeed) wants to remove t-addr now, only when all the shielded tech & support is ready & we (Zcash) have (dev) funds to do that.
Something else Iâve observed, in addition to âbuilding is more effective at resolving how-to-proceed than arguing isâ:
âTrying it out is a more effective way to learn than arguing about it isâ
Iâve seen that people really have a different feeling and different understanding â a much more positive feeling and a much more accurate understanding â when theyâve tried tossing some ZEC around using ZecWallet Lite, Nighthawk, or Unstoppable. Donate to EFFâs taddress! Or donate to their zaddress! Post on ZECpages! Private message your friends! Buy stuff from PayWithZ.cash! Look at your transactions on blockchair.com. It really helps.
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Weâre not learning the lessons of digicash
Oh no! I didnât mean that I thought you were arguing in bad faith!
I meant that I could see why Ian might get frustrated and think you were, because from his point of view he can see a way to add transparency on top of a private default.
But I totally agree with you that thereâs a difference between having a dead-easy way to do this that everyone who understands Bitcoin immediately understands, and having Zcash-specific ways to do it. Weâve been doing stuff like messaging and username registration in Zbay with viewing keys and it is no picnic! So I totally agree with the following point!
And @secparam, just to give one super concrete example of this, if you have an address on a public ledger you can look it up on any block explorerâpiece of cake. But if you have a viewing key, if that particular block explorer hasnât seen that viewing key before, it has to rescan the whole chain to tell you whatâs happened at that address! I mean, one can definitely conceive of infrastructure that would do lots of this scalabley someday, and UX to explain to the first user why theyâre waiting an unusual amount of time, but like, itâs not the same as just looking something up on a public ledger that has already been indexed, you know?
There is someone on Twitter who think we should get rid of t-addr in the next NU. But yeah, until now thatâs the only one I know who wants to get rid of t-addr as soon as possible.
I think it has become clearer to me now that t-addr is here to stay. Can we get rid of it someday? Probably not on the chain called Zcash
.
Thanks @zooko and everyone. I will stay away from the this forum for a while.
The next thing that I will do in relation to ZEC
is to make sure WZEC and RenZEC on Ethereum can start to be useful.
We need a solution for existing shielded transactions anyway! hopefully Nighthawk delivers this as well.
So sad to see another member exit! I was on the verge of it. Not sure how Zcash will survive without enthusiastic members!
Per @secparam DM
Maybe ECC/ZF can make relentless efforts to write to and work with exchanges to implement Z-address setups and make it the default deposit/withdraw method.
So many small-cap projects have actually taken that relentless approach and got their unique token listed with deposit & withdraws. All Zcash team needs to do is to make exchanges use Z-addrs and ultimately the users will catch up!
I think the argument is that the Ren bridge bringing zec to ethereum wouldnât exist right now without t2t transactions. Right now you can store your zec in the shielded pool, de shield and take you zec over to all sorts of defi things on ethereum, and then go back to the zec shielded pool. You can do all this with pretty good privacy even though the ren bridge uses t2t transactions to unlock your zec.
Would you really want to get rid of t2t transactions even at the cost of losing applications like the ren bridge?
REN canât accept transfers from shielded ZEC? IIUC, WZEC accepts shielded ZEC.
Just like how ECC worked with Gemini to support shielded withdrawals, some work needs to be done, so users can still get RENZEC without t2t. There is large downside of acquiring potential users vs keeping t2t for the sake of one dependency which can be mitigated.
Status quo needs to change. Dependencies need to be upgraded. This is common with any service that will be deprecated for greater good & better service.
Yes, but you can use ren right now because Zcash has t addresses. Ren doesnât currently support monero and I doubt it would have supported Zcash if we had already rushed to remove t addresses.
T addresses make it very easy for developers to support Zcash ASAP with little extra effort. This is a network effect we inherited from Bitcoin. We shouldnât throw it away, at great potential cost, and often no gained privacy benefits.
The losses of throwing away t addresses are very real. The supposed privacy gains are dubious. Iâm very skeptical about doing all this in the name of a âculture resetâ proposal.
It can accept zec z2t like any other service. there is a t2t transaction when you remove your zec from ren.
Edit: the key point is that you can use ren right now with good privacy even though their service currently uses a t2t tx. As long as you immediately send the zec you receive into the shielded pool.
Canât you do t2z? from Ren @aristarchus
Itâs not for privacy gains. I thought that was clear. It is to reset perception.
ETH ecosystem with smart contracts seem way more complex than integrating with shielded ZEC. Then we should make it trivial for developers to improve integration process.
Yes, you can use RenZEC by sending from your stash of ZEC stored in the z-pool to Renâs t-address. That means nobody can see from the blockchain where your ZEC came from or what else it is linked to, but that you can use Renâs functionality that theyâve already implemented and deployed using t-addresses. Itâs the best of both worlds.
It is basically impossible for anyone to add ZEC support into their new product without thereby adding utility and options and value to shielded-pool-users, and shielded pool users can use that added utility without revealing where their ZEC came from or what other transactions their ZEC is linked to. Few understand this. Am I memeâing right ?
So we remove t addresses, even though there may be no benefit, and high potential costs, so that uninformed potential users think we made a real improvement? I must be misunderstanding
Edit: this is about the âreset perceptionâ comment by @dontbeevil