W / 1

Soroban Upgrades

Soroban Upgrades is a safety gate for contract releases. It compares compiled WASM and produces a deterministic plan before a signer approves an upgrade.

Ecosystem
Stellar / Soroban
Category
Release infrastructure
Status
Open-source alpha
Technical ownership
Biel Carpi
Abstract dark blue surfaces folding into a continuous path
Editorial systems studyEditorial image by tyrone biggums / Unsplash
PROJECT EVIDENCE2026
1

45 engine and CLI tests in the showcase

2

8 adversarial Protocol 28 tests

3

6 documented release decisions

4

Apache-2.0 licensed

1 / Problem

The release or operating risk.

Soroban replaces contract WASM but keeps the contract address and ledger state. A source diff does not prove that the compiled artifact is safe. Teams must review interfaces, stored data, upgrade paths, and protocol capabilities.

2 / Approach

The technical approach.

The CLI uses compiled WASM as the release boundary. It inspects artifact hashes, Contract Spec XDR, metadata, imports, exports, storage schemas, migrations, and rollback requirements. Each finding identifies a fact, an inference, or an unknown.

3 / Result

The available evidence.

The alpha includes a reproducible showcase, JSON reports, adversarial fixtures, and a release plan that cannot sign transactions. Historical Testnet evidence shows an upgrade at the same address. The project is ready for evaluation and Testnet pilots. It is not audited or ready for Mainnet.

Technical surface

Stack and evidence

  • Rust
  • Soroban SDK
  • WASM
  • Stellar CLI
  • Contract Spec XDR
Contact

Discuss your next engineering mandate.

Tell us the objective, operating environment, and current technical boundary. We will identify a suitable scope and review process.

hello@eloiz.xyz