History Collector

Scan the history archives of the kin blockchain, and create a database that contains payment and account creations.

How does it work?

The python script constantly downloads files from the blockchain's s3 archive, parses them using xdrparser, filters payments and account creations and store these operations in a postgres SQL database.

Notes

• Only payment and creation operations are saved to database.
• Operation indexes start counting from 0
• Saved attributes are: source, destination, memo text, tx hash, fee, fee_charged, tx_status, operation_status, and timestamp
• For payments, amount is also saved
• For creation, starting balance is also saved
• The source account will be the source of the operation, if it exists.
• The service stores the last file scanned in the database, so you can restart the service without starting all over again

Prerequisites

1. Install docker
2. Install docker-compose

Configuration

Edit the docker-compose file to configure it

Variable	Description
S3_STORAGE_AWS_ACCESS_KEY	AWS Access Key ID : Optional - if not mentioned, uses default aws credentials on the server. User should have S3 Read/Write/Delete access
S3_STORAGE_AWS_SECRET_KEY	AWS Secret Access Key - Used only if AWS Access Key ID supplied
S3_STORAGE_BUCKET	S3 Bucket to use for output data
S3_STORAGE_KEY_PREFIX	S3 prefix to which a default folder name will be appended. The all output will be stored there. Recommendation: end prefix with '/'
S3_STORAGE_REGION	Region of S3 bucket on AWS. If remain empty, region us-east-1 will be used by default
POSTGRES_PASSWORD	Master password for the postgres database
PYTHON_PASSWORD	Password for the postgres user 'python' (will be created by the script)
KIN_ISSUER	Issuer of the kin asset
FIRST_FILE	The first file to download If you know the ledger sequence
NETWORK_PASSPHRASE	The passpharse/network id of the network
MAX_RETRIES	Max number of tries to download a file before quitting, there is a 3 minute wait time between each try.
BUCKET_NAME	S3 bucket name
CORE_DIRECTORY	The path leading to transactions/ledger/results... folders, can be ''
POSTGRES_HOST	The host of the postgres database
APP_ID	An app id to filter transactions for. If left empty, all transactions will be saved regardless of app
LOG_LEVEL	The level of logs to show, "INFO"/"ERROR"/"WARNING"

Usage:

To run the service, simply clone the docker-compose.yaml file, edit the configurations and run

$ sudo docker-compose up -d

Logs can be accessed using

$ sudo docker-compose logs

Demo:

You can test this service with the demo app, in the sample folder