Publishing rules and asset permits
Freeze rules for one exact target and explicit automatic execution bounds.
Step by step
- Under Where rules apply, bind the saved revision to a specific Node, wallet or address. A binding does not publish rules. Select it from the list; older bindings show their own pinned revision.
- For withdrawal rules, open the saved graph and review its conditions, selected approvers and target. Publication applies that exact revision, independently of unsaved editor changes. Unsupported blocks and empty approval rosters cannot be published.
- For automatic actions, add a separate permit for each exact asset, up to 32. Each permit selects its API client, network, up to 32 distinct recipients, principal and fee caps, lifetime budgets and validity. The same asset cannot appear twice, even for different clients. Date inputs use local time. Every applicable rule still evaluates normally; a token permit never bypasses another asset condition.
- Confirm the review and publish with the current platform confirmation. Publication does not start a transfer itself. After a lost reply, read the state or resume the original publication: its identifier and bounds remain unchanged.
- Revoking publication or removing a binding requires typed DELETE and current rights. A revoked publication cannot be reactivated; create a new binding for new rules. Already admitted, signed or uncertain operations retain their original recovery path.