đDrc-20 : Basis Rules
How It Works
Raise your paw, Shiba Scout! đž Let's walk through these crucial points:
Be careful not to send inscriptions to Taproot addresses that aren't Doginal compatible. It would be like telling your dog to fetch a ball you never tossed!
Trading balances might not fully integrate with existing marketplace infrastructures. Keep in mind, the transfer of a mint function never leads to a balance change.
Each transfer inscription is akin to a one-time fetch command; it can only be used once.
The first ticker to be deployed claims the name, much like the quickest pup to the toy! Remember, tickers are case insensitive (DRC = drc).
If two events occur in the same block, the order of confirmation in the block determines who fetched first.
Mint a transfer inscription to yourself first to secure your balance.
For public drc-20 mints, we're following the 'first fetch wins' approach, just like bitcoin punks / .sats names.
The mint function and the second step of the transfer function are the only actions that cause changes in balances.
The first mint to go over the max supply gets the fraction that's within bounds. Imagine a 21,000,000 toy limit, 20,999,242 toys in circulation, and a 1000 toy mint inscription = 758 toys added to the game.
Mint function inscriptions don't need padding!
Spending a Doginal on transaction fees is like throwing a toy that doesn't exist. If it happens during the inscription process, we'll just ignore it. If it happens during the second phase of the transfer, it's like the toy comes back to the sender's pile.
You can't have more than 18 decimals (default), just like you can't split a dog toy into infinite pieces.
Our standard operates within a numerical limit, referred to as uint128. (340 undecillion) Picture this as the maximum number of toys your dog can play with at once.
The maximum supply of any token can't exceed the value of uint64_max. (18.4 quintillion) This is like a rule that caps the total amount of a specific type of toy in circulation.