hakkane84 / navigator-sia Goto Github PK

The transactions to the burning address are showing a wrong timestamp. Apparently, it is only the AddressesChanges entry:

https://siastats.info:3500/navigator-api/hash/000000000000000000000000000000000000000000000000000000000000000089eb0d6a8a69

It is possible it is using the contract formation timestamp instead of the end of contract timestamp (timestamp delta makes sense)

This plan aims to add these new functionalities:

• Make Navigator independent of the Sia's explorer module
• Add richlist functionalities support
• Add capabilities and endpoints showing information about unspent outputs, what will enable apps related to offline signing of transactions (like Ledger tools) and Lite clients (using navigator as a trusted node)

PHASE 1:

• Hashrate and Difficulty calculation
  • FIRST: Explore my hypotheses of Hashrate calculation creating a test script
  • IMMEDIATE: Create an script that collects hashrates and difficulty of blocks of current Db on a persistent JSON
  • IMMEDIATE: Make Siastats save on this file on every new block. Then re-arrange the array
  • Make siastats.js modules to graciously handle empty entries (null, "") hashrates and difficulties for day averages

PHASE 2:

• Successful contract resolutions: trigger not on storage proof, but on end of the proof window:
  • The function that checks unresolved contracts has to manage both successful and unsuccessful (OPTIONAL CHANGE)
• Handle errors better:
  • On Sia calls (check decentralizer)
  • On File read calls (check Decentralizer)
  • Check SQL error calls are being graciously handled
• Richlist:
  • Create a new SQL table ScBalances: Address - Balance (Indexes on both)
  • Every 10000 blocks, save a persistent JSON including the distribution:
    • Request balaces > 0 order by Balance
    • Count the number of addresses
    • Balances of top10, top50 top100, top500, top1000, top5000
    • Balances of percentiles 10, 20, 30, 40..., relative to the % of Supply
  • SiaStats script that daily collects the top 10 addresses, their balance and their % of Supply
• Outputs:
  • Create new SQL table ScOutputs: Hash* - address* - balance - spent (boolean) - createdOnBlock - spentOnBlock
  • Create output as hashtype
  • Navigator visualization of outputs (a simple table)
  • On each Sc operation: update as spent the sending outputs; create in the receiving outputs
  • Create API endpoint for unspent outputs of a certain address

PHASE 3:

• Hashrate and Difficulty calculation
  • On each block:
    • if block < current: find the entry on the persistent JSON file
    • if there is no entry in the JSON file, leave the fields empty (Esto es una chapuza, pero hasta que anyadan esto a /consensus, es mi unica salida para dejar de usar explorer)
    • if block = current: make a consenus call: block has to be concordant (otherwise, leave empty) and synced has to be true (otherwise, repeat after timeout)
      • The difficulty of the NEXT block is included on the call. Divide by 1000 and make the floor?
      • When calculating hashrate, it uses a tally of the last 144 difficulties
      • The codeflow needs to carry on the tally of difficulties and a tally of timestamps (to use the older one for calculating hashrate)
      • I need to confim these hypotheses: create the script that collects those 144 blocks and simulates
• Find parent unlockhashes on my own database: add a new array ("orphans") that contains: output, address, amount
• New codeflow:
  • Data collection like right now
  • Parent finder
  • Difficulty & hashrate scripts
  • Save the SQL queries
  • Repeat for next block

https://hyperstats.info/navigator?search=327076da2e2fb85d917b0701539e0f2f481854a1860303ec6fc4011349ac33d0

Possibly related to multiple inputs from the same address

I need to perform a sanity check on the block height of TXs being indexed, not allowing it to be 0 if the timestamp does not correspond with Genesis. Otherwise, assign it to "-" or "-1" (that will require me to change the type on the SQL database) or "null" or not index the TX at all.

The contract formation operations made by us look to be using a format incompatible with my code partially. While I am still accounting for each coin movement in the addresses, I am not displaying the returning change of the renter, which is indicated on siacoinoutputs[0]

To be addressed during the Navigator 1.1 revamp

sudo node navigator.js

The output

======================================================
                  STARTING NAVIGATOR
======================================================


Logging started: 14/4/2022 - 12:32:56
* Navigator will use a local Sia instance in port 9980
* Connected to the SQLite database!
* API HTTP server running on port: 80
//// SQLite read error: SQLITE_ERROR: no such table: BlockInfo
* Creating tables for the database...
// Local Sia node unavailable for a /consensus call. Timing out 300000ms

this would give a picture of the health of the network over time.