Permission to create.
Only the configured issuer can propose new tokens, within a per-policy lifetime issuance cap. The recipient accepts before a holding is created.
Aurets is being built on Canton. The contract prototype now implements standard holding views and standard transfer factory/instruction interfaces, alongside test issuance and burning.
Custom prototype contracts. No claim of Canton partnership, certification, or shared-network deployment.
Only the configured issuer can propose new tokens, within a per-policy lifetime issuance cap. The recipient accepts before a holding is created.
The owner offers a transfer. The recipient accepts or rejects it; the sender can cancel while it is pending. Partial transfers preserve the change.
The owner can burn a test holding. A ledger receipt records the destruction. Burning does not send dollars or create a bank payout.
This checks configuration, not a payment or token balance.
The website does not hold a customer signing key. A production wallet and signing integration remain to be selected and verified.
The registry has not been checked. A token name alone does not establish its identity.
This compares a registry’s administrator and instrument ID with Aurets’ configured identity. The network label is operator-configured. A metadata match does not prove reserves, value, contract deployment, or payment readiness.
Choose a compatible wallet and approve account access there. This connection displays your account and network; it does not submit a transaction or request a signature.
Loading the wallet connection module…
Network: Not connected
Connect a wallet and check the token identity to compare networks.
Not checked. This checks read access only; it does not verify Aurets deployment or enable payments.
No wallet accounts connected. Never enter a seed phrase or private key on Aurets.
Loading the build report…
The prototype implements the official v1 Holding, TransferFactory, and TransferInstruction interfaces. A read-only registry identity adapter is implemented. Registry hosting, complete transaction-history interoperability, allocations, and shared-network wallet validation remain.
No. A network records the asset and its transactions. A stable dollar value needs a separate issuer, backing, and redemption arrangement.
No. The package is a development artifact. Shared-network issuance is disabled.
No. Banking credentials and account details belong in a future provider-hosted onboarding flow. Do not submit them in the demo, request notes, or email.