|
|
||
|
|
I tried to clarify on StackExchange how this vulnerability can be exploited: https://bitcoin.stackexchange.com/questions/96310/hardware-wallet-vulnerability-fix-verifying-input-value/96315#96315 |
|
|
|
admin
1 year ago |
on: Design for a CoinSwap Implementation for Massively Improving Bitcoin Privacy and Fungibility
Discussion in mailing list: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-May/017898.html |
|
|
|
Exploit is fixed in firmware version 5.0.0 |
|
|
|
admin
2 years ago |
on: What the upcoming years might hold in store for bitcoin (a technical outlook by Bitcoin Core contributor John Newbery)
Original twitter thread: https://twitter.com/jfnewbery/status/1208559196465184768 |
|
|
|
Here is a Twitter thread discussing the project: https://twitter.com/StepanSnigirev/status/1208417265789669376 Just be careful! It should probably only be used as an educational resource as is likely to make something go wrong! |
|
|
|
This project was just launched a week ago and we are working hard to cover all major wallets and then automate reevaluation for new releases to catch when a verifiable wallet misses to share code before pushing an update. In the future we will raise the bar further. |
|
|
|
Paper: https://arxiv.org/abs/1905.10518 Recent talk by the paper author (not the Medium article author): https://www.youtube.com/watch?v=ZUWs00Anpaw Transcript of the talk: https://diyhpl.us/wiki/transcripts/london-bitcoin-devs/2019-11-13-gleb-naumenko-p2p-erlay/ |
|
Discussion on the Bitcoin mailing list: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-June/017941.html