Skip to content

Calling pause() when already paused emits redundant event in settlement #348

Description

@therealjhay

Files: settlement_contract/src/lib.rs:278-301

Problem: If pause() is called when the contract is already paused, it writes true to storage (same value) and emits a pause event. This produces a misleading event stream showing two consecutive pause events with no intervening unpause. Off-chain indexers may misinterpret this as a double-pause or missed unpause.

Fix: Add a redundant-pause guard (see Issue 10). Emit a warning or explicitly document in the event docstring that duplicate pause events should be ignored by indexers if the guard is not added.

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions