BengarTrust infrastructure

Documentation

Bengar documentation

Written against the code at the commit it ships with. Where the product cannot do something, the page says so rather than describing the version somebody hopes to ship.

Getting started

Getting started

Two ways in: the offline primitives, or a running authorization service.

Quickstart

From an empty checkout to a real ALLOW, a real DENY and a real approval.

Core concepts

Six nouns and the sentence that connects them.

Authentication

API keys for machines, sessions for people, and why they never cross.

Concepts

Identity

An Ed25519 keypair and a did:key. What names a party in the Trust protocol.

Principal

A person inside an organization — and the three things it is not.

Agent

The thing acting — a program, a model, a script — named by a DID.

Permit

A signed document saying what a party may ever ask for. Not authority.

Intent

What an agent is trying to achieve, stated before it acts.

Policy

Deterministic rules that say what may happen now.

Approval

A person deciding, recorded so that the decision can be checked later.

Risk

A score that can require a person, never one that grants permission.

Execution

Acting on an ALLOW, and knowing what actually happened.

Audit

Two records answering two questions: what agents did, and what people did.

Proof

Checking an audit record against something outside the system that wrote it.

Custody

Where signing keys live — and why an outage there is not an outage here.

Network

The chain: a witness for the audit trail, not a step in a decision.

Assets

Issued tokens with a fixed or capped supply, optionally gated by Trust.

Guides

Policy

Deterministic rules that decide ALLOW, DENY or REQUIRE_APPROVAL — versioned, simulated, then activated.

Permits

Issue, verify, delegate and revoke the signed documents that bound what an agent may ask for.

Approvals

The human approval ceremony: what the reviewer sees, what the passkey proves, and what Custody signs.

Execution

The four outcomes, why UNKNOWN is not FAILED, and how idempotency works.

Proofs

Verifying an audit event against an anchored Merkle root, with four outcomes that stay four.

Custody

Where signing keys live. Software custody today, hardware as an option later.

Custody key classes

Which keys Custody holds, which it deliberately never holds, and the reasoning for each.

Software custody

What encrypted-at-rest software custody defends against, and what it does not.

Hardware HSM

An optional higher-assurance backend. Not what Bengar ships today.

Error reference

What each code means, whether it may be retried, and what to do about it.

Network

Assets

Issued tokens with a fixed or capped supply, and the absences that are the design.

Creating an asset

What is decided at creation, and cannot be changed afterwards.

Minting

Only for CAPPED_MINTABLE, only by the mint authority, only up to the cap.

Burning

You can burn what you hold. Nobody can burn what somebody else holds.

Transfers

Moving an asset, and what happens when the asset is gated.

The asset lifecycle in the Console

Create, mint, burn and transfer, and who may do each.

How an asset transaction is signed

Where the key lives, what crosses each boundary, and why the review is the signature.

Trust-gated assets

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

The Bengar network

A Cosmos SDK chain that witnesses the audit trail and carries assets.

Accounts

secp256k1 accounts, bech32 addresses, and what holding one does not grant.

Native BGR

The network's own denomination — and why the name you see says DEVBGR.

Fees

What a transaction costs and what bounds it.

Staking

Delegation and rewards — and the authority that staking does not confer.

Validators

Who produces blocks, and what happens when one misbehaves.

Governance

Exactly four actions, and a separation the module enforces.

Products

Bengar Scan

The public explorer, page by page.

Bengar Wallet

A personal wallet whose key stays in the browser — with its current limits.

The organization treasury

Receiving into an address your organization controls, and sending from it under policy.

The network views

Reading the chain from the Console: status, validators, staking, governance and the network treasury.

Bengar Console

Every screen a person can reach, what it needs, and what it can and cannot do today.