Choosing a pathway

The pathway says how the asset reaches the registry and who controls its token. Every pathway is held to the same twelve standards.

An application made in the issuer console goes to VORUNEX's admission staff, who open it as a case. Nothing is added to the registry until they do. The console then shows the case's stage, its open deficiencies and conditions, and the fee quote to accept.

A token you already issued is brought in from the issuer console, under Token import. You name the network, its environment and the token's own identifier there, with the standard it claims and the asset it belongs to, which must already have an admission case. Where VORUNEX reads that network, it reads the contract and shows what it observed beside what you declared. Where it does not, the request is kept, waits and says why.

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. 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.

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. 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.

Moving the units of an asset already on the registry to a new contract or network, or re-issuing them, is opened as a lifecycle request in the issuer console. Two people at VORUNEX decide it on the authority you show, and the executor you name carries it out and reports. VORUNEX carries nothing out, and the registry's link to the original contract changes only by its own decision.