Vote duration
24h
Pass threshold
51%
Universal threshold
51%
Fast pass threshold
1
Quorum
1
Loading initial...
24h
51%
51%
1
1
Reviewed 2026-10-11 · Prepared for Fact-check a debate.
Moving BTC into a documented sidechain changes the trust and exit assumptions. That does not establish the recommendation that users should never use any sidechain. The disagreement is mainly about whether added functionality justifies those assumptions.
Consensus security and bridge security must be distinguished. Liquid uses federated block signing; Rootstock also uses merged mining. Faster settlement and lower fees can be benefits, but congestion and crossing between chains affect the overall experience.
Claim
Assessment
Reason and evidence
Normative recommendation
The word 'should' expresses a risk preference. The evidence establishes a changed trust model, not that every use of every sidechain is unacceptable. Liquid Technical Overview · What is a Liquid peg-in?
Supported for the documented implementations
Liquid's peg-in documentation expressly distinguishes LBTC from mainchain BTC. Rootstock's PowPeg also adds bridge-contract and hardware assumptions. These examples support the difference; they are not a security audit of all sidechains. What is a Liquid peg-in? · PowPeg and the security model
Needs qualification
This roughly describes federated Liquid, but merges consensus and bridge security into one layer. Rootstock also uses merged mining. The statement is too broad if read as a universal account of sidechains. Liquid Technical Overview · PowPeg and the security model
Supported with conditions
Liquid documents rapid settlement during normal operation and a fee market with a low minimum. This supports 'can', not 'always'. Peg-in/peg-out waiting time, congestion and conversion costs matter; no live end-to-end fee benchmark was performed. Liquid Technical Overview · How do transaction fees on Liquid work? · What is a Liquid peg-in?
Risk preference
Whether functionality compensates for a different trust model depends on the use case and user's risk tolerance. It is not a universal measurable verdict. Liquid Technical Overview
Conditional recommendation
The added assumptions are documented; the assessment of what is reasonable is a value judgment. This is compatible with recognizing different trust models. What is a Liquid peg-in? · PowPeg and the security model
Mixed factual premise and opinion
The factual premise that the security models differ is supported. Calling an action a mistake remains a recommendation. Keep the mixed statement's factual flag unchanged. What is a Liquid peg-in? · PowPeg and the security model
Not established by the reviewed evidence
Documentation availability does not prove that experienced users can reliably evaluate protocol security. No empirical competence study is cited. This is unverified, not demonstrated false. No external evidence establishes this statement
Hypothetical motivation
This describes a possible personal motivation rather than an observed population-level fact. No behavioral evidence is provided. No external evidence establishes this statement
Precautionary recommendation
It advises caution rather than reporting a measured outcome. Different trust and exit assumptions explain the concern without proving a categorical suitability rule. Liquid Technical Overview · What is a Liquid peg-in?
Liquid Technical Overview — sections: Sidechain Basics; Network Roles; Block Signer; General Public. Liquid uses federation block signing, while watchmen safeguard the pegged BTC. Users can verify the chain themselves, but the public cannot independently peg out. Normal operation offers roughly two-to-three-minute settlement.
What is a Liquid peg-in? — sections: Introduction; How Peg-Ins Work; Peg-Outs. The documentation explicitly distinguishes LBTC's security model from mainchain BTC. BTC is locked at a federation-controlled address. Peg-in requires 102 mainchain confirmations; direct peg-out is restricted to federation members.
How do transaction fees on Liquid work? — sections: How Are Fees on Liquid Determined?. The help page describes a low minimum fee and a demand-dependent fee market. This supports possible fee savings, not a guarantee: transaction size, congestion and moving between chains affect total costs.
PowPeg and the security model — sections: How the PowPeg is secured; Defense in depth. Rootstock separates merged-mining consensus from bridge-contract and PowHSM security. Sidechain consensus and bridge security are distinct layers, so one description of federation operators cannot represent every sidechain.
Reviewed all six indexed transcript blocks, nine unique linked argument claims, and the central debate claim. Evidence is evaluated against each assertion, not used to declare a debate winner. An opinion is not classified as false merely because it lacks empirical proof. Is factual identifies a checkable statement rather than a verified truth.
All six indexed transcript blocks and their nine unique linked argument claims were reviewed, together with the central debate claim. Video/audio was not independently transcribed or timestamp-verified.
Primary project documentation describes design and behavior; it is not independent verification of deployment safety. The Liquid and Blockstream pages are related sources, not independent confirmations.
No exact original publication dates are supplied by these documentation pages. No dates will be invented; the Rootstock last-update date is not substituted for publication.
No live transaction-cost benchmark or comprehensive sidechain security audit was performed.
Is factual classifies whether an assertion is checkable; it does not mean the assertion has been proved true.
The published debate's background description mentions an alleged exploit. This review does not independently verify that allegation and does not rely on it.