From 0af3db3f8a06cb748f7a14eca6093f08c66535e8 Mon Sep 17 00:00:00 2001 From: indirection42 Date: Wed, 30 Oct 2024 10:18:15 +0800 Subject: [PATCH] add read-only execution suggestion --- text/0126-introduce-xcq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0126-introduce-xcq.md b/text/0126-introduce-xcq.md index 59694e34..a6acfe43 100644 --- a/text/0126-introduce-xcq.md +++ b/text/0126-introduce-xcq.md @@ -354,7 +354,7 @@ Some strategies to address this issue include: - Integration tests to ensure proper interaction with off-chain wallets/UI and on-chain XCM, including the aforementioned use cases in **Motivation** section. - Security: - - The XCQ system must enforce a strict read-only policy for all query operations. A mechanism should be implemented to prevent any state-changing operations within XCQ queries. + - The XCQ system must enforce a strict read-only policy for all query operations. A mechanism should be implemented to prevent any state-changing operations within XCQ queries. For example, use `frame_support::storage::with_transaction` to do a rollback after the query. - Clear guidelines and best practices should be provided for parachain developers to ensure secure implementation. ## Performance, Ergonomics, and Compatibility