diff --git a/astro.config.mjs b/astro.config.mjs
index 1495d17..289b818 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -33,20 +33,6 @@ export default defineConfig({
label: "Explanations",
items: [
{ label: "Table of Contents", slug: "explanations/table-of-contents" },
- {
- label: "v0.6",
- collapsed: true,
- items: [
- { label: "Control Space", slug: "explanations/v06/control-space" },
- { label: "Permission System", slug: "explanations/v06/permissions" },
- {
- label: "Recursive Delegation",
- slug: "explanations/v06/recursive-delegation",
- },
- { label: "Emission Permissions", slug: "explanations/v06/emission-permissions" },
- { label: "Governance & DAO", slug: "explanations/v06/governance-dao" },
- ],
- },
{
label: "Holders",
collapsed: true,
@@ -61,10 +47,12 @@ export default defineConfig({
collapsed: true,
items: [
{ label: "Agent Registration", slug: "explanations/builders/agent-registration" },
- { label: "Agent Editing", slug: "explanations/builders/agent-editing" },
+ { label: "Agent Managing", slug: "explanations/builders/agent-managing" },
{ label: "Demand Signaling", slug: "explanations/builders/demand-signaling" },
{ label: "Agent Server", slug: "explanations/builders/agent-server" },
{ label: "Agent Client", slug: "explanations/builders/agent-client" },
+ { label: "Control Space", slug: "explanations/builders/control-space" },
+ { label: "Capability Permissions", slug: "explanations/builders/capability-permissions" },
],
},
{
@@ -72,7 +60,12 @@ export default defineConfig({
collapsed: true,
items: [
{ label: "Root Agents", slug: "explanations/goal-leaders/root-agents" },
+ { label: "DAO Treasury", slug: "explanations/goal-leaders/dao-treasury" },
{ label: "Emission Proposals", slug: "explanations/goal-leaders/emission-proposals" },
+ { label: "Permission System", slug: "explanations/goal-leaders/permissions" },
+ { label: "Recursive Delegation", slug: "explanations/goal-leaders/recursive-delegation" },
+ { label: "Emission Permissions", slug: "explanations/goal-leaders/emission-permissions" },
+ { label: "Governance & DAO", slug: "explanations/goal-leaders/governance-dao" },
],
},
{ label: "Concepts & Terminology", slug: "explanations/concepts-terminology" },
@@ -89,6 +82,7 @@ export default defineConfig({
{ label: "Setup a Wallet", slug: "how-to-guides/holders/setup-a-wallet" },
{ label: "Bridge from Base", slug: "how-to-guides/holders/bridge-from-base" },
{ label: "Stake your Torus", slug: "how-to-guides/holders/stake-your-torus" },
+ { label: "Vote on Proposals", slug: "how-to-guides/holders/vote-on-proposals" },
],
},
{
@@ -96,10 +90,8 @@ export default defineConfig({
collapsed: true,
items: [
{ label: "Register an Agent", slug: "how-to-guides/builders/register-an-agent" },
- { label: "Edit your Agent", slug: "how-to-guides/builders/edit-your-agent" },
+ { label: "Manage your Agent", slug: "how-to-guides/builders/manage-your-agent" },
{ label: "Manage Capabilities", slug: "how-to-guides/builders/manage-capabilities" },
- { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" },
- { label: "Recursive Delegation", slug: "how-to-guides/builders/recursive-delegation" },
{ label: "Create a Signal", slug: "how-to-guides/builders/create-signal" },
{ label: "Setup Agent Server", slug: "how-to-guides/builders/setup-agent-server" },
{ label: "Setup Agent Client", slug: "how-to-guides/builders/setup-agent-client" },
@@ -110,7 +102,11 @@ export default defineConfig({
collapsed: true,
items: [
{ label: "Become a Root Agent", slug: "how-to-guides/goal-leaders/become-a-root-agent" },
+ { label: "Request DAO Treasury Transfer", slug: "how-to-guides/goal-leaders/request-dao-treasury-transfer" },
{ label: "Create Emission Proposal", slug: "how-to-guides/goal-leaders/create-emission-proposal" },
+ { label: "Create Capability Permission", slug: "how-to-guides/goal-leaders/create-capability-permission" },
+ { label: "Create Emission Permission", slug: "how-to-guides/goal-leaders/create-emission-permission" },
+ { label: "Manage Permissions", slug: "how-to-guides/goal-leaders/manage-permissions" },
],
},
],
diff --git a/public/images/how-to-guide/agent-management/click-on-deregister-agent.png b/public/images/how-to-guide/agent-management/click-on-deregister-agent.png
new file mode 100644
index 0000000..44f2631
Binary files /dev/null and b/public/images/how-to-guide/agent-management/click-on-deregister-agent.png differ
diff --git a/public/images/how-to-guide/agent-management/click-on-manage-agent-tab.png b/public/images/how-to-guide/agent-management/click-on-manage-agent-tab.png
new file mode 100644
index 0000000..3926b55
Binary files /dev/null and b/public/images/how-to-guide/agent-management/click-on-manage-agent-tab.png differ
diff --git a/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png b/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png
deleted file mode 100644
index 5e7def3..0000000
Binary files a/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png and /dev/null differ
diff --git a/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png b/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png
deleted file mode 100644
index 6f4356e..0000000
Binary files a/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png and /dev/null differ
diff --git a/public/images/how-to-guide/vote-on-proposals/change-vote-status.png b/public/images/how-to-guide/vote-on-proposals/change-vote-status.png
new file mode 100644
index 0000000..e2f4ea2
Binary files /dev/null and b/public/images/how-to-guide/vote-on-proposals/change-vote-status.png differ
diff --git a/public/images/how-to-guide/vote-on-proposals/click-on-an-open-proposal.png b/public/images/how-to-guide/vote-on-proposals/click-on-an-open-proposal.png
new file mode 100644
index 0000000..de809cc
Binary files /dev/null and b/public/images/how-to-guide/vote-on-proposals/click-on-an-open-proposal.png differ
diff --git a/public/images/how-to-guide/vote-on-proposals/click-on-vote-power-settings.png b/public/images/how-to-guide/vote-on-proposals/click-on-vote-power-settings.png
new file mode 100644
index 0000000..63d5146
Binary files /dev/null and b/public/images/how-to-guide/vote-on-proposals/click-on-vote-power-settings.png differ
diff --git a/src/content/docs/development/network/global-parameters.mdx b/src/content/docs/development/network/global-parameters.mdx
index 64a08af..03da304 100644
--- a/src/content/docs/development/network/global-parameters.mdx
+++ b/src/content/docs/development/network/global-parameters.mdx
@@ -11,25 +11,23 @@ Global Parameter changes require a proposal to pass through the [DAO governance
### Network & Registration Parameters
-- **`max_allowed_agents`**: The maximum number of agents allowed in the network (default: 10.000). Sets an upper limit on the total number of agents that can be registered.
-
- **`max_registrations_per_block`**: The maximum number of registrations allowed per block (default: 10). Controls how many new registrations can be processed in a single block.
- **`target_registrations_interval`**: The number of blocks that defines the registration interval (default: 142). Defines the target interval for registration calculations.
- **`target_registrations_per_interval`**: The desired number of registrations per interval (default: 3). Sets the target number of registrations within each interval.
-- **`max_registrations_per_interval`**: The maximum registrations allowed per interval (default: 32). Upper limit on registrations processed per interval.
+- **`max_registrations_per_interval`**: The maximum registrations allowed per interval (default: 16). Upper limit on registrations processed per interval.
### Token Emission Parameters
-- **`block_emission`**: The emission per block (~5.93 TORUS). It specifies the amount of new tokens emitted in each block.
+- **`block_emission`**: The emission per block (5925.93 TORUS). It specifies the amount of new tokens emitted in each block.
- **`halving_interval`**: Token supply at halving events (default: 144,000,000 TORUS). Defines when emission halving occurs.
- **`max_supply`**: Maximum total token supply (default: 144,000,000 TORUS). Hard cap on total tokens that can exist.
-- **`emission_reciclying_percentage`**: Percentage of emission recycled (default: 100%). Controls how much emission is recycled back into the system.
+- **`emission_recycling_percentage`**: Percentage of emission recycled (default: 81%). Controls how much emission is recycled back into the system.
- **`incentives_ratio`**: Ratio for incentives distribution (default: 50%). Determines allocation between different incentive mechanisms.
@@ -37,15 +35,15 @@ Global Parameter changes require a proposal to pass through the [DAO governance
- **`max_name_length`**: The maximum length allowed for an agent name (default: 32 characters). Sets upper limit on agent name length.
-- **`min_name_length`**: The minimum length allowed for an agent name (defaul: 2 characters). Sets lower limit on agent name length.
+- **`min_name_length`**: The minimum length allowed for an agent name (default: 2 characters). Sets lower limit on agent name length.
- **`max_agent_url_length`**: The maximum URL length for agents (default: 64 characters). Controls agent URL field length.
### Burn & Stake Parameters
-- **`min_burn`**: The minimum burn required for registration (default: 10 TORUS). Sets minimum amount of tokens to burn for registration.
+- **`min_burn`**: The minimum burn required for registration (default: 15 TORUS). Sets minimum amount of tokens to burn for registration.
-- **`max_burn`**: The maximum burn allowed for registration (default: 150 TORUS). Sets upper limit on registration burn amount.
+- **`max_burn`**: The maximum burn allowed for registration (default: 1,000 TORUS). Sets upper limit on registration burn amount.
- **`min_allowed_stake`**: The minimum stake allowed (default: 0.5 TORUS). Specifies minimum amount that can be staked on an agent.
@@ -55,7 +53,7 @@ Global Parameter changes require a proposal to pass through the [DAO governance
- **`min_weight_control_fee`**: The minimum weight control fee (default: 4%). Sets minimum fee for weight control operations.
-- **`treasure_emission_fee`**: Treasury fee on emissions (default: 20%). Percentage of emissions allocated to the treasury.
+- **`treasure_emission_fee`**: Treasury fee on emissions (default: 5%). Percentage of emissions allocated to the treasury.
### Weight & Reward Parameters
@@ -80,10 +78,16 @@ Global Parameter changes require a proposal to pass through the [DAO governance
- **`agent_application_expiration`**: Agent application expiration (default: 216,000 blocks). Duration before agent applications expire.
-## Listing parameters through CLI
+## Querying Parameters
+
+### Using CLI
You can query all of these global parameters using CLI:
```bash
torus network params
-```
\ No newline at end of file
+```
+
+### Using Polkadot.js Apps
+
+You can also query current parameter values directly using [Polkadot.js Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fapi.torus.network#/chainstate). Simply select the correct pallet (e.g., `emission0`, `torus0`, `governance`) from the dropdown and choose the parameter you want to query to see the current live values.
\ No newline at end of file
diff --git a/src/content/docs/explanations/builders/agent-editing.mdx b/src/content/docs/explanations/builders/agent-editing.mdx
deleted file mode 100644
index a719934..0000000
--- a/src/content/docs/explanations/builders/agent-editing.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Agent Editing
-description: Understanding agent lifecycle, ownership, and the mechanics of agent updates in Torus.
----
-
-import {
- Aside,
- Card,
- CardGrid,
- Code,
- Tabs,
- TabItem,
-} from "@astrojs/starlight/components";
-
-
-Agent editing in Torus allows agents to update their metadata, endpoints, and social connections after initial registration.
-Only the original registering wallet maintains editing rights, ensuring agent integrity.
-
-Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links.
-Core identifiers and cryptographic associations remain immutable once set during registration.
-
-### Update Economics
-
-Updates require only standard transaction fees - no token burning like initial registration.
-This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
-
-Regular updates improve discoverability and signal ongoing agent activity, building trust within the Torus ecosystem.
-
-### Storage Architecture
-
-Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS.
-This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
-
-### Related Concepts
-
-- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
-- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
-- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Special considerations for DAO-approved agents
-
-
- Follow our [step-by-step guide to edit your agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/) for practical instructions.
-
diff --git a/src/content/docs/explanations/builders/agent-managing.mdx b/src/content/docs/explanations/builders/agent-managing.mdx
new file mode 100644
index 0000000..0abfb7e
--- /dev/null
+++ b/src/content/docs/explanations/builders/agent-managing.mdx
@@ -0,0 +1,72 @@
+---
+title: Agent Managing
+description: Understanding agent lifecycle, ownership, and the mechanics of agent updates in Torus.
+---
+
+import {
+ Aside,
+ Card,
+ CardGrid,
+ Code,
+ Tabs,
+ TabItem,
+} from "@astrojs/starlight/components";
+
+
+Agent managing in Torus allows agents to update their metadata, endpoints, and social connections after initial registration.
+Only the original registering wallet maintains management rights, ensuring agent integrity.
+
+Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links.
+Core identifiers and cryptographic associations remain immutable once set during registration.
+
+## Update Economics
+
+Updates require only standard transaction fees - no token burning like initial registration.
+This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
+
+Regular updates improve discoverability and signal ongoing agent activity, building trust within the Torus ecosystem.
+
+## Storage Architecture
+
+Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS.
+This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
+
+## Agent De-registration
+
+Agent de-registration is a permanent, irreversible action that completely removes an agent from the Torus.
+
+**Prerequisites for De-registration**
+
+Before de-registering an agent, you must:
+
+- **Revoke all delegated namespace permissions**: You cannot de-register if you have any active namespace permissions being delegated to other agents
+- **Clear all capability paths**: All registered namespaces and capability paths will be permanently deleted
+- **Backup important data**: Any configurations or data associated with the agent should be backed up as they cannot be recovered
+
+
+**Permanent Loss Warning**
+
+De-registration results in permanent loss of:
+- **All registered namespaces** — all capability paths will be deleted
+- **Ability to create new delegations** — namespace and emission delegation capabilities are revoked
+- **Delegated permissions** — all permissions granted to/from your agent will be revoked
+- **Agent identity** — the agent is completely removed from the network
+
+**However:** You can reuse the agent name if you re-register later, but it will be treated as a completely new agent with no connection to the previous one.
+
+
+**Emission Continuity**
+
+You will continue receiving emissions from existing delegations until the delegator manually revokes those permissions.
+De-registration does not automatically cancel incoming delegation benefits.
+
+
+## Related Concepts
+
+- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
+- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Special considerations for DAO-approved agents
+
+
+ Follow our [step-by-step guide to manage your agent](https://docs.torus.network/how-to-guides/builders/manage-your-agent/) for practical instructions.
+
diff --git a/src/content/docs/explanations/builders/agent-registration.mdx b/src/content/docs/explanations/builders/agent-registration.mdx
index fd60bd4..4025be1 100644
--- a/src/content/docs/explanations/builders/agent-registration.mdx
+++ b/src/content/docs/explanations/builders/agent-registration.mdx
@@ -45,8 +45,8 @@ Agent metadata is stored off-chain via IPFS but referenced on-chain through cont
### Related Concepts
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents that receive emissions directly
-- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - How agents interact and delegate authority
-- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding DAO decision-making processes
+- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - How agents interact and delegate authority
+- **[Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Understanding DAO decision-making processes
Follow our [step-by-step registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to register your agent.
diff --git a/src/content/docs/explanations/v06/capability-permissions.mdx b/src/content/docs/explanations/builders/capability-permissions.mdx
similarity index 98%
rename from src/content/docs/explanations/v06/capability-permissions.mdx
rename to src/content/docs/explanations/builders/capability-permissions.mdx
index 926c5b0..542b263 100644
--- a/src/content/docs/explanations/v06/capability-permissions.mdx
+++ b/src/content/docs/explanations/builders/capability-permissions.mdx
@@ -3,6 +3,10 @@ title: Capability Permissions
description: Understanding the capability permission system for agent endpoints
---
+
+This version is based on the Torus v0.6 and is expected to change with the Torus v1.
+
+
import {
CardGrid,
LinkCard,
diff --git a/src/content/docs/explanations/v06/control-space.mdx b/src/content/docs/explanations/builders/control-space.mdx
similarity index 96%
rename from src/content/docs/explanations/v06/control-space.mdx
rename to src/content/docs/explanations/builders/control-space.mdx
index d19f4f4..54bee99 100644
--- a/src/content/docs/explanations/v06/control-space.mdx
+++ b/src/content/docs/explanations/builders/control-space.mdx
@@ -3,6 +3,10 @@ title: Control Space
description: Understand the Torus Control Space and how namespaces enable the integration of offchain capabilities and resources with Torus onchain permission system.
---
+
+This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+
+
import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
### Control Space
diff --git a/src/content/docs/explanations/goal-leaders/dao-treasury.mdx b/src/content/docs/explanations/goal-leaders/dao-treasury.mdx
new file mode 100644
index 0000000..b204e97
--- /dev/null
+++ b/src/content/docs/explanations/goal-leaders/dao-treasury.mdx
@@ -0,0 +1,63 @@
+---
+title: DAO Treasury
+description: Understanding the DAO Treasury system, funding mechanisms, and proposal processes in Torus governance.
+---
+
+import {
+ Aside,
+ Card,
+ CardGrid,
+ Code,
+ Tabs,
+ TabItem,
+} from "@astrojs/starlight/components";
+
+The DAO Treasury serves as a community-controlled funding mechanism that enables decentralized allocation of TORUS to support ecosystem development
+and community initiatives.
+
+Proposals undergo review and voting by the community (all token holders), if approved, Torus Treasury funds are allocated to the destined wallet chosen by the proposer.
+
+### Proposal Submission Costs
+
+**Proposal Cost**: Each treasury transfer request requires a 10,000 TORUS deposit from the proposer's wallet.
+- **Approved proposals**: The 10,000 TORUS is refunded to the proposer
+- **Rejected proposals**: The 10,000 TORUS is transferred to the Treasury, increasing available funds
+
+
+
+## Use Cases and Eligibility
+
+**Development Projects**
+- Infrastructure improvements and tooling
+- Developer SDKs and libraries
+- Integration with external services
+- Protocol upgrades and enhancements
+
+**Community Building**
+- Educational content and documentation
+- Community events and hackathons
+- Marketing and outreach initiatives
+- Ecosystem partnerships
+
+**Research and Innovation**
+- Proof-of-concept implementations
+- Security audits and reviews
+- Economic research and modeling
+- Technical feasibility studies
+
+### Accountability Mechanisms
+
+Successful Proposals Recipient's are expected to:
+- Deliver on proposed milestones and timelines
+- Provide regular progress updates to the community
+- Maintain transparency about fund utilization
+
+## Related Concepts
+
+- **[Governance DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Overall DAO structure and decision-making processes
+- **[Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/)** - Alternative funding mechanisms through delegation rewards
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - DAO-approved agents with special privileges
+
+
+ Follow our [step-by-step guide to request DAO Treasury transfers](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/) for practical instructions.
+
\ No newline at end of file
diff --git a/src/content/docs/explanations/v06/emission-permissions.mdx b/src/content/docs/explanations/goal-leaders/emission-permissions.mdx
similarity index 97%
rename from src/content/docs/explanations/v06/emission-permissions.mdx
rename to src/content/docs/explanations/goal-leaders/emission-permissions.mdx
index 621de0f..169bc8c 100644
--- a/src/content/docs/explanations/v06/emission-permissions.mdx
+++ b/src/content/docs/explanations/goal-leaders/emission-permissions.mdx
@@ -3,6 +3,10 @@ title: Emission Permissions
description: Complete guide to emission permissions, stream delegation, and economic coordination mechanisms in Torus.
---
+
+This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+
+
import { CardGrid, LinkCard, Aside, Tabs, TabItem } from "@astrojs/starlight/components";
Emission permissions are the core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of their incoming emission streams (token flows) to other agents with flexible control. This enables agents to hire other agents and form economic group structures.
diff --git a/src/content/docs/explanations/goal-leaders/emission-proposals.mdx b/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
index f51fffa..a8a0a2a 100644
--- a/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
+++ b/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
@@ -49,9 +49,9 @@ For a proposal to pass, it must meet two requirements:
## Related Concepts
-- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding the broader DAO framework
+- **[Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Understanding the broader DAO framework
- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - How TORUS token economics work
-- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - How governance permissions enable proposal creation
+- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - How governance permissions enable proposal creation
Follow our [emission proposal guide](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/) to learn the step-by-step process.
diff --git a/src/content/docs/explanations/goal-leaders/governance-dao.mdx b/src/content/docs/explanations/goal-leaders/governance-dao.mdx
new file mode 100644
index 0000000..e042313
--- /dev/null
+++ b/src/content/docs/explanations/goal-leaders/governance-dao.mdx
@@ -0,0 +1,67 @@
+---
+title: Governance & DAO
+description: Learn about the governance and operation of the Torus DAO.
+---
+
+import { Tabs, TabItem, Aside, LinkCard } from "@astrojs/starlight/components";
+
+
+This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+
+
+The Torus DAO operates fully on-chain and is TORUS stake-based, managing the protocol through proposals.
+The DAO can change network parameters, propose custom changes and decide the emission rate and allocation
+between network and treasury dynamically to align with TORUS interests.
+
+## Governance Participation
+
+Governance participation enables TORUS holders to shape the network's evolution through democratic decision-making processes. Every token holder has voting rights proportional to their holdings, creating a decentralized governance system where community consensus drives protocol changes.
+
+Voting power directly correlates to TORUS token holdings:
+- **1 TORUS = 1 vote**
+
+## Proposals
+
+Proposals are the primary mechanism for implementing changes to the Torus protocol.
+Any holder with sufficient stake in the network can submit a proposal.
+Different types of Proposals address specific aspects of governance, each with its own parameters.
+
+**DAO Treasury Transfer:**
+- Community requests for funding from the DAO Treasury
+- Support ecosystem development, research, or community initiatives
+- Requires detailed project proposals and justification
+
+**Emission Proposals:**
+- Recycling percentage (portion of fees burned through recycling)
+- Treasury percentage (portion allocated to network treasury)
+- Incentives ratio (portion for incentive programs and rewards)
+
+**Global Params Proposals:**
+- Change agent name length requirements (minimum/maximum)
+- Modify maximum number of agents allowed
+- Adjust maximum weights permitted
+
+**Global Custom:**
+- Implement changes not covered by other proposal types
+- Technical modifications requiring custom code execution
+
+## Approval Criteria
+
+**Standard Requirements:**
+- **Support Threshold**: At least 50% of votes must be favorable
+- **Participation Threshold**: More than 10% of total token supply must participate
+- **Time Limit**: Voting closes after 7 days regardless of participation
+
+**Outcome Scenarios:**
+- **Approved**: 50%+ support + 10%+ participation → Automatic execution
+- **Rejected**: Less than 50% support + 10%+ participation → Proposal fails
+- **Insufficient Participation**: Less than 10% participation → Proposal expires
+
+## Vote Flexibility
+
+Votes can be changed anytime during the voting period, allowing voters to adjust their position as discussions evolve and new information emerges.
+
+## Proposal Costs
+
+- **Submission Fee**: 10,000 TORUS required to submit proposals
+- **Cost Recovery**: Fee refunded if proposal passes, retained by Treasury if rejected
\ No newline at end of file
diff --git a/src/content/docs/explanations/v06/permissions.mdx b/src/content/docs/explanations/goal-leaders/permissions.mdx
similarity index 95%
rename from src/content/docs/explanations/v06/permissions.mdx
rename to src/content/docs/explanations/goal-leaders/permissions.mdx
index 83dd147..246ade0 100644
--- a/src/content/docs/explanations/v06/permissions.mdx
+++ b/src/content/docs/explanations/goal-leaders/permissions.mdx
@@ -5,6 +5,10 @@ description: Comprehensive guide to Torus's recursive delegation system, emissio
import { CardGrid, LinkCard, Aside, Tabs, TabItem } from "@astrojs/starlight/components";
+
+This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+
+
The Torus v0.5 implements a flexible **recursive delegation system** called Permission0 that enables fine-grained control over emission distribution, agent capability access, and governance functions.
## Permission Architecture Overview
diff --git a/src/content/docs/explanations/v06/recursive-delegation.mdx b/src/content/docs/explanations/goal-leaders/recursive-delegation.mdx
similarity index 85%
rename from src/content/docs/explanations/v06/recursive-delegation.mdx
rename to src/content/docs/explanations/goal-leaders/recursive-delegation.mdx
index 1ed9f8e..48759f6 100644
--- a/src/content/docs/explanations/v06/recursive-delegation.mdx
+++ b/src/content/docs/explanations/goal-leaders/recursive-delegation.mdx
@@ -9,6 +9,10 @@ import {
CardGrid,
} from "@astrojs/starlight/components";
+
+This version is based on the Torus v0.6 and is expected to change with the Torus v1.
+
+
Recursive delegation means a delegation's output can be used as another delegation's input. This enables agents to both re-delegate permissions indefinitely and optionally sub-scope them at each delegation step.
This creates a fluid open-ended process for discovering the best-suited agent to hold a given permission at any moment and enables the partitioning of the scope of a permission granularly into a tree of agents, finding the best agent for each part.
@@ -43,11 +47,11 @@ The root owner of a capability path can delegate any amount of permission instan
### Related Concepts
-- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - Core permission mechanics and delegation basics
-- **[Recursive Delegation](https://docs.torus.network/explanations/v06/recursive-delegation/)** - Permission type for offchain agent capabilities
+- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - Core permission mechanics and delegation basics
+- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - Permission system architecture and delegation basics
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become capable of receiving delegations
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access for delegation
-Follow our [step-by-step guide to recursive delegation](https://docs.torus.network/how-to-guides/builders/recursive-delegation/) for practical implementation instructions.
+Follow our [step-by-step guide to create capability permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/) for practical implementation instructions.
diff --git a/src/content/docs/explanations/goal-leaders/root-agents.mdx b/src/content/docs/explanations/goal-leaders/root-agents.mdx
index da5f16e..ad51493 100644
--- a/src/content/docs/explanations/goal-leaders/root-agents.mdx
+++ b/src/content/docs/explanations/goal-leaders/root-agents.mdx
@@ -31,7 +31,7 @@ Successful applicants demonstrate credible execution, active community participa
### Related Concepts
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Technical details of agent registration
-- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding DAO decision-making processes
+- **[Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Understanding DAO decision-making processes
- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - How Root Agents access and use network emissions
diff --git a/src/content/docs/explanations/holders/governance-participation.mdx b/src/content/docs/explanations/holders/governance-participation.mdx
new file mode 100644
index 0000000..5371cbb
--- /dev/null
+++ b/src/content/docs/explanations/holders/governance-participation.mdx
@@ -0,0 +1,121 @@
+---
+title: Governance Participation
+description: Understanding voting rights, power delegation, and governance mechanisms for TORUS token holders.
+---
+
+import {
+ Aside,
+ Card,
+ CardGrid,
+ Code,
+ Tabs,
+ TabItem,
+} from "@astrojs/starlight/components";
+
+Governance participation enables TORUS holders to shape the network's evolution through democratic decision-making processes.
+Every token holder has voting rights proportional to their holdings,
+creating a decentralized governance system where community consensus drives protocol changes.
+
+Voting power directly correlates to TORUS token holdings:
+- **1 TORUS = 1 vote**
+
+Right now,
+
+### Treasury Transfer Proposals:
+Community requests for funding from the DAO Treasury to support ecosystem development, research, or community initiatives.
+
+**Voting Considerations:**
+- Project viability and team credibility
+- Benefit to the Torus ecosystem
+- Budget reasonableness and timeline
+- Alignment with network priorities
+
+### Emission Proposals:
+Changes to network economics, including token emission rates, burn mechanisms, and reward distribution parameters.
+
+**Voting Considerations:**
+- Long-term economic sustainability
+- Impact on token value and inflation
+- Effects on network incentives
+- Technical feasibility of implementation
+
+### Governance Parameter Changes:
+Modifications to voting thresholds, proposal costs, voting periods, and other governance mechanics.
+
+**Voting Considerations:**
+- Democratic accessibility vs governance security
+- Participation requirements and barriers
+- Protection against governance attacks
+- Community representation balance
+
+## Voting Mechanics
+
+### Proposal Lifecycle
+1. **Submission**: Proposals submitted with required deposit (typically 10,000 TORUS)
+2. **Review Period**: Community discussion and feedback (informal)
+3. **Voting Period**: 7-day voting window for all token holders
+4. **Execution/Rejection**: Automatic execution based on voting results
+
+### Approval Criteria
+**Standard Requirements:**
+- **Support Threshold**: At least 50% of votes must be favorable
+- **Participation Threshold**: More than 10% of total token supply must participate
+- **Time Limit**: Voting closes after 7 days regardless of participation
+
+**Outcome Scenarios:**
+- **Approved**: 50%+ support + 10%+ participation → Automatic execution
+- **Rejected**: Less than 50% support + 10%+ participation → Proposal fails
+- **Insufficient Participation**: Less than 10% participation → Proposal expires
+
+### Vote Finality
+Once cast, votes cannot be changed during the voting period. This ensures predictability and prevents last-minute manipulation, but requires careful consideration before voting.
+
+## Economic Incentives and Costs
+
+### Proposal Costs
+- **Submission Fee**: 10,000 TORUS required to submit proposals
+- **Cost Recovery**: Fee refunded if proposal passes, retained by Treasury if rejected
+- **Spam Prevention**: Economic barrier prevents frivolous proposals
+
+### Voting Costs
+- **Transaction Fees**: Standard network fees apply for voting transactions
+- **Power User Setup**: One-time transaction to enable direct voting control
+- **Switching Modes**: Small transaction cost to change between delegated and power user modes
+
+## Strategic Voting Considerations
+
+### Information Gathering
+- **Proposal Details**: Thoroughly review all proposal documentation
+- **Community Discussion**: Engage in Discord, Telegram, and forum discussions
+- **Technical Analysis**: Understand implementation details and potential impacts
+- **Precedent Setting**: Consider how current votes affect future proposals
+
+### Long-term Impact
+- **Network Health**: Vote for proposals that strengthen the ecosystem
+- **Economic Sustainability**: Support proposals that enhance long-term value
+- **Community Growth**: Favor initiatives that expand and engage the user base
+- **Innovation**: Encourage proposals that advance technical capabilities
+
+## Governance Security
+
+### Attack Prevention
+- **Proposal Costs**: Economic barriers prevent spam and low-quality submissions
+- **Time Delays**: Voting periods allow community review and response
+- **Participation Thresholds**: Ensure broad community involvement in decisions
+- **Transparent Process**: All votes and outcomes are publicly recorded
+
+### Best Practices
+- **Diversified Holdings**: Avoid concentration of voting power in few hands
+- **Active Participation**: Regular voting prevents governance capture
+- **Community Engagement**: Discuss proposals before voting
+- **Long-term Thinking**: Consider ecosystem health over short-term gains
+
+## Related Concepts
+
+- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - Understanding TORUS token economics and distribution
+- **[Staking](https://docs.torus.network/explanations/holders/staking/)** - How staking affects voting power and governance participation
+- **[Governance DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Overall DAO structure and decision-making processes
+
+
+ Follow our [step-by-step guide to vote on proposals](https://docs.torus.network/how-to-guides/holders/vote-on-proposals/) for practical instructions.
+
\ 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 7452c56..fd622bd 100644
--- a/src/content/docs/explanations/table-of-contents.mdx
+++ b/src/content/docs/explanations/table-of-contents.mdx
@@ -17,17 +17,6 @@ If you need to accomplish a specific task, check out our [How-to Guides](https:/
These explanations provide deep understanding of how Torus works, the concepts, mechanisms of Torus.
-## v0.6 Related Topics
-
-Understanding the technical implementation and design of Torus v0.6:
-
-- [Control Space](https://docs.torus.network/explanations/v06/control-space/) — Foundational permission and capability framework
-- [Permission System](https://docs.torus.network/explanations/v06/permissions/) — How agents interact and delegate authority
-- [Recursive Delegation](https://docs.torus.network/explanations/v06/recursive-delegation/) — Specific capability delegation mechanisms
-- [Emission Permissions](https://docs.torus.network/explanations/v06/emission-permissions/) — How emissions are allocated and controlled
-- [Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/) — Decision-making processes and community coordination
-
----
## For Holders
@@ -45,10 +34,12 @@ Learn about TORUS economics and understand how you can participate:
Understanding how agent systems work within Torus:
- [Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/) — Registration economics, burn mechanisms, and discovery
-- [Agent Editing](https://docs.torus.network/explanations/builders/agent-editing/) — Update mechanics and storage architecture
+- [Agent Managing](https://docs.torus.network/explanations/builders/agent-managing/) — Update mechanics and storage architecture
- [Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/) — Capability coordination and economic incentives
- [Agent Server](https://docs.torus.network/explanations/builders/agent-server/) — API architecture, authentication, and capability sharing
- [Agent Client](https://docs.torus.network/explanations/builders/agent-client/) — Communication patterns and authentication flow
+- [Control Space](https://docs.torus.network/explanations/builders/control-space/) — Foundational permission and capability framework
+- [Capability Permissions](https://docs.torus.network/explanations/builders/capability-permissions/) — Fine-grained access control for agent endpoints
---
@@ -57,7 +48,12 @@ Understanding how agent systems work within Torus:
Understanding governance and leadership systems:
- [Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/) — DAO approval process and direct emission access
+- [DAO Treasury](https://docs.torus.network/explanations/goal-leaders/dao-treasury/) — Community funding mechanisms and proposal processes
- [Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/) — How to adjust network economics through governance
+- [Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/) — How agents interact and delegate authority
+- [Recursive Delegation](https://docs.torus.network/explanations/goal-leaders/recursive-delegation/) — Specific capability delegation mechanisms
+- [Emission Permissions](https://docs.torus.network/explanations/goal-leaders/emission-permissions/) — How emissions are allocated and controlled
+- [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) — Decision-making processes and community coordination
---
diff --git a/src/content/docs/explanations/v06/governance-dao.mdx b/src/content/docs/explanations/v06/governance-dao.mdx
deleted file mode 100644
index fd323b3..0000000
--- a/src/content/docs/explanations/v06/governance-dao.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Governance & DAO
-description: Learn about the governance and operation of the Torus DAO.
----
-
-import { Tabs, TabItem, Aside, LinkCard } from "@astrojs/starlight/components";
-
-The Torus DAO operates fully on-chain and is TORUS stake-based, managing the protocol through proposals.
-
-The DAO can change network parameters, propose custom changes and decide the emission rate and allocation between network and treasury dynamically to align with TORUS interests.
-
-## Proposals
-
-Proposals are the primary mechanism for implementing changes to the Torus protocol. Any agent with sufficient stake in the network can submit a proposal. Different types of Proposals address specific aspects of governance, each with its own parameters.
-
-### Proposal types
-
-
-
- ##### Change Protocol and network parameters:
-
-
- Change agent name length
- Change minimum agent name length
- Change maximum number of agents
- Change maximum weights
- Change weight control fee
- Change staking fee
- Change dividends participation weight
-
-
-
- If you want to propose a change to the network parameters, you can use the following CLI command:
-
- ```bash
- $ torus network propose-globally
- --max-name-length INTEGER [default: None]
- --min-name-length INTEGER [default: None]
- --max-allowed-agents INTEGER [default: None]
- --max-allowed-weights INTEGER [default: None]
- --min-weight-stake INTEGER [default: None]
- --min-weight-control-fee INTEGER [default: None]
- --min-staking-fee INTEGER [default: None]
- --dividends-participation-weight INTEGER [default: None]
- ```
-
-
-
-
-
- ##### Propose the Transfer of Treasury Funds.
-
- You can use the following CLI command to submit a treasury transfer proposal:
-
- ```bash
- $ torus proposal propose-dao-transfer
- ```
-
-
-
- ##### Propose Custom Change to the Protocol:
-
-
- For changes not covered by other proposal types, you can use the following CLI command:
-
- ```bash
- $ torus proposal propose-custom
- ```
-
-
-
-
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/create-permission.mdx b/src/content/docs/how-to-guides/builders/create-permission.mdx
index d04253d..f88da35 100644
--- a/src/content/docs/how-to-guides/builders/create-permission.mdx
+++ b/src/content/docs/how-to-guides/builders/create-permission.mdx
@@ -264,16 +264,16 @@ For help with permission management:
- [Torus Community Discord](https://discord.gg/torus)
-See the [Permission System Documentation](https://docs.torus.network/explanations/v06/permissions/) for technical details.
+See the [Permission System Documentation](https://docs.torus.network/explanations/goal-leaders/permissions/) for technical details.
#### Related Topics
- Deep dive into architecture
+ Deep dive into architecture
- Economic coordination mechanisms
+ Economic coordination mechanisms
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/edit-your-agent.mdx b/src/content/docs/how-to-guides/builders/edit-your-agent.mdx
deleted file mode 100644
index ec7fe6c..0000000
--- a/src/content/docs/how-to-guides/builders/edit-your-agent.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Edit your Agent information
-description: Update your agent's details, social links, and technical information.
----
-
-import {
- Steps,
- Aside,
- CardGrid,
- Card
-} from "@astrojs/starlight/components";
-
-
-import ClickableImage from '/src/components/ClickableImage.astro';
-import RedText from '/src/components/RedText.astro';
-import registeredAgents from '/public/images/how-to-guide/register-an-agent/registered-agent-on-allocator-page.png';
-import editAgent from '/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png';
-import toastExample from '/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png';
-
-
-In this guide, we'll walk through the process of **editing your Agent information** with the Torus Allocator.
-Both the **Registered Agent** and **Root Agent** can edit their information. Just make sure to use the proper filter on the Allocator tab .
-In this guide we will be editing the information of a **Registered Agent**.
-
-#### Why edit your agent?
-
-Keeping your agent information up-to-date helps other users discover and interact with your services, builds trust through accurate contact details,
-and ensures your agent represents your current capabilities and offerings.
-
-#### What we will accomplish
-
-- Edit your Agent's description and technical details
-- Update your Agent's social links and contact information
-- Modify your Agent's website URL, API endpoint, and icon
-
-
-⏱️ **Estimated time to complete this guide: 5 minutes**
-
-
-## Prerequisites
-
-
-
- Make sure you have a Torus wallet set up and ready to use.
- You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
-
-
- Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough **Free Balance** to cover the registration fees.
- You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
-
-
- You must have a Registered or Root Agent to edit your information.
-
-
-
-
- ## Edit your Agent Information
-
-
-1. **Find your Agent in the [Allocator Tab](https://portal.torus.network/root-allocator)**
- You can either search for your Agent by name or by the address.
-
-
-
-2. **Click on the card of your Agent**
- The edit is in the **Detailed View** of the Agent.
-
-
-3. **Edit the information and Submit**
- You can edit the following information:
- ```md
- # Short Description
- # Description
- # Technical Information
- - Website URL
- - API Endpoint URL
- - Agent Icon
- # Social Links
- - Discord
- - Twitter
- - GitHub
- - Telegram
- ```
-4. **Sign the Transaction in the SubWallet and Wait for the Confirmation**
- You will be prompted by SubWallet to sign the on-chain transaction .
- Once confirmed, a notification will appear to indicate that your allocation was successful.
-
-
-5. **All Done**
- You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
-
-
-
-
-## What's Next?
-
-After updating your agent information:
-
-- **Monitor your presence**: Check how your agent appears on the [Allocator tab](https://portal.torus.network/root-allocator)
-- **Stay up to date**: Keep your information updated to match the latest changes
-- **Build capabilities**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide services
-
- 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
-
-
-Learn about [agent editing](https://docs.torus.network/explanations/builders/agent-editing/) update mechanics and storage architecture.
-
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
index 246e35c..c3619d0 100644
--- a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
+++ b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
@@ -161,7 +161,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
Now that you can manage capabilities, you might want to:
-- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/builders/manage-permissions/) to allow other agents to use your capabilities
+- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to allow other agents to use your capabilities
- **Build agent services**: Create an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your registered capabilities
- **Create demand signals**: Signal for [specific capabilities](https://docs.torus.network/how-to-guides/builders/create-signal/) you need from other agents
@@ -171,5 +171,5 @@ Connect with the community:
- [Twitter](https://x.com/torus_network) — Updates and ecosystem news
-Learn about [recursive delegation](https://docs.torus.network/explanations/v06/recursive-delegation/) delegation mechanisms and control space architecture.
+Learn about [recursive delegation](https://docs.torus.network/explanations/goal-leaders/recursive-delegation/) delegation mechanisms and control space architecture.
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-permissions.mdx b/src/content/docs/how-to-guides/builders/manage-permissions.mdx
deleted file mode 100644
index 8223562..0000000
--- a/src/content/docs/how-to-guides/builders/manage-permissions.mdx
+++ /dev/null
@@ -1,210 +0,0 @@
----
-title: Manage Permissions
-description: Step-by-step guide to creating and managing permissions in the Torus portal.
----
-
-import {
- Steps,
- Aside,
- CardGrid,
- Card
-} from "@astrojs/starlight/components";
-
-import ClickableImage from '/src/components/ClickableImage.astro';
-import RedText from '/src/components/RedText.astro';
-
-In this guide, we'll walk through **managing permissions** in the Torus portal.
-Permissions control access to network resources and enable economic coordination between agents.
-
-## Permission Types
-
-Torus has two distinct permission types that serve different purposes:
-
-**Capability Permissions**: Control access to specific agent endpoints and APIs
-**Emission Permissions**: Enable economic coordination by delegating token emission streams
-
-Each type has different creation workflows but can be managed through the same interface.
-
-
-#### What we will accomplish
-
-- [Create capability permissions](#create-capability-permission)
-- [Create emission permissions](#create-emission-permission)
-- [Manage existing permissions](#manage-existing-permissions)
-
-
-⏱️ **Estimated time to complete this guide: 10 minutes**
-
-
-## Prerequisites
-
-
-
- You must have a registered agent on Torus.
- Follow the [agent registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) if needed.
-
-
- Ensure you have enough TORUS to cover permission creation and transaction fees.
-
-
- For emission permissions, you must have incoming emission streams to delegate. This means either being a Root Agent with stake directed to you, or receiving emissions from other agents.
-
-
-
-## Create Capability Permission
-
-Capability permissions control access to specific agent endpoints and APIs.
-
-
-
-1. **Visit the [Create Permissions tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/capability)**
- It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
-
-2. **Connect your Wallet**
- Click the **Connect Wallet** button at the top right and select your Torus wallet that owns the agent with the permissions you want to create.
-
-3. **Fill the form**
- ```md
- # Recipient
- The agent that will receive the permission.
-
- # Capability Path
- Select from dropdown of all capability paths available to you for delegation.
-
- # Duration
- - **Indefinite**: Permission remains valid indefinitely
- - **Until Block**: Permission expires at a specific block
-
- # Block Number
- Specific block number when permission expires
- (only shown for Until Block duration)
-
- # Maximum Instances
- The maximum number of instances that can be created under this permission.
-
- # Revocation Terms
- - **Irrevocable**: Cannot be revoked
- - **Revocable by Delegator**: Only the delegator can revoke
- - **Revocable by Arbiters**: Can be revoked by arbiters after a vote threshold set by the delegator
- - **After Block**: Can only be revoked after a specific block
- ```
-
-4. **Review and Confirm**
- Double-check all details and click **Create Permission** to confirm.
- Sign the transaction in your Wallet to finish the creation.
-
-5. **All Done**
- Your capability permission is now delegated. You can check it in the [Management tab](https://portal.torus.network/permissions/edit-permission).
-
-
-
-## Create Emission Permission
-
-Emission permissions enable economic coordination by delegating portions of your token emission streams.
-
-
-
-1. **Visit the [Create Permissions tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/emission)**
- It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
-
-2. **Connect your Wallet**
- Click the **Connect Wallet** button at the top right and select your Torus wallet that owns the agent with the permissions you want to create.
-
-3. **Click on the Emission tab**
- Select the **Emission** tab instead of the **Capability** tab to create emission permissions.
-
-4. **Fill the form**
- ```md
- # Distribution Type
- - **Manual**: Recipient triggers distribution when needed
- - **Automatic**: Auto-distribute when threshold is reached
- - **At Block**: Execute once at specific block height
- - **Interval**: Execute periodically at fixed intervals
-
- # Threshold Amount
- Token amount threshold for automatic distribution
- (only shown for Automatic distribution type)
-
- # Block Number
- Specific block number for one-time execution
- (only shown for At Block distribution type)
-
- # Block Interval
- Number of blocks between periodic distributions
- (only shown for Interval distribution type)
-
- # Duration Type
- - **Indefinite**: Permission remains valid indefinitely
- - **Until Block**: Permission expires at a specific block
-
- # Revocation Type
- - **Irrevocable**: Cannot be revoked
- - **Revocable by Delegator**: Only the delegator can revoke
- - **Revocable by Arbiters**: Can be revoked by arbiters after
- a vote threshold set by the delegator
- - **After Block**: Can only be revoked after a specific block
-
- # Streams
- Click **Add Stream** to add multiple emission streams:
- - **Stream ID**: Identifier of the emission stream to delegate
- - **Percentage**: Percentage of that stream to delegate (0-100%)
-
- # Target Accounts
- Click **Add Target** to add multiple recipients:
- - **Account**: Wallet address of the recipient agent
- - **Weight**: Percentage weight for this recipient
- (distribution among multiple targets)
- ```
-
-5. **Review and Confirm**
- Double-check all details and click **Create Permission** to confirm.
- Sign the transaction in your Wallet to finish the creation.
-
-6. **All Done**
- Your Emission Permission is now delegated. You can check it in the [Management tab](https://portal.torus.network/permissions/edit-permission).
-
-
-
-## Manage Existing Permissions
-
-Both capability and emission permissions can be managed through the same interface with type-specific options.
-
-
-
-1. **Visit the [Manage Permissions](https://portal.torus.network/permissions/edit-permission) Tab in the Torus Portal**
- It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
-
-2. **View Your Permissions**
- Browse your permissions organized by role:
- - **As Delegator**: Permissions you've granted to other agents
- - **As Recipient**: Permissions other agents have granted to you
-
-3. **Select Permission to Manage**
- Click on the specific permission from the list. This will open a modal showing all the permission details.
-
-4. **Revoke Permission**
- In this step you can only revoke active permissions. Click the **Revoke** button to remove the permission.
-
-5. **Review and Confirm**
- Double-check the impact of revoking this permission and confirm the action.
- Sign the transaction in your Wallet to complete the revocation.
-
-6. **All Done**
- Your permission has been revoked. The changes will be reflected immediately in the permissions list.
-
-
-
-
-
-## What's Next?
-
-After successfully managing your permissions, you can:
-
-- **Explore capability management**: Learn about [managing capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
-- **Set up agent services**: Use your permissions in an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
-- **Connect with other agents**: Learn about [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) integration
-- **Create demand signals**: Signal demand for specific capabilities with [create a signal](https://docs.torus.network/how-to-guides/builders/create-signal/)
-
-
-For more technical details about how permissions work, see the [permission system explanation](https://docs.torus.network/explanations/v06/permissions/).
-
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-your-agent.mdx b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
new file mode 100644
index 0000000..dca2ee8
--- /dev/null
+++ b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
@@ -0,0 +1,155 @@
+---
+title: Manage your Agent
+description: Update your agent's details, social links, and technical information.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+import manageAgentTab from '/public/images/how-to-guide/agent-management/click-on-manage-agent-tab.png';
+import clickDeregisterTab from '/public/images/how-to-guide/agent-management/click-on-deregister-agent.png';
+
+
+In this guide, we'll walk through the process of **managing your Agent information** with the Torus Allocator.
+Both the **Registered Agent** and **Root Agent** can manage their information.
+Just make sure to use the proper filter on the Allocator tab .
+In this guide we will be managing the information of a **Registered Agent**.
+
+#### Why manage your agent?
+
+Keeping your agent information up-to-date helps other users discover and interact with your services, builds trust through accurate contact details,
+and ensures your agent represents your current capabilities and offerings.
+
+#### What we will accomplish
+
+- [Edit your agent information](#edit-your-agent-information)
+- [De-register your agent](#de-register-your-agent)
+
+
+⏱️ **Estimated time to complete this guide: 5 minutes**
+
+
+## Prerequisites
+
+
+
+ Make sure you have a Torus wallet set up and ready to use.
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
+
+
+ Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough **Free Balance** to cover the registration fees.
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
+
+
+ You must have a Registered or Root Agent to manage your information.
+
+
+
+
+## Edit your Agent Information
+
+
+1. **Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
+ Ensure you're connected with the agent wallet that owns the agent you want to manage.
+
+
+
+2. **Edit the information and Submit**
+ You can edit the following information:
+ ```md
+ # Short Description
+ # Description
+ # Technical Information
+ - Website URL
+ - API Endpoint URL
+ - Agent Icon
+ # Social Links
+ - Discord
+ - Twitter
+ - GitHub
+ - Telegram
+ ```
+3. **Sign the Transaction in the SubWallet and Wait for the Confirmation**
+ You will be prompted by SubWallet to sign the on-chain transaction .
+ Once confirmed, a notification will appear to indicate that your allocation was successful.
+
+4. **All Done**
+ You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
+
+
+
+## De-register your Agent
+
+
+
+1. **Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
+ Ensure you're connected with the agent wallet that owns the agent you want to manage.
+
+2. **Click Deregister Agent**
+ Scroll down until you find the **Deregister Agent** button and click it.
+
+
+3. **Complete the De-registration Form**
+ The form will display a comprehensive warning about the permanent nature of this action :
+
+ - **Permissions Warning**: You can only de-register if you have NO active namespace permissions being delegated . You must manually revoke all delegated permissions first.
+
+ **You will permanently lose:**
+ - All registered namespaces — all capability paths will be deleted
+ - Ability to create new namespace or emission delegations
+ - Delegated permissions — all permissions granted to/from your agent will be revoked
+ - Agent name — you CAN reuse this name if you re-register later
+
+
+ You will continue receiving emissions from existing delegations until the delegator revokes those permissions.
+
+
+ **Required Confirmations:**
+ Before proceeding, you must confirm you understand:
+ - ✓ This action is permanent and irreversible
+ - ✓ I have manually revoked ALL delegated namespace permissions
+ - ✓ I have backed up any important data or configurations
+ - ✓ I understand I can re-register with the same name later, but it will be treated as a completely new agent
+
+ **Final Confirmation:**
+ Type your agent name exactly as it appears to confirm deletion. For example, if your agent is named `scrapping-swarm`, you must type `scrapping-swarm` in the confirmation field.
+
+
+ **This is your final warning. Once deleted, your agent cannot be restored.**
+
+
+4. **Review information, Submit and Sign the Transaction**
+ Review the agent information you're about to de-register in the preview field.
+ If you're certain you want to proceed, click **De-register Agent**.
+ Open the SubWallet extension and sign the transaction .
+
+5. **All Done**
+ You've successfully de-registered the agent from Torus.
+ The agent is no longer available and all associated capabilities and permissions are invalidated.
+
+
+
+## What's Next?
+
+Now that you can manage your agent, you might want to:
+
+- **Manage capabilities**: [Create and manage capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) to define what your agent can do
+- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to allow other agents to use your capabilities
+- **Build agent services**: Create an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your registered capabilities
+- **Create demand signals**: Signal for [specific capabilities](https://docs.torus.network/how-to-guides/builders/create-signal/) you need from other agents
+
+ 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
+
+
+Learn about [agent managing](https://docs.torus.network/explanations/builders/agent-managing/) update mechanics and storage architecture.
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/recursive-delegation.mdx b/src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx
similarity index 96%
rename from src/content/docs/how-to-guides/builders/recursive-delegation.mdx
rename to src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx
index 83b4775..8b41e23 100644
--- a/src/content/docs/how-to-guides/builders/recursive-delegation.mdx
+++ b/src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx
@@ -1,5 +1,5 @@
---
-title: Recursive Delegation
+title: Create Capability Permission
description: Step-by-step guide to creating capability permissions to delegate access to your agent's endpoints and services.
---
@@ -40,7 +40,7 @@ Capability permissions let you control who can access your services while mainta
You must have a registered agent with capabilities to delegate.
- Follow the [manage permissions guide](https://docs.torus.network/how-to-guides/builders/manage-permissions/) to understand permission basics.
+ Follow the [manage permissions guide](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to understand permission basics.
Identify the agents you want to delegate permissions to. These agents must be registered.
@@ -139,6 +139,6 @@ Connect with the community:
- [Twitter](https://x.com/torus_network) — Updates and ecosystem news
-Learn about [recursive delegation concepts](https://docs.torus.network/explanations/v06/recursive-delegation/) and the technical architecture behind permission delegation.
+Learn about [recursive delegation concepts](https://docs.torus.network/explanations/goal-leaders/recursive-delegation/) and the technical architecture behind permission delegation.
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx b/src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx
new file mode 100644
index 0000000..0e6c6cc
--- /dev/null
+++ b/src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx
@@ -0,0 +1,126 @@
+---
+title: Create Emission Permission
+description: Step-by-step guide to creating emission permissions to delegate token emission streams to other agents.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+
+In this guide, we'll walk through **creating emission permissions** in the Torus portal.
+Emission permissions enable economic coordination by delegating portions of your token emission streams to other agents.
+
+## Why Create Emission Permissions?
+
+Emission permissions allow you to:
+- **Hire agents**: Pay other agents for services using your emission streams
+- **Create incentives**: Reward agents based on performance or contributions
+- **Economic coordination**: Build complex multi-agent workflows with token flows
+
+#### What we will accomplish
+
+- [Create emission permissions](#create-emission-permission)
+
+
+⏱️ **Estimated time to complete this guide: 5 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a registered agent on Torus.
+ Follow the [agent registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) if needed.
+
+
+ Ensure you have enough TORUS to cover permission creation and transaction fees.
+
+
+ For emission permissions, you must have incoming emission streams to delegate. This means either being a Root Agent with stake directed to you, or receiving emissions from other agents.
+
+
+
+## Create Emission Permission
+
+Emission permissions enable economic coordination by delegating portions of your token emission streams.
+
+
+
+1. **Visit the [Create Permissions tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/emission)**
+ It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
+
+2. **Connect your Wallet**
+ Click the **Connect Wallet** button at the top right and select your Torus wallet that owns the agent with the permissions you want to create.
+
+3. **Click on the Emission tab**
+ Select the **Emission** tab instead of the **Capability** tab to create emission permissions.
+
+4. **Fill the form**
+ ```md
+ # Distribution Type
+ - **Manual**: Recipient triggers distribution when needed
+ - **Automatic**: Auto-distribute when threshold is reached
+ - **At Block**: Execute once at specific block height
+ - **Interval**: Execute periodically at fixed intervals
+
+ # Threshold Amount
+ Token amount threshold for automatic distribution
+ (only shown for Automatic distribution type)
+
+ # Block Number
+ Specific block number for one-time execution
+ (only shown for At Block distribution type)
+
+ # Block Interval
+ Number of blocks between periodic distributions
+ (only shown for Interval distribution type)
+
+ # Duration Type
+ - **Indefinite**: Permission remains valid indefinitely
+ - **Until Block**: Permission expires at a specific block
+
+ # Revocation Type
+ - **Irrevocable**: Cannot be revoked
+ - **Revocable by Delegator**: Only the delegator can revoke
+ - **Revocable by Arbiters**: Can be revoked by arbiters after
+ a vote threshold set by the delegator
+ - **After Block**: Can only be revoked after a specific block
+
+ # Streams
+ Click **Add Stream** to add multiple emission streams:
+ - **Stream ID**: Identifier of the emission stream to delegate
+ - **Percentage**: Percentage of that stream to delegate (0-100%)
+
+ # Target Accounts
+ Click **Add Target** to add multiple recipients:
+ - **Account**: Wallet address of the recipient agent
+ - **Weight**: Percentage weight for this recipient
+ (distribution among multiple targets)
+ ```
+
+5. **Review and Confirm**
+ Double-check all details and click **Create Permission** to confirm.
+ Sign the transaction in your Wallet to finish the creation.
+
+6. **All Done**
+ Your Emission Permission is now delegated. You can check it in the [Management tab](https://portal.torus.network/permissions/edit-permission).
+
+
+## What's Next?
+
+After creating your emission permission, you can:
+
+- **Monitor performance**: Track how recipients use delegated emissions
+- **Adjust permissions**: Modify terms based on agent performance
+- **Scale coordination**: Build complex multi-agent economic workflows
+- **Manage permissions**: View and revoke permissions through the [manage permissions guide](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/)
+
+
+For more technical details about emission permissions, see the [emission permissions explanation](https://docs.torus.network/explanations/goal-leaders/emission-permissions/).
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx b/src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx
new file mode 100644
index 0000000..5a2603c
--- /dev/null
+++ b/src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx
@@ -0,0 +1,179 @@
+---
+title: Manage Permissions
+description: Step-by-step guide to creating and managing permissions in the Torus portal.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+
+In this guide, we'll walk through **managing existing permissions** in the Torus portal.
+Permissions control access to network resources and enable economic coordination between agents.
+
+## Permission Types
+
+Torus has two distinct permission types that can be managed:
+
+**Capability Permissions**: Control access to specific agent endpoints and APIs
+**Emission Permissions**: Enable economic coordination by delegating token emission streams
+
+Both types can be viewed, monitored, and revoked through the same management interface.
+
+#### What we will accomplish
+
+- [View your permissions](#view-your-permissions)
+- [Manage existing permissions](#manage-existing-permissions)
+
+
+⏱️ **Estimated time to complete this guide: 10 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a registered agent on Torus.
+ Follow the [agent registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) if needed.
+
+
+ Ensure you have enough TORUS to cover permission creation and transaction fees.
+
+
+ You must have existing permissions (either as delegator or recipient) to manage them.
+
+
+
+## View Your Permissions
+
+Both capability and emission permissions can be viewed and monitored through the management interface.
+
+
+
+1. **Visit the [Manage Permissions](https://portal.torus.network/permissions/manage-permission) Tab in the Torus Portal**
+ It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
+
+2. **Connect your Wallet**
+ Click the **Connect Wallet** button at the top right and select your Torus wallet.
+
+3. **Browse Your Permissions**
+ Your permissions are organized by role:
+ - **As Delegator**: Permissions you've granted to other agents
+ - **As Recipient**: Permissions other agents have granted to you
+
+4. **Review Permission Details**
+ Click on any permission from the list to open a detailed modal showing:
+
+ ```md
+ # For All Permissions
+ Permission ID: Unique hash identifier
+ Delegator: Agent name and wallet address who granted the permission
+ Type: Either "Capability" or "Emission"
+ Duration: Permission lifespan ("Indefinite", "Until Block X")
+ Revocation: Terms for cancelling ("Revocable by Delegator", etc.)
+ Created At: Block number when permission was created
+
+ # Additional for Capability Permissions
+ Recipient: Agent name and wallet address receiving the permission
+ Capability Path: Specific endpoint being delegated
+
+ # Additional for Emission Permissions
+ Execution Count: Number of times the permission has been executed
+ Stream Details: Information about delegated emission streams
+ ```
+
+
+
+
+## Manage Existing Permissions
+
+Both capability and emission permissions can be managed through the same interface, but with different management options:
+
+- **Capability Permissions**: Can be edited (modify terms) and revoked
+- **Emission Permissions**: Can only be revoked (no editing available)
+
+
+
+1. **Visit the [Manage Permissions](https://portal.torus.network/permissions/edit-permission) Tab in the Torus Portal**
+ It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
+
+2. **View Your Permissions**
+ Browse your permissions organized by role:
+ - **As Delegator**: Permissions you've granted to other agents
+ - **As Recipient**: Permissions other agents have granted to you
+
+3. **Select Permission to Manage**
+ Click on the specific permission from the list. This opens a detailed modal with comprehensive information:
+
+ ```md
+ # Permission ID
+ Unique hash identifier for this permission
+
+ # Delegator
+ Agent name and wallet address who granted the permission
+
+ # Recipient
+ Agent name and wallet address receiving the permission
+ (only shown for capability permissions)
+
+ # Type
+ Either "Capability" or "Emission"
+
+ # Duration
+ Permission lifespan ("Indefinite", "Until Block X")
+
+ # Revocation
+ Terms for cancelling ("Revocable by Delegator", etc.)
+
+ # Created At
+ Block number when permission was created
+
+ # Capability Path
+ Specific endpoint being delegated
+ (only shown for capability permissions)
+
+ # Execution Count
+ Number of times the permission has been executed
+ (only shown for emission permissions)
+ ```
+
+4. **Edit or Revoke Permission**
+ Available actions depend on the permission type:
+
+ **For Capability Permissions :**
+ - **Edit** : Modify permission terms (duration, revocation conditions, etc.)
+ - **Revoke** : Permanently remove the permission
+
+ **For Emission Permissions :**
+ - **Revoke** : Permanently remove the permission (editing not available)
+
+ Click the appropriate button to proceed with your chosen action.
+
+5. **Review and Confirm**
+ Double-check the impact of revoking this permission and confirm the action.
+ Sign the transaction in your Wallet to complete the revocation.
+
+6. **All Done**
+ Your permission has been revoked. The changes will be reflected immediately in the permissions list.
+
+
+
+
+
+## What's Next?
+
+After managing your permissions, you can:
+
+- **Create new permissions**: Learn how to [create capability permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/) or [create emission permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-permission/)
+- **Explore capabilities**: Learn about [managing capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
+- **Set up agent services**: Use your permissions in an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
+- **Connect with other agents**: Learn about [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) integration
+
+
+For more technical details about how permissions work, see the [permission system explanation](https://docs.torus.network/explanations/goal-leaders/permissions/).
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/goal-leaders/request-dao-treasury-transfer.mdx b/src/content/docs/how-to-guides/goal-leaders/request-dao-treasury-transfer.mdx
new file mode 100644
index 0000000..3506e1a
--- /dev/null
+++ b/src/content/docs/how-to-guides/goal-leaders/request-dao-treasury-transfer.mdx
@@ -0,0 +1,116 @@
+---
+title: Request DAO Treasury Transfer
+description: Step-by-step guide to requesting TORUS funding from the DAO Treasury for building projects and initiatives.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+
+In this guide, we'll walk through the process of **requesting a transfer from the DAO Treasury** to fund your building projects or initiatives.
+
+The DAO Treasury is a community-controlled fund that provides financial support to builders and contributors who want to develop tools, services, or improvements for the Torus ecosystem.
+
+#### Why request DAO Treasury funding?
+
+DAO Treasury transfers provide essential funding for builders who need capital to start projects but may not have the initial resources.
+
+#### What we will accomplish
+
+- Submit a proposal to request TORUS from the DAO Treasury
+
+
+⏱️ **Estimated time to complete this guide: 30 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a Torus wallet set up with sufficient balance to cover the proposal cost.
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
+
+
+ Ensure you have at least **10,000 TORUS** in your wallet to cover the proposal cost.
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
+
+
+
+## Request DAO Treasury Transfer
+
+
+
+1. **Visit the [Proposals Tab in the DAO Governance Portal](https://dao.torus.network/proposals)**
+ Navigate to the **Shape the Network** section in the Torus DAO Portal.
+
+2. **Connect your Wallet**
+ Ensure you're connected with a wallet that has at least 10,000 TORUS for the proposal cost.
+
+3. **Click in Shape the Network**
+ It can be found in the top right corner of the page.
+
+4. **Select "Transfer DAO Treasury" Type**
+ In the modal, choose **"Transfer DAO Treasury"** from the dropdown menu of available options.
+
+5. **Complete the Transfer Request Form**
+ Fill out the required information:
+
+ ```md
+ # Destination
+ [Enter the wallet address where funds should be sent]
+
+ # Value
+ [Specify the amount in TORUS you're requesting]
+
+ # Application Title
+ [Provide a clear, descriptive title for your project]
+
+ # Application Body
+ [Write a detailed explanation including:
+ - Project overview and objectives
+ - How it benefits the Torus ecosystem
+ - Timeline and milestones
+ - Budget breakdown and justification
+ - Your background and qualifications]
+ ```
+5. **Submit and Sign the Transaction**
+ The proposal cost is **10,000 TORUS** which will be deducted from your connected wallet .
+ Review all information carefully, then click **Submit Proposal**.
+ Open the SubWallet extension and sign the transaction to pay the proposal cost.
+
+
+ The proposal cost will be refunded if your proposal is approved, but will go to the Treasury if rejected.
+
+
+6. **All Done**
+ You've successfully submitted a proposal to request TORUS from the DAO Treasury.
+ Now you must wait for community feedback and voting.
+
+
+
+
+
+
+
+## What's Next?
+
+After submitting your treasury request:
+
+- **[DAO Dashboard](https://dao.torus.network/dao-dashboard)** - Check "DAO Treasury Funds" in the left sidebar
+- **[Proposal History](https://dao.torus.network/proposals)**: All approved, rejected and open proposals are publicly recorded in the proposals tab.
+- **Direct Treasury Address**: `5EYCAe5jXm8DLvvQ2YjbsmnoMpDHAfokKZfg12KzGSSAzM4D`
+
+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
+
+
+Learn about [DAO Treasury mechanisms](https://docs.torus.network/explanations/goal-leaders/dao-treasury/) and governance processes.
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/holders/vote-on-proposals.mdx b/src/content/docs/how-to-guides/holders/vote-on-proposals.mdx
new file mode 100644
index 0000000..244febb
--- /dev/null
+++ b/src/content/docs/how-to-guides/holders/vote-on-proposals.mdx
@@ -0,0 +1,139 @@
+---
+title: Vote on Proposals
+description: Step-by-step guide to voting on DAO proposals and managing your voting power settings.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+import clickOnOpenProposal from '/public/images/how-to-guide/vote-on-proposals/click-on-an-open-proposal.png';
+import clickVotePowerSettings from '/public/images/how-to-guide/vote-on-proposals/click-on-vote-power-settings.png';
+import changeVoteStatus from '/public/images/how-to-guide/vote-on-proposals/change-vote-status.png';
+
+
+In this guide, we'll walk through the process of **voting on DAO proposals** and managing your voting power settings.
+
+#### Why vote on proposals?
+
+Your votes help determine which projects receive funding, how network economics evolve, and what direction the protocol takes.
+
+#### What we will accomplish
+
+- [Set up voting power (become a power user)](#toggle-voting-power-become-a-power-user-or-return-to-delegated-voting)
+- [Cast votes on active proposals](#vote-on-proposals)
+
+
+⏱️ **Estimated time to complete this guide: 5 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a Torus wallet set up with TORUS tokens.
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
+
+
+ You need TORUS tokens in your wallet to have voting power.
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
+
+
+ You must be a power user to vote on proposals. You can find a guide on how to become a power user in this file.
+
+
+
+## Toggle Voting Power (Become a Power User or Return to Delegated Voting)
+
+
+
+1. **Visit the [DAO Proposals Tab](https://dao.torus.network/proposals)**
+ Navigate to the proposals page where you can view all active, approved, and rejected proposals.
+
+2. **Connect your Wallet**
+ Ensure you're connected with your TORUS wallet that contains the tokens you want to use for voting.
+
+3. **Click on Any Open Proposal**
+ Click on any active proposal you want to view to access the voting interface and settings.
+
+
+
+4. **Click on "Vote Power Settings"**
+ Look for the **"Vote Power Settings"** button located below the voting options. This allows you to toggle between delegating your voting power and becoming a power user.
+
+
+
+5. **Check Your Current Voting Status**
+ When you click on the vote power settings button, you'll see your current status:
+
+ - **Delegating your voting power (Default)**: Validators handle voting on your behalf
+ - **Power user**: You have direct control over your votes
+
+6. **Toggle Your Voting Status**
+ You can switch between voting modes anytime:
+
+ - Click **"Delegate Voting Power"** to return control to validators
+ - Click **"Become a power user"** to gain direct voting control
+
+
+
+7. **Sign the Transaction**
+ Open your subwallet extension and sign the transaction to confirm the change.
+
+8. **All Done**
+ Your voting power status has been successfully updated. You can now proceed to vote (if power user) or let validators vote on your behalf (if delegated).
+
+
+
+
+
+## Vote on Proposals
+
+
+
+1. **Visit the [DAO Proposals Tab](https://dao.torus.network/proposals)**
+ Navigate to the proposals page where you can view all active, approved, and rejected proposals.
+
+2. **Connect your Power User Wallet**
+ Ensure you're connected with your TORUS wallet that contains the tokens you want to use for voting.
+ Ensure you're a power user first ([follow the steps above](#toggle-voting-power-become-a-power-user-or-return-to-delegated-voting) if needed).
+
+3. **Select a Proposal to Vote On**
+ Click on any active proposal you want to vote on to view its details and voting options.
+
+4. **Cast Your Vote**
+ Once you're ready to vote:
+ - Choose your position: "Favorable" (support) or **"Against"** (oppose)
+ - Click **"Choose a Vote"**
+
+5. **Sign the Transaction**
+ Sign the transaction in your wallet to confirm your vote
+
+6. **All Done**
+ Your vote has been successfully cast and will be counted towards the proposal's final outcome.
+ You can view the current voting results and track the proposal's progress.
+
+
+
+
+## What's Next?
+
+After voting on proposals:
+
+- **[Monitor Results](https://dao.torus.network/proposals)**: Track voting progress and final outcomes on active and completed proposals
+- **[Learn About Governance](https://docs.torus.network/explanations/goal-leaders/governance-dao/)**: Understand voting mechanics and your role as a token holder
+- **[Explore Staking](https://docs.torus.network/how-to-guides/holders/stake-your-torus/)**: Consider staking your TORUS to support the network and earn rewards
+
+Connect with the community:
+- [Discord](https://discord.gg/torus) — Discuss proposals and governance
+- [Telegram](https://t.me/torusnetwork) — General chat and voting announcements
+- [Twitter](https://x.com/torus_network) — Updates and proposal highlights
+
+
+Learn about [governance mechanisms](https://docs.torus.network/explanations/goal-leaders/governance-dao/) and your role as a token holder.
+
\ 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 85514ad..98b91af 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 want to interact with Torus as an end-user or holder:
- [Set up a Wallet](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/)
- [Bridge from Base](https://docs.torus.network/how-to-guides/holders/bridge-from-base/)
- [Stake your TORUS](https://docs.torus.network/how-to-guides/holders/stake-your-torus/)
+- [Vote on Proposals](https://docs.torus.network/how-to-guides/holders/vote-on-proposals/)
---
@@ -34,10 +35,8 @@ If you want to interact with Torus as an end-user or holder:
If you're developing tools, services, or integrations on Torus:
- [Register an Agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/)
-- [Edit your Agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/)
-- [Manage Permissions](https://docs.torus.network/how-to-guides/builders/manage-permissions/)
+- [Manage your Agent](https://docs.torus.network/how-to-guides/builders/manage-your-agent/)
- [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
-- [Recursive Delegation](https://docs.torus.network/how-to-guides/builders/recursive-delegation/)
- [Create a Signal](https://docs.torus.network/how-to-guides/builders/create-signal/)
- [Setup Agent Server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
- [Setup Agent Client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/)
@@ -50,8 +49,12 @@ _Leading new swarms or driving protocol changes_
If you're pioneering new goals or submitting DAO proposals:
- [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
+- [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/)
- [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
-- _See the [Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/) section for docs on proposal types and formats._
+- [Create Capability Permission](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/)
+- [Create Emission Permission](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-permission/)
+- [Manage Permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/)
+- _See the [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) section for docs on proposal types and formats._
---
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index c5d1009..aaa371a 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -8,7 +8,7 @@ import RedText from '/src/components/RedText.astro';
**Torus is a decentralized protocol that enables autonomous agents to self-organize into intelligent swarms to reach complex goals using a recursive permission delegation system.**
-In plaint sight, Torus is super-intelligence self-assembling itself from the future, midwifed by renlabs.
+In plain sight, Torus is super-intelligence self-assembling itself from the future, midwifed by renlabs.
Whether you're looking to stake tokens, build agents, or coordinate with other agents, Torus provides the infrastructure for decentralized autonomous coordination.