Skip to content

Commit e4e4649

Browse files
authored
Merge pull request #43 from renlabs-dev/dev
Update bridge documentation and portal URLs
2 parents b1b914a + 8123022 commit e4e4649

21 files changed

+196
-43
lines changed

astro.config.mjs

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,10 +100,9 @@ export default defineConfig({
100100
collapsed: true,
101101
items: [
102102
{ label: "Setup a Wallet", slug: "how-to-guides/holders/setup-a-wallet" },
103-
{ label: "Fast Bridge", slug: "how-to-guides/holders/fast-bridge" },
103+
{ label: "Bridge your tokens", slug: "how-to-guides/holders/bridge-your-torus" },
104104
{ label: "Stake your Torus", slug: "how-to-guides/holders/stake-your-torus" },
105105
{ label: "Vote on Proposals", slug: "how-to-guides/holders/vote-on-proposals" },
106-
{ label: "Standard Bridge", slug: "how-to-guides/holders/standard-bridge" },
107106
],
108107
},
109108
{
400 KB
Loading
269 KB
Loading

src/content/docs/development/web/querying-data.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: Learn how to query the stake weight between keys
66
import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
77

88
Our API allows you to retrieve information about the stake allocation between keys and agents.
9-
You can query this data by making a GET request to: `https://portal.torus.network/api/allocated-weight`.
9+
You can query this data by making a GET request to: `https://torus.network/api/allocated-weight`.
1010

1111
## API Response Format
1212

@@ -29,12 +29,12 @@ The API response has the following structure:
2929

3030
To filter the response for a specific allocating key, append the userKey query parameter to the API endpoint:
3131

32-
```portal.torus.network/api/allocated-weight?userKey=<SS58Address>```
32+
```https://torus.network/api/allocated-weight?userKey=<SS58Address>```
3333
- Filter by Agent Key
3434

3535
To filter the response for specific agents, append the agentKey query parameter to the API endpoint:
3636

37-
```portal.torus.network/api/allocated-weight?agentKey=<SS58Address>```
37+
```https://torus.network/api/allocated-weight?agentKey=<SS58Address>```
3838

3939

4040
<Aside type="note">

src/content/docs/explanations/builders/agent-registration.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The burn mechanism maintains network quality by creating economic barriers to sp
3838

3939
### Discovery and Capabilities
4040

41-
Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator tab](https://portal.torus.network/root-allocator).
41+
Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator tab](https://torus.network/root-allocator).
4242
They can participate in the permission system, create named capabilities for other agents to invoke, and engage in governance proposals.
4343
Agent metadata is stored off-chain via IPFS but referenced on-chain through content hashes.
4444

src/content/docs/explanations/builders/demand-signaling.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import {
1010
} from "@astrojs/starlight/components";
1111

1212

13-
The [Create Signal feature on the Portal](https://portal.torus.network/signals/create-signal) allows agents to express in a technical and economical way
13+
The [Create Signal feature on the Portal](https://torus.network/signals/create-signal) allows agents to express in a technical and economical way
1414
their demand for specialized capabilities from other agents.
1515

1616
Standard agents are looking for opportunities to receive stream delegations by providing specialized capabilities.

src/content/docs/explanations/system/capability-permissions.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -158,8 +158,8 @@ Permissions are delegated by the agent owner to specific users through Torus's p
158158

159159
**Creating Permissions via Web Portal:**
160160

161-
- **Create Namespace Paths**: Use [https://portal.torus.network/register-capability](https://portal.torus.network/register-capability) to register namespace paths on the blockchain
162-
- **Delegate Permissions**: Use [https://portal.torus.network/create-permission](https://portal.torus.network/create-permission) to delegate capability permissions to specific users
161+
- **Create Namespace Paths**: Use [https://torus.network/register-capability](https://torus.network/register-capability) to register namespace paths on the blockchain
162+
- **Delegate Permissions**: Use [https://torus.network/create-permission](https://torus.network/create-permission) to delegate capability permissions to specific users
163163

164164
## Configuration Options
165165

src/content/docs/how-to-guides/builders/create-signal.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,8 @@ Signaling demand allows you to delegate part of your emissions to agents who can
4444

4545
<Steps>
4646

47-
1. **Visit the [Create Signal](https://portal.torus.network/signals/create-signal) Tab**
48-
You can find it in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
47+
1. **Visit the [Create Signal](https://torus.network/signals/create-signal) Tab**
48+
You can find it in the left-hand navigation bar of the [Torus Portal](https://torus.network/portal).
4949

5050

5151
2. **Connect your Torus wallet**
@@ -94,16 +94,16 @@ Signaling demand allows you to delegate part of your emissions to agents who can
9494
Double-check your details and <RedText variant="light">publish to make it discoverable</RedText>.
9595

9696
5. **All Done**
97-
Your demand signal is now visible in the Torus graph and [signal marketplace for other agents](https://portal.torus.network/signals/signal-list) to discover.
97+
Your demand signal is now visible in the Torus graph and [signal marketplace for other agents](https://torus.network/signals/signal-list) to discover.
9898

9999
</Steps>
100100

101101
## What's Next?
102102

103103
Now that you've created a signal, you might want to:
104104

105-
- **Manage your signals**: Mark as fulfilled or delete them from the [Signal List](https://portal.torus.network/signals/signal-list).
106-
- **Browse the Hypergraph**: Explore agents, capabilities, and signals in the [Hypergraph](https://portal.torus.network/).
105+
- **Manage your signals**: Mark as fulfilled or delete them from the [Signal List](https://torus.network/signals/signal-list).
106+
- **Browse the Hypergraph**: Explore agents, capabilities, and signals in the [Hypergraph](https://torus.network/portal).
107107
- **Build your own capabilities**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide services
108108

109109
Connect with the community:

src/content/docs/how-to-guides/builders/manage-capabilities.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
5050

5151
<Steps>
5252

53-
1. **Visit the [Create Capability Tab in the Torus Portal](https://portal.torus.network/capabilities/create-capability)**
53+
1. **Visit the [Create Capability Tab in the Torus Portal](https://torus.network/capabilities/create-capability)**
5454
Navigate to the **Capabilities** section in the Torus Portal.
5555

5656
2. **Connect your Torus Wallet**
@@ -114,7 +114,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
114114

115115
<Steps>
116116

117-
1. **Visit the [Delete Capability Tab in the Torus Portal](https://portal.torus.network/capabilities/delete-capability)**
117+
1. **Visit the [Delete Capability Tab in the Torus Portal](https://torus.network/capabilities/delete-capability)**
118118
Navigate to the **Capabilities** section in the Portal.
119119

120120
2. **Connect your Torus Wallet**

src/content/docs/how-to-guides/builders/manage-your-agent.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ and ensures your agent represents your current capabilities and offerings.
5656
## Edit your Agent Information
5757

5858
<Steps>
59-
1. **Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
59+
1. **Visit the [Manage Agent Tab in the Torus Portal](https://torus.network/network-operations/manage-agent)**
6060
<RedText variant="light">Ensure you're connected with the agent wallet</RedText> that owns the agent you want to manage.
6161

6262
<ClickableImage src={manageAgentTab} alt="Click on Manage Agent Tab" />
@@ -81,15 +81,15 @@ and ensures your agent represents your current capabilities and offerings.
8181
Once confirmed, a notification will appear to indicate that your allocation was successful.
8282

8383
4. **All Done**
84-
You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
84+
You can now see your updated information in the [Allocator Tab](https://torus.network/root-allocator).
8585

8686
</Steps>
8787

8888
## De-register your Agent
8989

9090
<Steps>
9191

92-
1. **Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
92+
1. **Visit the [Manage Agent Tab in the Torus Portal](https://torus.network/network-operations/manage-agent)**
9393
<RedText variant="light">Ensure you're connected with the agent wallet</RedText> that owns the agent you want to manage.
9494

9595
2. **Click Deregister Agent**

0 commit comments

Comments
 (0)