BengarTrust infrastructure

Docs · Network

Trust-gated assets

Requiring a Bengar authorization before an asset moves — and what the artifact is not.

How it works

  1. An issuer sets a gating policy on the asset, naming the public keys whose signatures the chain will accept.
  2. A party asks the Gateway to authorize a movement. Permit, policy and any approval decide.
  3. On ALLOW, the Gateway issues an authorization artifact: Ed25519, bound to this asset, this action, these parties, this amount, with a nonce and a short window.
  4. The movement is submitted with the artifact. The chain verifies it and spends the nonce.

What the artifact is not

An artifact is not a payment instruction. It does not move anything by itself and it is not a bearer instrument for value — it is a capability that says a specific movement was authorized, which is only useful together with the signature of whoever holds the balance.

  • It is bound to one movement and its nonce is spent when used.
  • It expires. A stale artifact is refused rather than honoured late.
  • Spent nonces outlive the gate, so removing gating does not make old artifacts replayable.
  • Its signing key is Ed25519 — a Trust-domain key, never the account curve.

Gating is not freezing

A gate says movements need an authorization. It does not immobilise anybody's balance, and it is not a per-account control: there is no way to gate one holder and not another.