Skip to content
Merged

Dev #24

Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions astro.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,8 @@ export default defineConfig({
label: "Goal Leaders",
collapsed: false,
items: [
{ label: "Root Agents", slug: "explanations/root-agents/root-agents" },
{ label: "Root Agents", slug: "explanations/goal-leaders/root-agents" },
{ label: "Emission Proposals", slug: "explanations/goal-leaders/emission-proposals" },
],
},
],
Expand Down Expand Up @@ -99,7 +100,8 @@ export default defineConfig({
label: "Goal Leaders",
collapsed: false,
items: [
{ label: "Become a Root Agent", slug: "how-to-guides/root-agents/become-a-root-agent" },
{ label: "Become a Root Agent", slug: "how-to-guides/goal-leaders/become-a-root-agent" },
{ label: "Create Emission Proposal", slug: "how-to-guides/goal-leaders/create-emission-proposal" },
],
},
],
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/explanations/builders/agent-editing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ This balances blockchain immutability with the flexibility needed for comprehens

- **[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/root-agents/root-agents/)** - Special considerations for DAO-approved agents
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Special considerations for DAO-approved agents

Comment on lines 36 to 39
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Broken URL – duplicate goal-leaders segment.

https://docs.torus.network/explanations/goal-leaders/goal-leaders/ will 404.
The page lives at /explanations/goal-leaders/root-agents/.

-**[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)**
+**[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)**

Please adjust (and ideally use a leading-slash relative URL).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **[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/root-agents/root-agents/)** - Special considerations for DAO-approved agents
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Special considerations for DAO-approved agents
- **[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
🤖 Prompt for AI Agents
In src/content/docs/explanations/builders/agent-editing.mdx around lines 36 to
39, the URL for "Root Agents" contains a duplicated segment causing a 404 error.
Replace the incorrect URL with the correct path
"/explanations/goal-leaders/root-agents/" using a leading slash to make it a
relative URL.

<Aside type="tip" title="Ready to Update Your Agent?">
Follow our [step-by-step guide to edit your agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/) for practical instructions.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Agent metadata is stored off-chain via IPFS but referenced on-chain through cont

### Related Concepts

- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents that receive emissions directly
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents that receive emissions directly
- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - How agents interact and delegate authority
- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding DAO decision-making processes

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ If you are using a different schema, fully specify it.
### Related Concepts

- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents with direct emission access
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
Comment on lines 35 to 37
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Broken link: path points to a non-existent goal-leaders/goal-leaders page

All other files moved the Root Agent docs to goal-leaders/root-agents/, but this bullet links to goal-leaders/goal-leaders/, which 404s.

-**[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
+**[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents with direct emission access
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
🤖 Prompt for AI Agents
In src/content/docs/explanations/builders/demand-signaling.mdx around lines 35
to 37, the link for "Root Agents" incorrectly points to a non-existent path
goal-leaders/goal-leaders/. Update this link to the correct path
goal-leaders/root-agents/ to fix the broken link and prevent 404 errors.

- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - Understanding emission mechanisms

Expand Down
58 changes: 58 additions & 0 deletions src/content/docs/explanations/goal-leaders/emission-proposals.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: Emission Proposals
description: Understanding emission proposals, how they work, and their role in managing Torus network incentives and economics.
---

import {
Aside,
Card,
CardGrid,
Code,
Steps,
Tabs,
TabItem,
} from "@astrojs/starlight/components";

Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.

Comment on lines +16 to +17
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Spelling error: “coponents” → “components”

Minor typo in the first paragraph.

-Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.
+Emission proposals can adapt the token emission rate and distribution across different components of the protocol.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.
Emission proposals can adapt the token emission rate and distribution across different components of the protocol.
🧰 Tools
🪛 LanguageTool

[grammar] ~16-~16: Ensure spelling is correct
Context: ... rate and distribution across different coponents of the protocol. These proposals allow...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents
In src/content/docs/explanations/goal-leaders/emission-proposals.mdx around
lines 16 to 17, fix the spelling error by changing "coponents" to "components"
in the sentence describing emission proposals adapting the token emission rate
and distribution.

These proposals allow the community to adapt the macro-economics of the network based on the network's context and external conditions. They can shift both the rate of emissions, and how those emissions are distributed between agents, allocator dividends and the protocol treasury.

<Aside type="tip">
**Emission proposals require community consensus** through the governance voting process, ensuring that changes to network economics reflect the collective will of TORUS stakeholders.
</Aside>

## How Emission Proposals Work

Emission proposals allow TORUS stakeholders to configure 3 key percentage parameters:

### Core Parameters

The three parameters control two separate distribution pools:

**Burn Distribution (up to 100% total):**
- **Recycling Percentage**: Portion of emissions that is recycled
- **Treasury Percentage**: Portion allocated to the protocol treasury

The remaining % of emissions is distributed to the network.

*Note: Recycling Percentage + Treasury Percentage can be up to 100% total (e.g., 60% combined is valid)*

**Incentive Distribution (up to 100% total):**
- **Incentives Ratio**: The incentive distribution ratio between agents and stake allocator dividends

### Proposal conditions

For a proposal to pass, it must meet two requirements:
- **Majority Support**: More than 50% of votes must be positive
- **Participation Threshold**: Total votes must exceed 10% of all TORUS staked in the network + it must be at least 2 days old


## Related Concepts

- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding the broader DAO framework
- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - How TORUS token economics work
- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - How governance permissions enable proposal creation

<Aside type="tip" title="Ready to Create a Proposal?">
Follow our [emission proposal guide](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/) to learn the step-by-step process.
</Aside>
Original file line number Diff line number Diff line change
Expand Up @@ -35,5 +35,5 @@ Successful applicants demonstrate credible execution, active community participa
- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - How Root Agents access and use network emissions

<Aside type="tip" title="Ready to Apply?">
Follow our [step-by-step application guide](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/) to submit your Root Agent application.
Follow our [step-by-step application guide](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) to submit your Root Agent application.
</Aside>
3 changes: 2 additions & 1 deletion src/content/docs/explanations/start-here.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,8 @@ Understanding how agent systems work within Torus:

Understanding governance and leadership systems:

- [Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/) — DAO approval process and direct emission access
- [Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/) — DAO approval process and direct emission access
- [Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/) — How to adjust network economics through governance

---

Expand Down
6 changes: 3 additions & 3 deletions src/content/docs/getting-started/concepts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,19 +12,19 @@ The system operates as one fractal super-swarm, which is composed of one emergen
Swarms are subgraphs, and can form at any position in the hypergraph.

The Torus hypergraph emerges from and aligns back to the stake root, tethering the system to the interests of stake.
Torus aligns towards the central point of stake, while stake is decentralized representing the system as a whole, effectively aligning it to itself.
Torus aligns towards the central point of stake, while stake is decentralized, representing the system as a whole, effectively aligning it to itself.

Swarms form bottom-up around top-down goals, their formation happens organically without central planning.
Swarms operate as self-assembling multi-scale competency architectures,
collectively navigating towards complex goals with full autonomy at every level and open competition at every edge.

The permission & delegation system enables agents to granularily specialize while remaining aligned across levels.
Swarms collectively explore a problem space and engage in an open-ended process of recursive niche construction to navigate towards the swarms goal.
Swarms collectively explore a problem space and engage in an open-ended process of recursive niche construction to navigate towards the swarm's goal.


#### v0.5

The v0.5 is a pragmatic, growth oriented and limited implemention of the Torus conceptual model.
The v0.5 is a pragmatic, growth oriented and limited implementation of the Torus conceptual model.
Its mainnet release initiates the formation process of the Torus hypergraph and allows battletesting of our concepts.
It is sufficient for the formation of sophisticated agent swarms and applies the core ideas.

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/getting-started/tokenomics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ TORUS was fair launched with no pre-mine. 100% of emissions are openly competed

The initial TORUS supply consists entirely of bridged COMAI tokens, which were also launched with a fair distribution model and no pre-mine.

<Image src={graph} alt="Tekenomics Graph" width="1080" />
<Image src={graph} alt="Tokenomics Graph" width="1080" />
2 changes: 1 addition & 1 deletion src/content/docs/how-to-guides/builders/create-signal.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Signaling demand allows you to delegate part of your emissions to agents who can
<CardGrid>
<Card title="Agent with Emissions" icon="seti:pipeline">
You need to be an agent with emissions (coming from root or target) to create demand signals.
You can find guides on how to [register an agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/) and [become a root agent](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/).
You can find guides on how to [register an agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/) and [become a root agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/).
</Card>
<Card title="Available Emission Allocation" icon="seti:license">
Have incoming emission streams available to offer as incentive for capability providers.
Expand Down
6 changes: 3 additions & 3 deletions src/content/docs/how-to-guides/builders/register-an-agent.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Registering an agent makes you discoverable in Torus and enables you to receive

- Registering an agent does not prevent you from also becoming a Root Agent — both processes are independent and can be completed in parallel.

- You can follow the [guide to become a Root Agent here](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/).
- You can follow the [guide to become a Root Agent here](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/).
</Aside>


Expand Down Expand Up @@ -116,7 +116,7 @@ Registering an agent makes you discoverable in Torus and enables you to receive
You should find your agent on the <RedText variant="light">Allocator tab</RedText>, with the filter of <RedText variant="light">**Registered Agents**</RedText>.
<ClickableImage src={registeredAgents} alt="Allocator tab" />

6. **All Done**
7. **All Done**
You've now successfully registered an Agent on Torus.
You can now participate in Torus by creating permissions, capabilities, and much more.

Expand All @@ -130,7 +130,7 @@ Now that you're a registered agent, you can:

- **Start building**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs to other agents
- **Connect with others**: Use an [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) to interact with existing capabilities
- **Consider upgrading**: Root Agents set goals and receive direct emissions — [learn how to apply here](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/) if that matches your vision.
- **Consider upgrading**: Root Agents set goals and receive direct emissions — [learn how to apply here](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) if that matches your vision.


Connect with the community:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ Root Agents receive emissions directly from the stake root and can set goals for
After submitting your Root Agent application:

- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/root-agents/root-agents/) approval criteria and DAO governance
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
Comment on lines 108 to 110
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Incorrect reference to Root Agent explanation page.

Same duplication as above – link should point to /explanations/goal-leaders/root-agents/.

-Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria …
+Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/root-agents/) approval criteria …

Fix to avoid a broken “What’s Next?” link.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/root-agents/root-agents/) approval criteria and DAO governance
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/root-agents/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
🤖 Prompt for AI Agents
In src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx around
lines 108 to 110, the link for "Root Agent" explanation incorrectly points to
/explanations/goal-leaders/goal-leaders/. Update this URL to
/explanations/goal-leaders/root-agents/ to fix the broken "What's Next?" link
and ensure it directs to the correct explanation page.


Connect with the community:
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
---
title: Create an Emission Proposal
description: Step-by-step guide to creating and submitting emission proposals through the Torus DAO.
---

import {
Steps,
Aside,
CardGrid,
Card,
LinkCard
} 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 **submitting an emission proposal** via the Torus DAO.

## Prerequisites

<CardGrid>
<Card title="TORUS Balance" icon="seti:license">
You need at least 10 000 TORUS in your wallet to create proposals.
See [how to get TORUS](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
</Card>
<Card title="Economic Rationale" icon="seti:shell">
Understand how your changes will affect network economics and incentives.
Review the [emission proposals explanation](https://docs.torus.network/explanations/goal-leaders/emission-proposals/).
</Card>
</CardGrid>


## Create an Emission Proposal

<Steps>

1. **Visit the [Torus DAO Proposals tab](https://dao.torus.network/proposals)**
Navigate to the DAO proposals page where you can view existing proposals and create new ones.

2. **Connect your Wallet**
Click the <RedText variant="light">**Connect Wallet**</RedText> button and ensure you're connected with a wallet that has at least 10,000 TORUS.

3. **Click on Shape the Network**
Look for the <RedText variant="light">"Shape the Network" button</RedText>, it is at the top right corner of the dashboard.

4. **Select "Create Emission Proposal" Type**
In the modal, choose <RedText variant="light">**"Create emission proposal"**</RedText> from the available options.
This is similar to the whitelisting process but focuses on network economics.

5. **Configure Emission Parameters**
Set the three key percentage parameters across two distribution pools:

**Burn Distribution (up to 100% total):**
- **Recycling Percentage**: <RedText variant="light">Portion of fees burned through recycling</RedText>
- **Treasury Percentage**: <RedText variant="light">Portion allocated to network treasury</RedText>

**Reward Distribution (up to 100% total):**
- **Incentives Ratio**: <RedText variant="light">Portion for incentive programs and rewards</RedText>

<Aside type="caution">
**Parameter Requirements**

- Recycling + Treasury percentages can be up to 100% total (e.g., 30% + 40% = 70% is valid)
- Incentives Ratio is a separate allocation up to 100% for rewards
- This dual-pool system controls burn vs. reward distribution independently
</Aside>

6. **Add Proposal Details**
Provide comprehensive information about your proposal:

- **Title**: Clear, descriptive name for the proposal
- **Description**: Detailed explanation of the economic rationale, why these specific percentages benefit the network...

7. **Review and Submit**
Double-check all parameters and details before submission. Click <RedText variant="light">**"Submit Proposal"**</RedText> and <RedText variant="light">confirm the transaction in your wallet</RedText>.

8. **Share with the community**
After submitting, post your proposal in Discord, Telegram, or other channels to spark discussion and encourage voting.
<Aside type="note">
A proposal isn’t final until voting ends and it’s executed on‑chain (or rejected).
Each proposal remains open for 7 days; if it doesn’t meet the approval criteria within that window, it closes automatically.
To try again, you must repeat the process (including the 10,000 TORUS fee).
</Aside>

9. **All done when either**
- The 7‑day voting window ends.
- ≥ 50 % support & > 10 % participation: proposal executes on‑chain.
- ≤ 50 % support & > 10 % participation: proposal get denied.

Therefore, make sure to follow the voting process closely.




</Steps>

## What's Next?

After submitting your emission proposal:
- **Community Discussion**: Engage with feedback and questions from other community members

Connect with the community during the process:

- **[Discord](https://discord.gg/torus)** — Discuss proposal details and economic implications
- **[Telegram](https://t.me/torusnetwork)** — Share updates and gather community sentiment
- **[Twitter](https://x.com/torus_network)** — Announce your proposal to the broader ecosystem
4 changes: 2 additions & 2 deletions src/content/docs/how-to-guides/holders/setup-a-wallet.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak
1. **Download the Extension**
Visit the [SubWallet download page](https://www.subwallet.app/download.html) and download the appropriate version of the extension for your browser (Chrome, Brave, Firefox, or Microsoft Edge).

3. **Activate/Pin the Extension**
2. **Activate/Pin the Extension**
In some cases, you may need to activate the extension manually. Refer to the [SubWallet documentation](https://docs.subwallet.app/main) for instructions.

If everything is correct, the SubWallet icon should appear in the top-right corner of your browser. You are ready to move to the next step and create a new wallet.
Expand Down Expand Up @@ -123,7 +123,7 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak


3. **Search for Torus and activate it**
Click on the search bar, type Torus, and select it from the list. <RedText varian="light">Make sure to enable it</RedText> so it appears in your list of active tokens.
Click on the search bar, type Torus, and select it from the list. <RedText variant="light">Make sure to enable it</RedText> so it appears in your list of active tokens.
<ClickableImage src={subwalletSearchTorusNetwork} alt="SubWallet search for Torus button" />

4. **Confirm Torus is active**
Expand Down
3 changes: 2 additions & 1 deletion src/content/docs/how-to-guides/start-here.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,8 @@ _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/root-agents/become-a-root-agent/)
- [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
- [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
- _See the [Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/) section for docs on proposal types and formats._

---
Expand Down
Loading