Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

🔄Protocol Upgrades

Audience: Nexus and TAP package developers.

Goal: Choose an application package upgrade path and preserve package, identity, business-state, and settlement evidence.

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.

Use the release and network inputs in Developer Setup, and preserve package, identity, business-state, and settlement evidence throughout the upgrade.

Last updated