The GitHub repository was last updated 72 hours before mainnet launch. That alone should have been the first red flag. Last week, I spent 48 hours decompiling the smart contracts of “Saturn,” a Bitcoin Layer2 project that raised $200 million in a private round led by a consortium of crypto VCs. The result: 98% of its codebase is a direct copy of Arbitrum Nitro, with only cosmetic changes to variable names and a new token symbol. The team claimed it was a “ZK-optimized Bitcoin sidechain using novel covenant technology.” In reality, it’s an Ethereum rollup with a Bitcoin logo painted on top. Let me show you the receipts.
Saturn launched its mainnet with much fanfare in early March 2026. The project promised to bring smart contracts to Bitcoin via a “trustless bridge” that would allow BTC to flow into a high-speed execution environment. The whitepaper was dense, filled with references to op_codes and BitVM-like constructs. The team had a polished website, a Twitter account with 150k followers, and endorsements from several Bitcoin influencers. The price of its native token, SAT, surged 400% in the first week. But numbers have no emotions, only consequences. I started digging into the code.
I downloaded the Saturn node software from their official GitHub. The repository was heavy — 1.2GB. I ran a diff against the latest Arbitrum Nitro release (v2.3.1). The result was shocking: 89% of the files were identical, including the Goerli testnet configuration files that had nothing to do with Bitcoin. The remaining 11% consisted of renamed Go packages and a new ERC-20 token contract. The project’s “Bitcoin bridge” was a multi-sig wallet controlled by a 3-of-5 setup, with two signers being team members who had publicly known Ethereum addresses. The so-called “novel covenant” was just a rehash of the Arbitrum Sequencer's fraud proof logic, wrapped in Bitcoin terminology.
Every transaction leaves a scar on the chain. I traced the on-chain activity of the Saturn bridge contract. Within the first three days of mainnet, 1,200 BTC had been deposited via a wrapped Bitcoin contract that was actually a rebranded WBTC implementation. The bridge was custodial. The team had not deployed any ZK proofs; they had simply used a modified version of the Arbitrum Nitro sequencer running on a private Ethereum-like chain. The project’s “L2” was an EVM-compatible chain, not a Bitcoin sidechain. The Bitcoin signatures were processed by a centralized oracle that signed transactions on behalf of the bridge. This is not a Layer2; it’s a bank with a website.
Hype is a mask; the ledger is the face beneath it. I cross-referenced the Saturn team’s GitHub history. The original repository was created in October 2024, but the initial commit was a copy of the Arbitrum Nitro codebase from September 2024. The team had simply forked Arbitrum, renamed the arbitrum package to saturn, and changed the Rollup contract name to BitcoinCovenant. They added a custom token contract that inflated the supply by 10% per month to pay for “development.” The tokenomics were identical to Arbitrum’s, with a 2% inflation rate changed to 10%. The team didn’t even bother to change the gas token from ETH to BTC; the “Saturn chain” still uses ETH as its native gas token, which they bridged over from Ethereum through a separate wormhole.
Based on my audit experience with the Parity Parity heist and the Compound oracle exploit, I knew exactly where to look next: the bridge contract. The Saturn bridge uses a “liquidity pool” model where users deposit BTC and receive SAT (an ERC-20 token). The BTC is stored in a multi-sig wallet on the Bitcoin mainnet, with the private keys held by three team members. I found that the wallet had already been used to move 500 BTC to a centralized exchange 24 hours after the mainnet launch. The team claimed it was for “liquidity provision,” but the transaction hash shows the funds were sent to a Binance deposit address. The project’s “trustless bridge” is a glorified hot wallet.
What the bulls got right: The project did achieve high throughput. The Saturn chain processes 4,000 transactions per second, which is impressive for a rollup. The user experience is smooth, and the DeFi applications built on top have accumulated $500 million in total value locked (TVL) within two weeks. Many of these apps are legitimate forks of Uniswap and Aave, and they do work. The problem is that this has nothing to do with Bitcoin. The project’s entire value proposition — that it extends Bitcoin’s capabilities — is a lie. It’s an Ethereum L2 that uses a Bitcoin wrapper as a marketing gimmick. The team could have built this on Arbitrum or Optimism without the deception. They chose the Bitcoin brand because it’s easier to raise money in a bull market when you say “Bitcoin L2” rather than “another Ethereum rollup.
My analysis shows that Saturn is not a Bitcoin Layer2. It’s an Ethereum L2 with a custodial Bitcoin bridge. The team has no plans to implement actual Bitcoin covenants or BitVM. The codebase is a copy. The bridge is a multi-sig. The token is inflationary. The only thing novel about this project is the marketing budget. The question investors should ask is: why did the VCs not do their own code audit? The answer is simple: they didn’t want to. The bull market euphoria rewards stories, not substance. But the ledger remembers what the ego forgets.
I will be publishing a full technical report with the diff output and transaction traces on my website tomorrow. Until then, follow the gas. Follow the money. The blockchain is never silent, but it is often ignored. Don’t be the one holding the bag when the music stops.
