(Outdated post) Network Explorer

[inccry]

1.7.8 version released

This is a technical release.

New feature:

• New specific endpoints for Staking Rewards integration

New API endpoints are:

• https://api.incscan.io/external-integrations/staking-rewards/v1/prv/price
• https://api.incscan.io/external-integrations/staking-rewards/v1/fees?from=2020-11-14&to=2020-11-15
• https://api.incscan.io/external-integrations/staking-rewards/v1/prv/supply
• https://api.incscan.io/external-integrations/staking-rewards/v1/prv/engaged-balance
• https://api.incscan.io/external-integrations/staking-rewards/v1/prv/volume

---

What’s next?

The next feature will be “staking” focused.

I indexed the committee state at every block, so I should be able to allow every validator to get the full staking history of their nodes.

It’s a work in progress, stay tuned

[abduraman]

@inccry

I indexed the committee state at every block, so I should be able to allow every validator to get the full staking history of their nodes.

I think we are a little bit same-minded. Probably, we are on the same or similar work

[abduraman]

@inccry

This number seems ok If you have different numbers, please share them!

Hey @inccry, I think you and the team measure #stakers differently since #stakers in the explorer is 2296 but gettotalstaker RPC returns 2305.

[inccry]

@abduraman

I think we are a little bit same-minded. Probably, we are on the same or similar work

The required endpoint to do that has been released few weeks ago, that’s why I started this work

[inccry]

@abduraman

Hey @inccry, I think you and the team measure #stakers differently since #stakers in the explorer is 2296 but gettotalstaker RPC returns 2305.

I don’t count beacon stakers, that’s why you see a different number.

[abduraman]

@inccry

The required endpoint to do that has been released few weeks ago, that’s why I started this work

Since I couldn’t find it after a long research, I modified the code of the fullnode That’s why I had asked this: BeaconBestState by beacon height.

Btw, what’s the method name? Let me check.

[inccry]

get committee state by height

[abduraman]

@inccry

I don’t count beacon stakers, that’s why you see a different number.

Still +1 extra? 2296+8 = 2304. Anyway, I think I miss something and I should do more research

[Jamie]

8 shards, and the beacon itself, probably. That would make 9

[abduraman]

Found the problem, I think I examined the code and got the result of the getbeaconbeststate at the 2357th epoch. In that epoch, incscan shows 2307 and gettotalstaker returns 2316. Futhermore, the official explorer shows the same numbers. Here is the related part of pretty-printed json result:

If we follow the code (getAllStaker() at https://github.com/incognitochain/incognito-chain/blob/dev/master-consensus-v2-optimized/dataaccessobject/statedb/statedb.go) and do math, we get 2316 (=7+1989+8*32+8*8). Surprisingly, the beacon committee has 7 validators, not 8. Why? ( To any devs from the team ) If this is true, incscan should show gettotalstaker - 7. Otherwise, incscan should show gettotalstaker - 8

Currently, incscan shows gettotalstaker - 9. If this is true and not a bug, where does -1 comes from? Again, any help from the team is appreciated. @Support The calculation of the correct number is also required for IncogWhaleBot.

[Josh_Hamon]

FWIW When I run https://api.incscan.io/network/staking-nodes/total I get 2307 validators but when I go to the website I see 2193 active validators.

[inccry]

@Josh_Hamon please force refresh your Incscan page.

[Josh_Hamon]

That worked for me, do I need to be refreshing the page?

[inccry]

A fix was deployed few days ago and it seems you didn’t get the last client side code. Could be a Cloudflare issue, will inspect that later. (the force refresh fixed that)

[inccry]

1.7.9 version released

New feature:

• Pair of the month dashboard widget: A new widget has been added to simple and advanced dashboards, it shows key figures about a selected trading pair. The first pair is PRV-QUEST and next pairs will be chosen by the community and the incognito team.

  

[duc]

hey @abduraman, I’d like to confirm that the beacon committee size is currently 7 so please update your formula if needed, thanks

[abduraman]

This means that incscan shows 2 missing or is there another reason for that? @inccry

[inccry]

I don’t know, my calculation is : 176 (fixed nodes) + staking transactions count - unstaked transactions counts

It’s possible that I missed few transactions for some reason, but hard to debug the full blockchain history

Let’s wait for the staking detailed statistics feature on Incscan, it will be easier to try to find an explanation.

[inccry]

1.7.10 version released

New feature:

• Coin of the month dashboard widget: A new widget has been added to simple and advanced dashboards, it shows key figures about a selected coins. The first coin is pBTC and next coins will be chosen by the community and the incognito team.

  

Changes

• Custom pairs volume: Volume on custom pairs charts is back. It wasn’t displayed since trades v2 feature was delivered.

  

[abduraman]

Hey @inccry,

I think incscan read the wrong pETH (there are two pETH) from api.incognito.org/ptoken/list. That’s why ETH ERC-20 (un)shieldings are seen as ETH BEP2. FYI.