iotaledger / iota / 34176202233

70%

Build Type

push

github

Committed by web-flow

Commit Message

feat(iota-protocol-config): disable Move-based sponsor authentication on mainnet in v34 (#12850)

# Description of change

Disables Move-based sponsor account authentication on mainnet at
protocol version 34, via the dedicated
`enable_move_authentication_for_sponsor` feature flag.

- The flag (and `pre_consensus_sponsor_only_move_authentication`) were
turned on for mainnet in v32; v34 clears both for `Chain::Mainnet` only.
Devnet and testnet are unaffected.
- Both flags have to be cleared together:
`pre_consensus_sponsor_only_move_authentication()` asserts that
`enable_move_authentication_for_sponsor()` is set, so leaving it on
would panic on mainnet at v34.
- `enable_move_authentication` (the general flag) is untouched — only
the sponsor path is off.

## Links to any relevant issues

N/A

## How the change has been tested

- [x] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [x] Patch-specific tests (correctness, functionality coverage)
- [ ] 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

`cargo test -p iota-protocol-config`: 9 passed, 0 failed. The only
snapshot that changed is `Mainnet_version_34`, where the two flags drop
out of the serialized output.

### Release Notes

- [x] Protocol: Move-based sponsor account authentication is disabled on
mainnet from protocol version 34.
### Release Notes
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] gRPC:

<!-- Do not remove: everything below this line is ignored by the
release-notes check. -->

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Coverage Stats

8 of 8 new or added lines in 1 file covered. (100.0%)

291 existing lines in 25 files now uncovered.

179314 of 253916 relevant lines covered (70.62%)

445700.79 hits per line