CBTC.kor

Outsourced workforce but it's just a revenue sharing paid membership member-run clubhouse

Bitcoin Under the Hood ⚡ An Intro to raw Transactions with Anika & rawBit

First release of Bitcoin-TUI is here v0.8.2 github.com/janb84/bitcoin…

BIP376: "Spending Silent Payment Outputs with PSBTs" has been published.

Introducing THINCS 🤔 SLH-DSA is the most conservative standardised post-quantum signature scheme we have. Its security reduces entirely to hash function properties (no lattice assumptions or algebraic structure). The tradeoff is size; the smallest fast variant produces 17,088-byte signatures and the smallest compact variant still comes in at 7,856 bytes. This is because the standardised parameter sets all support up to 2^64 signatures per key, and the signatures are massive as a result. Most signing keys will never need anywhere near that many signatures. To put 2^64 in perspective, signing once per second would take 42 times the age of the universe to exhaust the key. A firmware key might sign a few thousand times, a CA root a few hundred. If you know your actual budget, the underlying construction lets you trade that unused capacity for much smaller signatures at the same security level. As ecosystems start adopting hash-based signatures, there will be applications where tuning the scheme to the actual signing requirement makes more sense than using the general-purpose defaults. This is why I built THINCS. It is a Rust CLI. You give it a total amount of signatures you need it to support and a security level, and it finds and builds the smallest possible signature scheme that meets your requirements. You can then keygen, sign, and verify with it directly.

Our final @BitcoinDojo1 call will take place this Monday 11:00 UTC. We will discuss next steps which are: - Joining a @rawBit_io study cohort - Start contributing to Good First Issue - Start a Code Orange workshop - Join @MITBitcoinClub hackathon

The Bitcoin elliptic curve has an algabraic structure that is important to understand. Additionally, the transactions defined by the protocol have a structure that is important to understand. Magic Internet Math is going hard to create materials and resources to develop this understanding in the context of becoming a stronger human. magicinternetmath.com/index.html

Try em out! They’re both mature enough for me to say it’s ok if you start using them for actual things! github.com/utreexo/utreex… github.com/getfloresta/Fl…

No internet? No problem. Bala just dropped the ultimate cypherpunk demo at the BOSS Summit: From Off-Grid to On-Chain He literally broadcasted a live Bitcoin transaction using Mesh Radio. No ISPs, no Wi-Fi, no cellular data. Just pure radio waves bypassing the traditional internet layer to hit the mempool. When we say we are building unconfiscatable money for uncertain times, this is exactly what we mean. Mind blown. Here is the repo used to connect meshtastic to bitcoin core:github.com/BTCtoolshed/Me…

All of my nodes have been completely offline for 24+ hours and will not return. If this were a true sybil attack there would/could have been actual negative impacts to the bitcoin node network, especially as there were hundreds of nodes that were -only- connecting to my nodes at any given time. A lot more people now know what sybil and eclipse attacks are, and how to detect/investigate them. I have some ideas on ways to bring in more BGP routing table data into bitcoin node decisions, including not just origin AS but full AS path. In what I stood up as a demonstration, I also was able to defeat asmap because I used multiple origin ASNs, but if there is visibility available into the AS paths to reach nodes, that would then be detectable.

@dathon_ohm @moon33_blue 95+%

I wonder how much hashpower needs to be signaling before Core devs will consider BIP-110 to have "broad" support. #issuecomment-4137959250" target="_blank" rel="nofollow noopener">github.com/bitcoin/bitcoi…

@w_s_bitcoin @ZeusLN A BIP, even.

Should be an bitcoin industry standard tbh.

@bonomat Imagine monetizing sub-conf weakwork. Getting paid BEFORE finding a work-template match to satisfy difficulty. Thus, having an extra nonce by rotating these sub-conf template space bidders is just an added benefit. That's your mempool on -kapnet #MineWithKapnet @KNUPool

I’m not an expert on Bitcoin, Bitcoin L2s, atomic swaps or anything, but I know that you know that 0-conf doesn’t sound very safe.

Today we’re publishing Brink's 2025 Engineering Impact Report covering the work of the eight Bitcoin Core engineers we funded last year and why we think this work is important.

Exponential performance decay is not caused by payload, it's a consequence of non-scalable implementation. More nodes on the same architecture will not solve this, nor will censorship.

@BTCProofofPlay @ProductionReady @BitcoinKnots oops, all Core.

The Three Flavours Node Trilogy #Core #Knots #Productionready

Fewer 503(c) more DAOs on -kapnet

@josebitcoiner @Excellion Absolutely cleaning house. Keep the grassroots dry by affinity grifting latent philanthropic arbitrage. GG

Hey Bitcoiners, let's donate some Sats⚡️☕️🔥😎

@bitcoin_bugle Bitcoin is @BlockHorology

@callebtc Less weight, more shoulders. @BitcoinCreds on -kapnet

The Bitcoin builder space is at a moral low. A handful of teams are still moving things forward. You matter more than ever, and we see you. More weight, fewer shoulders. Keep going 🫡