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

# Technical Disclosure

Published technical information and disclosure requirements for RLY.

## Technical Disclosure

This page separates published token information from details that remain pending official confirmation. Participants must rely only on identifiers published through official RescueLoyal or Project Rescuecoin channels.

### Published framework

The [Tokenomics](/rescueloyal.io-docs/token-and-protocol/tokenomics.md) framework identifies:

* **Token:** RescueLoyal (`RLY`)
* **Network:** DANNYCHAIN
* **Standards:** DAN-69 and DAN-5069
* **Fixed supply:** 1,000,000,000,000 RLY

### Network confirmation

RLY is confirmed for DANNYCHAIN under the DAN-69 and DAN-5069 standards. The roadmap's historical implementation and verification milestones apply to this network.

The authoritative contract address, chain identifier, and verification location must be published explicitly. Until then, users must not infer deployment details from roadmap references or third-party listings.

### Pending technical disclosures

The following information requires official publication:

* contract address and chain identifier;
* token decimals and verified source location;
* audit scope, auditor, report, and remediation status; and
* any bridge, wallet, exchange, staking, or platform integration.

### Security guidance

Verify the network and contract address before interacting with RLY. Do not rely on unsolicited messages, search-engine advertisements, or unverified social-media posts.

{% hint style="warning" %}
No contract address, audit report, or integration is confirmed by this document.
{% endhint %}


---

# 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://rescueloyal-io.gitbook.io/rescueloyal.io-docs/token-and-protocol/technical-disclosure.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.