Signed at the source · Apache-2.0

Proof for everything
the machine does.

Git signatures prove who pushed. Matrix Scroll proves who authorized the agent that wrote the lines.

Local Ed25519 envelopes at commit time — verify offline, gate in CI, no vendor in the trust path. SSX360 is the hosted control plane for fleet policy and enterprise pilots.

Ed25519 · offline verify MCP baselines · rug-pull defense Apache-2.0 · free forever
Local Code Signature Block SHA256 Match
app/auth_controller.py signed changes
1 def authenticate(request):
2 token = request.headers.get("Auth")
3 + if not token or is_revoked(token):
4 + raise AuthenticationError("Invalid Agent Origin")
5 return verify_claims(token)

Rug-pull defense

Tools change after you approve them.

Snapshot at authorization. One changed character trips verification before the agent runs.

  1. 1
    Approve a tool

    Snapshot the MCP tool definition at authorization time with matrixscroll mcp scan.

  2. 2
    Quiet edit

    Someone changes the tool description — the classic rug-pull / tool-poisoning path.

  3. 3
    Verification fails loudly

    Hash mismatch fails loudly with exit code 2 and blocks CI. Free, open source, works offline — pip install "matrixscroll==0.6.1".

tool pin · verify

            

Notary, not watchtower

Inventory is not authorization. Dashboards that attest to themselves are not proof.

NHI control planes rent a dashboard. Matrix Scroll gives you a portable evidence record you own — verify years later without SSX360, your servers, or any SaaS lookup in the trust path.

Before action

Sign declared actor, tool, scope, and changed surface before merge or tool drift is accepted.

Offline proof

Verify the record in CLI, browser, or CI with the same RFC 8032 bytes — no SaaS lookup required.

Governs agents, not people

Records what an autonomous agent was authorized to do — not keystrokes or developer productivity.

Complements NHI

Keep your NHI inventory and ITDR stack. Add the authorization record they do not produce.

Secure GitLab workflow

From device possession to merge gate.

Hardware-authenticated developer sessions, policy enforcement before merge, and audit export — governed agent authorization, not productivity surveillance. Enterprise pilots via SSX360.

  1. 1

    Device authentication

    Connect USB-C hardware, press the physical button, and enroll into fleet policy. Session authorization confirms possession — L2 Hardware prototype in pilot, not GA.

  2. 2

    Policy & merge gate

    Scroll Gate enforces repository rules before merge. Out-of-policy changes are blocked or flagged; instant revocation supports incident response.

  3. 3

    Cryptographic signing

    Commits, pull requests, and agent actions are recorded with declared actor, tool, timestamp, and Ed25519 signature — keys stay local.

  4. 4

    Audit & monitoring

    Logs export to your SIEM; Prometheus and Grafana visualize fleet health. Evidence packs verify offline without SSX360 in the trust path.

Built to scale

Customer environment · platform · monitoring.

Three layers for regulated teams — open protocol locally, hosted control plane for fleet policy, your monitoring stack for continuous visibility.

01 · Customer environment

Developer laptops & GitLab

USB-C hardware keys, Git hooks, and protected-branch CI on GitLab or GitHub. Signing and verification stay on the machine.

02 · Management platform

Fleet, identity, policy

Device onboarding, identity management, policy engine, audit logging, and merge gate controls — SSX360 hosted control plane.

03 · Monitoring stack

Prometheus · Grafana · SIEM

Metrics and security events export to your stack. Authorization evidence remains offline-verifiable without vendor uptime.

The Security Gap

The AI-Assisted Code Blindspot

Autonomous developer agents and autocomplete engines are changing files directly inside your environment. Standard checks can't tell the difference between human logic and machine output.

Traditional GPG Commits

Signs your name, even if AI wrote it

Standard GPG models sign off on the commit metadata. If an AI agent edits 40 lines across 3 modules and commits them, your credential signs off on it anyway. There is no proof or trace of who generated the core logic.

Signed by: dev_user@company.com [IDENTITY ASSUMED OK]

Matrix Scroll Protocol

Cryptographically signs the declared origin

At commit time, the envelope records the declared actor and tool (for example, a Claude agent or Copilot session) and signs that claim with Ed25519. Assessors can verify the signature offline; the envelope does not detect authorship by itself.

Author: claude-agent [TOKEN CHECKED & VERIFIED AT GATE]

Interactive Anatomy

Interactive Protocol Breakdown

Click each block below to see what metadata is cryptographically tied together at the instant of code creation.

MANIFEST ANATOMY (Click keys to view data maps) commit-envelope.v1.json

Parameter Mapping

Actor Type

Declares whether the commit was attested by a human, agent, or CI system — self-reported at commit time.

Terminal Playground

Interactive Terminal Simulator

Simulate installing and executing the open source SDK CLI. Scroll Gate checks use the product console (simulated) — not a shipped local binary.

Step 1: Run Command

matrixscroll-cli · product console (simulated)
# Run a command on the left to start sandbox operations
$

Live proof / client-side

Inspect a real signed sample — no upload required.

browser-verifier — matrixscroll.identity.v1
sample manifest ed25519 / browser verify

                

MCP Server

Attest inside Cursor, Claude, or VS Code

The public MCP server audits repositories, scaffolds hook configs, and verifies agent commits directly in your editor.

Get the MCP Server

Post-quantum (POC 2)

Ed25519 today — lattice overlay for Q-Day

Ed25519 is not quantum-resistant. Software signers can attach NIST ML-DSA or SLH-DSA overlays via matrixscroll[pqc] while hardware stays Ed25519 until firmware catches up.

Crypto roadmap

PyPI 0.6.1

Reference SDK on PyPI

Published conformance vectors, Git hooks, and Scroll Gate PR checks make the signature contract auditable today.

View on PyPI

Standard Integrity Maps

How Matrix Scroll Compares

Why standard signature models fall short when managing the risk profile of autonomous AI code generation.

Integrity Vector Standard GPG Signatures Sigstore / in-toto Matrix Scroll Protocol
Identity Verification Human Committer Developer OIDC Account Signed actor/tool declaration
Line-Level Attribution ✗ None Whole commit metadata ✓ Self-reported actor/tool at commit time
Offline Generation Checks Requires GPG Key Server Requires OpenID connection ✓ Fully offline signature match
Hardware Token Roadmap Yubikey Support Hardware token profiles L2 Hardware prototype — Pico 2 W + GMT130 locked; SE050 M1 PoC bench-validated (Jul 2026); not GA

See the full comparison including SLSA, Sigstore, and artifact attestations.

Free & open source

The protocol costs nothing. It always will.

Matrix Scroll is Apache-2.0 code and a CC0 specification — signing, git hooks, the MCP server, and offline verification run entirely on your machine, free forever. Organizations that need centralized policy, hosted verification, and audit export across teams can explore SSX360, a separate hosted control plane built on this protocol.

What's free

No signup, no license, no usage limits — the entire protocol.

Read the docs
  • Local Ed25519 SDK (PyPI 0.6.1)
  • Optional PQC overlay (ML-DSA / SLH-DSA)
  • Public MCP server
  • Unlimited offline verification
  • Git hooks integration

Regulated teams

Authorization pilots and compliance mapping for institutions — by consultation, no self-serve checkout.

  • Scoped pilot rollout after consultation
  • NIST SSDF / SLSA mapping
  • SIEM export (roadmap)
  • Fleet policy & hardware preview

Enterprise value is fleet policy, SIEM, and hardware — not a self-serve price ladder. Request Pilot Consultation or Book 30 min.

Central Policy Control

Need Enterprise Control & Audit Ledger?

A dashboard can't forge what was signed at the source. Matrix Scroll runs locally on developer machines and gates offline verification pipelines — central policy, hosted verification, and audit export live in SSX360.

Matrix Scroll Protocol

Free and open source. Sign edits inside developer environments, verify locally, commit and inspect signature integrity locally.

SSX360 Enterprise Control

Hosted verification engine. Sync rules globally, export evidence packs aligned to DORA, PCI DSS 4.0, SSDF, and EU AI Act record-keeping readiness — evidence mapping only, not a certification claim.

Request Pilot Consultation Book 30 min