Skip to content

A log parser for idena-node-proxy logs, creating useful statistics from idena validations

Notifications You must be signed in to change notification settings


Repository files navigation

idena-node-proxy validation log parser

A command-line log parser for idena-node-proxy logs, creating validation statistics for administartors of idena shared/rented nodes.



idena-node-proxy is used to provide multiple different identities shared access to an idena Proof-of-Person blockchain node.

This command-line script parses the log file created on the idena-node-proxy during an idena validation ceremony.


  • This script was created to work with a shared node set up using my Idena shared node guide and may not work with your setup, but probably will provided you have the correct log files.
  • idena-node-proxy log files should be written to a file (access.log by default) using the "logs": { "output": "file", option in the config.json file as described in step 3 of my shared node guide. If you are writing logs to the default stdout its up to you to extract them to an appropriate file to be able to use the instructions for this log parser.
  • The log parser uses the dna_identity entries from the log file on the day of validation, meaning it will include anyone that connected to your node whether they actually validated on your node or not. The actual validation results are retrieved from the idena API using the identity that connected to your node, meaning that if the identity only connected to your node once but in the end switched to a different node for validation, they will still be included in the statistics. You should also make sure that the API keys from previous validations are removed from your idena-node-proxy before validation day.
  • It is recommended that you keep all the individual log files created by the full instructions below, and keep them for each validation, as features could be added to this script to make use of them retroactively.
  • It is required to keep the (for example)73_ids_good.txt file that the script generates for each epoch processed, this is used to calculate the "Repeat customers from previous validation" statistic. If this file is not present for the previous statistic, it will show as zero repeat customers.
  • The "Rejected API keys" statistic are identities trying to use an old API key for your node from a previous validation, or some random API key, or an API key for a different node or their local node.


The script is not fully automated and requires some manual actions performed before the data is actually analyzed. Ideally, this is done immediately after concensus on validation has been reached to not pick up identities connecting to your node for the next validation.

  • Automated preparation of idena-node-proxy logfile for further processing
  1. Complete the Script Usage section first
  2. Run the helper shell script, as follows: ./ 2021-09-21 74 You may skip the rest of these instructions if you are using this method, this shell script will run the python script as well.
  • Manual prepration of idena-node-proxy log file for further processing
  1. Change directory to wherever your access.log file from idena-node-proxy is located: cd idena-node-proxy
  2. Extract only the log entries for the date of the validation (edit the date and filename to match the validation you want to parse from logs) : cat access.log | grep 2021-09-21 > validation.epoch.74.log
  3. This validation.epoch.74.log file now contains all the logs for that specific validation day, but we only want the dna_identity entries: cat validation.epoch.74.log | grep dna_identity > dna_identity.epoch.74.log
  4. Now, because dna_identity endpoint is accessed many times by every identity, we need to remove all duplicates: awk '!a[$3]++' dna_identity.epoch.74.log > dna_identity.epoch.74.unique.log
  5. We now have the file we will actually process with the log parser script, so: python3 ./ dna_identity.epoch.74.unique.log 74

Script Usage

  1. clone this repo
  2. apt install python3-pip
  3. pip3 install -r requirements.txt
  4. make sure you have the requests python library installed
  5. rename logparser.ini_default to logparser.ini. You do not need to edit anything in this version of the script.
  6. Follow the instructions above

Found this script useful? I accept iDNA donations to address 0x8dc26a6fbdbe2fdb8b5284ab55f56e720b3c42ad


A log parser for idena-node-proxy logs, creating useful statistics from idena validations






No releases published