🔄Protocol Upgrades
Use Protocol Upgrades and Compatibility to classify a change before choosing a package upgrade path. A successful protocol release does not by itself validate an update to a registered Tool, DAG, TAP, skill, Task, payment, or business object.
Upgrade an On-Chain Tool and Preserve Its Identity for candidate verification, a compatible package-pointer change, and replay of the baseline operation.
Upgrade a TAP Package for package, Tool, DAG, and application-state checks.
Use the release and network inputs in Developer Setup, and preserve package, identity, business-state, and settlement evidence throughout the upgrade.
Last updated

