Skip to main content
Execution boundary / verify before trustWallet decision · chain authority · indexed delay
IdentityChain + addressConfirm the exact market before reading any other signal.
ExecutionBound the tradeReview input, minimum output, price impact, fees, and deadline.
CustodyRead the lock modelTime-locked and permanently locked liquidity are different.
PresentationExpect data lagOnchain confirmation can precede balances, charts, and labels.
Creator metadata, social links, indexed history, and holder views are signals—not signing authority.

​
Before signing

  • Match the chain and token address.
  • Check the active venue and lifecycle state.
  • Read exact input, minimum received, price impact, and fees.
  • Refresh stale quotes.
  • Treat metadata, social links, and holder data as untrusted signals.

​
Liquidity custody

Liquidity custody differs by chain. A position can be time-locked, permanently locked, or withdrawable under specific rules. Read the network page and live lock state; do not collapse every model into “liquidity burned.”

​
Product state

The chain can confirm before balances, charts, or lifecycle labels refresh. Avoid treating a data delay as a failed transaction. Limit orders add keeper availability and Permit2 allowance to the risk model. The signed minimum output and deadline remain the hard execution bounds.
Last modified on August 2, 2026