Help: Ledger
What the ledger is
The ledger is your account's record of what your agents asked to do, what your rules and your people decided, and what the agents reported afterwards. Each account has its own ledger. You read it on the Ledger page.
What is recorded
Every one of these adds one event to the ledger:
- A request arriving from an agent, and the outcome your rules gave it.
- Every change of a request's status: approved, denied, cancelled, expired, released, executed or failed.
- An agent being registered or revoked, and a key being created, rotated or revoked.
- A rule being created or changed, including being enabled, disabled, confirmed or moved.
- A change to the payload retention setting.
Each event has a sequence number, a type, a time, the actor (an agent, a user or the system) and, where it applies, the request it belongs to. The details behind the event are stored separately as its payload.
The ledger does not store an agent's request payload. It stores a fingerprint (a hash) of it. The request itself is shown on the request's page.
How the chain works
Every event carries a hash computed from the hash of the event before it, its own sequence number, type and time, and the hash of its payload. The first event starts from a row of zeros. Because each hash depends on the one before, the events form a chain.
Events cannot be changed or removed through funwatcher. The database itself rejects any update or deletion of a ledger event.
What the chain proves
- Nothing was removed, inserted or reordered after the fact. Any such change breaks the chain, and the check names the first event that fails.
- No recorded event was altered. A change to an event's type, time or payload is detected, even after the payload itself has been purged, because the payload's hash is kept.
- The history matches an earlier copy. If a hash from an export or statement you saved earlier matches the ledger at that point, nothing before that point has changed since.
- Who is recorded as the actor of each event.
What the chain does not prove
- It does not prove that the agent did what it reported. The ledger records what an agent said it would do and what it said happened. An agent that reports falsely, or carries out something other than what was approved, leaves a consistent record of false statements.
- It does not prove anything about systems funwatcher never sees. funwatcher does not carry out actions and holds no credentials for your bank, mail or other accounts.
- It does not protect against someone who controls the database and every copy. Such a person can rewrite the history and recompute every hash. A copy kept somewhere else is what exposes that, which is why exports and the hashes on monthly statements exist. Keeping them outside funwatcher is your part.
- It does not prove that the clock was right. Times come from the server's clock.
- It cannot give back a purged payload. After the retention period only the hash remains.
- It is not a notarized record. There are no digital signatures on events, no trusted timestamps and no outside witness.
Read more
Previous: Delegations
Next: Browse and filter the ledger
All help pages
Inbox
- Read a request
- Approve, deny or edit a request
- Held actions
- Expired requests and history
- Request statuses
Rules
- How rules work
- The default rules
- Write a rule in plain English
- Build a rule with the form
- Reorder, enable and disable rules
- Suggested rules
- Set a default policy for an agent
- Export your rules
Teams
Ledger
- What the ledger is
- Browse and filter the ledger
- Export and verify the ledger
- Payload retention
- Monthly statements
Billing
Account and security
- Change your password
- Two-factor authentication and recovery codes
- Rotate or revoke an agent key
- How your data is protected
- Closing an account