From Bitcoin's workbench to Solana's kitchen

Bitcoin has a scripting language — called Script — that is deliberately constrained. It is not Turing-complete, it does not allow loops, and it permits only basic operations: verifying signatures, handling timelocks, or setting up multisignature (multisig) arrangements. This simplicity helps make Bitcoin's behaviour predictable and reduce the execution surface, although Bitcoin's security depends on many components of the protocol.

Ethereum chose a different path: it introduced the EVM (Ethereum Virtual Machine), a Turing-complete environment in which smart contracts can be executed. At the protocol level, state transitions are handled according to a sequential model, although implementations may carry out some internal tasks in parallel.

Solana answered the scalability challenge with a radically different architecture: the SVM (Solana Virtual Machine) and the Sealevel runtime.

The account model of Solana (and of the SVM)

In Ethereum, a smart contract “owns” its state: the data resides in the contract itself. In the SVM, the design is decoupled:

- The code resides in a program account; its upgradeability depends on the deployment mechanism and a designated authority
- The data (the state) resides in separate accounts, controlled by the program

This allows Sealevel to analyse transactions in advance: if transaction A concerns accounts {X, Y} and transaction B accounts {Z, W}, the two can be executed in parallel and without conflict.

This model allows the parallel execution of transactions that do not touch the same accounts. It can increase throughput, but does not, in itself, warrant any conclusion about a quantitative advantage over the EVM on comparable hardware. No specific performance test has been published for Bitcoin Hyper.

What this means for developers

SVM programs are written in Rust (or C/C++) and compiled to eBPF bytecode. A widely used framework is Anchor, which adds macros and conventions to make development easier.

Bitcoin Hyper's documentation sets itself the goal of direct compatibility, or “drop-in compatibility”, with the Solana ecosystem. According to the project, an existing program could run with limited changes — for example, by changing the RPC endpoint and a few network parameters. The documentation also anticipates compatibility with tools such as the Solana CLI, Anchor and IDE plugins. The actual degree of compatibility remains to be independently verified.

Were this degree of compatibility to be achieved, it could lower the barrier to entry for developers familiar with Solana. Sharing an SVM-based environment does not, however, in itself guarantee the compatibility of programs, APIs, system programs, tools or runtime behaviour. This remains a design goal rather than an independently verified outcome.

What remains to be clarified

Even so, several points are worth stating openly:

Full compatibility has not been independently verified: the Devnet is selective and public testing is limited
Differences in the fee model: according to the project documentation, Bitcoin Hyper uses $HYPER for fees rather than SOL, which means that some abstractions differ
Dependencies on Solana's system programs: some Solana applications rely on system programs (such as the official Token Program) that may not be available in identical form

The claim of “drop-in” compatibility remains to be verified. Assessing it requires public technical documentation, sufficient access to the Devnet, and reproducible tests covering programs, tools and system dependencies.

The franchise analogy

The SVM can be thought of as the kitchen of a franchise restaurant. The recipe corresponds to the code, and the premises to the network on which it runs. Bitcoin Hyper aims to offer tools compatible with Solana, but it has not yet been demonstrated that all the components are identical or that the result is the same in every case.

The difference lies in the main ingredient: instead of SOL, $HYPER would be used here as the kitchen's “fuel”.

The Solana Virtual Machine, explained for Bitcoin users