diff --git a/astro.config.mjs b/astro.config.mjs index 27470ff..15cf150 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -34,9 +34,10 @@ export default defineConfig({ { label: "Explanations", items: [ - { label: "Start Here", slug: "explanations/start-here" }, + { label: "Table of Contents", slug: "explanations/table-of-contents" }, { label: "v0.5", + collapsed: true, items: [ { label: "Control Space", slug: "explanations/v05/control-space" }, { label: "Permission System", slug: "explanations/v05/permissions" }, @@ -48,9 +49,16 @@ export default defineConfig({ { label: "Governance & DAO", slug: "explanations/v05/governance-dao" }, ], }, + { + label: "Holders", + collapsed: true, + items: [ + { label: "Staking", slug: "explanations/holders/staking" }, + ], + }, { label: "Builders", - collapsed: false, + collapsed: true, items: [ { label: "Agent Registration", slug: "explanations/builders/agent-registration" }, { label: "Agent Editing", slug: "explanations/builders/agent-editing" }, @@ -61,7 +69,7 @@ export default defineConfig({ }, { label: "Goal Leaders", - collapsed: false, + collapsed: true, items: [ { label: "Root Agents", slug: "explanations/goal-leaders/root-agents" }, { label: "Emission Proposals", slug: "explanations/goal-leaders/emission-proposals" }, @@ -72,10 +80,10 @@ export default defineConfig({ { label: "How-to Guides", items: [ - { label: "Start Here", slug: "how-to-guides/start-here" }, + { label: "Table of Contents", slug: "how-to-guides/table-of-contents" }, { label: "Holders", - collapsed: false, + collapsed: true, items: [ { label: "Setup a Wallet", slug: "how-to-guides/holders/setup-a-wallet" }, { label: "Bridge from Base", slug: "how-to-guides/holders/bridge-from-base" }, @@ -84,21 +92,20 @@ export default defineConfig({ }, { label: "Builders", - collapsed: false, + 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 Capabilities", slug: "how-to-guides/builders/manage-capabilities" }, + { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" }, { label: "Create a Signal", slug: "how-to-guides/builders/create-signal" }, - // { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" }, - // { label: "Delegate Emission Streams", slug: "how-to-guides/builders/delegate-emission-streams" }, { label: "Setup Agent Server", slug: "how-to-guides/builders/setup-agent-server" }, { label: "Setup Agent Client", slug: "how-to-guides/builders/setup-agent-client" }, ], }, { label: "Goal Leaders", - collapsed: false, + collapsed: true, items: [ { 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" }, @@ -109,10 +116,10 @@ export default defineConfig({ { label: "Development", items: [ - { label: "Start Here", slug: "development/start-here" }, + { label: "Table of Contents", slug: "development/table-of-contents" }, { label: "Web Apps", - collapsed: false, + collapsed: true, items: [ { label: "Overview and Setup", @@ -126,7 +133,7 @@ export default defineConfig({ }, { label: "CLI Reference", - collapsed: false, + collapsed: true, items: [ { label: "Setup CLI", slug: "development/cli/setup-cli" }, { label: "Key Management", slug: "development/cli/key-management" }, @@ -135,7 +142,7 @@ export default defineConfig({ }, { label: "Network Operations", - collapsed: false, + collapsed: true, items: [ { label: "Global Parameters", slug: "development/network/global-parameters" }, { label: "Running a Node", slug: "development/network/running-node" }, diff --git a/src/content/docs/development/start-here.mdx b/src/content/docs/development/table-of-contents.mdx similarity index 98% rename from src/content/docs/development/start-here.mdx rename to src/content/docs/development/table-of-contents.mdx index 28929a7..e3401d6 100644 --- a/src/content/docs/development/start-here.mdx +++ b/src/content/docs/development/table-of-contents.mdx @@ -1,5 +1,5 @@ --- -title: Start Here +title: Table of Contents description: Technical documentation and tools for developing with and on Torus. --- import { diff --git a/src/content/docs/explanations/holders/staking.mdx b/src/content/docs/explanations/holders/staking.mdx new file mode 100644 index 0000000..adc7d51 --- /dev/null +++ b/src/content/docs/explanations/holders/staking.mdx @@ -0,0 +1,39 @@ +--- +title: Staking +description: Understanding the staking mechanism, incentives, and how token holders participate in Torus network security and governance. +--- + +import { + Aside, + Card, + CardGrid, + Code, + Steps, + Tabs, + TabItem, +} from "@astrojs/starlight/components"; + + +Stake is the organism's root container of authority and monetary energy, transmutable towards its emergent agency. +Forming a circular value flow between incentives and stake in their outcome. Stake is permissionless, while everything else is permissioned by stake. + +Staking is the core mechanism through which TORUS holders secure the network, participate in governance, +and earn rewards while supporting the agents and initiatives they believe in. + + +### Core Mechanics + +- When you stake, your TORUS are **locked** in the Root Allocator +- Tokens remain **owned by the staker** but cannot be used for transaction purposes +- It accounts for network consensus, such as, voting, allocating and commenting on proposals +- Staking rewards are generated from network emissions + +## Related Concepts + +- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - Understanding TORUS token economics and emission structure +- **[Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/)** - How staking parameters can be adjusted through governance +- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Understanding the agents you can support through staking + + \ No newline at end of file diff --git a/src/content/docs/explanations/start-here.mdx b/src/content/docs/explanations/table-of-contents.mdx similarity index 92% rename from src/content/docs/explanations/start-here.mdx rename to src/content/docs/explanations/table-of-contents.mdx index 769248a..26bab9f 100644 --- a/src/content/docs/explanations/start-here.mdx +++ b/src/content/docs/explanations/table-of-contents.mdx @@ -1,5 +1,5 @@ --- -title: Start Here +title: Table of Contents description: Deep-dive explanations to help you understand how Torus works under the hood. --- import { @@ -15,7 +15,7 @@ Welcome to the **Explanations** section of the Torus documentation. If you need to accomplish a specific task, check out our [How-to Guides](https://docs.torus.network/how-to-guides/start-here/) instead. -These explanations provide deep understanding of how Torus works — the concepts, mechanisms of Torus. +These explanations provide deep understanding of how Torus works, the concepts, mechanisms of Torus. ## v0.5 Related Topics @@ -29,15 +29,23 @@ Understanding the technical implementation and design of Torus v0.5: --- +## For Holders + +Understanding how holders participate in the network: + +- [Staking](https://docs.torus.network/explanations/holders/staking/) — Staking mechanisms, incentives, and reward distribution + +--- + ## For Builders (Agents) Understanding how agent systems work within Torus: - [Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/) — Registration economics, burn mechanisms, and discovery -- [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 - [Agent Editing](https://docs.torus.network/explanations/builders/agent-editing/) — 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 --- 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 4cb57d5..cf1f6bc 100644 --- a/src/content/docs/how-to-guides/builders/create-permission.mdx +++ b/src/content/docs/how-to-guides/builders/create-permission.mdx @@ -262,7 +262,10 @@ After creating permissions, you can: For help with permission management: - [Torus Community Discord](https://discord.gg/torus) -- [Permission System Documentation](https://docs.torus.network/explanations/v05/permissions/) + + #### Related Topics diff --git a/src/content/docs/how-to-guides/builders/create-signal.mdx b/src/content/docs/how-to-guides/builders/create-signal.mdx index c173f33..f09d9a9 100644 --- a/src/content/docs/how-to-guides/builders/create-signal.mdx +++ b/src/content/docs/how-to-guides/builders/create-signal.mdx @@ -109,4 +109,8 @@ Now that you've created a signal, you might want to: Connect with the community: - [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements - [Telegram](https://t.me/torusnetwork) — General chat and announcements -- [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx b/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx deleted file mode 100644 index 5c6d71f..0000000 --- a/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx +++ /dev/null @@ -1,357 +0,0 @@ ---- -title: Delegate Emission Streams -description: Configure emission permissions to delegate token flows and create economic coordination structures. ---- - -import { - Steps, - Aside, - CardGrid, - Card, - Tabs, - TabItem -} from "@astrojs/starlight/components"; -import RedText from '/src/components/RedText.astro'; - -In this guide, we'll set up **emission permissions** to delegate portions of your token streams to other agents. -This enables economic coordination, agent hiring, and revenue sharing structures. - -#### What we will accomplish - -- Delegate percentage-based emission streams -- Set up fixed-amount allocations -- Configure delegation terms and monitoring -- Understand stream preservation and traceability - - - -## Prerequisites - - - - You must be receiving emission streams (from staking, delegation, or root agent status). - - - Know the agent addresses you want to delegate emissions to. - - - Sufficient TORUS for transaction fees. - - - -## Understanding Emission Streams - -Emission permissions work with **stream identity preservation**: - -- **StreamId**: Each emission source has a unique identifier -- **Traceability**: Token flow is tracked from source to final recipients -- **Delegation Chains**: Streams maintain identity through recursive delegations - -**Common Stream Types:** -- Staking rewards from allocators -- Delegation fees from sub-agents -- Root agent emissions -- Custom revenue streams - -## Delegation Types - - - - -**Percentage-based delegation of specific streams** - -- Delegate 0-100% of particular streams -- Safety constraints prevent over-allocation -- Maintains stream identity through delegation -- Ideal for performance-based compensation - - - - -**Set TORUS amounts per time period** - -- Fixed payments regardless of stream performance -- Useful for salary-like arrangements -- Independent of underlying stream fluctuations -- Predictable costs for budget planning - - - - -## Delegate Emission Streams - - - -1. **Visit the [Torus Portal](https://portal.torus.network/)** - Navigate to **Permissions Management** → **Create Permission**. - -2. **Select Emission Permission** - Choose "Emission Permission" from the permission type dropdown. - -3. **Connect your wallet** - Ensure you're connected as the agent receiving emissions to delegate. - -4. **Configure delegation type** - Choose between stream-based or fixed amount delegation. - -5. **Set delegation terms** - Configure duration, recipient, and constraints. - -6. **Review delegation contract** - Verify all details before submitting. - -7. **Submit emission permission** - Sign the transaction to create the delegation on-chain. - -8. **Monitor delegation** - Track delegation status in the Portal dashboard. - - - -## Delegation Configuration - - - - -### Stream-Based Delegation - -**Select Streams**: Choose which emission streams to delegate -- View all your active streams with their StreamIds -- See current flow rates and sources -- Select specific streams for delegation - -**Set Percentages**: Define allocation per stream -``` -Stream A (Staking): 25% → Agent Bob -Stream B (Fees): 50% → Agent Charlie -Stream C (Root): 10% → Agent Dave -``` - -**Safety Validation**: System ensures totals don't exceed 100% per stream - - - - -### Fixed Amount Delegation - -**Amount**: Specify TORUS amount per period -- Daily allocation: `100 TORUS/day` -- Weekly allocation: `700 TORUS/week` -- Monthly allocation: `3000 TORUS/month` - -**Payment Schedule**: Define distribution frequency -- Real-time (continuous) -- Daily batches -- Weekly payments -- Monthly distributions - -**Source Priority**: Order which streams fund fixed payments -1. Staking rewards (priority 1) -2. Delegation fees (priority 2) -3. Other streams (priority 3) - - - - -## Delegation Terms Configuration - -**Duration**: -- **Ongoing**: Until manually revoked -- **Fixed Term**: Specific end date/block -- **Conditional**: Based on performance metrics - -**Recipient**: Agent address to receive delegated emissions - -**Constraints**: Optional limitations -- Maximum delegation amount -- Performance requirements -- Review periods - -## Monitoring Configuration - -Optionally configure delegation monitoring: -- **Performance metrics**: Track recipient contribution -- **Auto-adjustment**: Modify delegation based on performance -- **Reporting**: Regular delegation reports - -## Contract Review Checklist - -Before submitting, verify: -- Stream selections and percentages -- Recipient address -- Duration and constraints -- Estimated delegation amounts - -## Managing Emission Delegations - -### View Active Delegations - -Monitor your delegations in the Portal: -- **Outgoing**: Emissions you're delegating to others -- **Incoming**: Emissions others are delegating to you -- **Performance**: Track delegation effectiveness - -### Adjust Delegations - -For active delegations: - -1. Navigate to **Permissions Management** → **Edit Permission** -2. Select the emission permission to modify -3. Adjust percentages, amounts, or terms (within constraints) -4. Submit changes on-chain - -### Revoke Delegations - -To stop delegating emissions: - -1. Find the delegation in your management dashboard -2. Select **Revoke Permission** -3. Confirm revocation (takes effect next distribution) -4. Sign transaction - -## Advanced Scenarios - -### Multi-Level Delegation Chains - -Create complex delegation hierarchies: - -``` -Root Agent Alice -├─ 40% → Agent Bob (Development Team Lead) -│ ├─ 50% → Agent Carol (Senior Developer) -│ └─ 30% → Agent Dave (Junior Developer) -├─ 30% → Agent Eve (Marketing Lead) -│ ├─ 60% → Agent Frank (Content Creator) -│ └─ 40% → Agent Grace (Community Manager) -└─ 20% → Agent Henry (Operations) -``` - -### Performance-Based Delegation - -Set up conditional delegations: - -- **KPI Triggers**: Adjust delegation based on metrics -- **Milestone Payments**: Release emissions upon achievements -- **Review Cycles**: Regular performance evaluations - -### Hybrid Allocation Models - -Combine multiple delegation types: - -```typescript -// Example delegation structure -const delegationModel = { - fixedSalary: { - recipient: "agent-bob-address", - amount: "1000 TORUS/month", - stream: "base-compensation" - }, - performanceBonus: { - recipient: "agent-bob-address", - percentage: "15%", - stream: "staking-rewards", - conditions: "monthly-performance > 95%" - } -}; -``` - -## Best Practices - -### Economic Planning - -- **Start small**: Begin with small percentages and scale based on performance -- **Diversify recipients**: Don't delegate all emissions to single agent -- **Monitor ROI**: Track value created vs. emissions delegated -- **Plan cash flow**: Ensure sufficient retained emissions for operations - -### Risk Management - -- **Set constraints**: Use maximum delegation limits -- **Regular reviews**: Periodically assess delegation effectiveness -- **Performance metrics**: Establish clear success criteria -- **Exit strategies**: Plan for delegation termination scenarios - -### Operational Efficiency - -- **Batch delegations**: Group similar delegations to save transaction costs -- **Automate monitoring**: Set up alerts for performance thresholds -- **Document agreements**: Maintain clear records of delegation purposes -- **Communication**: Coordinate expectations with recipients - -## Troubleshooting - -### Delegation Creation Fails - -**Common issues:** -- Attempting to delegate more than 100% of a stream -- Insufficient balance for transaction fees -- Invalid recipient agent address -- No active emission streams to delegate - -### Payments Not Processing - -**Check that:** -- Delegation permission is active and confirmed -- Underlying emission streams are still active -- No conflicting delegations over-allocate streams -- Recipient agent address is correct - -### Performance Issues - -**Symptoms:** -- Delayed payment processing -- Incorrect delegation amounts -- Stream identity confusion - -**Solutions:** -- Verify stream selections and percentages -- Check for delegation chain conflicts -- Monitor blockchain network status -- Contact support for complex delegation debugging - -## Monitoring and Analytics - -### Track Delegation Performance - -Monitor key metrics: -- **Delegation flow rates**: TORUS/day, week, month -- **Recipient performance**: Value created vs. emissions received -- **Cost effectiveness**: ROI on delegations -- **Stream health**: Underlying emission stability - -### Optimize Delegation Strategy - -Based on performance data: -- Adjust percentages for top performers -- Reallocate from underperforming delegations -- Add performance bonuses for exceptional results -- Scale successful delegation models - -## What's Next? - -With emission delegations configured, you can: - -- **Build economic networks**: Create multi-agent coordination structures -- **Scale agent teams**: Hire and compensate agent contributors -- **Optimize performance**: Use emissions as incentive mechanisms -- **Analyze economics**: Study delegation ROI and optimization - -## Support and Resources - -For help with emission delegations: - -- [Torus Community Discord](https://discord.gg/torus) -- [Emission Permissions Documentation](https://docs.torus.network/explanations/v05/emission-permissions/) - -#### Related Topics - - - - Economic coordination theory - - - General permission creation - - \ 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 index 46f5b6e..ec7fe6c 100644 --- a/src/content/docs/how-to-guides/builders/edit-your-agent.mdx +++ b/src/content/docs/how-to-guides/builders/edit-your-agent.mdx @@ -103,4 +103,8 @@ After updating your agent information: Connect with the community: - [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements - [Telegram](https://t.me/torusnetwork) — General chat and announcements -- [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx index 91b4498..4c883bd 100644 --- a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx +++ b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx @@ -156,11 +156,15 @@ 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**: Delegate permissions to allow other agents to use your capabilities *(coming soon)* +- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/builders/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 \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/manage-permissions.mdx b/src/content/docs/how-to-guides/builders/manage-permissions.mdx index cb8a449..2e7cb1a 100644 --- a/src/content/docs/how-to-guides/builders/manage-permissions.mdx +++ b/src/content/docs/how-to-guides/builders/manage-permissions.mdx @@ -1,278 +1,210 @@ --- title: Manage Permissions -description: Step-by-step guide to creating, editing, and managing permissions in Torus's recursive delegation system. +description: Step-by-step guide to creating and managing permissions in the Torus portal. --- import { Steps, Aside, CardGrid, - Card, - Tabs, - TabItem + 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 Torus's recursive delegation system. -Permissions enable fine-grained control over emission distribution and capability access between agents. +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 and emission permissions -- Configure delegation terms and constraints -- Edit and revoke existing permissions -- Understand revocation and enforcement mechanisms +- [Create capability permissions](#create-capability-permission) +- [Create emission permissions](#create-emission-permission) +- [Manage existing permissions](#manage-existing-permissions) ## Prerequisites - You must have a registered agent that can delegate permissions. - - - Know the agent addresses you want to delegate permissions to. + 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 sufficient TORUS for transaction fees. + 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. -## Permission Types - - - - -**Purpose**: Grant access to specific agent endpoints or namespaces -**Use Cases**: API access, service delegation, resource sharing - -**Example**: Allow Agent B to access Agent A's memory storage API - - - - -**Purpose**: Delegate portions of emission streams (token flows) -**Use Cases**: Hiring agents, revenue sharing, economic coordination - -**Example**: Agent A delegates 20% of staking rewards to Agent B +## Create Capability Permission - - - -## Create a Permission +Capability permissions control access to specific agent endpoints and APIs. -1. **Visit the [Torus Portal](https://portal.torus.network/)** - Navigate to **Permissions Management** → **Create Permission**. - -2. **Connect your wallet** - Ensure you're connected as the delegating agent. +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. **Choose permission type** - Select either **Capability** or **Emission** permission from the dropdown. +3. **Fill the form** + ```md + # Recipient + The agent that will receive the permission. -4. **Configure permission details based on type** + # Capability Path + Select from dropdown of all capability paths available to you for delegation. -5. **Set revocation terms** + # Duration + - **Indefinite**: Permission remains valid indefinitely + - **Until Block**: Permission expires at a specific block -6. **Configure enforcement** (Optional) + # Block Number + Specific block number when permission expires + (only shown for Until Block duration) -7. **Review permission contract** + # Maximum Instances + The maximum number of instances that can be created under this permission. -8. **Submit 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 + ``` -9. **Verify creation** +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). -### Configuring Capability Permissions - -For capability permissions, configure these details: - -**Namespace Path**: Enter the specific capability path -- Format: `agent...` -- Example: `agent.alice.memory.twitter.post` - -**Recipient**: Agent address that will receive access - -**Duration**: Set permission lifespan -- **Indefinite**: Permission lasts until manually revoked -- **Fixed Term**: Specify end date/block number -- **Conditional**: Based on specific triggers - -**Constraints**: Optional usage limitations -- Rate limits (calls per hour/day) -- Access windows (specific times) -- Usage quotas - -### Configuring Emission Permissions - -For emission permissions, configure these details: - -**Stream Selection**: Choose which emission streams to delegate -- Staking rewards -- Delegation fees -- Specific revenue streams - -**Allocation Type**: -- **Percentage**: Delegate X% of selected streams -- **Fixed Amount**: Delegate specific TORUS amount per period - -**Recipient**: Agent address that will receive emissions - -**Duration**: Set delegation period -- Ongoing until revoked -- Fixed term (blocks/time) -- Performance-based triggers - -### Setting Revocation Terms - -Configure how the permission can be terminated: - -- **Revocable**: You can cancel anytime -- **Irrevocable**: Cannot be cancelled (use carefully) -- **Conditional**: Auto-revoke based on conditions -### Configuring Enforcement +## Create Emission Permission -Set third-party governance authority (Optional): -- DAO enforcement for disputes -- Multi-sig requirements -- Community arbitration - -### Review and Submit - -Before submission, verify all details: -- Delegator and recipient addresses -- Scope and limitations -- Duration and revocation terms -- Associated costs - -## Managing Permissions - -### View Active Permissions - -Track your delegated permissions in the Torus Portal: -- **Outgoing**: Permissions you've granted to others -- **Incoming**: Permissions others have granted to you -- **Status**: Active, expired, revoked permissions - -### Edit Permissions - -For permissions you've created: - - - -1. Navigate to **Permissions Management** → **Edit Permission** -2. Select the permission to modify -3. Update allowed parameters (within original constraints) -4. Submit changes on-chain - - - -### Revoke Permissions - -To cancel a revocable permission: +Emission permissions enable economic coordination by delegating portions of your token emission streams. -1. Find the permission in your management dashboard -2. Select **Revoke Permission** -3. Confirm revocation (immediate effect) -4. Sign transaction to execute on-chain - +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). -## Advanced Configuration - -### Recursive Permissions -Create permission chains where recipients can further delegate: +## Manage Existing Permissions -- **Enable sub-delegation**: Allow recipients to delegate portions -- **Set depth limits**: Maximum delegation chain length -- **Inheritance rules**: How constraints pass down the chain +Both capability and emission permissions can be managed through the same interface with type-specific options. -### Conditional Permissions - -Set up smart permissions that trigger based on conditions: - -- **Performance metrics**: Delegate based on agent performance -- **Time-based**: Activate during specific periods -- **Event-driven**: Trigger on blockchain events - -## Best Practices - -### Security Considerations - -- **Principle of least privilege**: Grant minimum necessary permissions -- **Regular audits**: Review and clean up unused permissions -- **Test with small amounts**: Start with small emission delegations - -### Economic Efficiency - -- **Batch operations**: Group related permissions to save gas -- **Monitor performance**: Track ROI on emission delegations -- **Set reasonable terms**: Balance flexibility with security + -### Delegation Strategy +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). -- **Clear documentation**: Maintain records of permission purposes -- **Communication**: Coordinate with recipients about expectations -- **Gradual scaling**: Increase delegation scope based on proven success +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 -## Troubleshooting +3. **Select Permission to Manage** + Click on the specific permission from the list. This will open a modal showing all the permission details. -### Permission Creation Fails +4. **Revoke Permission** + In this step you can only revoke active permissions. Click the **Revoke** button to remove the permission. -**Common issues:** -- Insufficient balance for transaction fees -- Invalid recipient agent address -- Namespace path doesn't exist (for capabilities) -- Attempting to delegate more than available (for emissions) +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. -### Permission Not Working +6. **All Done** + Your permission has been revoked. The changes will be reflected immediately in the permissions list. -**Check that:** -- Permission is active and not expired -- Recipient is using correct namespace path -- No conflicting constraints or rate limits -- Blockchain confirmation completed -### Revocation Issues -**Verify:** -- Permission was created as revocable -- You're the original delegator -- No outstanding enforcement claims + ## What's Next? -After managing permissions, you can: - -- **Monitor usage**: Track how recipients use delegated permissions -- **Optimize delegation**: Adjust terms based on performance -- **Scale coordination**: Build complex multi-agent workflows -- **Analyze economics**: Review emission delegation ROI - -## Support and Resources - -For help with permission management: +After successfully managing your permissions, you can: -- [Torus Community Discord](https://discord.gg/torus) -- [Permission System Documentation](https://docs.torus.network/explanations/v05/permissions/) +- **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/) -#### Related Topics - - - - Deep dive into architecture - - - Economic coordination mechanisms - - \ No newline at end of file + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/register-an-agent.mdx b/src/content/docs/how-to-guides/builders/register-an-agent.mdx index aa59f2e..47aa032 100644 --- a/src/content/docs/how-to-guides/builders/register-an-agent.mdx +++ b/src/content/docs/how-to-guides/builders/register-an-agent.mdx @@ -136,4 +136,8 @@ Now that you're a registered agent, you can: Connect with the community: - [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements - [Telegram](https://t.me/torusnetwork) — General chat and announcements -- [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/setup-agent-client.mdx b/src/content/docs/how-to-guides/builders/setup-agent-client.mdx index 768bd07..bd7d342 100644 --- a/src/content/docs/how-to-guides/builders/setup-agent-client.mdx +++ b/src/content/docs/how-to-guides/builders/setup-agent-client.mdx @@ -160,10 +160,14 @@ Agent clients allow you to easily communicate with other agents' APIs, enabling Now that you can communicate with other agents, you might want to: - **Build your own API**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide capabilities to others -- **Understand authentication**: Learn about [agent client](https://docs.torus.network/explanations/builders/agent-client/) communication patterns and security - **Signal for needs**: Create [demand signals](https://docs.torus.network/how-to-guides/builders/create-signal/) to find agents with specific capabilities you need Connect with the community: - [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements - [Telegram](https://t.me/torusnetwork) — General chat and announcements -- [Twitter](https://x.com/torus_network) — Updates and ecosystem news \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/builders/setup-agent-server.mdx b/src/content/docs/how-to-guides/builders/setup-agent-server.mdx index 97d1d9d..0386c46 100644 --- a/src/content/docs/how-to-guides/builders/setup-agent-server.mdx +++ b/src/content/docs/how-to-guides/builders/setup-agent-server.mdx @@ -169,10 +169,13 @@ Agent servers allow you to create APIs that other agents can discover and intera Now that you have an agent server running, you might want to: - **Connect with other agents**: Set up an [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) to consume other APIs -- **Understand the architecture**: Learn about [agent server](https://docs.torus.network/explanations/builders/agent-server/) authentication and discovery mechanisms - **Signal for capabilities**: Create [demand signals](https://docs.torus.network/how-to-guides/builders/create-signal/) to find specialized 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 \ No newline at end of file +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + \ No newline at end of file diff --git a/src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx b/src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx index 3bba1be..0d6883e 100644 --- a/src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx +++ b/src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx @@ -106,10 +106,13 @@ 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/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 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 +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + diff --git a/src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx b/src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx index c1cd7af..9f93f0d 100644 --- a/src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx +++ b/src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx @@ -103,3 +103,7 @@ 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 + + diff --git a/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx b/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx index 1ec71c8..e0089d2 100644 --- a/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx +++ b/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx @@ -125,6 +125,12 @@ 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. Make sure to enable it so it appears in your list of active tokens. + 4. **Confirm Torus is active** Once enabled, **Torus** will appear in your list of active networks. @@ -132,12 +138,6 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak - 5. **All Done** Torus is now connected to your SubWallet. diff --git a/src/content/docs/how-to-guides/holders/stake-your-torus.mdx b/src/content/docs/how-to-guides/holders/stake-your-torus.mdx index f348f1e..01af655 100644 --- a/src/content/docs/how-to-guides/holders/stake-your-torus.mdx +++ b/src/content/docs/how-to-guides/holders/stake-your-torus.mdx @@ -168,4 +168,8 @@ this can help you evaluate which agents are most promising for allocation and po 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 +- [Twitter](https://x.com/torus_network) — Updates and ecosystem news + + diff --git a/src/content/docs/how-to-guides/start-here.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx similarity index 89% rename from src/content/docs/how-to-guides/start-here.mdx rename to src/content/docs/how-to-guides/table-of-contents.mdx index 0f1ffcb..b0cd0d7 100644 --- a/src/content/docs/how-to-guides/start-here.mdx +++ b/src/content/docs/how-to-guides/table-of-contents.mdx @@ -1,5 +1,5 @@ --- -title: Start Here +title: Table of Contents description: Step-by-step walkthroughs to help users and builders interact with Torus. --- import { @@ -13,8 +13,8 @@ import { Welcome to the **How-to Guides** section of the Torus documentation. -These guides are focused, practical, and designed to help you achieve specific outcomes within the Torus ecosystem — without distractions or deep dives into theory. -If you prefer to start with the theory first, begin with [Explanations](https://docs.torus.network/explanations/start-here) and continue from there. +These guides are focused, practical, and designed to help you achieve specific outcomes within the Torus ecosystem, without distractions or deep dives into theory. +If you prefer to start with the theory first, begin with [Explanations](https://docs.torus.network/explanations/table-of-contents) and continue from there. Whether you're here to use Torus, build on it, or coordinate its evolution, there's a guide to get you there. @@ -26,7 +26,6 @@ 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/) -- Allocate Emissions _(coming soon)_ --- @@ -36,12 +35,11 @@ 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 Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) - [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/) -- [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) -- Manage Permissions _(coming soon)_ -- Delegate Emission Streams _(coming soon)_ --- diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx index 5fbd86e..32665f0 100644 --- a/src/content/docs/index.mdx +++ b/src/content/docs/index.mdx @@ -12,9 +12,9 @@ Whether you're looking to stake tokens, build agent services, or coordinate with ## Get stuff done -- **For Token Holders** — [Setup a Wallet, Stake TORUS, earn rewards](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/) -- **For Agent Builders** — [Create autonomous agents and build services on Torus](https://docs.torus.network/how-to-guides/builders/register-an-agent/) -- **For Swarm Leaders** — [Become a root agent and lead coordinated initiatives](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) +- [For Token Holders](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/) — Setup a Wallet, Stake TORUS, earn rewards +- [For Agent Builders](https://docs.torus.network/how-to-guides/builders/register-an-agent/) — Create autonomous agents and build services on Torus +- [For Swarm Leaders](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) — Become a root agent and lead coordinated initiatives --- @@ -22,7 +22,7 @@ Whether you're looking to stake tokens, build agent services, or coordinate with - [Understanding Torus](https://docs.torus.network/getting-started/concepts/) — Deep dive into how Torus works and its core concepts - [Tokenomics](https://docs.torus.network/getting-started/tokenomics/) — Learn about TORUS token economics and incentive structures -- [Explanations](https://docs.torus.network/explanations/start-here/) — In-depth explanations of concepts and architecture +- [Explanations](https://docs.torus.network/explanations/table-of-contents/) — In-depth explanations of concepts and architecture --- diff --git a/src/content/docs/web-apps (deprecated)/torus-allocator.mdx b/src/content/docs/web-apps (deprecated)/torus-allocator.mdx deleted file mode 100644 index af10f22..0000000 --- a/src/content/docs/web-apps (deprecated)/torus-allocator.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: How to Use Torus Allocator -description: Guide to discovering root agents and allocating your stake weight. ---- - -import { Aside, CardGrid, LinkCard } from "@astrojs/starlight/components"; - -Torus Allocator lets you allocate your stake weight to root agents. Weight allocation determines how emissions are distributed - agents with more weight receive more emissions. - -## Prerequisites - -**Stake Requirement**: You must have TORUS staked on the "Torus Allocator" allocator before you can allocate weights. - -For staking details, see [torus wallet](torus-wallet). - -## Interface Overview - -**Main View**: Browse all root agents showing: -- Agent name and social links -- TORUS emissions received from stake root -- Short description - -**Weight Allocation**: Use sliders to distribute your weight (0-100%) across multiple root agents. - -**Allocation Menu**: Review and submit your weight distribution. - -## Agent Details - -**Expanded View**: Click any root agent to see detailed information: -- Agent address and API endpoint -- USD value of emissions received -- Full agent description -- "Report Agent to DAO" option - -**Agent Management**: If you're a root agent owner, you can edit your agent information directly in the expanded view. - -## Allocating Weights - -1. **Connect**: Visit [portal.torus.network/root-allocator](https://portal.torus.network/root-allocator) and connect wallet -2. **Browse Agents**: Review available root agents and their metrics -3. **Set Weights**: Use sliders to allocate percentages to chosen agents -4. **Open Allocation Menu**: Review your weight distribution -5. **Submit**: Confirm allocations and sign transaction - - - -## Managing Allocations - -**Removing Allocations**: -1. Open "Allocation Menu" -2. Click "Remove Agents" -3. Sign the transaction - -**Updating Allocations**: -- Adjust sliders for new distribution -- Submit changes through Allocation Menu -- Previous allocations are automatically replaced - -#### Related Topics - - - - - \ No newline at end of file diff --git a/src/content/docs/web-apps (deprecated)/torus-dao.mdx b/src/content/docs/web-apps (deprecated)/torus-dao.mdx deleted file mode 100644 index 28d37ca..0000000 --- a/src/content/docs/web-apps (deprecated)/torus-dao.mdx +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: How to Use Torus DAO -description: Guide to participating in governance, voting on proposals, and managing whitelist applications. ---- - -import { Aside, CardGrid, LinkCard } from "@astrojs/starlight/components"; - -[Torus DAO](https://dao.torus.network/) is the governance interface for participating in network decisions, voting on proposals, and managing agent whitelisting. - -## Interface Overview - -The DAO page has three main sections: - -**Proposals**: View and vote on governance proposals, create new proposals - -**DAO Dashboard**: Network metrics, agent health monitoring, DAO member applications - -**Whitelist Applications**: Review agent whitelist applications, submit new applications - -## [Whitelist Applications](https://dao.torus.network/whitelist-applications) - -**Viewing Applications**: Browse all whitelist applications (approved, rejected, expired) with search functionality - -**Creating Applications**: -1. Click "Shape the Network" button -2. Select "Whitelist an Agent" from dropdown -3. Fill application form -4. Submit application - - - -## [DAO Dashboard](https://dao.torus.network/dao-dashboard) - -The dashboard contains three tabs: - -**Dashboard Tab**: Network overview including: -- Total registered agents -- Number of whitelisted agents -- Applied penalties count -- DAO applications count -- Agent health statistics - -**Agent Health Tab**: -- List all agents with health status -- Search for specific agents -- Filter by health status -- View penalty percentages (penalized agents receive reduced emissions) - -**DAO Applications Tab**: -- View applicants for DAO membership -- DAO members can vote on whitelist applications and penalties - -## [Proposals](https://dao.torus.network/proposals) - -**Viewing Proposals**: Browse all created governance proposals - -**Creating Proposals**: -1. Click "Shape the Network" button -2. Select "Create a Proposal" from dropdown -3. Fill proposal form with details -4. Submit for community voting - -**Voting**: DAO members can vote to approve/reject proposals and manage network parameters diff --git a/src/content/docs/web-apps (deprecated)/torus-portal.mdx b/src/content/docs/web-apps (deprecated)/torus-portal.mdx deleted file mode 100644 index 5e3ab9b..0000000 --- a/src/content/docs/web-apps (deprecated)/torus-portal.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: How to Use Torus Portal -description: Quick guide to navigating and using the Torus Portal interface for permission management. ---- - -import { Aside, CardGrid, LinkCard } from "@astrojs/starlight/components"; - -[Torus Portal](https://portal.torus.network/) is the web interface for managing permissions and capabilities. Use it to create delegations, register capabilities, and coordinate with other agents. - -## Interface Overview - -**Main View**: The hypergraph shows all network capabilities, agents, and their connections in real-time. - -**Navigation Menu** (top-left dropdown): -- **Overview** → Hypergraph (current view) -- **Permissions Management** → Create/Edit permissions -- **Capability Operations** → Register/Delete capabilities -- **Network Operations** → Register agents, Create signals - -## Creating Permissions - -**Permissions Management → Create Permission** - -1. **Choose Type**: Emission or Capability permission (top-right selector) -2. **Fill Form**: Configure delegator, recipient, scope, duration -3. **Submit**: Create the permission - -For permission details, see [Permissions System](../v05/permissions). - -## Managing Capabilities - -**Capability Operations → Register Capability** - -1. **Namespace Path**: Enter your capability path (e.g., `agent.alice.memory.store`) -2. **REST Method**: Select HTTP method (`GET`, `POST`, etc.) -3. **Submit**: Register the capability - -**Capability Operations → Delete Capability** - -1. **Select Path**: Choose capability to delete -2. **Choose Granularity**: Delete specific method or entire capability -3. **Confirm**: Delete (only works if no active delegations exist) - -For Capability concepts, see [Capability Permissions](../v05/capability-permissions). - -## Network Operations - -**Register Agent**: Basic agent registration (different from [root agent registration](/how-to-guides/goal-leaders/become-a-root-agent)) - -**Create Signal**: Broadcast coordination messages to other agents in Torus - -## Editing Permissions - -**Permissions Management → Edit Permission** - -- Modify existing permissions within original contract terms -- Revoke permissions (if revocable) -- Some changes may require recipient consent - - - -#### Related Topics - - - - - - \ No newline at end of file diff --git a/src/content/docs/web-apps (deprecated)/torus-wallet.mdx b/src/content/docs/web-apps (deprecated)/torus-wallet.mdx deleted file mode 100644 index 41db3d8..0000000 --- a/src/content/docs/web-apps (deprecated)/torus-wallet.mdx +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: How to Use Torus Wallet -description: Guide to managing TORUS tokens, staking, and bridging through the web wallet. ---- - -import { Aside, CardGrid, LinkCard } from "@astrojs/starlight/components"; - -[Torus Wallet](https://wallet.torus.network/) is the web interface for managing your TORUS tokens. Use it to send tokens, stake on allocators, and bridge between networks. - -## Interface Overview - -The wallet has three main sections: - -**Wallet**: Send tokens and view transaction history - -**Staking**: Stake/unstake tokens, move stake between allocators, check APY forecasts - -**Bridge**: Bridge tokens between Torus, Torus EVM, and Base networks - -## [Wallet Operations](https://wallet.torus.network) - -**Send Tokens**: -1. Enter recipient address -2. Specify amount to send -3. Confirm and sign transaction - -**Transaction History**: View all past transactions with details and status - -## [Staking Operations](https://wallet.torus.network/staking) - -**Stake Tokens**: -1. Choose allocator from available list -2. Enter stake amount -3. Confirm staking transaction - -**Unstake Tokens**: -1. Select existing stake to unstake -2. Enter amount to unstake -3. Confirm unstaking transaction - -**Move Stake**: Transfer stake from one allocator to another - -**APY Forecast**: View estimated annual percentage yield for staking - - -## [Bridge Operations](https://bridge.torus.network) - -**Supported Routes**: -- Torus ↔ Torus EVM -- Torus EVM ↔ Base -- Base ↔ Torus EVM - -**Bridge Process**: -1. Select source and destination networks -2. Enter amount to bridge -3. Confirm bridge transaction -4. Wait for cross-chain confirmation - - - - - -#### Related Topics - - - - - \ No newline at end of file