XAHAU · ON-CHAIN ANCHORING

Xahau URITokenMint Hooks — On-Chain Score Anchoring

Ghost Layer, ScriptMasterLabs' Go routing backend, submits real URITokenMint transactions to the Xahau ledger to anchor data on-chain. SqueezeOS uses this to anchor each agent's ARGUS credit score after every paid call — a self-payment of 1 XAH drop carrying a memo with the score, tier, and timestamp, independently verifiable by anyone.

Quick facts

  • Transaction type: URITokenMint (Xahau transaction type 45), submitted by Ghost Layer's xahau.go.
  • What gets anchored: a memo JSON containing { agentDid, score, tier, anchoredAt }.
  • Cost: a 1-XAH-drop self-payment per anchor.
  • Verification: anyone can independently confirm an anchor at https://xahau.network/tx/<txHash>.
  • Lookup endpoint: GET https://squeezeos-api.onrender.com/api/credit-score/anchor/:wallet

Frequently asked questions

What is a URITokenMint transaction used for here?

It's the on-ledger vehicle Ghost Layer uses to write a small, verifiable piece of data (an agent's updated credit score) to the Xahau chain — URITokenMint lets a memo carry that payload alongside a minimal self-payment.

Can I verify an anchor myself, or do I have to trust SqueezeOS's word?

You can verify independently — every anchor has a real Xahau transaction hash, viewable at xahau.network/tx/<txHash>, showing the exact memo that was written.

Does this require the XAHAU_SEED to be configured?

Yes — anchoring only runs when the server has a Xahau signing seed configured; otherwise the score still updates off-chain but isn't anchored.

Related