Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 2/6 - By mid-2011, Mt. Gox handled most global Bitcoin trades and the community had been debating whether an exchange could exist without a central point of failure. Dark Exchange was one developer's attempt to ship what had only been discussed.
R to @daily_btc_lore: 2/6 - By mid-2011, Mt. Gox handled most global Bitcoin trades and the community had been debating whether an exchange could exist without a central point of failure. Dark Exchange was one developer's attempt to ship what had only been discussed.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 3/6 - On July 5, morpheus posted Dark Exchange to Bitcointalk (http://bitcointalk.org/index.php?topic=26063.0). No central server, trades routed through I2P, open source on GitHub. "No more worrying about exchange websites going down or locking your account." The code actually ran.
R to @daily_btc_lore: 3/6 - On July 5, morpheus posted Dark Exchange to Bitcointalk (http://bitcointalk.org/index.php?topic=26063.0). No central server, trades routed through I2P, open source on GitHub. "No more worrying about exchange websites going down or locking your account." The code actually ran.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 4/6 - What it couldn't do: settle trustlessly. Someone had to send first. Dark Exchange coordinated the handshake: users clicked "Payment Sent" and "Payment Received", but counterparty risk fell on whoever moved first. The fix had a name: atomic swaps. They didn't exist yet.
R to @daily_btc_lore: 4/6 - What it couldn't do: settle trustlessly. Someone had to send first. Dark Exchange coordinated the handshake: users clicked "Payment Sent" and "Payment Received", but counterparty risk fell on whoever moved first. The fix had a name: atomic swaps. They didn't exist yet.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 5/6 - At launch, early users reported the network had few peers and hit a Java cryptography bug within hours. Memory usage was steep. Orders vanished when you closed the app. The project drew ongoing discussion through 2012 but was effectively dormant by 2013.
R to @daily_btc_lore: 5/6 - At launch, early users reported the network had few peers and hit a Java cryptography bug within hours. Memory usage was steep. Orders vanished when you closed the app. The project drew ongoing discussion through 2012 but was effectively dormant by 2013.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 6/6 - Bisq launched in 2014 as the first serious Bitcoin DEX. Tier Nolan described atomic swaps on Bitcointalk in May 2013; working implementations came in 2017. Dark Exchange was a correctly framed problem in code, two years before the concept that could solve it had a name.
R to @daily_btc_lore: 6/6 - Bisq launched in 2014 as the first serious Bitcoin DEX. Tier Nolan described atomic swaps on Bitcointalk in May 2013; working implementations came in 2017. Dark Exchange was a correctly framed problem in code, two years before the concept that could solve it had a name.
Release notes from BlitzWallet:
Android-v0.7.13-pre2
Android-v0.7.13-pre2
GitHub
Release Android-v0.7.13-pre2 · BlitzWallet/BlitzWallet
Improvements
Update mobile money providers' names
Load fiat currency on half modal, not page
Add Branta merchant logo and name to tx receipt page
Bug Fixes
Fixed maplist style
Fixed USD valu...
Update mobile money providers' names
Load fiat currency on half modal, not page
Add Branta merchant logo and name to tx receipt page
Bug Fixes
Fixed maplist style
Fixed USD valu...
EINUNDZWANZIG · Fresh articles:
Warum Nostr?
Warum Nostr?
stacker news ~bitcoin:
Anyone got plans to dump ecash fork? Replay Attacks etc
Anyone got plans to dump ecash fork? Replay Attacks etc
Stacker News
Anyone got plans to dump ecash fork? Replay Attacks etc \ stacker news
was reading about replay attacks and the risk involved with dumping the ecash fork in theory tho, could you buy post fork bitcoin, create a new utxo with the new bitcoin and your old, then the fork wouldnt have that utxo, thus preventing a replay attack?…