> For the complete documentation index, see [llms.txt](https://runelink.gitbook.io/runelink-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://runelink.gitbook.io/runelink-doc/runelink-protocol-extension/on-chain-rendering-functionality.md).

# On-Chain Rendering Functionality

RuneLink will implement on-chain rendering based on extended fields, modularizing the rendering environment and inscribing it on the blockchain to achieve true on-chain rendering. Assets under the RuneLink protocol can seamlessly integrate with the Ordinals protocol environment, facilitating decentralized 3D model rendering on the blockchain.

**Compared to conventional inscriptions:**

RuneLink inscriptions achieve modular rendering references without needing a centralized platform, and will expand more rendering components in future improvements, including effects like material self-illumination (already implemented), glow, ray tracing, and dynamic particle effects.

**Compared to BRC420:**

Unlike BRC420's centralized rendering logic, where assets listed on third-party exchanges or stored in user wallets cannot display actual models due to the lack of full-chain rendering support—viewing only the inscription ID and related info—RuneLink assets can be viewed and interacted with in any Ordinals-compatible marketplace.


---

# 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:

```
GET https://runelink.gitbook.io/runelink-doc/runelink-protocol-extension/on-chain-rendering-functionality.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.