---
# System prepended metadata

title: Untitled

---

- [x] Endpoint validation (covered by e2e)
- [x] Add module for KAPI already working with curated module (covered with e2e)
- [x] Empty DB
  - [x] Update works for one modules (covered by e2e)
  - [x] Update works for two modules (covered by e2e)
- [x] DB is not empty, add unused keys/add used keys (registry has test with changing usedSigningKeys in operator, update happen from usedSigningKeys to totalSigningKeys; if change totalSigningKeys, when keys will be updated from usedSigningKeys (or 0) to new value of totalSigningKeys).
- [x] New operators was added (covered by e2e ?)
- [x] execution layer meta updates always when we run job for a new block
- [x] changing operator (covered by e2e)
- [x] add new operator (covered by e2e)
- [x] add new module
    - [x] module without keys (covered by e2e)
    - [x] module with 1 operator, 0 keys (e2e)
    - [x] module with N operators, M keys (covered by e2e)


check number of keys in kapi
  - goerli
  - [x] mainnet

will not check:
- [ ] what will happen if module was deleted from list of sr modules , how kapi process it? 
- [ ] Could the name and type of the module be changed? How KAPI should behave? ( process exit)
- [ ] if type is not simple-dvt-onchain-v1 or curated-onchain-v1, process exit