You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/storage.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ As of now, RocksDB is used as a key-value database for all Storages.
6
6
- Sequence numbers start from 1 and then increase by 1 for each new transaction. There are no gaps in sequence numbers.
7
7
- RocksDB is used as a key-value storage where key is the sequence number and value is the transaction.
8
8
- A transaction is serialised (currently as MsgPack) before storing in the ledger, more on this in the Serialisation doc.
9
-
- Exact format of each transaction can be found in [Indy Node Transactions](https://github.com/hyperledger/indy-node/blob/master/docs/transactions.md).
9
+
- Exact format of each transaction can be found in [Indy Node Transactions](https://github.com/hyperledger/indy-node/blob/master/docs/source/transactions.md).
10
10
- Each node hosts several ledgers each identified by a unique id:
11
11
- Audit Ledger (id is `3`): Contains transactions for every ordered 3PC Batch with information about the pool state at the moment of batch ordering.
12
12
It's used for synchronization between other ledgers and recovering of pool state by new or restarted nodes.
0 commit comments