Runbook: verify the fee account holds a trustline before registering a token or rotating the fee account

[0xdevcollins]

Source: docs/threat-model.md v1.0, DoS.15 (accepted; process control).

set_fee_account performs no validation and deposit_with_fee_at / release_with_fee_at transfer to the fee account without try_. A fee account without a trustline for a supported token makes create_event, add_funds, and crowdfunding claim_milestone revert for every event in that token until the admin rotates the account.

• Add a pre-flight check to docs/multisig-preflight.md / the ops runbook: for every registered token, confirm the fee account's trustline exists and is authorized before register_supported_token and before set_fee_account
• Add the check to scripts/admin/verify-multisig.sh or a sibling script
• Alert on FeeAccountUpdated and TokenRegistered (see the monitoring issue)

[omeruahelisha8-png]

I have experience in this issue please assign me the task

[abojeEdwin]

Hi maintainer, I've gone through the issue and I have a clear understanding of the fix for this issue. I'd love to be assigned to this issue. Thank you

[prosperceed]

I am excited to work on this issue. I have worked on similar stuff especially with my current project, Peernotary. I will love to work on this issue also.

[guptakumarranjeet150]

Hi maintainers,

I am interested in working on this issue.
Plan:

1. Implement Runbook: verify the fee account holds a trustline before registering a token or rotating the fee account with explicit require_auth checks, secure state storage, and gas optimization.
2. Ensure contract compiles cleanly and passes all cargo tests without warnings.

Looking forward to collaborating on this—please assign!