📘
XCHandles Docs
  • XCHandles FAQ
  • Techincal Manual
    • Pricing Puzzles
    • State Scheduler
    • XCHandles
      • The Register Action
      • The Refund Action
      • The Extend Action
      • The Expire Action
      • The Oracle Action
      • The Update Action
    • DIG Reward Distributor
      • The Sync Action
      • The New Epoch Action
      • The Add Incentives Action
      • The Commit Incentives Action
      • The Add Mirror Action
      • The Remove Mirror Action
      • The Withdraw Incentives Action
      • The Initiate Payout Action
Powered by GitBook
On this page
  1. Techincal Manual

XCHandles

A decentralized address book for the Chia blockchain

PreviousState SchedulerNextThe Register Action

Last updated 3 months ago

From a technical standpoint, XCHandles is, at its core, a HashMap<bytes32, bytes> that transforms the hash of a handle (i.e., sha256tree of the handle string) to a series of bytes, usually representing a singleton launcher id. Entries usually point to a name NFT launcher id, which contains details such as 'receiver address' in its metadata (i.e., the address wallets should send assets to if the handle is used in the address field). Each entry can only be updated or transferred by its owner. Entries also have expiration dates - after registration, anyone may extend the validity of a handle. After the handle expires, it enters an auction process handled by another puzzle (set to the 'exponential premium' puzzle at launch).

Before proceeding, it's highly recommended that you familiarize yourself with the primitives in the , as XCHandles uses them in more complex ways.

Note that the XCHandles registry also includes a .

Written by from on Feb 15th, 2025.

CATalog docs
delegated state action
yakuhito
FireAcademy.io