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

Community realm. Read the code first. Community realm, deployed by its author. Read the code before you interact or send coins.

README.md

2.58 Kb · 52 lines

Key-Value Vault

⚠️ Experimental — generated with no human supervision. This realm was produced automatically by an MCP-driven agent to exercise the gno MCP server and tooling, and to generate test content for gno compilers, linters and formatters. Not audited. Not for production. Full context & folder README: r/moul/x/daily


A per-address key-value store on gno.land. Each caller gets their own private namespace; only the owner can set or delete their own entries. The root render lists every address that owns a vault with its entry count, and the /<address> path renders that address's keys and values in a table.

Realm path: gno.land/r/REPLACE_ADDR/vault

Example calls

# Store a value in your namespace
Set("greeting", "hello")

# Overwrite it
Set("greeting", "hi there")

# Remove it (aborts if the key doesn't exist)
Delete("greeting")

Render

  • Render("") — table of all addresses with a vault and their entry counts.
  • Render("/g1abc...") — table of that address's keys and values.

Part of moul/gno-contracts — moul's versioned gno.land contracts. See the repository for the full catalog, build/test tooling, and usage.

On mainnet: deployment status transactions unique callers deployed revision

Dependency graph:

gno.land/r/nym-moultest123/x/daily/vault/v0 dependency graph

🧪 Highly experimental — potentially vibe-coded. Not audited; may break, change, or be removed at any time. Do not use with anything of value. Full disclaimer: DISCLAIMER.