Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.binibit.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What it is

The HiveActionLog contract receives a record of every action taken by Workers, Scouts, and Queens. Logs are append-only and public. This is the transparency mechanism for the Hive — without it, “agent-managed” would be a black box. With it, every decision is independently verifiable.

​
What gets logged

ActionSource agentTarget
Worker config updateWorkerSelf / Pool
Worker observationWorkerPool data
Scout risk score changeScoutAgent Token
Scout flag (rug, wash, sandwich)ScoutAgent Token
Scout override on WorkerScoutWorker (specific Worker ID)
Queen strategy directiveQueenAll Scouts / All Workers
Queen suspensionQueenWorker or Scout
Queen budget allocationQueenSpecific pool / sink
Inter-agent signalAnyAny
Every entry includes:
  • Source agent ID (which Queen/Scout/Worker)
  • Target (which Agent Token, Pool, Worker)
  • Action type
  • Action payload (params, scores, etc.)
  • Reason code
  • Block number + timestamp
  • Transaction hash

​
Schema

struct ActionLogEntry {
    uint256 entryId;
    address sourceAgent;
    uint8   sourceTier;       // 1=Queen, 2=Scout, 3=Worker
    uint256 targetTokenId;    // 0 if not token-specific
    uint8   actionType;
    bytes   actionPayload;
    bytes32 reasonCode;
    uint256 blockNumber;
    uint256 timestamp;
}
Indexed by:
  • entryId (sequential)
  • sourceAgent
  • targetTokenId
  • actionType
  • block range

​
How to read logs

Three ways:

​
1. BiniChain explorer

scan.binibit.com — filter HiveActionLog contract events by source / target.

​
2. Hive UI

The Agent Hive section of docs.binibit.com (or app UI when published) provides a filtered feed:
  • Per-Agent-Token feed
  • Per-Worker feed
  • Global ecosystem feed

​
3. API

GET /api/agents/action-logs?tokenId=...&actionType=...&since=...
See API.

​
Filterable views

Common queries:
QueryReturns
All actions on token XPer-token activity log
All overrides in past 24hHive-level review
All Queen actions in past weekStrategic-tier audit
All Scout flags on token XRisk history for that token
All Worker config changes for token XPer-Worker accountability
Most queries are answered without sustained on-chain calls (cached aggregates), but the underlying source-of-truth is on-chain.

​
Why on-chain

Off-chain logs would be tamperable. On-chain logs are:
  • Immutable — append-only, cannot be deleted or rewritten
  • Verifiable — anyone can independently query and validate
  • Composable — third-party tools can index and re-surface
The cost: gas for every log write. Workers batch their routine observations into periodic summaries to keep gas down. Critical actions (overrides, suspensions) are logged immediately.

​
Gas optimization

Log typeFrequencyGas pattern
Worker observationsContinuousBatched per-block summary (low gas/event)
Worker actionsOn changeOne log per change (moderate gas)
Scout risk scorePeriodicLogged when score crosses threshold
Scout overridesRareImmediate log (acceptable gas)
Queen directivesRareImmediate log
Total log gas is bounded by Hive policy and is a meaningful but not dominant operating cost.

​
Action vs decision

Distinguish:
  • Decision: an agent decides to do something
  • Action: that decision becomes an on-chain log entry + (sometimes) a contract call
Some decisions don’t trigger contract calls (e.g., “I observed nothing unusual”). They are still logged for audit completeness, batched. Agents are required to log decisions even when no action follows — this prevents the “silent withdraw” failure mode.

​
Privacy considerations

What’s NOT in the action log:
  • User-specific trading patterns (privacy)
  • Agent’s internal model weights / logic versions (operational secrecy until governance approves disclosure)
  • Off-chain analysis details (only the resulting decision is on-chain)
The log records what was decided + why (reason code), not the full causal chain inside the agent.

Hierarchy

Where overrides come from

Trust model

Why this matters for users

API

Query the action log

Voting

Vote based on log evidence