> For the complete documentation index, see [llms.txt](https://documentation.record.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.record.nexus/usdrecord-token.md).

# $RECORD Token

The native token powering ecosystem governance, risk-sharing, and incentive alignment:

* Governance (voting, proposals).
* Risk underwriting via Guard (in progress).
* Credibility signaling within Pools (in progress).
* Collateral commitments from issuers (in progress).

The $RECORD token strategically aligns stakeholder interests, embedding governance directly into the protocol's financial infrastructure.

#### $RECORD as a Multichain Token

$RECORD is deployed as a multichain token powered by LayerZero, an omnichain interoperability protocol that enables native token messaging across blockchains. This allows $RECORD to maintain a single, unified total supply across multiple chains, rather than fragmented wrapped versions.

To ensure seamless, secure movement of $RECORD between supported networks, we use Stargate, the liquidity transport layer built on LayerZero. Stargate facilitates native asset transfers with instant finality, deep liquidity, and minimal slippage.

#### How it works:

1. LayerZero provides the messaging layer for verifying and executing token transfers across chains.
2. Stargate handles the actual bridging of $RECORD tokens using unified liquidity pools.
3. Users can move $RECORD from one chain (e.g., Plume) to another (e.g., Solana or Base) without wrapping or manual mint/burn steps.
4. The RECORD token contract remains fully synchronised across chains, preserving governance and utility wherever the token travels.

#### **$RECORD Contracts**

* #### [Plume Contract](https://phoenix-explorer.plumenetwork.xyz/token/0x3c48130227B657630e5D30F136A8CBB110640aA5?tab=token_transfers)
* #### [Solana Contract](https://solscan.io/token/nMRuwNqQsTt47yyQ5LqDtXgeegvyu5kNvCJQ369KKp5)
* #### [Base Contract](https://basescan.org/address/0xE642657E4F43e6DcF0bd73Ef24008394574Dee28)
* #### [Stargate Bridge](https://stargate.finance/bridge?srcChain=base\&srcToken=0xE642657E4F43e6DcF0bd73Ef24008394574Dee28\&dstChain=plumephoenix\&dstToken=0x3c48130227B657630e5D30F136A8CBB110640aA5)

#### **$RECORD links**

* #### [CoinMarketCap](https://coinmarketcap.com/currencies/music-protocol/)
* #### [CoinGecko](https://www.coingecko.com/en/coins/music-protocol)
* #### [GitHub](https://github.com/orgs/Music-Protocol/repositories)
* #### [Audit](https://certificate.quantstamp.com/full/music-protocol-token-staking-and-dao/3cb260d9-3d7c-47a8-b247-6ca4ce733ab6/index.html)<br>


---

# 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://documentation.record.nexus/usdrecord-token.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.