> For the complete documentation index, see [llms.txt](https://ninjalerts.gitbook.io/bitcoin-ordinals-pizza-ninjas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ninjalerts.gitbook.io/bitcoin-ordinals-pizza-ninjas/upgradability.md).

# Upgradability

<div data-full-width="true"><figure><img src="/files/QsNl5rGl2oeUbH2l9N1p" alt=""><figcaption></figcaption></figure></div>

When it comes to upgradability, there has traditionally been a trade-off involving trust. However, this is changing. While smart contracts are typically upgradeable unilaterally by developers, the Sat Endpoint on Ordinals introduces a new structure. Here, developers can release upgrades, and holders have the option to opt into these through re-inscription. This is facilitated by our loader.js file, where the sat endpoint references the latest inscription on the holder's satoshi. This enables holders to select the loader.js file they wish to use for their Ordinal asset.

Our development team can issue upgrades, including new features and fixes for compatibility issues or other unforeseen problems, by re-inscribing an updated version of the loader.js file onto the same sat. Loader.js essentially serves as a directory of JavaScript files used in the project. Over time, we plan to expand this directory and modularize our codebase into distinct components.

We believe this approach is not only elegant but also offers significant advantages over the smart contract paradigm. On Ethereum and other chains, the options are limited to either having a contract that can be unilaterally upgraded or requiring developers to request holders to transition to a new smart contract, effectively splitting the collection. In our model, holders remain within the same collection and have the flexibility to upgrade their assets to the version they prefer, or to opt out entirely.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ninjalerts.gitbook.io/bitcoin-ordinals-pizza-ninjas/upgradability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.