I was looking at neovim's donation footer at the bottom of their site and saw a bitcoin donation address. Thought I'd check how much in donations they've gotten. And I saw this massive 10 Bitcoin donation from back in…
Thought I'd check how much in donations they've gotten. And I saw this massive 10 Bitcoin donation from back in 2023 (worth $800,000 now...)
From the activity history, neovim last sent bitcoin out of the address in 2019 so it's been max 7 years since they've definitely had access.
Does anyone from the neovim project know about this? Seems like a pretty significant amount of funding to have sitting there. Hope it can come to good use as I use neovim daily.
https://www.blockchain.com/explorer/addresses/btc/1Evu6wPrzjsjrNPdCYbHy3HT6ry2EzXFyQ
277 comments
That extrapolation is missing the 1000s (thousands) of commits + person-years of work spent on maturing vim.lsp since those few weeks.
Hope to see you around again norcalli.
I'm slowly starting to come out of my shell again.
I wonder how people at large crypto exchanges handle that. Perhaps shamir share the access to the pkey password and store parts at secure places like a bank? And make official access protocol akin to dnssec, but simplified?
We explored using smart contracts to have logic perform the 3/5 consensus rather than a cryptosystem, but that was never rolled out while I was there. Social recovery wallets in general did not take off, which was a big learning moment for me that very few people actually cared about the technology and what they really wanted was an app with as many gambling features as possible that uploaded their keys to google drive.
People who are not HN-profile never care about the technology, and always care about usable, convenient features. The shocker is: most HN-profile people feel the same way.
Also see: https://m.xkcd.com/2501/
The difference is that with Shamir you have to reconstruct the private key in one place before you can sign. With threshold signatures multiple servers can collaboratively sign without ever reconstructing the private key in a single place.
For chains like Solana, Aptos, SUI that use ed25519 (schnorr signature), there's a pretty clean solution called FROST.
For Bitcoin and Ethereum/EVMs that use ECDSA it's a bit trickier but there's been a lot of research recently, so there are solutions.
(At the moment, there's a smallest fraction you can send on the network, but they can change that.)
Bitcoin addresses encode the ripemd160 hash of the public key, so by default when payments are made to new addresses they are not quantum crackable.
But when someone spends from an address they publish the public key to the chain as part of the spend. From then on, any new deposits sent to the same address are at risk of quantum attack
part of me feels like this is most likely a defunct wallet and nobody involved with the project has the keys anymore
Read the full thread on Hacker News →
Related stories
- Hacker News · 3 points · 3 days ago
- Launch HN: Vespper (YC F24) – SOTA Docx MCPvespper.comHacker News · 31 points · 2 days ago
- Show HN: NetWasm – Independent .NET Compiler/Runtime (82.5 KB Hello World in C#)playground.netwasm.comHacker News · 5 points · 1 day ago
- Hacker News · 1 points · 8 days ago
- Hacker News · 15 points · 13 days ago
- Hacker News · 1 points · 4 days ago