Bitcoin Layers is an open-source platform covering bitcoin scaling, bitcoin-backed assets, and more. From the @blockspace team.
Bitcoin
Joined February 2024
- Tweets481
- Following5
- Followers4.1K
- Likes440
Bitcoin Layers retweeted
COLD CARD BITCOIN WALLET GIVEAWAY!
We're teaming up with @COLDCARDwallet to do another unit giveaway. All you need to do is...
1) Follow @blockspace
2) Retweet & comment "opnext" below
3) Like this post!
We will pick a lucky winner of a Cold Card & a GA ticket to @OPNEXT2026!
Bitcoin Layers retweeted
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"
Bitcoin Layers retweeted
do not trust @BitcoinLayers team - they are notorious slavic impersonators
This quoted post is unavailable.
Bitcoin Layers retweeted
Great, quick explainer video on Bitcoin L2s, how to classify them, etc.
at @btc_summit, bitcoin layers' lead maintainer finally defined what a bitcoin l2 is and why it doesn't matter. he also shared our project's holistic approach to analyzing offchain usecases for bitcoin. watch below 👇
Bitcoin Layers retweeted
Bitcoin L2s: the good, bad, and the ugly - @januszg_
@btc_summit 2025 🇭🇰🚀
Bitcoin Layers retweeted
Stoked to collab with the man, the myth, the legend @JakeBlockchain on this!!!
Following the treasury narrative *a lot* of products make the claim that they can help you grow your stack .
Inspired by the @BitcoinLayers team, we’re here to separate the good, the bad, & the ugly.
Follow the account👇 & drop us some feedback (though be gentle, very much an MVP atm 🥹)
Introducing BitcoinYield 💰
Your new go-to hub for all things Bitcoin yield is here 🙌
Brought to you by a team of veteran developers & media founders, our goal is to grow into the #1 trusted source of authority & news on how to securely grow your stack.
Bitcoin Layers retweeted
This ALBY COMMUNITY CALL ☎️🐝will see awesome guests again!
Join us for a 1-hr chat with👇
@getAlby
@lendasat
#Rizful #Megalithic
@BitcoinLayers
3PM UTC at communitycall.getalby.com
Bitcoin Layers retweeted
🚨 BitcoinFi State of the Union X Space 🚨
⏲️ Thursday, Aug 21 | 10am PST · 5pm UTC
We’re bringing together leading voices in Bitcoin-native finance to explore what’s next.
Guest:
🎙️ @0xCryptoSam from @MessariCrypto
🎙️ @BTC_Mick from the @BTCFiNetwork
🎙️ @januszg_ from @BitcoinLayers
Hosted by Maestro's @davis_rich
Where is BitcoinFi headed? Don’t miss it. Set your reminder 👇
Bitcoin Layers retweeted
NEW PANEL ANNOUNCEMENT 🔥
Go behind the scenes of BitVM’s architecture!
August 28 • Genesis Stage 🇭🇰
Bitcoin Layers retweeted
TUNE IN THIS FRIDAY 🎙️‼️
𝕏 Spaces: We're Not Breaking Bitcoin: The Case for CTV + CSFS | Feat. Janusz, Evan Kaloudis, Owen Kemeys, Shinobi, & Juan Galt
RSVP & join the discussion 🧵👇
Bitcoin Layers retweeted
We’re proud to support @januszg_ and the @BitcoinLayers initiative, bringing much-needed clarity to the fast-growing world of Bitcoin L2s.
Let’s make Bitcoin scaling clear and credible for everyone 🧡
This quoted post is unavailable.
Bitcoin Layers retweeted
Interesting nomenclature in the Bitcoin scaling space by @BitcoinLayers (@januszg_)
Statechain: A protocol where users enter a 2-2 multisig with a federated entity and transfer ownership of a UTXO to an intended recipient by providing them a statechain private key for that specific UTXO
Bitcoin native: A protocol that enables offchain transaction execution and sees users retain custody of their funds. This means they enable unilateral exit if the system goes offline. Arks, Statechains, and Lightning are bitcoin native protocols. Rollups, CSV protocols, and alternative rollups with validity proof bridges can be bitcoin native if there is a soft fork to bitcoin.
As per that nomenclature, besides the Lightning Network - only @mercurylayer & @buildonspark falls under "Bitcoin native" scaling solutions as Statechains.
Bitcoin Layers retweeted
BITCOIN RAILS EPISODE #20: Breaking Down the Great Covenants Debate | with Janusz @januszg_ and Red @redvelvetzip
If you’re following Ordinals, you’ve likely heard the term “OP_CAT,” a proposed Bitcoin opcode popularized by the @TaprootWizards
In this episode, I brought on Janusz and Red from @BitcoinLayers to break down what OPCAT is, how it works, and what it makes possible for Bitcoin—hint hint: you’re gonna learn all about ‘covenants’ and their role in trustless bridging in this episode.
Of course, this interview wouldn’t be complete without a breakdown of other covenant-enabling opcodes on the table—especially OP_CTV and OP_TXHASH.
Fair warning: this episode goes deep into what an OP_CAT (or covenants) future for Bitcoin might look like… as well as the potential dark side of “doing nothing.”
In this episode, we discuss:
-The difference between CTV, TXHASH, and CAT
-Why more expressivity isn’t always better
-The Risks and Rewards of upgrading (+ the great script restoration debate)
-Is the window for making changes to Bitcoin closing?
-Why ossification won’t matter in a post-OPCAT world
As always, this episode can be viewed on Spotify or YouTube—full episode in the comments or linktree in my bio.
This episode is powered by Best In Slot—the leading API for Ordinals and BRC20 data aggregation and indexing.
TIMESTAMPS:
0:00 Intro
01:20 Janus and Red’s backgrounds
03:30 What Ordinals revealed about degens and Bitcoin
05:48 What the fuck is a covenant?
06:38 Specific proposals that enable covenants: CTV, TXHash, OP_CAT
07:55 Using covenants for bridging
09:20 Are there limits to CTV?
11:15 What is TXHash?
13:20 What about OP_CAT?
15:35 OP_CAT enables SNARKs
17:30 Red’s analogy comparing the 3 proposals
20:00 How many Opcodes should we introduce?
21:15 Bitcoin’s Final Upgrade? Running out of time
24:00 The consequences of not changing Bitcoin
26:50 Bitcoin rollups will benefit Bitcoin security
31:57 Do we need to break BTC’s 21m supply cap?
35:00 Softforks can help more than just rollups
38:00 Every Bitcoin L2 is trusted right now
42:55 What does Bitcoin “scaling” mean?
44:00 Lightning can actually be trustless
46:20 Do all L2s need an L1 transaction to onboard?
52:10 Money making as a BitVM operator
Bitcoin Layers retweeted
opcode series continues
"How does OP_CSFS help BitVM?"
let's start by breaking down the current state and then I'll show where CSFS comes in
Current model
-BitVM operators facilitate withdrawals by only posting an aggregated state update bc our default state is to assume everyone plays fair
-if anyone thinks the operator isn't playing fair, then can challenge the operator
-Begin the challenge game. For an operator to clear its name, it must prove correctness onchain with a dispute tx(s)
-Now the full state of the new state is required (instead of just the aggregated state which is always posted)
-This 'full state' is put onchain in the form of 'bit commitments'. ie the operator signed the state change msg with a lamport scheme, meaning that every single bit of that state has a binary preimage, a 0 or a 1. Well now it's time to start posting those 0s and 1s, checking those individual bits one by one
(this is the descendent of the bi-section game from early models, which is much more intuitive to initially learn about imo. if you're confused, learn about the bisection game then come back to lamport challenging)
-The witness size (and overall tx size) grow linearly with the number of bit commitments. 100 bytes each. more state data == more cost in the challenge game
INSERT CSFS
What if instead of validating each bit from a lamport signature, you could just validate the lamport signature itself? sounds pretty cool ey
CSFS is like CHECKSIG, it renders a tx valid if a message is signed. in CHECKSIG, that msg is a tx and that signature has to come from the pubkey of the tx sender
but in CSFS, the message is whatever you want and the signer is whoever you want
so let's make the required message the state change, and make the required signer the operator
boom now you're handling challenge disputes in constant size, 100 bytes no matter what instead of 100 bytes per bit in the lamport signature of the aggregated state