Operations

State chain blocks contain an array of operations that modify the in-memory KV store. There are two operation types: set and delete.

#Op struct

1type Op struct {2    Action string          `json:"action"` // "set" or "delete"3    Key    string          `json:"key"`4    Value  json.RawMessage `json:"value,omitempty"`5}

#Actions

#Set

Creates or updates a key with a JSON value:

1{2  "action": "set",3  "key": "sys.dao_keyset",4  "value": {"keys": ["aabb..."], "threshold": 2}5}

#Delete

Removes a key from the KV store:

{  "action": "delete",  "key": "config.deprecated_param"}

#Key format

Keys must match the regex ^[a-z0-9_.-]+$:

• Lowercase letters, digits, underscores, dots, and hyphens only.
• Minimum length: 1 character.
• Maximum length: 128 characters (MaxKeyLength).

#Value constraints

#System keys

Keys prefixed with sys. have special validation rules:

#sys.dao_keyset validation

When setting sys.dao_keyset, the value must be a valid DAOKeyset:

• At least one key.
• No duplicate keys.
• Each key must be exactly 64 hex characters (32-byte ed25519 public key).
• Each key must be valid hex (not just 64 characters).
• Threshold must be >= MinDAOThreshold (2).
• Threshold must be <= number of keys.

The DAOKeyset() accessor also enforces MinDAOThreshold=2 at read time, so even a keyset written by an older version is validated on access.

#sys.timekeepers validation

When setting sys.timekeepers, the value must be a valid timekeeper config:

• At least one key.
• Each key must be exactly 64 hex characters.
• Threshold must be between 1 and the number of keys (inclusive).

#KV Store

The KVStore is an in-memory key-value store that holds the accumulated state of all applied operations.

type KVStore struct {    data map[string]json.RawMessage}

#Methods

#ApplyOps

Operations are applied in order. A set overwrites any existing value; a delete removes the key. There is no transaction rollback -- if a block is accepted, all its ops are applied.

1func (kv *KVStore) ApplyOps(ops []Op) {2    for _, op := range ops {3        switch op.Action {4        case "set":5            kv.data[op.Key] = op.Value6        case "delete":7            delete(kv.data, op.Key)8        }9    }10}

#Block hash computation

The block hash is computed over the operations only, not the signatures or other metadata. This is critical because it allows DAO members to sign the same hash independently -- they agree on what the block does, not on who else has signed it.

#Common use cases

#DAO keyset rotation

Adding a new signer and increasing the threshold:

1{2  "ops": [3    {4      "action": "set",5      "key": "sys.dao_keyset",6      "value": {7        "keys": [8          "aabb11...existing1",9          "ccdd22...existing2",10          "eeff33...new_member"11        ],12        "threshold": 213      }14    }15  ]16}

#Timekeeper configuration

Setting up trusted timekeepers for compute lease attestations:

1{2  "ops": [3    {4      "action": "set",5      "key": "sys.timekeepers",6      "value": {7        "keys": [8          "1122...timekeeper_a",9          "3344...timekeeper_b",10          "5566...timekeeper_c"11        ],12        "threshold": 213      }14    }15  ]16}

#Arbitrary configuration

The KV store can hold any governance-related data:

1{2  "ops": [3    {"action": "set", "key": "config.emission_rate", "value": 100},4    {"action": "set", "key": "config.max_lease_days", "value": 365},5    {"action": "delete", "key": "config.deprecated_flag"}6  ]7}

#Op validation

Every operation in a block is validated before the block is accepted: