Native assets

Native assets are shares, bonds, stablecoins and other assets issued on the TensorCash chain itself. They are held and sent in the same way as $TSC, from the same wallet, without any custom contract code. The rules of each asset are set when it is issued, and the network checks them on every transfer [1]. Native assets are live on mainnet.

Issuing an asset

Issuing starts with reserving a ticker, the name of the asset on the chain, which can already be done before a project launches. Reserving a ticker requires a deposit of at least 5 $TSC, which is returned to the issuer once the fees paid on the asset reach a threshold the issuer sets, which is at least the deposit. This works as a filter that keeps throwaway tickers off the chain, without a listing fee [1]. If the asset never trades, the deposit stays locked.

Under a ticker, an issuer can create child assets, for 0.0001 $TSC each. One ticker can then hold many related assets, such as vesting tranches for a team or a series of bonds. The options on the network difficulty already work this way, with a call and a put issued as two child assets under the ticker COMPUTE [2].

An asset can be loyalty points for a café, for example, or shares in a company that only verified investors may hold.

Issuance rules

Units are the individual pieces of an asset, like single shares of a company. At issuance, the issuer declares the rules for those units [1].

After that, the issuer acts through a dedicated control unit on the chain, the Issuer Control Unit (ICU), which holds the authority to act within the limits set at issuance [1]. The issuer cannot take what someone holds, unlike central parties. For assets that require KYC, the issuer is able to remove a holder from its approved list.

Together, this makes it possible to issue anything from a community asset with a provably fixed supply to a fund open only to approved holders, or any other asset that fits within these rules.

Legal documents

Up to 100 KB of compressed text can be attached to the ICU, which is roughly 100 pages of plain text [1]. Every version stays recorded on the chain. The current terms can only be replaced through the governance the asset allows (see Holder governance). A bond can, for example, carry its prospectus and the terms of its interest payments inside the asset itself, so every holder can read what they bought.

Signatures can be stored with the document, for example from the issuer's board or lawyer, including qualified electronic signatures, the strictest standard for electronic signatures in the EU. Anyone can then check both the content and who approved it.

Holder-only disclosures

Some information is meant only for investors, such as a quarterly report. The documents attached to an asset can therefore be public or encrypted. An encrypted document is published with a key delivered to each holder, so only the holders of the asset can read it. The chain itself does not know who holds the key, so investors can receive confidential information without their identity ending up in the open [1].

Accepting the terms

Many assets come with terms the holder has to agree to, such as the conditions of a bond or the subscription agreement of a fund. These terms are part of the legal documents attached to the ICU of the asset. When holders receive the asset, they can accept the terms or return the asset. Either choice is a transaction recorded on the chain, meaning the issuer can always look up who accepted the terms [1]. This makes it possible to keep an on-chain record of consent for a regulated offering, including a shareholder register that stays up to date.

Holder governance

Changes to an asset fall into three groups. The core rules, such as whether units can be minted or burned, cannot change after issuance. The governance fields, including the legal terms, can only change with the quorum of holders set at issuance. Operational compliance data, such as the list of approved holders, can be updated by the issuer without a vote [1]. Holders who are in favour of a governance change co-sign it with their units, and holders who are against it leave it unsigned. The network only accepts the change once the quorum has been reached [1]. Proposals and votes can be collected on the bulletin board of the network, so a shareholder meeting can be held on TensorCash without the need for a separate governance token or outside voting tool.

Zero-knowledge KYC

Regulated assets often require holders to pass KYC. On TensorCash, a holder can prove they are on the approved list of the issuer with a zero-knowledge proof, without revealing any of their information. As a result, a holder can stay anonymous. A holder completes KYC once, and can then generate proofs for new addresses without going through enrolment again, as long as they stay on the list the issuer controls [1].

Where it all comes together

Every function above is available in the TensorCash Core wallet, which gives issuers a full control panel for their assets. The same functions are available through RPC, the interface developers use to control a node from their own software, so issuers can also build their own interface on top.

References

1. [1]Asset Protocol whitepaper.tensorcash.org/whitepapers/Asset_Protocol_Whitepaper-modern.pdf
2. [2]TensorCash blog, COMPUTE: options on the network difficulty, 19 July 2026.tensorcash.org/blog/tokenised-difficulty-options/