You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to better introspect the number of validators running charon. One of the low trust ways to approximate it, is to measure the number of charon blocks produced.
This repo is an ml classifier of blocks. This PR might give us an indication about how we go about classifying us as existing client. Or we might have to add training data as described here, sigp/blockprint#1 (we would also need to have blocks produced with charon in that training data, the data that's in the repo if for mainnet won't include any charon blocks)
If there is anything to highlight as out of scope for this issue, please outline it here.
The text was updated successfully, but these errors were encountered:
OisinKyne
changed the title
Add charon examples to blockprint by sigma prime so rated and other tools can identify charon blocks
Add charon examples to blockprint rated and other tools can identify charon blocks
Dec 12, 2022
OisinKyne
changed the title
Add charon examples to blockprint rated and other tools can identify charon blocks
Add charon examples to blockprint to identify charon blocks
Dec 12, 2022
Problem to be solved
We want to better introspect the number of validators running charon. One of the low trust ways to approximate it, is to measure the number of charon blocks produced.
Proposed solution
Blockprint
This repo is an ml classifier of blocks. This PR might give us an indication about how we go about classifying us as existing client. Or we might have to add training data as described here, sigp/blockprint#1 (we would also need to have blocks produced with charon in that training data, the data that's in the repo if for mainnet won't include any charon blocks)
Relevant from Arisk
Out of Scope
If there is anything to highlight as out of scope for this issue, please outline it here.
The text was updated successfully, but these errors were encountered: