iotaledger / iota / 30230091073

69%

Build Type

push

github

Committed by web-flow

Commit Message

feat(iota-node,iota-swarm-config): submit deny rule proposals on startup and epoch change (#12221) (#12232)

# Description of change

Part of #10749. Validators now announce their local
`TransactionDenyConfig` as a `DenyRuleProposal` through consensus, on
startup and on every epoch change (vote tracking is epoch-scoped).

- Submission hook in `IotaNode` next to the capabilities submit, gated
on `deny_rule_governance`; empty configs are not announced
- `DenyRuleProposal::new` stamps a wall-clock generation so a
resubmission supersedes earlier proposals (mirrors
`AuthorityCapabilitiesV1::new`)
- `TransactionDenyConfig::to_deny_rule_set()` converts the local config
to the full-state proposal payload
- `with_transaction_deny_config` knob through the validator
config/swarm/test-cluster builders (test infra)
- E2e simtest verifying proposals converge and become active on all
validators
- Doc fix in `post_consensus_validation.rs` left over from #12231

Stacked on the #12220 branch (PR #12231).

## Links to any relevant issues

Fixes #12221.

## How the change has been tested

- [x] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [x] Patch-specific tests (correctness, functionality coverage)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] I have checked that new and existing unit tests pass locally with
my changes

Coverage Stats

86 of 139 new or added lines in 8 files covered. (61.87%)

487 existing lines in 18 files now uncovered.

169196 of 244121 relevant lines covered (69.31%)

461482.66 hits per line