Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding BLOOM/DARK #134

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

leo42
Copy link

@leo42 leo42 commented Oct 31, 2023

BLOOM operates a large cluster including the DARK pool.

The operation also serves several stake-pool-as-a-service clients for whom we do not have any solid information

All Submissions:

  • Have you followed the guidelines in our Contributing documentation?
  • Have you verified that there aren't any other open Pull Requests for the same update/change?
  • Does the Pull Request pass all tests?

Description

/* Add a short description of your Pull Request */

Checklist

/* Keep from below the appropriate checklist for your Pull Request and remove the others */

New Ledger Support Submissions:

  • What mapping information did you add for the new ledger?
    • identifiers
    • addresses
    • clusters
    • legal links
  • Did you create a new parser?
    • If yes, did you create a unit test for the new parser?
    • If no, which parser did you reuse?
      • DefaultParser
      • DummyParser
      • EthereumParser
  • Did you create a new mapping?
    • If yes, did you create a unit test for the new mapping?
    • If no, which mapping did you reuse? /* mapping name */
      • DefaultMapping
      • DummyMapping
      • EthereumMapping
      • CardanoMapping
      • TezosMapping
  • Did you enable the parser for the new ledger in consensus_decentralization/parse.py?
  • Did you enable the mapping for the new ledger in consensus_decentralization/map.py?
  • Did you document support for the new ledger as described in our Contributing documentation?

Update Mapping Support Information Submissions:

  • For which ledger do you update the mapping information?
    • /* ledger name */
  • What mapping information do you update?
    • identifiers
    • addresses
    • clusters
    • legal links
  • Did you update the tests (if needed)?

New Metric Support Submissions:

  • Did you put the metric's script under consensus_decentralization/metrics?
  • Did you name the metric's main function of the script compute_{metric name}?
  • Did you import the metric's main function to consensus_decentralization/analyze.py?
  • Did you add the new metric (and possible parameter values) to config.yaml?
  • Did you write unit tests for the new metric?
  • Did you document the new metric in the documentation pages?

BLOOM operates a large cluster including the DARK pool.

The operation also serves several stake-pool-as-a-service clients for whom we do not have any solid information
@dimkarakostas
Copy link
Member

Which reward address do these two pools share? Is there any other public info to correlate them?

Also could you edit the PR's description to remove the parts of the template that don't apply here? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants