registry-autobase-patterns

Create an Autobase instance with open, apply, and close callbacks where open returns a HyperDB view with extension set to false. Define operations with Hyperdispatch, route them through a Router in the apply function, and bootstrap additional writers using the autobase key.

Call base.addWriter only from within the apply function by appending an add-writer operation encoded with Hyperdispatch. Wait for the new writer's is-indexer event before it can participate in consensus and accept writes.

This happens when store.replicate(conn) runs before the ProtomuxRPC handler is registered, causing the remote's session message to arrive before the protocol handler exists. Always create the ProtomuxRPC instance first, then call store.replicate(conn).

No, Autobase is incompatible with the Hyperbee extension. Initialize the view with extension set to false and autoUpdate set to true, otherwise the multi-writer linearization will not work correctly.

Blind pairing uses invite codes to add new writers to an Autobase, while blind peering synchronizes read-only mirrors without write access. The QVAC registry server uses blind peering for mirror synchronization, not blind pairing.

Copying a live Corestore corrupts the underlying hypercores because RocksDB holds an exclusive lock and data may be mid-write. Use blind peers or read-only replicas that replicate the view over Hyperswarm as the safe backup strategy.