Andrew Arnott 🛡️ retweetledi
We're excited to announce a machine-checked proof, written in Lean, that Zcash's new Ironwood pool cannot contain undetectable counterfeiting bugs.
tachyon.z.cash/blog/ironwood-…
English
Andrew Arnott 🛡️
7.9K posts
Andrew Arnott 🛡️
@aarnott
Principal Software Engineer. This is not my employer's account. I have a wonderful family and faith in a real, bona-fide Heavenly Father. Will work for Zcash.
Longmont, CO Katılım Mayıs 2008
149 Takip Edilen1.7K Takipçiler
Andrew Arnott 🛡️ retweetledi
BREAKING: Ironwood is live on Zcash mainnet.
Provable supply integrity, quantum recoverability, and formal verification. Zcash is evolving.
English
@LH_exe Oooh. I wonder how long you had to wait for ZEC show show a 24h trendline like that. I bet you've been waiting months for that. Congratulations.
English
@DavidLBurkhead I notice you only included the image of her post. Did you perhaps do that so that likes and retweets accrue exclusively to you instead of its author?
For folks who want to Like the original, here it is: x.com/Sassafrass_84/…
Sassafrass84@Sassafrass_84
Just a psa: You came here screaming “they’ll kill me if I go back!” Ok. You can stay and seek asylum. The asylum ends the second you send cash back, wave their flag, or book a vacation to the “death trap”you escaped. Pick a lane. We’re not running a hotel for frauds.
English
It just occurred to me: in the Zcash Ironwood migration, you can't necessarily do it piecemeal. If you have 10 ZEC in just 1 note, you have to send it all to Ironwood at once, since you can't create new Orchard notes. So your ZEC balance amount will leak. That's all that will leak -- no name, no address. But the public can see that 10 ZEC migrated in one transaction between pools. Zcash usually shields the amount, but moving between pools like this leaks that information. It can't be tied to you, unless the lightwallet server you use captures your IP address when you send (or read) the transaction.
Ideally then, our wallets would allow breaking up notes into random amounts before Ironwood hits. Kinda late for that now though. :(
Short of that, like @zooko said in his excellent right up x.com/zooko/status/2…, be sure you use an anonymizing VPN when you migrate.
zooko🛡🦓🦓🦓 ⓩ@zooko
Recommendations for Zcashers for the Ironwood era, which begins tomorrow: 1. Don’t rush to migrate your funds out of Orchard right away—take your time. Know what you’re going to do before you start. ⤵️
English
Oh, so many questions with that Zodl article. It even claims that you don't have to move from Orchard to Ironwood right away, and that the wallet will let you make payments to others, and only the amount of that payment will leak as it crosses into Ironwood.
I'd really like to know how that reconciles with Orchard being sealed and therefore the inability to keep change in the same pool.
Also, I heard that Orchard 'actions' were indistinguishable whether they nullified a note or created a new one. How then, can Orchard be sealed from receiving a payment but be open to making payments? Is it really that orchard-to-orchard works fine even after Ironwood network activation?
English
Per support.zodl.com/article/42-mov… there's supposedly going to be a way to move partial balances across. But I just don't see how that's possible given Orchard will be closed to receiving all payments (which is how 'change' works).
English
Andrew Arnott 🛡️ retweetledi
For most members, Sam's Club opens at 9:00 a.m. every day of the week, including Sundays. Plus members receive exclusive early access starting at 8:00 a.m. each day. So Sam's does the exact same thing that Costco does.
English
So @Costco - my wife was just turned away from your store because she wasn’t a premium customer - and told she would have to return an hour later. She had no idea that there was premium member only shopping time.
After talking to two different people, explaining that this is our daughter’s wedding weekend - and that she wouldn’t have time to come back after 10am - they finally let her in.
The customer service agent scolded her on her way in - “next time you won’t be allowed in.”
My wife’s thought? “Next time I’ll go to @SamsClub”
English
Will the Zodl wallet offer a privacy-supporting migration of funds from orchard to ironwood? I'm thinking of automated moves of random amounts at random times. #zcash
English
Along with locking in daylight savings permanently, the bill from congress also does away with time zones entirely. The whole U.S. will finally be in the same time zone.
To find out what happens to your time zone after the transition, visit stardatecalculator.com.
Oh, and just to simplify crossing of the international date line, the bill also fixes the date. And I do mean fixed. Once passed, it will always be April 1.
English
Not really, no. That article focuses on how the turnstile will reveal/limit any damage already done in Orchard. It doesn't talk about any new capability within Ironwood itself to make the supply provable.
From the article:
"Ironwood restores users' ability to independently verify that the protocol's supply limits are being enforced"
That's an interesting wording choice, because users have never had the ability to independently verify supply limits were being enforced. That's been a criticism for Zcash for years, vs. other privacy coins that have less privacy but are allegedly auditable. So to say Ironwood restores an ability that was never there before is odd.
Your article also mentions that a lot of code inspection by humans and AI has been done. This is great. But it's not a proof.
@ebfull's response x.com/ebfull/status/… is more directly responding to my concern, in that he claims a new "specific kind of proof that undetectable counterfeiting vulns cannot exist inside of the new Ironwood pool, ... we can see that it was exploited once a bug is later discovered."
That sounds more interesting and I'd like to learn more about that, since it's the only allusion to it I've seen anywhere.
Sean Bowe@ebfull
Ironwood provides a specific kind of proof that undetectable counterfeiting vulns cannot exist inside of the new Ironwood pool, except if a cryptographic assumption or heuristic were violated. As long as the assumptions hold, then what remains must be detectable (aka we can see that it was exploited once a bug is later discovered.) We cannot make that claim about the Orchard pool, precisely because this was *not* true about that pool in the past. Ironwood helps enormously with that though. It's already unrealistic that counterfeiting occurred, but even if it had and the attacker stashed their coins behind the turnstile, Ironwood prohibits payments within the old pool. It forces hypothetical counterfeiters to leave it, because otherwise they can't do anything with their fraudulent coins. For one thing, that should accelerate the timeline for retrieving evidence of counterfeiting even further. It also shows that we are not uncomfortable smoking out a possible counterfeiter. Bring it on! Let's empty the pool as fast as possible and prove to everyone that either the counterfeiter doesn't exist, or is the biggest moron on the planet. I think @zooko's post does a better job of explaining this though.
English
@aarnott @ebfull Please see this and let me know if it answers those questions or not: x.com/zooko/status/2…
zooko🛡🦓🦓🦓 ⓩ@zooko
English
Ironwood goes live in ten days.
The possibility of counterfeiting bugs in our project has kept me awake at night. No more. Mathematical proof that undetectable counterfeiting bugs don't exist in Ironwood changes how even *I* feel about Zcash, as a protocol dev of ~10 years.
Zakura@ZakuraZcash
Ironwood goes live in 10 days. The Great Ironwood Migration achieves three goals: - Provide a credibly sound shielded pool - Give evidence no counterfeiting occurred in Orchard - Re-establish the circulating supply of ZEC. Here's what you need to know... 🧵
English
Andrew Arnott 🛡️ retweetledi
Ironwood Ironwood Ironwood!
Humanity is going to have a form of money that is unstoppable, private, and has full correctness proofs (formal verification) of some of its key properties, thanks to heroic math by an awesome team led by @TachyonZcash.
English
I just used Grok Build to create an Eternal Terminal client for Windows, written in rust, in under 15 minutes. The first try failed to connect. Grok fixed it with just one more 'turn' and it works now. Amazing.
English
