Skip to main content
SuperformOS Merkle Trees — hook configs, roots, and proof publishing Merkle Trees are the authorization layer for keeper and strategy execution. A keeper can only execute a hook when the hook call matches a leaf in an authorized merkle tree. Public SuperVault detail pages expose hook and proof context as read-only inspection tabs. Drafting, activating, generating, syncing, and publishing remain manager workflows in Operate. The operational flow is:
  1. Draft a root configuration.
  2. Activate the configuration version.
  3. Generate a merkle tree from the active config.
  4. Primary manager proposes / publishes the root onchain.
  5. Publish the proof artifact for consumers.

​
Hook Configs

Hook configs define which hook + parameter combinations the vault authorizes. When creating a config, choose hooks from the registry and set inspect parameters such as:
  • yield_source — target yield source address.
  • token — token address.
  • oracle — oracle address.
  • Freeform hook parameters.
Each parameterized row becomes a merkle leaf. Keepers must supply the matching proof at execution time.

​
Activate Config

Only one config version is active at a time. Activating a config selects the version used for the next tree generation. Activating a config does not update the onchain root by itself. It selects what Erebor will generate next.

​
Generate Tree

Generation is asynchronous:
A 409 Conflict means generation is already in progress for the vault. The generated tree includes:
  • Root hash.
  • Leaf count.
  • Config hash / version.
  • Leaf details and proof paths.

​
Sync Root Onchain

The Sync action compares generated tree state to onchain state and returns the next action:
Strategies and emergency exits depend on active merkle withdrawal hooks. A yield source can be whitelisted but still unavailable for execution if the active merkle root does not authorize the required hook path.

​
Publish Proof Artifact

Publishing makes the active proof set available to integrators, keepers, and frontends without Erebor authentication. The app exposes this as a primary-manager-gated Publish or Re-publish action on the active tree. Once the current artifact matches the active tree, the button state becomes Published.
Publishing is separate from syncing. Sync updates the protocol root; publish exposes the proof artifact. A published response includes: When is_stale is true, re-publish before relying on the artifact for execution. Even when is_stale is false, verify root_hash against the onchain SuperVaultAggregator state; offchain publish and onchain root sync are independent steps.

​
Emergency Exit Dependency

Emergency liquidity exit requires an active withdrawal hook for the target yield source. If the active config has no matching withdrawal hook or the proof artifact is missing the leaf, the Pause page cannot arm that source until the merkle configuration is fixed.

​
API Reference