> For the complete documentation index, see [llms.txt](https://docs.gnodi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gnodi.io/documentation/the-constitution/article-xii-protocol-changes-and-technical-upgrades.md).

# Article XII: Protocol Changes and Technical Upgrades

**Section 1: Technical Proposal Requirement**

Material protocol changes, validator-impacting changes, Delphi Node-impacting changes, tokenomics-impacting changes, security-critical upgrades, and major application integration standards must be submitted through a technical proposal process.

**Section 2: Technical Review**

Governance may require technical review by qualified developers, auditors, validators, Delphi Node\
operators, security reviewers, or other technical experts before a technical proposal proceeds to vote.

**Section 3: Emergency Patches**

Emergency patches may be implemented without prior full governance approval only when necessary to address critical vulnerabilities, network attacks, legal compliance emergencies, or material threats to the Gnodi Blockchain. Emergency action must be narrowly tailored, documented, and submitted for post-action governance review as soon as reasonably practicable.

**Section 4: No Hidden Protocol Changes**

No Service Provider, developer, validator, Council member, or other participant may intentionally\
implement a material protocol change that bypasses governance approval unless emergency authority applies.

**Section 5: Upgrade Records**

All material technical upgrades shall be documented in a public change log or governance record, subject to temporary security-related confidentiality where necessary.