# Verifiable Signed Exports: Trust That Travels

By [Orchestra](https://paragraph.com/@orchestra) · 2025-07-10

---

As blockchains become more composable with the real world, it’s no longer enough to record state. Systems need to **prove** it — beyond the chain, across domains, and on demand.

With this update, **Orchestra now supports signed exports**: verifiable snapshots of onchain state that can be independently verified, anchored, and audited off-chain. They’re simple, deterministic, and portable — enabling better trust coordination between institutions, ledgers, and systems that don’t speak Orchestra natively.

* * *

### The Problem

A lot of systems can hold state. Few can **prove** it.

In real-world contexts — finance, identity, public registries, or compliance — onchain state often needs to:

*   Be exported and presented to external systems
    
*   Be signed by a trusted actor (validator, institution, or collective)
    
*   Include canonical structure, hash, and signature
    
*   Remain verifiable **without replaying the full chain**
    

Most chains don’t support this. They either require centralized APIs, or a full node replay just to verify someone’s status or ownership. That’s fine for closed ecosystems. It’s a bottleneck for real-world interoperability.

* * *

### The Update

Orchestra now ships a new module for **signed exports** — tamper-evident bundles of onchain data that can be validated anywhere.

#### Key Components

*   `SignedExport` object A JSON structure with:
    
    *   `export_id`: human-readable label
        
    *   `type`: e.g., `identity_bundle`, `asset_state`
        
    *   `payload`: canonicalized snapshot (object data, metadata, diffs)
        
    *   `signer`: the validator or collective who produced the export
        
    *   `signature`: cryptographic proof (same keys used for block signing)
        
    *   `timestamp`: when it was produced
        
*   **New CLI commands**
    
        orchestra create-export --type identity --id identity:org:abc
        orchestra verify-export --file org-abc.export.json
        
    
*   **RPC methods**
    
    *   `getSignedExport(export_id)`
        
    *   `verifyExport(payload, signature, signer)`
        
*   **Event emissions**
    
    *   `export_created`
        
    *   `export_verified`
        

Exports can also be **anchored into external chains** (via the existing `ANCHOR_COMMITMENT` transaction) for public notarization and timestamping.

* * *

### Example Use Case

An identity provider (or DAO) wants to issue verifiable proof that a given identity was active, credentialed, and trusted as of block `X`.

They generate a signed export:

    {
      "type": "identity_bundle",
      "payload": {
        "identity": "id:org:abc",
        "credentials": [...],
        "roles": ["issuer", "custodian"],
        "registered_at": "2024-10-15T12:45:00Z"
      },
      "signer": "validator_001",
      "signature": "base64...",
      "timestamp": "2025-07-09T18:00:00Z"
    }
    

That file can now be attached to:

*   Compliance reports
    
*   External workflows (e.g., banking, procurement, grants)
    
*   Verification endpoints for off-chain systems
    

No need to sync the chain. No need to decode transaction logs.

Just verify the signature using Orchestra’s validator registry or anchor hash.

* * *

### Why This Matters

Signed exports are not a feature for crypto-native use cases. They’re for **bridging trust with the outside world**:

*   Regulated finance? Produce a verifiable asset registry.
    
*   DAO service provider? Export your role assignments and programs.
    
*   Open registry? Snapshot a collective’s credential graph.
    

The goal is composability **across systems** — not just inside the chain.

* * *

### What’s Real Today

*   Exports for:
    
    *   Identities (`identity_bundle`)
        
    *   Assets (`asset_state`)
        
    *   Registries (`registry_snapshot`)
        
*   Validator-signed canonical snapshots
    
*   CLI tooling for creation and verification
    
*   RPC for programmatic use
    
*   Anchor integration via existing anchor commitment infrastructure
    

* * *

### What’s Next

This lays the foundation for:

*   **Collective signing** (multisig or delegated signers)
    
*   **Zero-knowledge exports** (e.g. for privacy-preserving attestations)
    
*   **Continuous proof feeds** (e.g. timestamped registries every 24h)
    
*   **Human-readable disclosures** for institutional users and auditors
    

It also connects to the growing need for **structured, regulated, interoperable data** that lives onchain — but is readable and provable _offchain_.

* * *

### Closing Thought

Verifiable state isn’t just a blockchain feature — it’s a requirement for coordination. Orchestra now makes that state **portable, signed, and accountable**.

No replay required. Just trust you can inspect.

---

*Originally published on [Orchestra](https://paragraph.com/@orchestra/verifiable-signed-exports-trust-that-travels)*