Use cases

Games and virtual economies

Bots and services acting for players, without handing them a wallet.

The problem

In-game automation is normal. Handing a bot a player's key is not, and neither is a trading service holding everybody's balance.

Without Bengar

• A player pasting a private key into a third-party tool.
• A custodial service that becomes the target.

With Bengar

• A permit scoped to specific actions and items, with an expiry.
• Assets whose movement can require an authorization the issuer's rules produced.
• A wallet whose key stays in the player's browser.

The flow

1. The player issues a permit to the service.
2. The service asks for each action; scope and limits are checked.
3. Movements of gated assets carry an authorization artifact bound to that movement.

Components used

Permits · Assets · Wallet · Policy

Example

bengar permit issue --issuer player \
  --audience <bot did> \
  --can trade --with 'resource://game/items/consumables/*' \
  --max-per-tx 500:GOLD --expires 24h

Security properties

Try it →