not approved

The Tipchecker

$3,000.00 Requested
Ideascale logo View on ideascale
Community Review Results (1 reviewers)
Addresses Challenge
Feasibility
Auditability
Solution

The Tipchecker is a small unix-way tool you can use to get your relative sync state!

Problem:

Sometimes it's hard to understand if your cardano node(s) synced with the network properly. Is it stuck? Or does it have stable undersync?

Yes Votes:
₳ 20,231,918
No Votes:
₳ 19,040,444
Votes Cast:
106

  • download
  • download

Detailed Plan

The Tipchecker is a little but powerful hivemind system that can help you to build your powerful monitoring system.

It's a small and simple unix-way tool. Also it's already used in the production environment for some pools as a part of their monitoring\failover system. You can use it right now. More nodes in the hive, more stability for the service! Join!

How to use it:

  1. Download at https://adawallet.io/tipchecker

  2. Run it to discover your relative block height and send your absolute height to the server:

tipchecker.sh (path/to/cli) (path/to/cardano.socket) [node_name]

It returns a simple INT value, so you can use it in every tool you want like a simple unix-way command.

Less or equal to zero is good, positive values are bad. +5 is about critical desync, try to avoid it.

Would be nice if you added it to some cycle-running task to increase its efficiency. There is a garbage collector, so don't worry if you left some records after renaming, etc.

But why?

Because you can't be sure if your node\nodes\relays\BP is perfectly synced with the network without a tool like this.

Key features:

  1. There is an "anti-poisoning" protection. It analyzes incoming data and detects anomalies. So it can't be screwed up by some wrong data. It's not just a "data collector" :)

  2. There is a tiny API that returns your node data as a JSON if needed:

https://adawallet.io/tipchecker/index.php?id=your_tipchecker_Id

e.g. <https://adawallet.io/tipchecker/index.php?id=5e04f22256414d60932c8465c5af5a1b>

  1. It doesn't store your IP's. All your stored data you can retrieve from API by id

  2. You can send data from the same machine for different nodes! Just set them different names

  3. It's already released :)

What will we do with money?

  1. Better analytics algorithms

  2. Better dashboard (there wasn't any dashboard at project, but users asked for it)

  3. tg bot? Why not!

  4. Full-fledged failover overseer Integrated with the Tipchecker tool if you don't want to write your own one :)

Open source???

Yes, but later.

Community Reviews (1)

Comments

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00