LayerTwo Labs

"Bro just watch the dub" The dub in question:

Since this post was made, 3 quasi official statements have been issued from @cake and @spark alike. Here at L2L, we believe in debate as one of the best tools people have for arriving at truth. We invite all parties involved for an unscripted, moderated, and live X Space here

@kphur Would someone from Spark like to participate in a live moderated debate with Matthew Vuk? He's accepted already, would be Thursday/Friday around 11am EST tentatively. Would be good to clear the air for the community and get to the bottom of this in an organic way.

There's been a round of misinformation about Spark going around, so for the sake of setting the record straight, I'll briefly clear up a few things. For one, unilateral exit has been around since the early days of Spark. Many developers and users have used it. This has been demonstrated many times both here on X and during the process of integration by developers. Unilateral exit also does not require the SOs to be online when a user wishes to exit. When a transaction is received, users can save the unilateral exit information and later use those pre-signed, valid L1 Bitcoin transactions at any time on Bitcoin. There are existing Github issues to expose unilateral exits in a more intuitive way in the SDKs, but unilateral exits themselves have been functional for a very long time. Unilateral exits do require CPFP - this is used to ensure that the expected value for an attacker is negative. The typical user would perform a cooperative exit, which does not require any on-chain funds and is an atomic swap of on-chain funds in exchange for Spark funds. Unilateral exits are generally reserved for a worst-case scenario and can be sponsored by an L1 fund provider if needed. Second, the confusion around "Sparkcore". At Lightspark, we use a monorepo for our server code. This one service is called Sparkcore - the naming of which preceded the creation of Spark. Lightspark runs an SSP within this service. Our Lightning infrastructure uses both LDK and LND - both of which we contribute code towards. Sparkcore itself is not open sourced - that would mean open sourcing our entire server-side stack for every product we have built. The Spark network code, however, has always been open source - and that's the openness that matters, because it's the code that actually enforces the rules of Spark. The SSP is an optional, replaceable convenience role. A recent post claimed that APIs used for other products are part of the SSP. We have many products, and we have never been shy about describing UMA, which allows regulated entities to exchange information to process transactions over Lightning. This is not a Spark product. The SSP does not hold your seed phrase (that should never leave your device), the SSP cannot freeze your funds, and the SSP isn't even a required role to use Spark - it is the interop layer between Lightning and Spark and helps do swaps for exact denominations of leaves. Running an SSP is something we have talked with many partners about. The client chooses which SSP they wish to interact with (if any) - we cannot control if a client talks to a new SSP. Finally, privacy. I've discussed this many times in the past, so won't belabor the point again. Spark allows for transactions to be hidden from external visibility. As I've spoken about at length both here and at various conferences, we care deeply about making sure that there is true privacy, and we aren't satisfied with anything short of that. It's an ongoing effort to continue to further the research in this area. I'll leave it with this. In the network our critics operate, the default payment path is one where the operator colluding with any prior owner can double-spend the current holder - their own docs say so. Receiving over Lightning means trusting that the operator deleted a key - their own docs say so. If you don't come online every 28 days, the operator can take your funds. In their founder's own words: "In theory it could steal it." The automatic re-issuance of expired funds promised in March 2025 still hasn't shipped. Their operator's liquidity costs scale with payment volume, which by their own admission "will translate into user fees." And there is exactly one operator - their own docs tell everyone else: "Do not attempt to run an Ark server in production (yet!)." Spark has three independent operators, exits that don't expire, and no flow where a single operator can take user funds. Users can judge for themselves. Our users and the developers building on top of Spark care about bringing Bitcoin to more people. They value the ease of use and simplicity of Spark. They care that we have 3 independent SOs. They care that we are pushing for more and better functionality. And they value that we spend all of our time thinking about how to make Spark better each and every day. Ok, now back to building because that's what we do at Spark.

@Cryptolution Knots sisters.....

🚨JUST IN: BIP-110 Signaling rate drastically drops to 0% in the past 125 blocks. Source: bip110.org/monitor

@sethforprivacy @matthewvuk2 Hello, would you be interested in doing a debate on X with Matthew regarding his findings? We can bring in Vlad Costea or Paul or both to moderate. Around 11am EST Thursday or Friday?

@vikrantnyc @matthewvuk2 Would you be interested in doing a Space with Matthew to discuss his findings, we can bring in Paul or someone else as a moderator. Thursday or Friday ~11am EST?

@matthewvuk2 Thanks for retweeting our tweet. Your agenda is very obvious here. We are open to whatever Tech works and is the best for users and are willing to change in the future when other things are working. However your attacks on us make me question what is your real agenda here.

The "Sparkcore" SSP is building a profile on you: it logs every payment you make and the pubkey of every lightning node you pay to. It has a CHAINALYSIS integration inside that registers who you pay and runs "RISK SCREENING" on your txs with a 3rd party. Not very private...

@w_s_bitcoin I prefer the real data x.com/LayerTwoLabs/s…

This is the right way to market Ocean. Mechanic and Luke set them back by wasting so much time focusing on fighting spam. I see a rebranding in the works.

@rodpalmerhodl @TheRulersBroken plebs watchin 👀

@TheRulersBroken so are the plebs

The haters are watching you. They're not at the gym watching you do every rep. They don't see the books you're reading or the podcasts you're listening to, but they notice you getting strong, smarter, and more confident. They see you making yourself better. Keep going. Give them something to watch. You've already exceeded all their expectations, you're making them look silly now. Let them mock. Let them doubt. Let them hate. But NEVER let them win. Turn them into believers and inspire them. #Bitcoin

AI is a collective telepathic hive mind

@decentmoney2009 @LukeDashjr Same

@LayerTwoLabs @LukeDashjr Thanks for this btw I’m genuinely surprised it’s not higher to rival his “liar” posting

Thread: @Lukedashjr CSAM / Pedo / CP Posting By The Numbers Account-wide since July 2012: - 159,919 total posts - 0.27% (424) of all posts contain “CSAM”, “pedo”, or whole-word “CP” - first matching tweet: March 20, 2018 - highest combined term month: 92 posts in October 2025 - 2025: 198 matching posts - 2026 YTD: 191 matching posts - latest 6-month rolling share: 1.81% of posts contain “CSAM”, “pedo”, or whole-word “CP” Charts and vid below 👇

@mith_os @coinjoined @LukeDashjr We don't recognize Lightning here

@LayerTwoLabs @coinjoined @LukeDashjr lmfaooooooo 🤣🤣 you have to drop your lightning address, i need to show some love to a fellow autistic person

@realizingerin @LukeDashjr Steel sharpens steel sir

@LayerTwoLabs @LukeDashjr Thank you for this hard hitting journalism

Thread: @Lukedashjr Liarposting By The Numbers Account-wide since July 2012: - 159,875 total posts - 0.95% (1526) of all posts contain “liar” - first “liar” tweet: February 4, 2017 - highest LPM (liars per month): 97 times in April 2026 - 2025: 381 “liar” posts - 2026 YTD: 339 “liar” posts - latest 6-month rolling share: 3.09% of posts contain “liar” Charts below 👇

@itsdonnyok @cbspears It's real

@cbspears Please tell me this is a real scrape from X api

WOULD YOU BUY THIS CHART??? It's clearly a trend. But what you DON'T KNOW is that there's a HUGE liquidity unlock on August 8. Buyers beware.

@LayerTwoLabs @LukeDashjr What's the LNAV (Liar to net asset value) of Ocean?