Zooko Wilcox-O'Hearn [ARCHIVE]

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2012-02-29 to 2016-01-12
💬 Posted a total of 3 messages
📚 Participated in the following categories: Bitcoin-development, bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Public Key

npub198hn0klxaeu622g84p832yd4hglek0h3p9cy8aklkcxv56cr5kwql949yg

Profile Code

nprofile1qqsznmehm0nwu7d99yr6snc4zx6m50um8mcsjuzr7m0mvrx2dvp6t8qprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdg06ce0

Publishing to

relay.noswhere.com

Author Public Key

npub198hn0klxaeu622g84p832yd4hglek0h3p9cy8aklkcxv56cr5kwql949yg

Show more details

Last Notes

2023-06-07 03:09:49

- reply

📅 Original date posted:2012-02-28
📝 Original message:Could you spell out the attack explicitly? Presumably there aren't a
lot of people with the "malice energy" to perform the attack but not
to figure it out for themselves. I, however, have the "niceness
energy" to think about it for a few minutes but not to figure it out
for myself. If in your opinion it is realistically dangerous to post
it publicly, would you be so kind as to include me in the private
sharing of the explanation?
By the way, I found a couple of cases of slightly bad handling of
merkle trees when I inspected the code (v0.4) that was, I'm 99% sure,
not exploitable. I never got around to reporting it yet. I'm sorry
about that. My discoveries might interact with the one you're talking
about here. I should definitely explain mine to y'all soon. (Possibly
in private for the first pass, in case it is more exploitable than I
thought, or has become exploitable since v0.4.)
I showed it to a couple of other people at the time who helped me make
sure that it wasn't exploitable.
I'll make time to explain what I found within a week.
Regards,
Zooko