-
Notifications
You must be signed in to change notification settings - Fork 33
Indexer Readme
user_name edited this page May 3, 2023
·
3 revisions
txIndexer
implementation uses a KVStore
(interface) to index the transactions.
Key | Index | Value | Description |
---|---|---|---|
HASHKEY | h/SHA3(TransactionProtoBytes) |
IndexedTransactionProtoBytes | store value by hash (the key here is equivalent to the VALs below) |
HEIGHTKEY | b/height/txIndex |
HASHKEY | store hashKey by height |
SENDERKEY | s/senderAddr |
HASHKEY | store hashKey by sender |
RECIPIENTKEY | r/recipientAddr |
HASHKEY | store hashKey by recipient (if not empty) |
The height/txIndex store uses ELEN. This is to ensure the results are stored sorted (assuming the KVStore
uses a byte-wise lexicographical sorting).
Contents
- Home
- Persistence
- Changelog
-
Persistence
- Indexer
- Rpc
- Runtime
- State_Machine
-
Guides
- Roadmap
-
Guides
- Learning
- Guides
-
Guides
- Contributing
- Devlog
-
Guides
- Dependencies
-
Guides
- Releases
- Guides
- P2P
-
Shared
- Crypto
- Shared
-
Shared
- Modules
-
Build
- Config
- Consensus
-
Guides
- Telemetry
- Utility
- Logger