Step 1 Access the Quantova Permission Manager

Open a Quantova compatible permission management interface from within QMask or an approved Quantova service.

This interface provides a complete on chain view of

• All QVM applications authorized by your account
• The scope of execution rights granted
• The asset classes affected
• Whether permissions are bounded or open ended

Permissions are enforced at the protocol level by QVM and cannot be bypassed by applications.

Step 2 Connect Your QMask Wallet

Connect QMask to load your Quantova account state.

QMask

• Does not transmit private keys
• Does not custody assets
• Acts as a secure signing and visibility layer for QVM execution permissions

Once connected, QMask retrieves permission data directly from Quantova’s execution layer, ensuring accuracy and integrity.

Step 3 Review Authorized QVM Applications

Select an authorized application to inspect its execution scope.

For each application, QMask displays

• Execution authority type transfer, lock, mint, burn, delegate
• Asset coverage QTOV or protocol issued assets
• Permission duration explicitly limited or ongoing
• Last execution timestamp

This allows users and institutions to audit application access without interacting with the application itself.

Step 4 Revoke Execution Rights

Revoke an application’s execution authority with a signed action via QMask.

Once revoked

The QVM will reject all future execution requests from that application

No transfers, state changes, or asset operations can occur

Revocation is immediate and final until explicitly reauthorized

Revocation does not require application cooperation and cannot be overridden.

Frequently Asked Questions

Does revoking execution rights terminate staking, pooling, or lending activity?

Revocation halts future execution, not historical state.

This means

• No new staking, pooling, or lending actions can occur
• Existing positions remain recorded on chain
• Withdrawal or modification requires new, explicit authorization

This design prevents asset loss while preserving on chain state consistency.

Is disconnecting QMask from an application the same as revoking permissions?

No.

Disconnecting QMask only removes the interface connection. Execution rights remain active until they are explicitly revoked at the QVM level.

Only permission revocation changes on chain enforcement.

When do execution permissions expire?

Permissions persist until one of the following occurs

• The user explicitly revokes them
• The application defines an execution limit enforced by QVM
• A protocol level upgrade invalidates the permission scope

QMask displays the active status and any defined constraints.

Why do some applications request broad or open ended execution authority?

Certain applications require continuous execution rights to operate correctly, such as

• Automated settlement systems
• Continuous liquidity mechanisms
• Protocol level infrastructure services

Quantova makes these permissions transparent, auditable, and revocable, ensuring users remain in full control.