Skip to content
Sign inConnect Wallet

For issuers

Bring your token

Keep your contract and your keys. VORUNEX reads the contract where it can, asks for proof of authority over it by a signed message, and reviews the rights behind it. The token stays on its own network.

Open Token import in the issuer consoleWhat is supported on each network

Importing an existing token is not open right now

Importing an existing token is not open on VORUNEX right now. Nothing about any token or asset has changed, and every request already made is kept. The steps below are how it works when it is open. An issuer can apply for admission of the asset from the issuer console in the meantime.

How it works

  1. 01

    Apply for admission of the asset

    An import joins the asset's admission case and never replaces it. Importing a token is not admission. The asset is admitted, or not, by its own admission case, on evidence.

  2. 02

    Name the deployment

    From the issuer console, a member of your organisation names the network, its environment and the token's own identifier there, with the standard it claims. A ticker is not an identifier, and an address is never taken without its network.

  3. 03

    VORUNEX reads the contract, where it can

    Where VORUNEX has a reader for the network and importing is supported on it, the contract is read at a final block and each answer is kept with that block. Where the network is not read, the request is kept and waits, and says why.

  4. 04

    Prove issuer authority

    Holding a token is never authority over it. Only an address the contract itself names as its owner, an admin or a minter can prove issuer authority. Proving authority asks the wallet to sign a message, never a transaction. Signing moves nothing, spends nothing, approves nothing and costs nothing.

  5. 05

    Two reviews, then the link

    Technical Review decides on the deployment and the proof. Legal Review decides on the rights. The two reviews are recorded by two different people. An accepted request proposes the link. The link itself is a decision of two people at VORUNEX, and nothing is linked before the second person approves.

What is read from your contract

What you declare, what VORUNEX's reader observed and what a reviewer confirmed are kept apart. A value that was not read says so, with the reason, and is never shown as zero.

A contract at this identifier
Whether anything answers as a contract at the identifier you named.
Token standard
Which standard's reads the contract answers. Some standards share an interface, and the record says when a read cannot tell them apart.
Decimal places
The contract's own answer, shown beside the number you declared and never in its place.
Units in existence
The contract's own total, kept as the digits it gave. A total that was not read is shown as not read, never as zero.
Owner
The address the contract names as its owner, where it names one.
Who may mint
Whether the contract exposes a standard read for minting, and whether it names the address you gave.
Who may pause
Whether the contract can be paused, where it exposes that.
Who may change the contract's code
Whether the contract's code carries a standard marker that it can be pointed at new code.
Who may freeze a holder
Whether the contract exposes a standard read for freezing a holder's address.

What a signature does not answer

Control of the contract and ownership of the asset are checked apart

Controlling a token's contract and owning the asset behind it are two questions. A signed message answers the first. The second is answered by the asset's own record and its admission case, never by a signature.

A linked token is never silently replaced

A linked contract is never silently replaced. A second import for the same asset is a new request made against the link in force, and a replaced link stays on the record. Once the token is linked, its holder register and its supply figures are read from the registry's own records of that link. Nothing is copied from this request.

Which networks

A network being live in the world does not mean VORUNEX supports it. Each function on each network is supported only after VORUNEX has qualified it and two people have switched it on. Listing a network here switches nothing on.

Importing an existing token is not supported on any network yet

A token that already exists on this network cannot be brought into an admission yet. You do not need to move or reissue the token. Check this page again: it changes when this is qualified and switched on.

What VORUNEX never does on your chain

The token stays on its own network. Nothing is moved, bridged, reissued or signed for, and VORUNEX holds no key. It never co-signs, freezes, mints or moves a token, on any network.
    Bring your token, VORUNEX