Control Surfaces

Control surfaces are where practical authority still sits once the product story is stripped away.

Use this lens when something looks open at the UI layer but the real leverage still lives in a few stubborn chokepoints:

• verifier or validator selection
• pause, veto, or emergency-stop rights
• bridge or token-pool admission
• rate limits, quotas, or routing defaults
• upgrade keys, gateway policy, or attestation services

Curated comparison set

• Bridge and interop control planes: cctp and chainlink-ccip
• Visible-account versus hosted-signer custody control: safe and fireblocks
• Wallet-session control: walletconnect
• Payment and settlement routing authority: open-payments

Focused traversal notes

• bridge-control-planes
• wallet-and-custody-control-planes
• payment-routing-and-settlement-operators
• rollup-operator-control-planes

Useful comparison question

When a product claims to be open or neutral, where does practical authority still pile up: bridge admission, signer workflow, payment routing, or chain operation?

Adjacent lens

• permissions-and-policy
• Keep the comparison budget short. The point of this note is to force the authority question, not to become a directory of every place authority can hide.