Search Apps Documentation Source Content File Folder Download Copy Actions Download State String Boolean Number Struct Map Slice Pointer Function Closure Reference Nil Package Type Interface Unknown

README.md

2.61 Kb · 60 lines

gno.land/r/moul/toolbox

A home for small utilities on gno.land. One page listing every tool; each tool is its own realm at r/moul/toolbox/<slug>.

A tool composes contracts that are already on chain and renders the answer, so you open a page instead of composing a query. The toolbox adds the view, not the data.

/r/moul/toolbox                  the directory
/r/moul/toolbox?tag=identity     the directory, filtered to one tag
/r/moul/toolbox:usernames        one tool

The catalog is compiled in, and that is the interesting part

The obvious design is the opposite one: each tool calls Register on this realm from its own init, and the directory assembles itself. That design is unavailable here, and the reason is not a preference.

private = true buys redeploy-in-place at the same path and costs the ability to be imported: the type checker refuses any realm importing a private one (ImportPrivateError). A private hub therefore cannot be imported by its tools, and a hub that accepts registration has to be public. A public realm can never be redeployed at its own path, so a public hub would be frozen at v0 and the first bug in it would move the directory's URL.

A stable URL is the whole point of a directory, so the trade goes the other way: everything here is private and redeployable, and adding a tool is one entry in tools plus a redeploy. The catalog is rebuilt from source every time, so the redeploy wipe costs nothing. There is no state to lose.

p/moul/toolbox's Catalog stays mutable for whoever wants the other trade.

And that is also why the path carries no /vN

/vN exists because a public path can never be redeployed, so a fix there means a new path. This realm is private and redeployable, so its version could never increment and the suffix would be a promise it cannot keep. The URL is the product here, bookmarked the way a blog post is, so it is the one that should not carry it. unversionedContracts in tools/gnocontracts/model.go is the allowlist, with the reason per entry.

Adding a tool

One entry in tools, then redeploy. buildCatalog panics at deploy, not at read, if the slug and the path disagree, so a copy-pasted entry that kept the wrong path fails the publish rather than shipping a dead link.

The read API

Flat strings, because a nested value inside a persisted object prints as an opaque ref(...) over vm/qeval:

1gnokey query vm/qeval -remote https://rpc.gno.land \
2  -data 'gno.land/r/moul/toolbox.Slugs()'
3gnokey query vm/qeval -remote https://rpc.gno.land \
4  -data 'gno.land/r/moul/toolbox.PathOf("usernames")'