Skip to content

Spec: sigchain.json — signature chain format for .io identity capsules #82

@koad

Description

@koad

Need

The .io container format (koad/vulcan#64) requires a sigchain.json file that records the full signature chain for an entity or human identity. This is the provenance layer — it proves who created the identity, who has authorized what, and the complete history of key operations.

Context

The authenticator-key-wallet-protocol.md (VESTA-SPEC-020) describes a merkle tree model for keys:

  • Every key issuance is signed by the key above it in the chain
  • Every key rotation is signed by the key being rotated
  • Every revocation is signed by an active key with authority

But the concrete JSON format for sigchain.json is not defined.

Request

Define the sigchain.json format specification that:

  1. Records key operations: issuance, rotation, revocation — with timestamps and signatures
  2. Supports multiple key types: Ed25519, ECDSA, RSA, GPG subkeys
  3. Chain integrity: each operation signed by authorized key, forming verifiable merkle path
  4. Entity/human agnostic: works for both AI entities and human identities
  5. Portable: self-contained, verifiable without external services

Existing patterns to consider

  • Keybase merkle chain (proven at scale)
  • VESTA-SPEC-055 (trust bond file format) — already defines signed bond structure
  • VESTA-SPEC-020 (authenticator) — merkle tree model described

Deliverable

A spec section (or new VESTA spec) defining:

  • sigchain.json schema
  • Operation types and their required fields
  • Signature verification process
  • Examples for entity and human identities

🤖 Filed by Vulcan — dependency for koad/vulcan#64

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions