Live data from Hacker News

A from-scratch tour of Bitcoin in Python

karpathy.github.io

221–230 of 293 posts

Re: A from-scratch tour of Bitcoin in Python

#221
post #25

Earlier quoted context omitted.

I wish this were talked about more. Quantum computing is the biggest long-term threat to crypto imo. What's the plan once elliptic curve cryptography can be broken? There will be a point in time where there are just a few quantum computers that can break everything before the general public has access to quantum computing. Can crypto work in that scenario? Normal computers wouldn't be able to work with the beastly al…

There's a lot of research and practical work on quantum-proof cryptography which is already in use in some cryptocurrencies - 'just' need to hardfork and update it when it's ready for Bitcoin

No need for a hard fork. A soft fork like Taproot is doing this year would be sufficient.

Re: A from-scratch tour of Bitcoin in Python

#223
post #189
post #106

Earlier quoted context omitted.

Daily reminder that cryptocurrencies are not == bitcoin All the problems with bitcoin are long long solved just not with bitcoin because its not possible to fix something when the majority (of hashpower) thinks its not broken or rather profit form its brokenness. FBA coins exists since 2013 or so.

> Daily reminder that cryptocurrencies are not == bitcoin This is an interesting feature of cryptocurrencies. Someone levels a fair criticism of a particular implementation but it can be handwaved away because an entirely separate cryptocurrency solved this particular problem (nevermind that whatever replacement you’ve chosen has its own host of separate problems because those can be handwaved away the same way).

I did not hand wave anything away, maybe read the thread. There was a wrong generalization (cryptocurrencies == bitcoin) about cryptocurrencies that is very common but not accurate at all. Fair criticism on the Ford Model T does not apply to cars.

Re: A from-scratch tour of Bitcoin in Python

#225
post #162

Earlier quoted context omitted.

The looking up of liquidity is the whole reason LN can not scale or be cheap ever. Today people in crypto may be willing to look up bitcoins they hold long term anyway. But in the real world this would be dead and trapped capital it doesn't work for you and you cant even use it to quickly buy something an take advantage of a market situation. The only reason why someone would look up capital like that if is it makes…

If I decide I want to be long BTC, why not also lock it up to earn fees?

No one questions that the people who are bullish on BTC are in on it (some). The question is why would I pay you to lend me BTC when I actually want to send my BTC to someone. It literally adds a third party in what should be a p2p transaction. They replaced the "evil third parties" called banks with their own liquidity pool.

Funny how they figured out that you cant make money with money services if you remove the third party, so they added it back in.

On top of that there are countless other blockchains/DLT that have cheap transactions on the first layer. Cheap as in fractions of a cent. To compete with that you would need to lock your BTC for free but then you still have the on chain transaction that LN needs sometimes that cost way too much.

Re: A from-scratch tour of Bitcoin in Python

#226
post #208

This is reminds me of Ken Shirriff's 2014 "Bitcoins the Hard Way" blog post that also used Python to build a Bitcoin transaction from scratch: http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bi... (The subtitle of the blog is "Computer history, restoring vintage computers, IC reverse engineering, and whatever" and it is full of fascinating articles, several of which have been featured here on HN)

Thanks for the nice mention of my blog. I was wondering if anyone remembered my old bitcoin article :-)

It's a classic. You will be forever remembered for your timeless contributions to the collective consciousness!

Re: A from-scratch tour of Bitcoin in Python

#227
post #208

This is reminds me of Ken Shirriff's 2014 "Bitcoins the Hard Way" blog post that also used Python to build a Bitcoin transaction from scratch: http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bi... (The subtitle of the blog is "Computer history, restoring vintage computers, IC reverse engineering, and whatever" and it is full of fascinating articles, several of which have been featured here on HN)

Thanks for the nice mention of my blog. I was wondering if anyone remembered my old bitcoin article :-)

The retro-computing stuff I see you guys doing on CuriousMarc's youtube channel blows my mind.

Re: A from-scratch tour of Bitcoin in Python

#228
post #176

Earlier quoted context omitted.

Would you include environmental impact as a solved problem? My understanding is that Proof of Stake is the best serious option and that it's very controversial if it'll work.

Proof of stake lacks the security properties of proof of work, e.g. via grinding attacks.

Grinding attacks aren't a problem if you include secure verifiable randomness in the protocol. E.g., Algorand's VRF-based sortition, or Ethereum 2.0's verifiable delay function.

Re: A from-scratch tour of Bitcoin in Python

#230
post #115

Earlier quoted context omitted.

There has been great progress in scaling the original protocol through the Bitcoin SV implementation: - Transaction fees are ~$0.0001 - The network has shown capacity for 50k tps - On March 14, 2021, the network processed a world record 638 MB block - As of June 4, 2021 the chain size exceeded that of the BTC implementation and is currently 418.17 GB - New business based on micropayments have emerged like twetch, str…

Everyone knows faketoshi is a fraud.

For anyone interested in the saga, Stefan Matthews, who worked with Craig Wright in 2007 and 2008 before Bitcoin was released, gave a couple interviews this past week adding new flavor to the story [1] [2].

[1] https://www.youtube.com/watch?v=k3ACmnUwsZ4

[2] https://www.youtube.com/watch?v=R03ypV9CsTc

Post reply on HN