Larry retweeted
An anti-poaching ranger sitting with and comforting one of the young gorillas he protects after its mother died
Larry retweeted
"Volunteers from a neighborhood committee keeping watch on a Beijing street." They don't regard this as a chore; they enjoy it. The aggressively conventional-minded are always there, in every country. All they need is an excuse to go after the rest of us.
Larry retweeted
Contributors to Braidpool can get a free ticket to @TheBitcoinConf . At this point I think we have 3 contributors. Pull requests are open!
We’re excited to add the following awesome projects to our Open Source Program, in collaboration with @HRF! 👇
@selfcustodykrux
@BlockchainComns
@CalyxOS
@StratumV2
@MutinyWallet
@AquaBitcoin
@MostroP2P
@nwc_dev
@AuthLN
@EttaWallet
@BorderWallets
@start9labs
@braidpool
@satsigner
@vexl
@VLSProject
@payjoindevkit
@get10101
Graphine OS
Chaincase
Enuts
BitVM
Ark
Minibits
Bitaxe
Bitcoin Core app
Nostr Development Kit
Blossom
Coinswap
FROST
Larry retweeted
Replying to @AJA_Cortes
Too much bias in his thinking.
People either have the following or they do not:
1) viable property rights
2) electricity
These 2 work in cohesion, when they don't, you can feel it, when they do, you can feel it.
Larry retweeted
Replying to @evoskuil @BtcCuracao
I started up Core latest on my same machine last week, and after 1.5 hours, with no indexing, it had archived 5% of the chain by size. At 1.5 hrs libbitcoin node is complete up to 840k blocks, with full indexing.
Larry retweeted
Replying to @eric_lombrozo @Gh4nder
Effectively getting technology into the hands of the individual is the best we can do. We cannot make people "good", but we can balance their power against each other.
Larry retweeted
This is why Libbitcoin does not require any consensus forks. All are implemented as options, going back to the beginning of time (still working on some old ones) and enabled via config. P2P also configures to any protocol level.
If Bitcoin Core is not the right venue to implement relay policy changes (whether or not I think it is, its pretty clear that core devs themselves decided it is not), than it certainly isint the right venue to implement consensus changes.
Soft fork activation code should never be in Bitcoin Core. If you want a soft fork, fork Bitcoin Core and put your soft fork code in it and get people to run it. Don't rely on Bitcoin Core to merge it. People automatically update Bitcoin Core for many reasons (bug fixes, security, optimizations, wallet features, etc) so it should never be used to activate contentious policies. Bitcoin Core devs should never put their users in a position to choose between missing out on Bitcoin Core improvements and activating a fork.
Security-wise, there is a big difference between running a completely different bitcoin node implementation and running a fork of Bitcoin Core with specific and targeter modifications.
"Just remember love is life and hate is living death
Treat your life for what it's worth and live for every breath
Looking back I've lived and learned, but now, I'm wondering
Here, I wait and only guess what this next life will bring, haha!"
youtube.com/watch?v=Q3Qzxkpx…
58

















