v0 state

Path

Path is this realm's package path, which every denom it issues embeds.

MinBase

MinBase and MaxBase bound a base denom name. The chain enforces exactly this (\`isValidBaseDenom\` in the banker stdlib): a lowercase letter, then 2 to 15 more lowercase letters or digits. Validating here rather than letting the banker abort is the difference between a usable error and a stack trace.

MaxBase

MinBase and MaxBase bound a base denom name. The chain enforces exactly this (\`isValidBaseDenom\` in the banker stdlib): a lowercase letter, then 2 to 15 more lowercase letters or digits. Validating here rather than letting the banker abort is the difference between a usable error and a stack trace.

pair

byBase

// base name -> \*pair

byKey

// grc20reg key -> \*pair

bases

// creation order, for a stable Render

home

// this realm's address: where every escrow sits

init.8

Home

Nativeify

Nativeify creates the native counterpart of a GRC20 registered in \`r/nt/grc20reg\`, and returns its denom. It issues nothing: [Wrap](#Wrap) does that. \`base\` is the part of the denom after the colon, yours to choose, unique in this realm and in the chain's charset. One native denom per underlying token: a second one would double the chain's per-denom storage for no new capability, and realm-denom balances live under their own store keys, which are not gas-metered.

Wrap

Wrap escrows \`amount\` of the underlying and issues the same number of native coins to the caller. You must \`Approve\` this realm's address on the underlying token first, through that token's own realm. Until you do, this realm has no authority over your balance at all, and Wrap fails with "insufficient allowance", which is the system working.

Unwrap

Unwrap destroys the native coins attached to this call and releases the same number of underlying GRC20 units to the caller. ### Why you have to send the coins rather than let this realm take them {#hdr-Why_you_have_to_send_the_coins_rather_than_let_this_realm_take_them} This realm holds a \`BankerTypeRealmIssue\` banker, and \`RemoveCoin\` takes an arbitrary address, so it could delete the caller's coins directly and save them a flag. It does not, and the reason is worth stating where somebody copying this will read it: a realm whose normal operation is to remove coins from addresses that did not hand them over has no way left to demonstrate that it only ever does so consensually. Every \`RemoveCoin\` here names this realm's own address, which anybody can check by reading the source, and the coins get to that address the only way a native coin ever moves, by their holder pushing them. So: attach them. -send <amount>/gno.land/r/moul/x/nativeify/v0:<base>

Denom

Denom returns the denom this realm issues for a base name.

TokenKey

TokenKey returns the grc20reg key of the underlying behind a base name.

Bases

Bases returns every base name this realm issues, in creation order.

Solvency

Solvency returns what is escrowed and what is issued for a base name. They are read from two different places on the chain, the GRC20 ledger and the bank, and this realm's own bookkeeping is not consulted for either: if they ever disagree, the disagreement is the answer.

IsSolvent

IsSolvent reports whether every coin issued for a base name is backed. It allows escrowed > issued, which is what a donation to this realm's address looks like and cannot hurt anybody, and refuses the reverse.

Underlying

Underlying returns the underlying token behind a base name, for a caller that wants its name, symbol or decimals.

mustPair

assertBase

assertBase applies the chain's own base-denom rule before the banker does, so the caller reads a sentence instead of a stack trace.

Render

Render lists the pairs. \`?\<base>\` shows one.

renderIndex

renderOne