# Ledger

The ledger records everything on the network, including [user identities](../features/identity-profiles), [account](accounts) balances, operation history, and [votes](../architecture/consensus/votes). All operations are added to the ledger once they are confirmed by the necessary representatives through the consensus mechanism and added to the account’s blockchain. The ledger contains the effects of every operation that has been made since the first operation on the network and can be referred to by the [nodes](nodes) for record-keeping.

The Keeta Network ledger maintains the state of the system and contains an up-to-date state for the following kinds of data:

**Voting Power:** As a result of balances being delegated to a representative using the “Set Representative” operation, that representative gains [voting power](../architecture/consensus/voting-power). Currently, voting power is the sum of all balances of the base token of the accounts which have delegated to that particular representative.

**Balances:** Within the ledger, balances are maintained on a per-token basis on each account and are maintained as an arbitrary large big integer.

**Tokens:** Tokens may be created with the “Create Identifier” operation and are stored within the Keeta Network ledger. Each token has the supply (total number of minted tokens) and outstanding balance of that token (tokens which have been issued to accounts) maintained as state within the ledger.

**Certificates:** [Certificates](certificates) are a specific type of metadata within the Keeta Network ledger which can be used to identify the user associated with an account. The certificate for an account is validated to share the same public key as the account.

**Metadata:** As a result of the “Set Info” operation, some basic user information may be set on an address for informational purposes.

**Permissions:** Keeta Network has an extensive [permissions](accounts/permissions) system, allowing for fine-grained control over accounts, tokens, and the network.

**Blocks:** In order to maintain ordering, [blocks](blocks) are recorded in the ledger. Blocks contain all of the updates made to the ledger, as well as which accounts are being updated.

**Votes:** Issued by ledgers as a side-effect of the ledger contents, votes are endorsements by a particular representative to insert a given block or set of blocks into their ledger. Votes come in two kinds: permanent and temporary. Only permanent votes end up on the“main” ledger, but a representative must maintain all votes it issues and so unpublished votes (whether permanent or temporary) will be stored in the “side ledger.”

**Side Ledger:** The side ledger is a secondary area where unpublished votes are stored. All temporary votes will be unpublished, but the representative that issued them must keep track of them throughout the lifetime of the vote.



<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Get Ledger History</strong></td><td><a href="https://1876017793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpitcpcamWc0BKEe28I1D%2Fuploads%2FHgY49P2KrE8fvfMRmNHn%2Fdev.png?alt=media&#x26;token=3e7e484c-3852-4c22-a809-29bfcdebdd6f">dev.png</a></td><td><a href="ledger/get-ledger-history">get-ledger-history</a></td></tr><tr><td><strong>Filter Ledger History</strong></td><td><a href="https://1876017793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpitcpcamWc0BKEe28I1D%2Fuploads%2FHgY49P2KrE8fvfMRmNHn%2Fdev.png?alt=media&#x26;token=3e7e484c-3852-4c22-a809-29bfcdebdd6f">dev.png</a></td><td><a href="broken-reference">Broken link</a></td></tr></tbody></table>
