Account details
rUZXZuqhjRP2ouHTmBncp2pmntt2WmNo9c

rUZXZuqhjRP2ouHTmBncp2pmntt2WmNo9c
Alert KYC Issuer Blackholed Deleted Genesis AMM -
Inactive account
The account can be activated by sending at least 1 XAH to this address.
Learn about reserves
Balance
0 XAH
Status
Un-activated
Deleted account
This account has been deleted, it was first activated using - transaction.
You can view this account transaction history.
Balance
0 XAH
Status
Deleted
Balance(s)
XAH
spendable XAH
reserved XAH
Domain
Settings & Flags
Loading...

Help

Help section is coming soon. In the meantime, you can check out Xahau documentation for more information.

About

The Namespaces & States Explorer helps you explore and understand how data is stored and used by hooks on the Xahau blockchain.

In this section, you can:
  • View the namespaces connected to an account
  • See the data (state) stored inside them
  • Define how that data should be displayed (using projections / ABI)
  • Publish ABI and make it available for everyone

Hook Namespaces

Think of a hook namespace as a database or folder that holds all the data for a specific feature or hook.

Developers use namespaces to keep their hook data organized. Each namespace has a unique ID (usually generated from a name chosen by the developer), so it can always be found and used reliably.

Each hook namespace has a unique name it is usually SHA256 of defined name set by Hook developer. Hook namespaces also provide a way to manage the state associated with hooks, allowing developers to store and retrieve data related to their hooks in a structured way.

Hook States

Hook states are the actual pieces of data stored inside a namespace.

Each piece of data is stored as a simple key-value pair:
  • The key is a unique identifier (like a label)
  • The key can be looked up directly via single ledger command
  • The value is the data itself
  • The value size limitation can be expanded (see ExtendedHookState)

This data can represent things like settings, user information, counters, or anything else a hook needs.

By storing and updating this data, hooks can react to changes and behave dynamically.

Projections (ABI)

The data stored in hook states is often in a raw (binary) format, which can be hard to read.

Projections in this explorer solve this by defining how to interpret and display that data in a human-friendly way by defining structured ABI (Application Binary Interface).

You may define projections for HookStates in this tool, and once published, they will be available in the explorer for easy access and interaction with the state data.