Skip to content

OIP v0.6.1

Choose a tag to compare

@jay-oraclizer jay-oraclizer released this 10 Nov 11:55
· 8 commits to main since this release
v0.6.1
0806876

OIP v0.6.1 extends wire version 6 with state commitment synchronization and enables Write in the Ed25519 reference configuration.

Added

  • SyncCommitment records an initial snapshot, an incremental commitment or an authorized full resynchronization for one asset and origin domain. CurrentCommitment reads the selected entry with its current authority epoch and revision.
  • Binary source attestations bind the deployment, asset, origin domain and event, source epoch and roster, position, commitment and predecessor. The reference source signs the record it reads from its authenticated journal and independent selection store.
  • SyncCommitment uses STATE_COMMITMENT_SYNCED (29), STATE_COMMITMENT_MISMATCH (39), STATE_COMMITMENT_STALE (40), and SOURCE_ATTESTATION_REJECTED (41). The exact authorized retry returns the retained result. Responses to earlier operations apply the existing unknown-code rules to these numbers.
  • The version 6 extension rules specify how to append an opcode within an existing family and distinguish an unknown opcode from a known operation excluded by the configured profile.

Reference behavior

  • Write uses its existing LOCK_MANAGEMENT opcode, operand layout and DATA_UPDATED response. A successful write records its value, next asset version and exact result in the selected authority image.
  • Generic mutable entry points enforce the selected ordered maintenance boundary.
  • The reference configuration accepts 28 of the 33 operations. The v0.5 correspondence records the disposition and owner of each remaining item.

Verification

  • Rust, Go and the exported Isabelle transport model matched all seven recorded fields across 692 transport vectors, including 512 generated cases. The versioned fixture directory preserves the v0.6.0 corpus.
  • The Rust signed-response paths matched the exported model across 261 standard inputs. The compatibility checks also compared 144 transport inputs, 115 signed client inputs and 10 sender inputs on the checked candidate.