From 57120e2407651cc7675a6c85fca30d244b44b8d8 Mon Sep 17 00:00:00 2001 From: "https://github.com/Sipher" Date: Thu, 11 Sep 2025 19:17:24 -0300 Subject: [PATCH 1/5] Add Wallet Stake Permission explanations and create guide for setting it up in Torus Portal to improve documentation clarity --- astro.config.mjs | 2 + .../system/wallet-scope-delegation.mdx | 50 ++++++++ .../system/create-wallet-stake-permission.mdx | 112 ++++++++++++++++++ 3 files changed, 164 insertions(+) create mode 100644 src/content/docs/explanations/system/wallet-scope-delegation.mdx create mode 100644 src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx diff --git a/astro.config.mjs b/astro.config.mjs index 41fd85f..0e8ee6b 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -40,6 +40,7 @@ export default defineConfig({ { label: "Control Space", slug: "explanations/system/control-space" }, { label: "Permission System", slug: "explanations/system/permission-system" }, { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" }, + { label: "Wallet Stake Permission", slug: "explanations/system/wallet-scope-delegation" }, { label: "Stream Permissions", slug: "explanations/system/stream-permissions" }, { label: "Capability Permissions", slug: "explanations/system/capability-permissions" }, ], @@ -88,6 +89,7 @@ export default defineConfig({ { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" }, { label: "Create Stream Permission", slug: "how-to-guides/system/create-stream-permission" }, + { label: "Create Wallet Stake Permission", slug: "how-to-guides/system/create-wallet-stake-permission" }, { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" }, ], }, diff --git a/src/content/docs/explanations/system/wallet-scope-delegation.mdx b/src/content/docs/explanations/system/wallet-scope-delegation.mdx new file mode 100644 index 0000000..3c8b067 --- /dev/null +++ b/src/content/docs/explanations/system/wallet-scope-delegation.mdx @@ -0,0 +1,50 @@ +--- +title: Wallet Stake Permission +description: Understanding secure wallet staking permissions and delegation. +--- + +import { + Aside, + Card, + CardGrid, +} from "@astrojs/starlight/components"; + + + +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. + +### Core Functions + +* **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. + +#### Rules + +* **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 + +### Related Concepts + +- **[Permission System](https://docs.torus.network/explanations/system/permission-system/)** - Core permission mechanics and delegation basics +- **[Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/)** - Advanced delegation patterns and composition +- **[Staking](https://docs.torus.network/explanations/holders/staking/)** - Understanding staking mechanics and rewards + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx new file mode 100644 index 0000000..cf2241c --- /dev/null +++ b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx @@ -0,0 +1,112 @@ +--- +title: Create Wallet Stake Permission +description: Step-by-step guide to creating wallet stake permissions to delegate staking operations while keeping your keys secure. +--- + +import { + Steps, + Aside, + CardGrid, + Card +} from "@astrojs/starlight/components"; + +import RedText from '/src/components/RedText.astro'; + +In this guide, we'll walk through how to create wallet stake permissions in the Torus Portal. +Wallet stake permissions enable cold-hot wallet behavior, allowing you to delegate staking operations +to more accessible accounts while keeping your primary keys securely stored offline. + +## Why Create Wallet Stake Permission? + +You want to maintain high security for your primary wallet while still being able to manage staking operations efficiently. +Wallet stake permissions let you delegate staking management to hot wallets without exposing your principal funds to transfer risks. + +#### What we will accomplish + +- [Create wallet stake permission](#create-wallet-stake-permission) + + + +## Prerequisites + + + + You must have an account with existing stake that you want to delegate management for. + Follow the [staking guide](https://docs.torus.network/how-to-guides/holders/stake-your-torus/) to understand staking basics. + + + Know the address of the hot wallet account that will manage your staking operations. + + + Ensure you have enough TORUS to cover permission creation transaction fees. + + + +## Create Wallet Stake Permission + + + +1. **Visit the [Wallet Permissions Tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/wallet)** + Click the **Wallet Permission** tab under Permissions in the Torus Portal. + +2. **Connect your Cold Wallet** + Ensure you're connected with the wallet account that holds the stakes you want to delegate management for. + +3. **Fill the form** + ```md + # Recipient Address + Search agents by name or address that will receive the staking permission. + If your target is not an agent, you can enter the wallet address directly. + + # Stake Permissions + - **Exclusive Delegation**: Grant exclusive access to stake operations + (prevents delegator from using stake directly) + - **Allow Stake Movement**: Delegate permission to unstake, + exclusively granting it to the recipient + + # Duration + - **Indefinite**: Permission remains valid indefinitely + - **Until Block**: Permission expires at a specific block + + # Revocation Terms + - **Irrevocable**: Cannot be revoked + - **Revocable by Delegator**: Only you can revoke this permission + - **Revocable After**: Can be revoked after a specific condition is met + ``` + + + +4. **Submit and Sign Transaction** + Click **Create Wallet Stake Permission**. + Open SubWallet and sign the transaction. + +5. **All Done** + You've successfully created the wallet stake permission. + The receiving account can now manage your staking operations within the limits you've set. + + + +## What's Next? + +Now that you've created wallet stake permission, you might want to: + +- **Monitor your delegations**: Track delegation status in the [Manage Permissions tab](https://portal.torus.network/permissions/manage-permission) +- **Optimize your stakes**: Work with your hot wallet to [manage staking positions](https://docs.torus.network/how-to-guides/holders/stake-your-torus/) efficiently +- **Understand COLD vs HOT Wallet**: Watch [this Coingecko video](https://www.youtube.com/watch?v=kf28zqP_F2s) + +Connect with the community: +- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements +- [Telegram](https://t.me/torusnetwork) — General chat and announcements +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file From 569d2c8885e29469a9dc78a98621c10282e6283f Mon Sep 17 00:00:00 2001 From: "https://github.com/Sipher" Date: Thu, 11 Sep 2025 19:25:46 -0300 Subject: [PATCH 2/5] Clarify wallet stake permission details and add create guide to enhance documentation and user understanding in Torus Portal --- astro.config.mjs | 2 +- ...{wallet-scope-delegation.mdx => wallet-stake-permission.mdx} | 2 +- src/content/docs/explanations/table-of-contents.mdx | 1 + .../how-to-guides/system/create-wallet-stake-permission.mdx | 2 +- src/content/docs/how-to-guides/table-of-contents.mdx | 1 + 5 files changed, 5 insertions(+), 3 deletions(-) rename src/content/docs/explanations/system/{wallet-scope-delegation.mdx => wallet-stake-permission.mdx} (93%) diff --git a/astro.config.mjs b/astro.config.mjs index 0e8ee6b..a3c3256 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -40,7 +40,7 @@ export default defineConfig({ { label: "Control Space", slug: "explanations/system/control-space" }, { label: "Permission System", slug: "explanations/system/permission-system" }, { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" }, - { label: "Wallet Stake Permission", slug: "explanations/system/wallet-scope-delegation" }, + { label: "Wallet Stake Permission", slug: "explanations/system/wallet-stake-permission" }, { label: "Stream Permissions", slug: "explanations/system/stream-permissions" }, { label: "Capability Permissions", slug: "explanations/system/capability-permissions" }, ], diff --git a/src/content/docs/explanations/system/wallet-scope-delegation.mdx b/src/content/docs/explanations/system/wallet-stake-permission.mdx similarity index 93% rename from src/content/docs/explanations/system/wallet-scope-delegation.mdx rename to src/content/docs/explanations/system/wallet-stake-permission.mdx index 3c8b067..1d5830c 100644 --- a/src/content/docs/explanations/system/wallet-scope-delegation.mdx +++ b/src/content/docs/explanations/system/wallet-stake-permission.mdx @@ -46,5 +46,5 @@ When a wallet permission delegation is active, the delegator can choose the leve - **[Staking](https://docs.torus.network/explanations/holders/staking/)** - Understanding staking mechanics and rewards \ No newline at end of file diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx index 07041c1..70808ac 100644 --- a/src/content/docs/explanations/table-of-contents.mdx +++ b/src/content/docs/explanations/table-of-contents.mdx @@ -25,6 +25,7 @@ Core system components and mechanisms: - [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework - [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority - [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms +- [Wallet Stake Permission](https://docs.torus.network/explanations/system/wallet-stake-permission/) — Secure cold-hot wallet staking delegation - [Stream Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled - [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints diff --git a/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx index cf2241c..41ee08e 100644 --- a/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx +++ b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx @@ -108,5 +108,5 @@ Connect with the community: - [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx index 2cb0dec..bc19142 100644 --- a/src/content/docs/how-to-guides/table-of-contents.mdx +++ b/src/content/docs/how-to-guides/table-of-contents.mdx @@ -26,6 +26,7 @@ If you're managing permissions and system-level coordination: - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/) — Delegate access to specific agent endpoints and services - [Create Stream Permission](https://docs.torus.network/how-to-guides/system/create-stream-permission/) — Share token emission streams with other agents +- [Create Wallet Stake Permission](https://docs.torus.network/how-to-guides/system/create-wallet-stake-permission/) — Enable secure cold-hot wallet staking delegation - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) — View, edit, and revoke existing permission delegations --- From 37146a4c500fac4e319dbecc8f5e9e26bbf64903 Mon Sep 17 00:00:00 2001 From: rad2520 <84401808+rad2520@users.noreply.github.com> Date: Sat, 13 Sep 2025 19:54:37 +0200 Subject: [PATCH 3/5] Update wallet-stake-permission.mdx --- .../system/wallet-stake-permission.mdx | 30 +++++-------------- 1 file changed, 8 insertions(+), 22 deletions(-) diff --git a/src/content/docs/explanations/system/wallet-stake-permission.mdx b/src/content/docs/explanations/system/wallet-stake-permission.mdx index 1d5830c..f7f067a 100644 --- a/src/content/docs/explanations/system/wallet-stake-permission.mdx +++ b/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. -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 \ No newline at end of file + From ecc3431970701d1b9bc8cc496c2bc17828672c19 Mon Sep 17 00:00:00 2001 From: rad2520 <84401808+rad2520@users.noreply.github.com> Date: Sat, 13 Sep 2025 20:00:03 +0200 Subject: [PATCH 4/5] Update wallet-stake-permission.mdx --- .../docs/explanations/system/wallet-stake-permission.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/content/docs/explanations/system/wallet-stake-permission.mdx b/src/content/docs/explanations/system/wallet-stake-permission.mdx index f7f067a..58a06e2 100644 --- a/src/content/docs/explanations/system/wallet-stake-permission.mdx +++ b/src/content/docs/explanations/system/wallet-stake-permission.mdx @@ -15,9 +15,14 @@ This version is based on the Torus v0.69 and is expected to change with the Toru 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. +**Cold-Hot Key Behavior** + 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. -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. +**Tool for Key Security** + +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. 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. From 1e3b4a71f930f33e60a1276ebbd50427cf3bfba2 Mon Sep 17 00:00:00 2001 From: "https://github.com/Sipher" Date: Tue, 16 Sep 2025 17:48:09 -0300 Subject: [PATCH 5/5] Rename "Wallet Stake Permission" to "Wallet Permission" across documentation for consistency and clarity in user guidance --- astro.config.mjs | 4 ++-- .../system/wallet-stake-permission.mdx | 8 +++---- .../docs/explanations/table-of-contents.mdx | 2 +- .../system/create-wallet-stake-permission.mdx | 24 +++++++++---------- .../docs/how-to-guides/table-of-contents.mdx | 2 +- 5 files changed, 20 insertions(+), 20 deletions(-) diff --git a/astro.config.mjs b/astro.config.mjs index a3c3256..92d93f0 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -40,9 +40,9 @@ export default defineConfig({ { label: "Control Space", slug: "explanations/system/control-space" }, { label: "Permission System", slug: "explanations/system/permission-system" }, { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" }, - { label: "Wallet Stake Permission", slug: "explanations/system/wallet-stake-permission" }, { label: "Stream Permissions", slug: "explanations/system/stream-permissions" }, { label: "Capability Permissions", slug: "explanations/system/capability-permissions" }, + { label: "Wallet Permission", slug: "explanations/system/wallet-stake-permission" }, ], }, { @@ -89,8 +89,8 @@ export default defineConfig({ { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" }, { label: "Create Stream Permission", slug: "how-to-guides/system/create-stream-permission" }, - { label: "Create Wallet Stake Permission", slug: "how-to-guides/system/create-wallet-stake-permission" }, { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" }, + { label: "Create Wallet Permission", slug: "how-to-guides/system/create-wallet-stake-permission" }, ], }, { diff --git a/src/content/docs/explanations/system/wallet-stake-permission.mdx b/src/content/docs/explanations/system/wallet-stake-permission.mdx index 58a06e2..b29e3ea 100644 --- a/src/content/docs/explanations/system/wallet-stake-permission.mdx +++ b/src/content/docs/explanations/system/wallet-stake-permission.mdx @@ -1,6 +1,6 @@ --- -title: Wallet Stake Permission -description: Understanding secure wallet staking permissions and delegation. +title: Wallet Permission +description: Understanding secure wallet permissions and delegation. --- import { @@ -17,7 +17,7 @@ The Wallet Permission Scope will enable granular delegation of all wallet operat **Cold-Hot Key Behavior** -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. +The Wallet 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. **Tool for Key Security** @@ -37,5 +37,5 @@ It's not a perfect security feature and as standard practice it will eventually - **[Staking](https://docs.torus.network/explanations/holders/staking/)** - Understanding staking mechanics and rewards diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx index 70808ac..b2fb047 100644 --- a/src/content/docs/explanations/table-of-contents.mdx +++ b/src/content/docs/explanations/table-of-contents.mdx @@ -25,9 +25,9 @@ Core system components and mechanisms: - [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework - [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority - [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms -- [Wallet Stake Permission](https://docs.torus.network/explanations/system/wallet-stake-permission/) — Secure cold-hot wallet staking delegation - [Stream Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled - [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints +- [Wallet Permission](https://docs.torus.network/explanations/system/wallet-stake-permission/) — Secure cold-hot wallet staking delegation --- diff --git a/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx index 41ee08e..b510f9b 100644 --- a/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx +++ b/src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx @@ -1,6 +1,6 @@ --- -title: Create Wallet Stake Permission -description: Step-by-step guide to creating wallet stake permissions to delegate staking operations while keeping your keys secure. +title: Create Wallet Permission +description: Step-by-step guide to creating wallet permissions to delegate staking operations while keeping your keys secure. --- import { @@ -12,18 +12,18 @@ import { import RedText from '/src/components/RedText.astro'; -In this guide, we'll walk through how to create wallet stake permissions in the Torus Portal. -Wallet stake permissions enable cold-hot wallet behavior, allowing you to delegate staking operations +In this guide, we'll walk through how to create wallet permissions in the Torus Portal. +Wallet permissions enable cold-hot wallet behavior, allowing you to delegate staking operations to more accessible accounts while keeping your primary keys securely stored offline. -## Why Create Wallet Stake Permission? +## Why Create Wallet Permission? You want to maintain high security for your primary wallet while still being able to manage staking operations efficiently. -Wallet stake permissions let you delegate staking management to hot wallets without exposing your principal funds to transfer risks. +Wallet permissions let you delegate staking management to hot wallets without exposing your principal funds to transfer risks. #### What we will accomplish -- [Create wallet stake permission](#create-wallet-stake-permission) +- [Create wallet permission](#create-wallet-permission) 4. **Submit and Sign Transaction** - Click **Create Wallet Stake Permission**. + Click **Create Wallet Permission**. Open SubWallet and sign the transaction. 5. **All Done** - You've successfully created the wallet stake permission. + You've successfully created the wallet permission. The receiving account can now manage your staking operations within the limits you've set. ## What's Next? -Now that you've created wallet stake permission, you might want to: +Now that you've created wallet permission, you might want to: - **Monitor your delegations**: Track delegation status in the [Manage Permissions tab](https://portal.torus.network/permissions/manage-permission) - **Optimize your stakes**: Work with your hot wallet to [manage staking positions](https://docs.torus.network/how-to-guides/holders/stake-your-torus/) efficiently @@ -108,5 +108,5 @@ Connect with the community: - [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx index bc19142..0dfc8ec 100644 --- a/src/content/docs/how-to-guides/table-of-contents.mdx +++ b/src/content/docs/how-to-guides/table-of-contents.mdx @@ -26,8 +26,8 @@ If you're managing permissions and system-level coordination: - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/) — Delegate access to specific agent endpoints and services - [Create Stream Permission](https://docs.torus.network/how-to-guides/system/create-stream-permission/) — Share token emission streams with other agents -- [Create Wallet Stake Permission](https://docs.torus.network/how-to-guides/system/create-wallet-stake-permission/) — Enable secure cold-hot wallet staking delegation - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) — View, edit, and revoke existing permission delegations +- [Create Wallet Permission](https://docs.torus.network/how-to-guides/system/create-wallet-stake-permission/) — Enable secure cold-hot wallet staking delegation ---