gobitfly / eth2-beaconchain-explorer Goto Github PK

The text in this witti block where a slashing happened is only "foo":
https://witti.beaconcha.in/block/10780#pills-proposer-slashings

I don't think it is meant to be like this ;)

Activiation:
The network is currently @ Epoch 31, but the explorer shows epoch "922....."

https://beaconcha.in/validators

Hi there, it would be useful to be able to find blocks by their contained graffiti as we could use this for some particular debugging situations for blocks proposed by Prysm validators we run internally in our testnet

User report:

Creating a visual representation of the state a validator is in would help people understand at what stage their validator is. The visualization should look similar to the visual depicted here. This should help give the user a better idea of what is going on.

Displays this for already active validators from the genesis event.

From the dashboard, it is easy to add all validators to your watchlist. However, then you have to go to the notification tab and need two clicks per validator to get notifications for balance decreases and slashings. There should be a button to activate all of them.

It would be nice to have a default dashboard (or a button that initializes the dashboard) with all the validators on your watchlist.

The attestation appeared missed on the list but proposed in the details page

https://beaconcha.in/validator/a09c5e7520ede03b932d3c06e74699f6770235e2011d3beca4ec77223f09977cf6316b460ebe2bcecedc6ff2d1daa527#pills-attestations
https://beaconcha.in/block/39487

Did i miss or proposed the attestation ?

Unify "Finalized" @ beaconcha.in/epochs

1. Show all history epochs as finalized if one finalized Epoch shows up.
   e.g. . Epoch 1-100 non finalized, Epoch 101 is finalized. Let the user know that Epoch 1-100 was finalized at Epoch 101.

OR

2. Do not change the history as above, but also do not change the finalization status of the previous 10 Epochs (which the explorer does now).

OR

3. Show both?

1. Shows correctly that it has an invalid sig but displays wrong index number/block proposals/Attestation

2. Can't find the validator through the search bar
   

https://beaconcha.in/validator/adbc3f63976d55ab7ade701b450824bcb74b35b6d4c242b802a61100f4048749132040a311c3397cd4d3731dbe01fcdd

1. Show amount of pending validators during genesis state , wait for API? prysmaticlabs/prysm#6445 (comment)

2. Show genesis validators in eth2deposits during genesis state

3. https://altona.beaconcha.in/validator/0xb8d8abb210420f8e47a4245f8ef10a62e1cc85bb1b02a0d03247923e05253edd55d4e083eae53cad0b67c25f64a455fa#deposits , doesn't show "Eth2 Deposits" during genesis

4. Dashboard doesn't accept importing validator during DEPOSITED state

5. https://altona.beaconcha.in/charts
   returns pre genesisThe requested data is currently unavailable, please retry in a few seconds
   to The charts will be available once the beaconchain starts producing blocks! ?

Summary

I found a few issues with the pagination function for search results.

1. The wrong total is shown (total number of validators instead of number of search results)
2. The last page shows the wrong view count (next decimal)
3. The "Last" result button jumps to nowhere.

Details

A picture says more than a thousand words:

I noticed this when using the search function to find validators by deposit address. I was expecting the pagination to show the total number of results found, but instead if seems to be showing the number of ALL known validators.

Additionally, left of the red circle it also shows the wrong count: "61 to 70", when in fact there are 63 results (so it should read "61 to 63").

Finally, when clicking the "Last" button I was expecting to end up on this same page (i.e. page 6). Instead, it shows an empty list (possibly page 1,731). The only way to get the last result page is to repeatedly click "Next".

Note that when I am already on the last page, the "Next" and "Last" buttons are not disabled. Clicking on either on them leads to an empty table.

For analysis of the validators it is helpful to display the validators index.

Currently the eth1+eth2 deposit page only show the pubkey.
If there is still room left on the page. please add the index.

If possible, also add the "Eth2 validator state" on the Eth2_deposit_page
(it is already there own the Eth1_deposit_page)

Witti validator 48 exited due to being slashed. Since then its validator page does not load and only yields an internal server error:

https://witti.beaconcha.in/validator/48

The explorer seems to be down/outdated?

From the URL I can read that it seems to be trying to display testnet3.
As far as I know testnet5 is the current testnet.

Is there a testnet5 version?

Thank you

Allow validators to be searched by index. Index easier to remember and type than pubkey.

I didn't find easy way to do so.

https://beaconcha.in/epochs

Ability to find all blocks by slot status (proposed, missed, orphaned)

Misconception "Slots" / "Blocks"

Slots can be empty, example:

https://beaconcha.in/validators

If sorted by Activation, the indices of the validators should be sorted (ascending).

Small request, but can you add commas to all the large numbers on beaconcha.in -- currently it is a little difficult to read (e.g. instead of 1000, write 1,000):

https://beaconcha.in/block/86239
https://beacon.etherscan.io/slot/86239

Slashings are supposed to be rare events, and for some people each slashing (not just their own validator) is interesting: For example, a spec developer and a client dev will want to investigate the root causes for slashings, where possible. It would be great for me to be able to get notified on all slashings.

Example: https://beaconcha.in/validator/b1971d7f691c3d592b3072e7394ad5a63c1756b9800138d4ae780526be91802edf7ee8db3e6edb5960280e6dc56f3872

Should go to validator 681, but goes to validator 0

For example "ETH" "eTh" and "eth" all return different results.

I think it should be case insensitive. What do you think?

he Y-axis shows incorrect scaling (all ticks are the same)

When doing multiple calls to deposit contract and multiple deposit event generated such as in https://goerli.etherscan.io/tx/0x6492c016dd82c4936489a33c00561d789fb4cd22522ef50b6a5758d1230e7bf3 , it seems that only the last validator in the call list is populated over at « https://altona.beaconcha.in/validators/eth1deposits?q=0x61201ee3bc5b988d7c616870fa0381200aa9a11c », the design also suggests that there SHALL be only one deposit per transaction whereas it MAY be so.

Last deposit data that works: https://altona.beaconcha.in/validator/0x8aa935ac52309037b67b54ec18c6509c508728ecaddc91d8eaece15a17ecccc8dc5cbccbb50e6cf2fb43a23a6692ec43#deposits
First deposit data that doesn't work (indicate non-existent): https://altona.beaconcha.in/validator/0x85fada4773297f49805a35f52225bde1799d9775f16e8c961a321b659525e7e33ddb1bfc1724468d016a6b8c8b49a476#deposits

Hello beaconcha.in! Love the work you guys are doing! Keep it up 😄

Experimentation with the graffiti field of a block is absolutely creative, love the ideas! Although, one issue it brings up is that we are unable to tell which validators belong to who from purely the graffiti. This may cause some issues with detecting forks, and restricts implementation teams to only using purely identifiable graffiti, so any looker can tell which block is from who.

Now, while adding a prefix would be great, an issue with this the graffiti field in a block only allows for 32 bytes, 28 of which are currently being taken up by graffitiwall:280:315:#6060ff, leaving only 4 bytes for a prefix. But along with support for a prefix, I propose making the graffitiwall test less verbose. Possible alternatives could be:

• wall:280:315:#6060ff (20 bytes)
• :280:315:#6060ff(15 bytes)
• gw:280:315:#6060ff (18 bytes)

With the prefix, this could be like: prylabs:280:315:#6060ff (20 bytes). The prefix could also be used for any future "on-hover" features planned.

One other option is to also use #RGB instead of #RRGGBB, but this would limit the color spectrum of the wall at little gain.

Anyways, I know this isn't a priority, and not something of importance currently. But I'm looking into how we can make graffiti more fun for our users in Prysm and an issue with the graffitiwall is the inability to tell whose block is who.

Thank you!

Text: "If the last Finalized Epoch is more than 4 Epochs behind the Head Epoch, all validators will get penalized"

Due to recent spec changes, should be:
"If the last Finalized Epoch is more than 4 Epochs behind, only dishonest validators will get penalized"

https://beaconcha.in/charts/network_liveness

As shown here:
https://www.beaconcha.in/validator/38052
https://www.beaconcha.in/validator/38124

Goes hand in hand with this: #95

Same for topaz testnet: https://beaconcha.in/block/0

https://schlesi.beaconcha.in/block/c9cbcb8ceb9b5f71216f5137282bf6a1e3b50f64e42d6c7fb347abe07eb0db82

https://altona.beaconcha.in/dashboard?validators=134,138,147,178,192,201,202,219,225,235,236 (teku grafitti)

"Proposer" instead of "Proposed by" seems clearer as latter suggests a proposal was already made.

With this change, "Missed" instead of "Skipped" seems clearer because proposers are never skipped, but a proposer can miss their chance of proposing. (While a proposer can deliberately skip their turn, it is not normal behavior, and more likely the proposer went offline and so missed their chance.)

https://beaconcha.in/blocks

When starting the frontend with an initialized but empty database it will throw the following error:

INFO[0000] Error retrieving latest epoch from the database: sql: Scan error on column index 0, name "max": converting NULL to uint64 is unsupported module=services

beaconcha.in reports the Altona genesis block root and state root incorrectly -- https://altona.beaconcha.in/block/0

Correct values can be found in the altona repo -- https://github.com/goerli/altona/tree/master/altona

I wanted to sort epochs by the Voted column, but unfortunately this is not possible. It would be nice if all tables had sortable columns.

It should probably be possible to use the code from #13 and create some form of reusable abstraction which allows to easily apply sorting to any table.

1. pending validators (https://beaconcha.in/ shows 0)

2. wrong average balance https://altona.beaconcha.in/
   only one validator has more than 32.06 ETH but average shows .09

3. Average Daily income chart & Staking rewards chart incorrect

For example my eth1 address is tied to @terencechain and i want to search all the blocks proposed by @terencechain validators

See validator https://beaconcha.in/validator/b8a113e73760699c593762f7816660553b6ce21dadac05b7c75eeafcf56fbcfa6af876166cd6652a1e441e919d1474fe

The axis labels on the first and second y axis do not match the displayed data.

Can we have a login with ETH adress and password not email so that it can save the validators?and can we have a future to add only the eth adress and the page gets the pubkey for the validator deposits?Thx

Just a feature request, but it would be really nice to see the validator attestation effectiveness on the dashboard (https://beaconcha.in/dashboard). The column would be very skinny so seems like it would fit well and not have many downsides.

Currently shows the last scheduled slot until a new epoch starts.
Better UX by showing Epoch, current_slot / last_scheduled_slot.

Not sure if this is supported today, I couldn't figure out how to do it. Would be nice to search and filter blocks base on block graffiti

When clicking a day "candle" in the "Proposal history for all Validators" chart in the Dashboard menu, there could be a list of the proposed blocks filtered for that day

Orphaned block proposals do not receive any rewards, showing them as proposed is misleading

https://beaconcha.in/dashboard?validators=5382 , onyx testnet

It would be nice to have a graph of the size of the beacon chain over time. Beaconscan has one (although it does not appear to be working). This feature could be useful down the line when new validators need to decide their hard drive requirements. I'd be happy to try an tackle this feature myself, but I'm not quite sure what the best way to calculate the chain size would be...