---
# System prepended metadata

title: 'Handover staking miner '
tags: [' parity', 2024H1]

---

## Handover staking miner dev

**what**: “Officially” hand over the staking miner development to a team or community 

**why**: Make sure someone takes ownership of an important – but not runtime related – building block of Staking. Polkadot 1.x a robust and full feature environment (KR-1.06).

**success**:
- [ ] make sure the documentation, tooling and testing envs are production ready
- [ ] find and onboard a team/person/community to maintain the staking miner
---

### 1. Prepare 
- [x] check current documentation
- [ ] check/improve the current integration tests (with trimming)
- [x] check the current ops/infra and monitoring setup. Who's currently responsible? (Bulat/Pierre)
- [ ] improve builds and operation visibility https://github.com/paritytech/devops/issues/3276

How to ensure that we keep an eye on the staking miner status, after handover? (monitoring)

#### Documentation
- [ ] Add Parity devops section (i.e. how to request new staking-miner to be released) to repo README https://github.com/paritytech/polkadot-staking-miner/
- [ ] Improve rustdocs https://docs.rs/polkadot-staking-miner/1.3.1/polkadot_staking_miner/
- [ ] README about how to run staking-miner profitably, both for our internal teams and external.
- [ ] Outline MB-Miner requirements (needs dev for parachain soon)

#### Infra setup/devops

- Currently maintained by the devops team
- Documentation of the current devops process/infra (mainly for devops) https://github.com/paritytech/devops/wiki/Staking-Miner
- For developers, the release process is to request staking-miner upgrades in  https://github.com/paritytech/devops/issues
- ⭐ Could be improved: automate by setting up `renovatebot` to upgrade in the few days following new releases
    - staking-miner is relatively stable, so perhaps no need to automate releases.

#### Monitoring:
- (for devs) current notifications (quite verbose) in [Staking-miner monitoring](https://matrix.to/#/!KNucnejatArfkBbyPg:parity.io?via=parity.io) Element channel.
- infra related https://grafana.teleport.parity.io/d/_WeQ9_G7k/staking-miner-overview?orgId=1
- more in https://github.com/paritytech/devops/wiki/Staking-Miner

### 2. Handover
- [ ] Post on Polkadot forum asking for contributors
- [ ] Request for contrib/project to run the infra for each chain for redundancy
- [ ] Tap into the Treasury to fund infra (and perhaps development?)

---

### Meetings with Niklas

- Monitoring is not paid very attention at the moment 
    - not perfect, what can be improved?
- Run integration-tests to keep track with the polkadot-sdk master (not releases.)
    - staking miner integration tests running every day
        - job: https://github.com/paritytech/polkadot-staking-miner/tree/main/.github/workflows/actions/prepare-binaries
        - builds off polkadot-sdk/release based on `master` and then tests it against it
    - TODO: (element integration) send a message every time it fails
- staking-miner playground is currently failing (babe integration required).
- Staking miner playground is not bulletproof
    - not fully deterministic due to the randomness introduced every test (hacky)
    - test trimming the solutions (not super critical in any case)
- Monitoring improvements:
    - we only improve whether the solution has been or not accepted
    - TODO: no monitoring wrt the other staking miners that may be competing
    - other solutions seem to be better
    - TODO: increase delay?