IntersectMBO / IntersectMBO/formal-ledger-specifications
DRep expiration is "bumped" when there are no proposals even if the DRep has already expired
Open
conformance
era: conway
- Dominant language
- Agda
- Stars
- 52
- Forks
- 20
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 7
Description
This behaviour shows up as a conformance testing failure as well, since the implementation only bumps the expiration epoch of DReps which are not expired.
This difference of behaviour is exhibited by the test:
- `LEDGER/Withdraw from a key delegated to a DRep that expired after delegation`
Contributor guide
Assessment
This issue has not been assessed yet.