xUDT, or Extensible User-Defined Token, is Nervos CKB’s standard for fungible tokens that need custom validation logic. It builds on the simpler sUDT model and lets an implementation attach additional Scripts for rules such as minting conditions or transfer restrictions. [1]
| Protocol documentation | Open documentation |
|---|---|
| Directories | Nervos Ecosystem Directory |
xUDT and sUDT
Both sUDT and xUDT represent fungible token balances using CKB Cells. The simpler sUDT model provides a predefined validation approach. xUDT is designed for cases where an application needs token-specific rules that go beyond that baseline; its extension Scripts can validate how token state changes during a transaction. [1]
For example, a token’s scripts could enforce a maximum supply, impose time-based transfer conditions, or allow minting only after a specified cryptographic check. These are possible design patterns in the documentation, not features that every xUDT token automatically includes. The behavior depends on the particular token and its deployed scripts. [1]
Why a project might use it
A project that needs custom on-chain rules can encode some of those checks into the token’s validation path rather than relying only on an issuer’s website or a separate service. That can make policy inspectable at the transaction level, but it also makes the token’s code and deployment choices important. A ticker or logo does not tell users what an xUDT contract permits.
Questions for users and developers
Before interacting with an xUDT asset, identify its issuing project and Type Script, check the token’s official documentation, and confirm that the wallet or exchange supports that exact asset. A token standard describes a compatible structure; it does not certify an issuer, promise a fixed supply, guarantee exchange listings, or make tokens interchangeable across implementations. Developers should document extension behavior and test how it handles minting, transfers, and edge cases.
See Also
Sources
Last updated: November 4, 2026.