Bitcoin SV (BSV)
Live pricing is temporarily unavailable from our data feed. The reference information below is unaffected.
About Bitcoin SV
Bitcoin SV split from Bitcoin Cash in 2018 in a dispute about how far block sizes should rise. Its position is that blocks should have no practical limit at all and that the chain should serve as a general data ledger, not only a payment network.
Removing the limit rather than raising it
Where Bitcoin Cash raised the cap, Bitcoin SV argues there should effectively not be one, on the view that miners and market forces will determine the right size. This is the furthest extension of the large-block position and follows directly from the same reasoning that produced the earlier split.
Data on-chain as the intended use
Very large blocks make it economical to store application data, records and files directly on the ledger. That is a different product from a payment network — closer to a public database with immutability guarantees — and it is what the design is optimised for.
The centralisation consequence is unavoidable
Storing and validating very large blocks requires substantial infrastructure, so the set of participants able to run a node shrinks to well-resourced operators. This is not incidental: it is the direct arithmetic of the design, and it concentrates the network among entities that can afford it.
Hash power and reorganisation risk
Sharing SHA-256 with a far larger chain while commanding a small fraction of the hash rate makes deep chain reorganisations economically feasible. This is the same structural vulnerability affecting any minority chain on a shared algorithm.
Context that belongs in an assessment
The project has been closely associated with prolonged litigation over claims about Bitcoin's origins, and several major exchanges have delisted it. Both facts affect liquidity and access, and both are matters of public record rather than opinion.
Technical data
Frequently asked
How does Bitcoin SV differ from Bitcoin Cash?
It removes practical limits on block size entirely rather than raising them, and positions the chain for large-scale on-chain data storage.
What is the consequence of unbounded blocks?
Running a node requires substantial infrastructure, so validation concentrates among well-resourced operators. That follows directly from the design.
Why is minority hash power a risk?
Sharing an algorithm with a much larger chain while holding a small fraction of its hash rate makes deep chain reorganisations economically feasible.