Update wallet-stake-permission.mdx

Author: rad2520

src/content/docs/explanations/system/wallet-stake-permission.mdx

@@ -13,31 +13,17 @@ import {
 This version is based on the Torus v0.69 and is expected to change with the Torus v1.
 </Aside>
 
-The Wallet scope enables cold-hot wallet behavior, where high-value accounts can delegate specific 
-operations to more accessible accounts without exposing private keys.    
-This significantly improves security by allowing cold storage accounts to remain offline while still participating in network staking activities.
+The Wallet Permission Scope will enable granular delegation of all wallet operations through the Torus Permission System. Currently, only Stake operations are implemented as low-hanging fruit for wallet security improvements. 
 
-### Core Functions
+The Wallet Stake Permission enables cold-hot wallet behavior, where high-value secured keys can delegate stake operations to less secure keys utilized only for active protocol participation. 
 
-* **Cold-Hot Wallet Architecture:** High-value accounts can delegate operational permissions while keeping primary keys in cold storage, eliminating the security-convenience tradeoff.
-* **Granular Operation Control:** Specific wallet operations can be delegated independently, allowing precise control over what delegated accounts can perform.
-* **Non-Transferable Delegation:** Delegated operations cannot access or transfer the principal funds, maintaining asset security even if hot wallets are compromised.
+This feature also enables to create a highly secure offline cold-key that never interacts with any webapp and delegate Stake Permission as exclusive (delegator loses permission) & irrevocable to the new key. If your main key gets compromised the tokens cannot be unstaked and hence not transferred. However, an attacker could attempt to immediately transfer as soon as you choose to unstake. But as long as staked, tokens are untouchable.
 
-#### Rules
+It's not a perfect security feature and as standard practice it will eventually be replaced by Transfer Permissions, but it is a meaningful improvement and we recommend high-value keys to apply it.
 
-* **Operation Scoping:** Each delegation specifies exactly which wallet operations are permitted, preventing scope creep.
-* **Principal Protection:** Delegated accounts cannot perform operations that would reduce the principal balance or transfer core assets.
-* **Revocation Terms:** Can be configured as revocable or irrevocable.
-* **Constraint Inheritance:** Security constraints from the cold wallet apply to all delegated operations, ensuring consistent security policies.
-* **Time-bound Delegation:** Delegations can include expiration times for automatic security cleanup.
-
-#### Active Delegation Behavior
-
-When a wallet permission delegation is active, the delegator can choose the level of operational control:
-
-* **Optional Exclusive Access:** The delegator can choose whether to retain direct control alongside the recipient through the exclusive access parameter
-* **Recipient Authority:** The designated recipient can perform the specific wallet operations covered by the permission
-* **Asset Constraints:** All operations are constrained to existing assets, meaning no new staking from available balance  
+### Core Functions of Stake Permission
+* **Exclusive Delegation** The delegator key loses the wallet permission.
+* **Improved Key Security:** Enables cold-hotkey behavior.
 
 ### Related Concepts
 
@@ -47,4 +33,4 @@ When a wallet permission delegation is active, the delegator can choose the leve
 
 <Aside type="tip" title="Ready to Set Up Wallet Delegation?">
 Follow our [step-by-step guide to create wallet stake permissions](https://docs.torus.network/how-to-guides/system/create-wallet-stake-permission/) for practical implementation instructions.
-</Aside>
+</Aside>