Runes ​

Etching ​

Etching is the process of creating a new Rune and setting its properties, similar to the deploy operation in brc20.

Parameters ​

• Rune (Ticker): The name you set for the etched Rune. The minimum character count for the Rune name you can deploy varies with block height, and it's recommended to choose a ticker name of at least 13 characters.

• Symbol: A rune's currency symbol is a single Unicode code point, for example $, ⧉, or 🧿, displayed after quantities of that rune. If a rune does not have a symbol, the generic currency sign ¤, also called a scarab, should be used.

When etching a Rune on the GeniiData platform, you have the option to select between Fair Launch and Fixed Supply modes.

Fixed Supply

Set the supply and divisibility of the Rune to be deployed. The corresponding Rune tokens will be minted to your wallet address after a successful etching.

Fair Launch

• Amount: Each mint transaction generates a fixed amount of new units of a rune, with a maximum limit per mint. (During etching, the 'amount' field represents the precise numerical value, while the displayed amount in the index may differ due to divisibility processing.)

• Cap: The number of minting times which minting remains valid after its deployment.

• Premine: The etcher of a Rune may optionally allocate to themselves units of the Rune being etched; if no allocation is desired, leave it blank.

• Advanced Options:

  • Divisibility: A Rune's divisibility is how finely it may be divided into its atomic units. Divisibility is expressed as the number of digits permissible after the decimal point in the amount of Rune.

  • Height: Optional. Specify the valid block height range for Rune minting. If not specified, there is no time limit for minting the Rune token.

  • Offset: Another parameter to specify the valid minting time for Rune. Instead of specific block heights, offset refers to the number of blocks to wait after the 'etch' transaction confirmation before starting minting, as well as the number of blocks to wait before ending minting.

  

Commit and Reveal ​

To prevent front-running, each etching operation is divided into two steps: commit and reveal. Reveal must be submitted 6 blocks after commit transaction confirmation to be considered valid. Separate fee rates can be set for Commit and Reveal.

Note: Once the order is submitted, the reveal fee rate can only be reduced, not increased. Therefore, for every etching order, it's advisable to opt for a higher fee rate to avoid being stuck in mempool due to network fluctuations after the revealing transactions are broadcast .

• When selecting Auto Reveal, the reveal transaction will automatically be submitted after 5 confirmations of the commit transaction. (If the block height has not reached #840000, it will be submitted on or after block #840000).

• Disabling Auto Reveal means the reveal transaction will not be automatically submitted. When you wish to proceed with the reveal operation, locate this transaction in the "orders" page, click "Resume" to broadcast your reveal transaction; If necessary, you have the option to lower your reveal fee rate by making edits to the settings. Note that the fee rate can only be decreased here, not increased.

Even when auto-reveal is enabled, it is still possible to manually pause by clicking the 'pause' button. (This action must be taken before the reveal transaction is broadcasted because once the transaction is broadcasted, it cannot be canceled.)

Mint ​

To locate the mintable Rune, navigate to the Mint Rank section on the homepage or the Rune list on the Index page. Click on "Mint" and adjust the count for bulk minting. Afterward, submit your mint order. Before submitting the order, remember to check the cap progress and block progress.