Valence Protocol primary sources — 2026-05-08

Classification takeaway

Valence Protocol is best treated as cross-chain execution and automation infrastructure for preconfigured multi-party programs rather than as a bridge, intent marketplace, or vault product. Its key mechanism is the split between program design and later execution: builders define accounts, libraries, subroutines, authorizations, and connector assumptions ahead of time, then Authorization and Processor contracts enforce those choices on each domain. That makes Valence especially useful for reasoning about where control sits when cross-chain workflows are compiled into bounded execution units instead of being discovered live by solvers.

Primary sources reviewed

1. Docs root / introduction — https://docs.valence.zone/

   • Best concise first-party framing of the protocol.
   • Used to confirm Valence positions itself as a unified environment for trust-minimized cross-chain DeFi programs that can often be deployed from configuration.

2. Programs overview — https://docs.valence.zone/components/_overview.html

   • Useful for establishing the high-level split between on-chain execution and off-chain execution via the ZK coprocessor.
   • Helps classify Valence as an execution environment rather than a single product flow.

3. Programs and authorizations — https://docs.valence.zone/components/programs_and_authorizations.html

   • Most important architectural source for the core mechanism.
   • Defines programs as arrangements of accounts and libraries across domains, subroutines as domain-bounded vectors of functions, and authorizations as the way creators constrain who may trigger what.

4. Authorization & processors overview — https://docs.valence.zone/authorizations_processors/_overview.html

   • Useful for confirming that Authorization and Processor contracts are the foundational execution pair.
   • Highlights the design goal of centralizing entry, permissions, and execution handling.

5. Authorization contract details — https://docs.valence.zone/authorizations_processors/authorization_contract.html

   • Important because it exposes the real control surface: label-based authorizations, sender checks, ZK authorizations, callback handling, and environment-specific permission enforcement.
   • Also useful for seeing how CosmWasm and EVM implementations differ.

6. Connectors — https://docs.valence.zone/authorizations_processors/connectors.html

   • Critical for understanding that cross-domain execution depends on explicit connector choices, currently Polytone for CosmWasm and Hyperlane for EVM.
   • Useful because it makes inherited relay and interoperability assumptions visible.

7. ZK overview — https://docs.valence.zone/zk/_overview.html

   • Best concise source for the offchain-computation side of the design.
   • Shows that Valence also aims to offload complex or private computation into a proving system rather than keeping all logic purely onchain.

8. GitHub repository landing page — https://github.com/timewave-computer/valence-protocol

   • Useful as a public code and status surface.
   • Important because the repo description and README note that the project is no longer under active development, while still framing which toolchain pieces stabilized.

9. Repository README — https://raw.githubusercontent.com/timewave-computer/valence-protocol/main/README.md

   • Best short source for the project’s own status statement and technical shorthand.
   • Confirms the resource-model framing, Cosmos/EVM support, and SP1-backed ZK-coprocessor direction.

Why it stays in the active corpus

• Strong comparison class for systems where authority is embedded in predeclared execution policy rather than live market routing.
• Useful bridge concept between vault-control planes, cross-chain automation frameworks, and verifiable offchain-compute stacks.
• Adds a design pattern that helps compare Veda/Mellow-style bounded execution, Mitosis-style multi-domain coordination, and Epoch-style orchestration against a more explicitly compiled authorization-processor model.