Asset information and documents

The asset record

A token's balances are only one part of an asset's information. The platform associates the token with its issuer, asset classification, collateral classification, jurisdiction, descriptive metadata, and supporting documents.

Asset and collateral classifications describe different things. An instrument's type describes what the investor holds; collateral describes what, if anything, supports the obligation. A classification is descriptive data, not a guarantee of asset quality or protection.

Files and on-chain records

Rich descriptions and files are stored outside the token contract. The supported publication flow validates metadata, pins content to IPFS, and prepares the on-chain write for the authorized issuer wallet.

On-chain records associate the token with metadata locations and document hashes. A hash lets a reader check whether the downloaded file matches the recorded version. It does not prove that the statements inside the file are true.

Public information and private evidence

Public asset material can include the description, logo, offering terms, and published reports. Identity documents and private subscription evidence serve different purposes and should not be added to the public document set.

Subscription-specific signed agreements and payment evidence belong to their dedicated workflow. They are not interchangeable with a publicly published agreement template.

Updating and listing an asset

An update requires the appropriate issuer or contract authority. Preparing or uploading a file does not complete the change: the associated on-chain write must succeed, and the indexer must observe it before all views reflect the update.

A new suite is initially unlisted in the public asset directory. Listing is a separate platform-controlled step; deployment or publication of metadata alone does not grant it. An unlisted token may still support authorized operations, so directory visibility should not be used as a proxy for its contract state.