Going down the Ren rabbithole. I'm in awe....

"When the Canadian dollar becomes worthless, we will be here to serve you, too." That was our closing reply to the Ontario Superior Court of Justice in 2022, when they ordered us to freeze and disclose information about the bitcoin involved in the Freedom Convoy protest. The

🎉 Fulcrum 2.0 is now availbale for StartOS! Initial sync time on Server One or Server Pure is ~36 hours. Performance after that is insane! Thanks to @cculianu for building, and to @linkinparkrulz_, @K0gen, @remcoros and others for getting it on StartOS. Enjoy everyone ❤️

I was this year old, when I learnt this from @tsoding

.NET 10 ships in a few hours. I’m very excited about the release. 10 years ago a few of us got pulled into a room to spike the first version of a new cross platform, open source .NET. We’re 10 years in and extremely proud of how far the product has come. #dotnet

EU requiring ID for every crypto transaction starting 2027 is FAKE NEWS. Thank you for your attention to this matter.

The next Fulcrum release on @start9labs comes with a config option for a server banner inspired by @VibrantBTC 's guide. With the blessing of Fulcrum creator @cculianu the default banner is FREESAMOURAI.

Almost got hacked today.

Nice write up by @bitcoinbrink grantee @theStack, comparing the performance of ECDSA signature validation in libsecp256k1 and OpenSSL. Nearly 10 years on, libsecp256k1 is ~8x faster than OpenSSL, and performance improvements continue to be made. The devs have been doing

Sparrow v2.3.1 has been released to restore BIP32 derivations for consolidation payments in PSBTs. In addition, hiding amounts is now supported, and the keystores that signed a multisig transaction are now shown on the transaction tab. Changelog here:

Love to see these kind of new project. Pointed one of my BitAxes to https://t.co/TdFwz5eCzo. Give him a follow: @_block_builder

@TheGoldenDays LOL. I am that old:

Many bcrypt packages in different languages will ignore the rest of the characters after 72 bytes. In Go, it will return an error if you attempt to hash a string longer than 72 bytes. If you need to hash a longer password, pre-hash it with SHA 256 and pass the result hash to

1. BIP47 is primarily designed for entities handling repeated payments to and from counterparties—think exchanges, mining pools, salary-paying companies, merchants, and the like.

In a technical debate, it's useful to start with the same axioms. I advise anyone to read (at least the terminology section of) cryptoeconomics from Erik Voskuil, which has some well-written, clearly defined axioms of various technical concepts:

Keep an eye on this: https://t.co/2ZApFY4zjt

sometimes i spend hours on a simple bug and think "i'm sub-par, the average techie would have solved this in like 5 mins" and then i get reminded of how dumb the average techie really is

How are so many people falling for this "temporary" soft-fork nonsense? There is no such thing as future consensus. Agreeing to run or activate some code in the future is a social/organizational construct, not consensus on the chain with most PoW.

https://t.co/kpYteOXYEQ

Running LND on StartOS? Make sure you always have a backup of the latest 'channel.backup' (SCB). I've created a simple service that automatically backs up to a network share whenever it changes. Link below 👇

"fork or I call the cops" wasn't on my bingo card for this year's bitcoin drama.