# INJRC-20

## Standard <a href="#idea" id="idea"></a>

All injective network users could interact with INJRC-20 protocol via sending a transfer operartion with base64 encoded operations in "memo" field

## Operations <a href="#idea" id="idea"></a>

* Create injrc-20 with the deploy function
* Mint an amount of injrc-20's with the mint function
* Transfer an amount of injrc-20's with the transfer function

injrc-20 balance state can be found by aggregating all of these function's activity together.

{% content-ref url="/pages/jkL21atgKR0zdADrminc" %}
[Deploy](/protocol/injrc-20/deploy.md)
{% endcontent-ref %}

{% content-ref url="/pages/Bb6ogVIgCIv1rey80vuS" %}
[Mint](/protocol/injrc-20/mint.md)
{% endcontent-ref %}

{% content-ref url="/pages/7dFSYdItn8VyvbFlTasu" %}
[Transfer](/protocol/injrc-20/transfer.md)
{% endcontent-ref %}

## Notes

* The first deployment of a ticker is the only one that has claim to the ticker. Tickers are not case sensitive (INJS = injs).&#x20;
* If two events occur in the same block, prioritization is assigned via order they were confirmed in the block. (first to last).
* The mint function and the second step of the transfer function are the only events that cause changes in balances.
* The first mint to exceed the maximum supply will receive the fraction that is valid. (ex. 21,000,000 maximum supply, 20,999,242 circulating supply, and 1000 mint inscription = 758 balance state applied)
* Standard limited to uint128
* Maximum supply cannot exceed uint64\_max


---

# Agent Instructions: 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://docs.injs.ink/protocol/injrc-20.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.