Skip to content

Releases: SOS-Soul-of-Satoshi/sos-node

SOS Node v0.3.4-testnet

Pre-release

Choose a tag to compare

@Shutaru Shutaru released this 20 Jul 06:40

SOS Public Testnet v0.3.4-testnet

Downloads

Download the matching .sha256 sidecar and verify every artifact against the
Sigstore-signed RELEASE-MANIFEST.json before running a binary. The Windows
executable is bound by the signed manifest but does not carry an Authenticode
signature.

Status

This verify-only node release is active on the generation-3 public testnet. It
normalizes shield-extension fields before strict validation and restores
retained consensus votes to local tallies in release builds.

The capped Route2 deployment passed coordinated canaries in both directions,
including replay rejection. Bridge intake is enabled for the capped public
testnet and guarded by fail-closed checks for contract identity, TVL accounting,
validator-set parity, relayer health and monitoring. The publication snapshot
reconciles 500,000 sats outstanding on both chains, with zero active locks.

A six-hour four-validator chaos/load campaign completed 21,600 invariant checks,
73 injected fault events and 4,626 accepted operations with zero violations.
The machine-readable report and its artifact hashes are attached to this release
and published under evidence/v0.3.4-testnet/.

This is unaudited testnet software. Testnet tokens have no monetary value and
testnet keys must not be reused on any other network.

SOS Node v0.3.3-testnet

Pre-release

Choose a tag to compare

@Shutaru Shutaru released this 20 Jul 04:02

SOS Public Testnet v0.3.3-testnet

Verify every artifact against the Sigstore-signed RELEASE-MANIFEST.json before
running a binary. The manifest records whether the Windows executable also has
Authenticode; otherwise its immutable ZIP remains Sigstore-bound. The existing
Route 2 deployment passed its coordinated two-way canary. Treat this binary as a
candidate until the post-deploy bridge canary and live TVL checks pass again.

Source commit: 49aba2d3c680cefabeb0e0fdceff64fdbf2fdd19
Genesis SHA-256: 6d20c7a7e6fa4706d4f9e2bcc0ad23c8a144601aee391301ef0912e3c809e524
Bridge contract: 0xB8863C0c094DE2f3f0C50EF96101b53B7374F0C9
Bridge domain: 0xb706d5afab98a2371bc5593e86be8ee1262f94dff4c1577741e1f506dd1a27ea

SOS Node v0.3.2-testnet

Pre-release

Choose a tag to compare

@Shutaru Shutaru released this 19 Jul 07:34

SOS Public Testnet v0.3.2-testnet

Verify the archive sidecar, the bundled SHA256SUMS, and the Sigstore-signed
RELEASE-MANIFEST.json before running either binary. The manifest records whether
the Windows executable also carries Authenticode; without a configured public
code-signing certificate, its immutable ZIP is Sigstore-bound but the PE remains
unsigned. The Route 2 bridge passed the coordinated two-way canary. Verify the
live operations flag and TVL policy before transferring funds.

Source commit: d7ab1afe0818918ba087f15ea559eea74a675a22
Genesis SHA-256: 6d20c7a7e6fa4706d4f9e2bcc0ad23c8a144601aee391301ef0912e3c809e524
Bridge contract: 0xB8863C0c094DE2f3f0C50EF96101b53B7374F0C9
Bridge domain: 0xb706d5afab98a2371bc5593e86be8ee1262f94dff4c1577741e1f506dd1a27ea

SOS Node v0.3.1 Testnet (Route2)

Pre-release

Choose a tag to compare

@Shutaru Shutaru released this 18 Jul 23:10

Verify-only SOS public testnet node for the Route2 network generation.

Release identity:

  • Source commit: ff2f55b42850b3694d9ae75893ec616ff83bc5a1
  • Source tree: 29623ef491a4ac89a5f0ef02993962a91144c2b6
  • Genesis SHA-256: 6d20c7a7e6fa4706d4f9e2bcc0ad23c8a144601aee391301ef0912e3c809e524
  • Sepolia bridge: 0xB8863C0c094DE2f3f0C50EF96101b53B7374F0C9
  • Bridge domain: 0xb706d5afab98a2371bc5593e86be8ee1262f94dff4c1577741e1f506dd1a27ea
  • wSOS: 0x131267484Bec89371dA22fe9Ebc8B0C8476Af679

Verify each archive with its .sha256 sidecar. Then verify RELEASE-MANIFEST.json using RELEASE-MANIFEST.sshsig, identity sos-release, namespace sos-release, and the attached allowed-signers file. The active ED25519 fingerprint is SHA256:c9hqz7F4dn6rWUF7ABbG8pLxJ9R45vEA95buNaVjuNE.

The Windows executable is not Authenticode-signed. Its exact digest is covered by the SSHSIG-signed release manifest and the archive checksum chain.

This is unaudited testnet software. Testnet tokens have no monetary value. Bridge activation remains fail-closed until the final public deployment canary succeeds.

SOS Node v0.2.0 Testnet

Pre-release

Choose a tag to compare

@Shutaru Shutaru released this 14 Jul 21:36

Testnet validator release

Production-mode SOS validator/verifier binaries for the current public testnet checkpoint. The binaries exclude --dev-rpc and were built by pinned Linux and Windows release workflows from core checkpoint 18192f342b2807937dbfb5b4115e4151d441d687.

Network identity:

  • Chain ID: 0x534F53
  • Genesis SHA-256: fc0ae56044642f14f5eee71ef165fea5d0868fdc260c9fd15b4acd5f13805e21
  • Three project-operated validators, currently co-hosted on one server. This release does not claim independent validator operation.

Operational warning:

  • The bridge is administratively paused.
  • The SOS and Sepolia validator-set hashes currently differ.
  • Do not submit bridge lock or burn operations until a separate reactivation announcement.

Archive SHA-256:

  • Linux x64: bf43f7e958cfc73ceccec7269970c7775ad8df55cc7f99858a25a2e5c769b53f
  • Windows x64: 6ec54a0d58fa12775781c28456b21106b5a610e8ca078da1b2b5579837541dd4

Raw binary SHA-256 values and the CycloneDX SBOM are included inside each archive. Verify SHA256SUMS against SHA256SUMS.sig with the included allowed-signers file. Release signing fingerprint: SHA256:5Ax7PUTlVR0ZpgrQYNDSjeOu/bR9zZZX7PrVAngS2WY.