SUM Innovation Inc. Mainnet …

SUM Innovation Inc. Delaware C-Corp

Blockchain infrastructure
built for the people who
think crypto is a scam.

Eight months. No outside capital. Rust throughout. Mainnet live.

Attested 0 0

Resolving

Network state

Network state

Reading https://rpc.sumchain.io

Block height

10,140,204

chain_getBlockHeight

Target interval

3,000ms

chain_getChainParams

Finality depth

6blocks

chain_getChainParams

Active validators

2

sum_getValidators

Storage replication

3x

chain_getChainParams

Canonical supply

800B Ϙ

chain_getSupplyInfo

Every figure above is read from the public endpoint at page load and refreshed while this section is on screen. Nothing here is illustrative. The latest block hash is printed in the footer.

The stack

One protocol.
One dependency graph.

Nothing here is a separate company wearing a shared logo. SUM Chain is the protocol. SNIP and OmniNode are subprotocols that settle against it. SUMail is the layer a person opens, with Tadris inside it. RUMUS is the open source framework underneath the compute. Select an entry to trace what it settles against and what it carries.

Application

Compute

Storage

Settlement

Select an entry

The settlement layer is the only thing everything else shares. Storage economics, inference rewards, credential issuance, and the company cap table all resolve on SUM Chain.

Per-field privacy

One breach exposes
millions of records.
That is architecture,
not negligence.

A central student database is a single object worth stealing. Remove the object. Every field of a credential is independently public, selectively shareable, or private, and the private ones never reach chain state at all.

SRC-810 · Academic credential

Issuer signed

  • credential_id

    0x4f2c…a91d

    Public, fixed

    Identifier. Always public. Carries no personal data.

  • issuer

    KFUPM

    Public, fixed

    The institution signs. Verifiers need to know who.

  • schema_hash

    SRC-810-COURSES-v1

    Public, fixed

    Which schema this record was canonicalized against.

  • title

    BSc Computer Science

    Public by default. An employer can read it without asking.

  • completion_date

    2026-05-22

    Selectively disclosed. Revealed to a named verifier, for a fixed window.

  • gpa

    3.87

    Selectively disclosed. Proven in zero knowledge, or revealed in full, at the holder decision.

  • subject_commitment

    0x9b71…04e2

    Private, fixed

    The student. A 32 byte commitment. Never a name, never an identifier.

  • transcript_payload

    snip://bafy…7k3q

    Course-by-course marks. Encrypted, stored on SNIP, never in chain state.

  • date_of_birth

    ••••-••-••

    Never written to chain state and never returned by the read RPC.

Key recovery

Losing a key cannot mean losing a degree. Recovery runs as multi-party computation across institutions that already staked on verifying the individual. No single institution holds a share that reconstructs anything, and no custodian holds the key at any point. The institutions that vouched for the person are the ones that can restore the person.

Proof of Contribution

Rewards are escrowed,
never minted.

Re-running an inference to check it costs as much as performing it. So the network verifies instead of re-executing, and pays out of a reserve that was allocated at genesis. There is no emission schedule and no inflation.

The life of a claim

  1. Inclusion

    A verifier-signed attestation lands in a block.

  2. Plus 6 blocks

    Finality depth clears. The attestation cannot be reorganized out.

  3. Plus dispute window

    Any party may challenge. A validator quorum resolves it, not a resolver key.

  4. Claimable

    Escrow releases. A refund cannot bypass a claim that is still immature.

Protocol reserve, unallocated

Read from chain_getProtocolReserve. 799 billion Ϙ of an 800 billion canonical supply remains in reserve, split by the work it pays for.

Governance reserve

319B Ϙ

Ecosystem

160B Ϙ

Archive contribution

120B Ϙ

Compute contribution

120B Ϙ

Validator

80B Ϙ

Enforced by consensus

  • Three-way storage replication, and reassignment when an archive exits.
  • Per-block Proof of Retrievability, with stake slashing on a missed challenge.
  • Attestation uniqueness and mempool admission against the activation gate.
  • Claim maturity, dispute resolution by validator quorum, and escrow refund.
  • Equity transfer restrictions, at contract level.

Deliberately off chain

  • Halo2 proof artifacts. The chain anchors the commitment, not the proof.
  • Semantic correctness of an inference result. No consensus claims to judge it.
  • Verifier bonds and slashing for inference. Neither exists in v1, and we say so.
  • Grades, submissions, answer keys, and every field marked private.
  • File bytes. Only merkle roots, access lists, and fee pools are on chain.

Institutional record

Claims with a
counterparty attached.

Each line below either resolves against a public endpoint or names the body that verified it.

  1. P-01

    Mainnet is live

    Proof of Authority consensus producing a block every 3,000 ms, public JSON-RPC at rpc.sumchain.io. The figures in the strip above this line are read from that endpoint, not from a content management system.

    rpc.sumchain.io

  2. P-02

    The company minted its own equity on chain

    SUM Innovation shares exist as SRC-83X equity records on SUM Chain, with transfer controls enforced at contract level rather than by a transfer agent.

    SRC-83X equity family

  3. P-03

    Corporate governance runs through on-chain voting

    Proposals, tallies, and execution are validator-quorum controlled. A 6,667 basis point authority threshold, 2,000 basis point quorum, 5,000 basis point pass threshold, and a 201,600 block voting period, which is seven days at the current block time.

    Governance v1, active at height 8,900,000

  4. P-04

    The whitepaper is under external cryptography review

    Read by an outside cryptography group rather than by the authors. The zero-knowledge circuits are being reviewed alongside the protocol description rather than after it.

    External review

  5. P-05

    Research lineage in graph search

    DARPA-backed graph search work at UCLA under Professors Andrea Bertozzi and Paolo Climaco. Propagation and partitioning results from that program inform proposer scheduling and deterministic chunk assignment.

    DARPA, UCLA

  6. P-06

    Outreach across 200 learning platforms

    Direct go-to-market conversations with more than two hundred learning platforms, alongside a university partnership pipeline with KFUPM, King Abdulaziz University, and Princess Nourah bint Abdulrahman University.

    200+ platforms, 3 universities

  7. P-07

    Presented in the Nevada blockchain adoption context

    Presented at RareEvo in Las Vegas, against the Nevada Secretary of State blockchain adoption program.

    RareEvo, Las Vegas

Selected writing

Read the protocol,
not the pitch.

  1. R-01 SUM Chain: verifiable coordination for storage, compute, and credentials Whitepaper Under external cryptography review
  2. R-02 Proof of Contribution and the case against re-execution Protocol note Active on mainnet
  3. R-03 Halo2 circuits for contribution attestation Circuit review In review
  4. R-04 Per-field privacy across nineteen document families Design analysis Published
All research

Three ways in

We do not sell speculation.
We ship infrastructure
people use daily.

  1. Builders Run a node, or read the source. Archive operation is Linux first. Client mode runs on macOS, Windows through WSL2, and ChromeOS through Crostini. Everything is MIT or Apache-2.0. github.com/SUM-INNOVATION
  2. Institutions Issue records you do not have to defend. Tadris runs a conventional registrar workflow. Students appear on chain as commitments, never as people. Partnership conversations are open with universities and learning platforms. leo@suminnovation.xyz
  3. Investors The brief, the cap table, the chain. Delaware C-Corp. Equity minted on chain with transfer controls in the contract. Governance executed by on-chain vote. The cap table is queryable. Investor brief