Bitcoin Layers

Bitcoin Layers has been acquired by @blockspace. Our founder, Janusz, will be joining Blockspace as an advisor as a part of the transaction. The integration will enable Bitcoin Layers to expand its onchain data suite and revamp its research platform.

@blockspace @OPNEXT2026 @cbspears @AsILayHodling @wsfoxley OPNEXT

BITCOIN TECH CONF FLASH TICKET GIVEAWAY! If you want to join BlackRock, Blockstream, Bitcoin Core and other leading Bitcoin tech companies at @OPNEXT2026 for free, simply... 🔸 Follow @blockspace 🔸 Repost this X post 🔸 Comment "OPNEXT"

my initial review on @citrea_xyz can be found below janusz.cash/layers/citrea tl;dr: citrea is a bitcoin sidesystem that uses bitcoin for data availability making it a bitcoin rollup it is an independent network with its own full node software. citrea advances its state by applying state transition logic over a set of transactions posted to bitcoin by the citrea operator (known as a sequencer) citrea full nodes initially gather blocks directly from the sequencer, execute them, and generate a new state root the sequencer then posts differences in state to bitcoin and full nodes verify that the state update posted to bitcoin matches the state they generated locally and every so often, a prover posts a validity proof to prove that the state transitions were executed correctly to finalize the full nodes view of the rollup as well as light clients to move bitcoin onto the network, citrea uses the clementine bridge which is an implementation of bitvm2 the clementine bridge vault has two primary spend paths the first sees 10, institutional signers, who participate in a 10-of-10 multisig set up, collectively spend funds out of the bridge vault contract to process withdrawals in the happy path clementine also contains an additional spend path where a 3-of-5 security council can spend funds out of the bridge vault contract in the event of one of the signers being unresponsive, or malicious, citrea leverages a bitvm-style game to enable operator-fronted withdrawals an operator kicks off the bitvm game by requesting a reimbursement transaction. in the transactions i analyzed, the kick off transaction was followed by two transactions where the corresponding utxo was spent by 1) a presigned tx spendable by the aggregate musig2 key from the clementine signers or 2) the clementine security council both script trees also contained an unrevealed path which most certainly contains the presigned transaction tree for the clementine bitvm protocol citrea is the first implementation of a bitcoin rollup, with an official bridge program, on bitcoin mainnet based on my findings, it does in fact use a bitvm-style protocol as outlined in its documentation site the network has training wheels on, but it's extremely promising to finally have a bitcoin rollup on mainnet with a verifying bridge!

@herogamer21btc @blockspace @cbspears 💯

@blockspace @cbspears Listening to the pod makes me think once we have multiple clients more matured and developed we could do with having multi-faces assessment like @BitcoinLayers on those clients

NEW @blockspace pod! Who is the newly appointed Bitcoin Core maintainer? What even is a “Maintainer”? "These are key holders, but they're more like janitors with keys." - @cbspears We discuss: ⚡ First one added since 2023 ⚡ No more lead maintainer ⚡ github owned by MSFT?

The Bitcoin Layers team will be at @OPNEXT2026 See you in New York 🤝 opnext.dev 🎟️

some news: @blockspace has acquired @BitcoinLayers the acquisition will enable bitcoin layers to expand its data capabilities we already have some great progress on this front courtesy of @khunpleb we’ll also be working on revamping the research portal and expanding it past bitcoin l2s and bitcoin-backed assets truthfully, it will be a 10x on what we were doing before i’m excited to work with @cbspears, @wsfoxley, and co. to get bitcoin layers to where it should’ve always been i do want to thank everyone; the l2 teams, crypto projects, various conferences, and ecosystem friends for giving us a chance at building a neutral platform for this emerging category and i want to thank @redvelvetzip for joining me on this journey. i also want to specifically thank @alexeiZamyatin and @0x_orkun for giving me the motivation & confidence to start the project over two years ago and personally supporting me during the early days

what i see as the main difference between @arkade_os and @flashnet let's say a user has an offchain utxo (leaf or vutxo) and wants to do some crazy shit to support this, flashnet uses an intent model where users send funds to an address controlled by validators. if intent is valid, the validators take a key share and pass it to the flashnet signer. if m-of-n validators pass the key share for the intent, the signer executes the transaction arkade extends their virtual mempool to support co-signing for more complex scripts. i.e., the arkade signer is able to sign off on things more complex than bitcoin scripts. a user needs to co-sign this execution, but model requires an honest signer for all offchain actions (like any out-of-round transaction) flashnet is an "at execution" custody risk. after execution, (in most scenarios) a user returns to a statechain model, meaning they have a pre-signed exit path for their utxo arkade has users remain in a "preconfirmed" state during all of this execution. post-execution, they can participate in a settlement transaction on bitcoin to gain full self-custody of their funds both models use TEEs for signing execution in flashnet, m-of-n validators need to collude and/or the TEE signer needs to be compromised to steal user funds in arkade, the TEE needs to be compromised and previous owners within a specific vtxo tx chain need to collude with the TEE i don't know which is *better* - just a different approach

someone asked for a @BitcoinLayers review on @arkade_os. i'll do it later but tl;dr custody - green tx data - green operator - dark red finality - green or yellow very good. congrats team

All in all, statechains are neat protocols where users retain pre-signed unilateral exit paths. But: - Users trust operators to delete keyshares post transfer - All transfers are completely public (no privacy) - LN payments are done via centralized swap providers

To pay LN invoices, Spark leverages centralized operators who facilitate LN swaps on users behalf. These swaps are atomic, meaning the swap provider can't steal your funds. But you do need at least one of these swap providers to be online to interact with LN.

Wallet of Satoshi is not (technically) a Lightning wallet. It uses a network, known as Spark, on the back end. Spark is a statechain. Let's go through a few of the assumptions:

More R&D related to bitcoin scaling is welcome. And, users should understand tradeoffs related to Starknet's current design related to bitcoin financial applications. Learn more about Starknet, from the lens of a bitcoin user, here: bitcoinlayers.org/layers/starknet

Starknet's R&D efforts, in addition to recent product developments, are focused on building towards a (more) trust-minimized bitcoin bridge. A partnership with @AlpenLabs is a part of this effort: x.com/EliBenSasson/s…

xBTC supply up and to the right 📈 @Starknet launched an implementation of wrapped bitcoin staking and saw its xBTC supply 5x over a week long period. A quick tl;dr on Starknet's recent updates 🧵