Bengar Assets PREVIEW
Issued tokens whose movement can require a Trust authorization.
What it is
- Assets with one of two supply models — FIXED or CAPPED_MINTABLE — optionally gated so that a movement requires an authorization artifact.
Why it exists
- Regulated instruments need movement rules. The usual answer is a freeze switch and an admin key, which is a power somebody can be compelled to use.
- Gating puts the rule in the authorization pipeline, where it is a policy decision with an audit trail, rather than in a privileged key.
How it works
- Create the asset with its supply model, decided once.
- Set a gating policy naming the keys whose authorizations the chain will accept.
- Each movement carries an artifact bound to that movement, with a nonce and a short window.
Who uses it
- Issuers of instruments with transfer conditions
Security boundary
- No generic administrator, no freeze, no blacklist, no authority transfer, no mutable metadata.
- An artifact is not a payment instruction and moves nothing by itself.
- A symbol is not an identity; the asset id is authoritative.
- Native BGR is not gated.
Example flow
A gated transfer
- A holder asks to transfer 100 units.
- The Gateway checks permit, policy and approval, and issues an artifact bound to that movement.
- The transfer is submitted with the artifact; the chain verifies it and spends the nonce.
- A replay of the same artifact is refused.
Current status
| Capability | Status | Where |
|---|---|---|
| Browse assets, holders and transfers | AVAILABLE | Scan → Assets |
| Issue an asset from the Console | AVAILABLE | /projects/[projectId]/assets/new |