Syscoin’s March 20, 2023 introduction of the final Rollux testnet made a broad social argument alongside its engineering pitch. It imagined inexpensive decentralized exchanges and financial applications reaching people poorly served by conventional banks. The collapse of FTX was part of the motivation for offering alternatives to custodial intermediaries. Solidity compatibility was supposed to bring existing Ethereum developers into that effort without requiring a wholly unfamiliar programming environment.

This was an official vision of greater access through cheaper application execution, not a description of a completed banking replacement. It explains why supporters spoke about Rollux as a new beginning for Syscoin rather than merely a faster place to transfer the same coin.

The foundation’s June 28, 2023 update announced Rollux mainnet and described an initial ecosystem spanning trading, NFTs, wallets and communications. Pegasys, Luxy, Pali and SuperDapp gave the launch a consumer-facing story alongside the chain itself. The update distinguished some available services from integrations still moving through testing, including prospective oracle features. That distinction helps reconstruct what actually arrived at launch. An application name in a partner list can mean an operating product, a planned integration or an experiment.

For Rollux, the early pitch was that several connected services would make the network usable immediately and give the SYS community reasons to transact beyond speculation about future infrastructure.

Rollux’s comparison with Optimism identifies its parent as Syscoin NEVM, its data-availability mechanism as BitcoinDA and its native gas currency as SYS. The OP-derived execution environment gives developers familiar contracts and tooling, while those parent-layer choices change the dependencies beneath them. Rollux is not the Syscoin UTXO ledger and is not an Ethereum-settled copy of Optimism. Its roadmap for decentralized sequencing remains separately described as research.

The presence of an open-source execution stack therefore says little by itself about who orders transactions today or who can change privileged contracts. Compatibility makes it easier to bring code across; it does not make every operational and security assumption portable with that code.

The mainnet connection guide identifies Rollux with chain ID 570 and SYS as its gas currency. It distinguishes direct withdrawals from an exchange that supports Rollux from the route starting with SYS on Syscoin’s UTXO chain. That latter path passes through NEVM and the Rollux bridge. A ticker does not tell a wallet or exchange which of those balances the user intends to move. The distinction also explains why this account has no separate Rollux market-token association: SYS serves the wider Syscoin architecture, rather than being a uniquely issued Rollux asset.

A network selection needs the correct chain and route, not merely a matching symbol beside a withdrawal button.

The Syscoin introduction describes a coordinated stack with a Bitcoin-derived UTXO chain and the NEVM execution environment. Auxiliary proof of work lets participating Bitcoin miners also secure Syscoin, while quorum-based signatures add a finality mechanism. BitcoinDA is another part of that design. These features explain the project’s Bitcoin-aligned identity, but the work performed by each component remains distinct. Mining helps determine the parent ledger; finality addresses how that ledger settles; data availability concerns obtaining the information required to reproduce execution.

None is an application audit. A user of a lending contract on Rollux therefore encounters the parent architecture, the rollup’s own controls and the contract’s rules together.

The BitcoinDA guide describes a sequencer submitting transaction data to Syscoin’s UTXO-side availability system, identified through Keccak hashes. An ancillary service indexes that data, and the batcher uses a contract lookup to confirm its availability before the rollup derives state from the referenced batches. The guide discusses external archival storage, initially Cloudflare R2 and later Filecoin through Lighthouse, for redundant retrieval. The important distinction is between a compact commitment and the transaction bytes needed to reconstruct a chain.

A correct hash identifies data but does not replace a copy of those bytes. Node operators need the retrieval path as well as the contract records that point to it.

Rollux’s fee documentation separates local execution from the cost of publishing data to Syscoin. The first component depends on the gas used and the transaction’s gas price. The second reflects the parent-side publication cost and the applicable fee parameters. An interface that displays only execution gas can therefore understate the total. This matters even when typical transactions are inexpensive: a wallet trying to send its entire balance must leave enough for both components.

The guide exposes RPC estimation and a GasPriceOracle method rather than recommending a permanently hardcoded fee. Changes in parent costs, transaction data and execution requirements mean that a quote belongs to a particular action and time.

The application-optimization guide focuses on transaction bytes as well as computation. It discusses compact encoding instead of automatically padding every argument to the standard ABI’s full word size, and selecting data types that fit an application’s actual range. This is an engineering tradeoff: a compact custom interface can reduce transmitted data while demanding more careful decoding and compatibility work. The documentation’s examples illustrate the approach, rather than establishing that every application should abandon standard interfaces.

A developer needs to preserve valid input ranges and predictable behavior before chasing smaller transactions. For users, the resulting benefit should appear as an understandable total fee and a reliable interaction, not an opaque format that makes independent inspection harder.

The Bedrock documentation published with Rollux describes a withdrawal in stages: initiate it on the execution layer, wait for an output that can support the proof, submit that proof on the parent, then finalize after the waiting period. Its documented mainnet flow uses a seven-day interval. This is different from how quickly a transaction first appears inside the rollup. It also creates work for an application that wants to present a clear exit status: initiated, proven and finalized are separate states.

The page retains some upstream Optimism terminology, so it is architectural documentation rather than a current transaction receipt for every Rollux bridge route. A third-party fast bridge adds its own liquidity and service assumptions.

Rollux’s beta-security page states that fault proofs are not available and that an anonymously managed multisig can upgrade core contracts without delay. It explains why fast upgrade authority limits the protection a challenge system could provide. The keys remain a trust dependency even when the parent chain operates correctly. Permissionless application deployment is a different feature from permissionless enforcement of correct withdrawals. The same page describes decentralized sequencing and removal of the multisig as future work.

Those ambitions cannot be substituted for a deployment record showing that the authority has changed.

A launch-day SuperDapp campaign connected prospective SUPR rewards to activities across the ecosystem, including Pegasys participation and Luxy NFT trading. It also discussed recognition for Syscoin masternodes and other community members. The campaign shows how developers tried to connect the new execution network with an existing audience: using one product could become a route into another. SUPR was an application token in that campaign, while SYS paid the chain’s gas. Historical eligibility and promised allocations should be read within the campaign’s dates and rules.

They do not turn ordinary Rollux activity into a permanent entitlement to a future airdrop or make the value of an application reward predictable.

The foundation’s February 2026 update described election-transparency work from Honduras in December 2025. According to that account, independent groups digitized tally sheets, stored artifacts on IPFS and anchored references using Rollux together with LACChain. The useful property was a record against which later changes to a document could be detected. This did not replace the official count or establish that every original sheet was accurate. The case illustrates a concrete service quite different from token trading: making a document’s subsequent alteration observable.

Its value depends on the collection and custody of the original evidence as well as the hash record. A blockchain preserves what was submitted; it cannot retrospectively witness how the underlying document was produced.

BigPoppa’s February 3, 2026 ecosystem-budget proposal described a transition in which developers, applications and partners would move toward zkSYS while Rollux remained supported during the handover. It contemplated scaling down and eventually dismantling legacy Rollux infrastructure after that transition. The proposal also framed its requested SYS funding around a reduced operating budget and the difficulty of financing work as the token’s market value fell. This is evidence of an explicit operating plan and its financial rationale, not an executed mainnet shutdown notice.

It raises practical questions for existing applications: which services will be maintained, what a migration requires and who remains responsible for users who have not moved.

The March 25, 2026 Genesis announcement introduced a public zkSYS testnet with chain ID 57057 and a separate Gateway testnet. Its architecture used ZK Stack and described purpose-built Edgechains settling through Gateway. Mainnet was still a future milestone in that announcement. This is a distinct deployment from Rollux mainnet 570, even though both belong to the Syscoin ecosystem and use SYS in their network descriptions. A new test environment does not automatically move old contracts, balances or users.

The difference also matters when reading performance claims: experiments on the successor testnet cannot be reported as upgrades already active on the older optimistic network.

The June 30 zkSYS update continued that testnet development with ZKsyncOS v31 and Airbender-related proving work. It described changes to the data-availability design and the engineering needed for the newer stack. These developments show where the team was directing research and implementation effort. They also explain why the older Rollux roadmap should not be read as a single uninterrupted list of completed upgrades. Moving to a different execution and proving architecture is a migration program, with new software and deployment assumptions.

The reviewed update still discussed a testnet; a reader needs a later mainnet activation record before treating the successor as a production destination for existing funds.

The October 16, 2025 ecosystem update records that the Rollux testnet was discontinued on October 8. It placed that decision alongside work on zkSYS and the surrounding software. Testnet retirement affects developers using its endpoints, faucets and historical experiments, but it does not by itself announce the shutdown of Rollux mainnet. The distinction is particularly important because documentation can continue linking to a retired test environment. A familiar network name in an old setup guide is therefore a historical reference until its current service status has been checked.

The update provides a definite date for this testnet change without supplying an equivalent mainnet retirement date.

Ankr’s September 2026 chain-support notice is a separate event. Published on September 8, it scheduled the end of Ankr’s Rollux mainnet RPC support for September 15, including the public-rpc endpoint. An infrastructure provider can stop offering access to a network without controlling whether the network itself continues. Applications built around that endpoint nevertheless need a replacement and may appear broken when their provider disappears. This also makes older recommendations of Ankr in Rollux onboarding material stale.

The provider notice establishes the service boundary that changed; it should not be repurposed as a claim that every Rollux node stopped producing or serving chain data.

Syscoin’s June 15, 2026 postmortem describes an exploit on June 7 in the UTXO-to-NEVM bridge. Duplicate asset commitments were interpreted differently by Core and the relay, permitting an unauthorized release reported as five billion SYS. The publisher says the funds were returned and burned through a recovery process, restoring the affected supply, and states that the bridge was paused at publication. These are the team’s incident and recovery claims.

The vulnerability was a mismatch at a bridge-validation boundary, rather than a demonstrated break of Bitcoin mining or Rollux’s transaction execution. For someone entering Rollux through the wider Syscoin stack, it nonetheless shows why the safety of each intermediate bridge matters.

The August 13, 2026 Liberty v5.1.0 announcement introduced Bridge V2 with proof verification before NEVM state changes and additional checks around assets, amounts, destinations and replay handling. It described coordinated Core and NEVM activation targets. Publishing the release and scheduling an upgrade are concrete events, but the schedule alone is not an independently observed activation receipt. The announcement also explicitly separated Liberty from the launch of zkSYS and from later Bitcoin-checkpoint work.

This prevents three different developments from being collapsed into a single security upgrade. The parent bridge remediation, a future checkpoint mechanism and a successor execution network each have their own deployment conditions and effect on users.