Re:What Bitcoin’s White Paper Got Right, Wrong and What We S...
by kylebenzle on Saturday October 31, 2020 @11:37AM
(#24952273)
Bitcoin Cash is what we call Bitcoin now. Lighting is obvious vaporware nonsense that solves only the problem of how to keep Blockstream in control of the GitHub repo they (Adam Back and Greg Maxwell) hijacked years ago.
Re:What Bitcoin’s White Paper Got Right, Wrong and What We S...
by petertodd on Saturday October 31, 2020 @11:44AM
(#24952340)
If you want to try Lightning out - and see for yourself whether or not it is vaporware - the easiest way to do that is to get a mobile Lightning wallet such as Eclair (fairly easy) or BlueWallet (easiest) from your appstore. As I mentioned, ManyVids accepts Lightning payments for a real product, as does https://www.bitrefill.com/ (phone refills, gift cards, etc). For testing with smaller amounts, https://yalls.org/ will let you buy access to blog posts for trivial amounts of money (eg one cent).
Re:What Bitcoin’s White Paper Got Right, Wrong and What We S...
by martinko on Saturday October 31, 2020 @11:52AM
(#24952431)
> Bitcoin Cash is what we call Bitcoin now
Really? The market begs to differ.
Re:What Bitcoin’s White Paper Got Right, Wrong and What We S...
by nighthawk24 on Sunday November 01, 2020 @01:40AM
(#24957634)
BTC limitation of SegWit/LN stole the Bitcoin brand name and the decade long Plan-B narrative from BCH's block upgrade, Schnorr signature, 0-conf(without Replace-By-Fee).
Bitcoin Cash market cap of ~$4.8B is good enough for it to be used as P2P Electronic Cash System that Bitcoin was built for.
Another example is how many porn sites and filesharing sites are also accepting Bitcoin. Eg ManyVids allows you to pay with Bitcoin via Lighting, which transfers the BTC almost instantly for quite low fees. There's obvious privacy advantages to that over credit card payments.
A non-monetary use-case is my OpenTimestamps protocol, which I was able to recently use to prove a specific DKIM key was used in the past: https://twitter.com/peterktodd/status/1322270551898030082
Though that use-case really just piggy-backs on the financial use-cases - if not for them OpenTimestamps in its current form would not be secure.