Add protocol-level emergency pause that halts buy and sell while keeping reads live

[Chucks1093]

Summary

If a critical bug or exploit is discovered after deployment, there is currently no way to stop the damage without abandoning the contract entirely. An emergency pause mechanism lets the protocol admin halt all state-changing operations (buy, sell, registration) while keeping all read-only view functions live, so users can still see their balances and prices while the team investigates and prepares a fix.

Scope

• Add a paused: bool field to protocol config storage (default: false)
• Add pause() and unpause() admin-only functions that set this flag and emit a ProtocolPaused / ProtocolUnpaused event
• At the start of buy, sell, and register_creator, check the flag and panic with a new ProtocolPaused error variant if true
• All get_* / quote_* read-only functions are unaffected — they must continue to work while paused
• Only the protocol admin address (from config) may call pause or unpause

Acceptance Criteria

• pause() sets the flag and emits ProtocolPaused event
• unpause() clears the flag and emits ProtocolUnpaused event
• Buy reverts with ProtocolPaused when paused
• Sell reverts with ProtocolPaused when paused
• Creator registration reverts with ProtocolPaused when paused
• All read-only view functions succeed while paused
• Non-admin caller to pause or unpause is rejected with Unauthorized
• Unit tests cover all of the above cases

---

Coordinate on Telegram

[KingDavid9999]

Here's a claim paragraph you can post:

---

Hi, I'd like to claim this issue. I'm familiar with Soroban's storage model, event system, and require_auth patterns from prior contributions, including bounded replay support on pulse-core and smart contract work on AgenticPay, a decentralized freelance payment platform on Stellar. The implementation plan is straightforward: add a paused: bool field to the protocol config (using the appropriate storage tier), wire up pause() and unpause() with admin-only auth guards and ProtocolPaused / ProtocolUnpaused events, then add a check at the entry point of buy, sell, and register_creator that panics with the new ProtocolPaused error variant. All get_* and quote_* view functions will be left untouched. I'll cover all seven acceptance criteria with unit tests. Can I be assigned?

[barry01-hash]

I would love to work on this project

[wheval]

Hello I would love to work on this task

[grantfox-oss]

🦊 GrantFox — @wheval has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #393)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.