Bengar Network PREVIEW
A chain that witnesses the trail. Not a step in a decision.
What it is
- A Cosmos SDK chain with identity, revocation and anchoring modules, plus assets, staking, slashing and a deliberately small governance module.
Why it exists
- Anchoring is what lets a customer check the audit trail without trusting us. Everything else the chain does follows from having one.
How it works
- Audit batch roots are anchored in transactions.
- Trust records — identities, revocations — are readable by anyone.
- Assets, staking and governance run as modules with closed action sets.
Who uses it
- Auditors
- Validators
- Asset issuers
Security boundary
- Never in the authorization hot path.
- No public testnet and no mainnet. Real multi-host validation is an open gate.
- Test coin has no value, and DEVBGR is devnet branding.
Example flow
An anchor
- A batch of audit events is hashed into a Merkle tree.
- The root is submitted in a transaction.
- Anybody can read that transaction and confirm the root at that height.