For the complete documentation index, see llms.txt. This page is also available as Markdown.

Evidence — an issuer

The issuer screenshots in Issuing are not mock-ups. They are a real asset — Aurelian Estate Fund (AURE) — issued and administered on Hadrian (chain 200010) by a real wallet, and every action behind them is a transaction you can open on the block explorer. The link is the claim.

Creating the asset — eight transactions, never one

The wizard's piecewise deploy (see Building on Bloom), each contract in its own transaction:

#
What it did
Transaction

1

Deploy the asset (proxy + initialize)

2

Deploy the allowlist module

3

Set you as its administrator

4

Enforce it on transfers

5

Deploy the yield module

6

Set you as its administrator

7

Enforce it on yield

8

Register with the factory

Setting up the sale and the allowlist

Action
What it did
Transaction

Move inventory

100 units to the shared storefront

Open the sale

100 units at 1 wUSDC

Allowlist a batch

three addresses in one transaction (batchAddToWhitelist)

Administering the asset

Action
What it did
Transaction

Set the payout currency

wUSDC (setYieldToken)

Grant a role

MANAGER_ROLE to a delegate (grantRole)

What the screenshots show is what these transactions did. The console's Sale tab reads the sale opened above; the "Who may hold it" count is the batch allowlist; the Rights tab reads the roles granted at deploy. Nothing in the guide is staged in a design tool — it is one asset, on one chain, and each number traces to a hash here.

Last updated

Was this helpful?