Welcome! 👋 This repository exists to help AVS (Actively Validated Service) providers contribute metadata about their reward and slashing policies to Dotrisk, a public dashboard powered by A41 restaking insights.
We want to make sure your AVS is accurately represented, and that the wider community can understand and evaluate your protocol’s mechanisms.
❓ First time here? Don’t worry! This guide walks you through everything you need to know.
This repository is used to collect structured metadata from AVS teams. Your submitted data helps populate two key pages in our frontend:
This section shows whether your AVS has clearly defined policies.
For more details, see Reward / Slashing Policy Status
This section evaluates your AVS’s slashing mechanisms using a standardized framework.
For more details, see Operator Set Slashing Mechanism
.
├── eigenlayer/
│ └── {network}/
│ └── {avs_address}/
│ ├── reward_slashing_policy_status.json
│ └── operator_set_slashing_mechanism.json
├── schema/
│ └── avs_category.json
├── sample/
│ ├── reward_slashing_policy_status.json
│ └── operator_set_slashing_mechanism.json
└── .github/
└── pull_request_template.md
🛠️ Place your metadata inside
eigenlayer/{network}/{avs_address}/.
Click the Fork button at the top of the GitHub page to make your own copy.
Go through the Pull Request Template.
It includes essential guidelines and a submission checklist.
Use this file:
📄 reward_slashing_policy_status.json
Use this file:
📄 operator_set_slashing_mechanism.json
Use your AVS address as the folder name:
/eigenlayer/{network}/{avs_address}/
Place the appropriate JSON(s) inside:
reward_slashing_policy_status.jsonoperator_set_slashing_mechanism.json
- From your forked repository, create a PR to the
mainbranch of this repository. - Make sure your metadata adheres to schema and naming rules.
- If introducing a new AVS category, leave a short explanation in the PR comments.
Feel free to open an issue or reach out to the Dotrisk team.
We’re happy to assist with your contribution.
Let’s make AVS metadata transparent and standardized — together! 🚀