Everything that uses pre-signed transactions gets improved with CTV. There is nothing complex in understanding this part.
Personally, I would use joinpool: https://gist.github.com/harding/a30864d0315a0cebd7de3732f5bd88f0
I have experimented with the idea on signet and it improves coinjoin.
Most things that use pre-signed transactions want to update them (eg lightning), which doesn’t work with CTV.
The dynamic he’s describing (where you have to convince “Core”) strikes me as an incredibly weird way of viewing it, though - it’s just a group of developers working on one project. I don’t really understand this perspective at all, tbh.
In terms of “well why didn’t CTV happen”, I responded on Twitter, but there’s nontrivial risk to the act of doing a fork in Bitcoin. That has to be weighed against the value of any fork. For me personally, I didn’t see a single use for CTV that was even remotely compelling (not like I wouldn’t use it, but I don’t think anyone will use it) until Timeout Trees, at which point every has given up on CTV.
I don’t think “well clearly we’re just not getting anything” is the right way to look at it. From where I sit, the attempts at adding covenant features to Bitcoin have been half-assed at best.
I think i agree with basically *all* of James' post here.
https://twitter.com/jamesob/status/1857049961235403101
Including the part at the end, where he doesn't have any solution ...
Really? His claim is mostly that there’s this clear consensus for various protocol changes for Bitcoin that aren’t happening because of “lack of leadership” in Bitcoin Core. But I’m really really struggling to see where that consensus is, and for what it is.
There’s nothing that requires someone contributing to Bitcoin Core regularly to lead the charge for creating consensus around a protocol change, and I’m happy others are trying, but nearly everything I’ve seen people pushing is just very very clearly not at the level of consensus yet.
That doesn’t imply that somehow Bitcoin Core contributors are at fault (or responsible for creating consensus around other peoples’ ideas), maybe the ideas just aren’t mature yet.
Huh? Yea it is rather easy to set up a server for bluesky, did you read the docs?
That said they’re not quite the same - clients don’t connect to multiple servers like they do in nostr (saving a ton of bandwidth in exchange for the server they’re using being able to censor), and the default server just serves your content, it doesn’t index other servers’ contents so you can use that to build your own feed (like nostr in that regard but more important in bluesky).
DVMs alone are a long way from an algorithmic feed, let alone user choice over a set of possible community-built feed algorithms.
Bluesky showing how their decentralized platform flies https://video.nostr.build/9949acfa8c3b16b0179dc86fa63dac8f4f8f7b8e643cfc64552ec0c8ad355537.mp4
And yet it’s growing at a rate that nostr isn’t. Sadly “supports an algorithmic feed” seems to be a pretty important feature if you want users to join a social media platform. Luckily nostr could support such a thing, but we have a lot of catching up to do.
I assume this will be misinterpreted - not saying the Dems were fated to lose through no fault of their own (they’re generally left of the American public in ways voters don’t appreciate, and that’s part of what they paid for) but those celebrating bitcoin-minded voters or a rightward swing because voters decided for those policies (rather than just mostly want to not have inflation) are also overly exuberant. nostr:note1sddxmdeps5mk3yz08ayqmfnjkty0adfcay7x9gnnzmnyjtrs8y0q2nz8pa
This is actually wild. In *every* election globally this year the ruling power lost vote share.
https://x.com/jburnmurdoch/status/1854485866548195735 nostr:note1cnsswjqrua80muq3qhsd6al5wrcsldq2l4un4reettm26p2z7xks6mutng
Errr sorry I got excited, in a developed country. Still, first time this ever happened.
This is actually wild. In *every* election globally this year the ruling power lost vote share.
https://x.com/jburnmurdoch/status/1854485866548195735 nostr:note1cnsswjqrua80muq3qhsd6al5wrcsldq2l4un4reettm26p2z7xks6mutng
56C isn’t hot? Memtest generally doesn’t get a CPU hot, just a bit warm.
We need to build technology that protects average users, not only the technologically advanced.
(Tweet quoted another pointing out that you should use a VPN when using nostr) nostr:note1kee0kk6gnc3l3kxkzq5jgxe94wzepjrz0a92fnjcz85h5u7ec5rqt608gz
Not that Kamala wasn’t a pretty poor candidate or that Trump didn’t generate excitement, of course, but the economy is a *really* strong headwind in any election. Don’t overread the general populace’s desire to “vote crypto” or for any other specific issue. nostr:note1vpzh0nc6hrmvzhkc2alztlj5gcc5yh62at9h63plx7ddsay40rfs63td56
(Not that Kamala wasn’t a pretty poor candidate or that Trump didn’t generate excitement, of course, but the economy is a *really* strong headwind in any election, one that’s nearly improve to overcome)
A lot of the “Trump won because….” takes feel incredibly US-myopic. This was the year of more democratic elections across the world than almost any other and nearly all of them “surprised” in how strongly they voted against the party in power (both left and right). The universal rule of politics remains undefeated - people vote their pocket books.
Memtest doesn’t tend to get your CPU hot, though. Different things can fail at different utilization levels…
A Bitcoin node will detect bugs in the matrix
since I'm not seeing any serious memory or disk issues, and assuming there are no bugs in bitcoin-core, I wonder if my bitcoin node is getting hit by cosmic rays and bits are getting flipped every now and then, leading to leveldb checksum errors.
I looked into ECC ram but I may need to build a home server, since it's not common in desktops motherboards.
Is this is why you’ve been going on about ecc memory nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj ? I found a post about it from greg maxwell 10 years ago as well, saying all his non-laptop machines use ecc memory:
https://www.reddit.com/r/Bitcoin/comments/2jpk54/risks_of_running_bitcoin_client_on_a_computer/cle3qyb/ nostr:note1ktns7scrqr00h9a400eajn8k23hcxzzp35syfr7j4tvzjkdpjjdsj4z0sf
You’re more likely hitting hardware issues that only crop up when running the machine hot. Try running y-cruncher and memtest. Similarly try testing your disk (don’t know any applications that test if it corrupts at high rate, I know they exist tho)
Private gossip efforts kinda stalled without a champion, sadly. Gossip v1.5 is mostly redoing gossip so that we can do taproot channel announcements and also minisketch the gossip sync protocol. It also theoretically supports announcing more aggregate channel capacity than UTXO proofs provided but unclear whether people will implement that (especially on the announcing side).
Ideally someone with a bit of time could sit down and spec out (and then implement) log-scale ringsig announcements, but I’m not sure it’s gonna happen soon on its own.
One team is led by a fraud who thinks he knows how to handle a sword, the other hires an actor who can dress up in a puppet outfit and convincingly hold a sword. We are not the same. 
Hopefully not on testnets!


