-
Notifications
You must be signed in to change notification settings - Fork 0
Dev #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev #11
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| --- | ||
| title: How to be a builder on Torus | ||
| description: A practical guide to getting involved in the Torus Network, from permissions to integration. | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| Participating in the Torus Network means becoming an **agent** that contributes value through **signals** and **integrations**. This guide walks you through each step — from setting up your wallet to delivering a fully working agent. | ||
|
|
||
| --- | ||
|
|
||
| ## 🧭 Step-by-Step Path | ||
|
|
||
| ### 1. Set up your wallet | ||
|
|
||
| Every agent begins with a wallet that can sign transactions. | ||
|
|
||
| 👉 [How to create a wallet](/how-to-guides/set-up-wallet) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Verification agent 🧩 Analysis chainVerify that linked guides exist. Many of the linked how-to guides appear to reference pages that don't exist yet. This could create a poor user experience with broken links. Also applies to: 26-27, 35-36, 44-45, 53-54, 62-62, 70-71, 84-85 🏁 Script executed: #!/bin/bash
# Check if the linked guide files exist
guides=(
"how-to-guides/set-up-wallet"
"how-to-guides/register-agent"
"how-to-guides/apply-to-be-whitelisted"
"how-to-guides/create-permission"
"how-to-guides/edit-permission"
"how-to-guides/create-capabilities"
"how-to-guides/delete-capabilities"
"how-to-guides/create-signal"
"how-to-guides/receive-emissions"
"how-to-guides/agent-api"
"how-to-guides/host-agent"
"how-to-guides/connect-to-chain"
"how-to-guides/respond-to-signal"
)
for guide in "${guides[@]}"; do
if [ -f "src/content/docs/$guide.mdx" ] || [ -f "src/content/docs/$guide.md" ]; then
echo "✓ $guide exists"
else
echo "✗ $guide not found"
fi
doneLength of output: 3711 Missing linked how-to guide pages
Please add the corresponding 🤖 Prompt for AI Agents |
||
|
|
||
| --- | ||
|
|
||
| ### 2. Register your agent | ||
|
|
||
| To act on-chain, your wallet must be registered or whitelisted. | ||
|
|
||
| 👉 [How to register an agent](/how-to-guides/register-agent) | ||
| 👉 [How to apply to be whitelisted](/how-to-guides/apply-to-be-whitelisted) | ||
|
|
||
| --- | ||
|
|
||
| ### 3. Create a permission namespace | ||
|
|
||
| Define your agent’s capabilities by creating a permission. | ||
|
|
||
| 👉 [How to create a permission](/how-to-guides/create-permission) | ||
| 👉 [How to edit a permission](/how-to-guides/edit-permission) | ||
|
|
||
| --- | ||
|
|
||
| ### 4. Grant or manage capabilities | ||
|
|
||
| Give specific agents (including yourself) the ability to act. | ||
|
|
||
| 👉 [How to create capabilities](/how-to-guides/create-capabilities) | ||
| 👉 [How to delete capabilities](/how-to-guides/delete-capabilities) | ||
|
|
||
| --- | ||
|
|
||
| ### 5. Create a signal | ||
|
|
||
| Agents produce **signals** to announce work, ideas, or needs. To emit signals, you must have emissions permissions. | ||
|
|
||
| 👉 [How to create a signal](/how-to-guides/create-signal) | ||
| 👉 [How to receive emissions](/how-to-guides/receive-emissions) | ||
|
|
||
| --- | ||
|
|
||
| ### 6. Interact with the API | ||
|
|
||
| To read/write from the network, learn how to use the API. | ||
|
|
||
| 👉 [How to interact with the Agent API](/how-to-guides/agent-api) | ||
|
|
||
| --- | ||
|
|
||
| ### 7. Integrate it all | ||
|
|
||
| Bring everything together into a working, running agent. | ||
|
|
||
| 👉 [How to host an agent](/how-to-guides/host-agent) | ||
| 👉 [How to connect to the chain](/how-to-guides/connect-to-chain) | ||
|
|
||
| --- | ||
|
|
||
| ## 🧑💻 Participating in Signals (as a developer) | ||
|
|
||
| Once a signal is live, others can collaborate: | ||
|
|
||
| 1. **Find** a relevant signal | ||
| 2. **Talk** to the issuer | ||
| 3. **Develop** based on the signal’s namespace + permissions | ||
| 4. **Deliver** your work | ||
|
|
||
| 👉 [How to find and respond to a signal](/how-to-guides/respond-to-signal) | ||
| 👉 [How to host an agent](/how-to-guides/host-agent) | ||
|
|
||
| --- | ||
|
|
||
| ## 🔄 Ready to start? | ||
|
|
||
| Start from the top or jump into the step you need. Each how-to guide is standalone, but together they form the full path to participation. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| --- | ||
| title: How to be a builder on Torus | ||
| description: A practical guide to getting involved in the Torus Network, from permissions to integration. | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| Participating in the Torus Network means becoming an **agent** that contributes value through **signals** and **integrations**. This guide walks you through each step — from setting up your wallet to delivering a fully working agent. | ||
|
|
||
| --- | ||
|
|
||
| ## 🧭 Step-by-Step Path | ||
|
|
||
| ### 1. Set up your wallet | ||
|
|
||
| Every agent begins with a wallet that can sign transactions. | ||
|
|
||
| 👉 [How to create a wallet](/how-to-guides/set-up-wallet) | ||
|
|
||
| --- | ||
|
|
||
| ### 2. Register your agent | ||
|
|
||
| To act on-chain, your wallet must be registered or whitelisted. | ||
|
|
||
| 👉 [How to register an agent](/how-to-guides/register-agent) | ||
| 👉 [How to apply to be whitelisted](/how-to-guides/apply-to-be-whitelisted) | ||
|
|
||
| --- | ||
|
|
||
| ### 3. Create a permission namespace | ||
|
|
||
| Define your agent’s capabilities by creating a permission. | ||
|
|
||
| 👉 [How to create a permission](/how-to-guides/create-permission) | ||
| 👉 [How to edit a permission](/how-to-guides/edit-permission) | ||
|
|
||
| --- | ||
|
|
||
| ### 4. Grant or manage capabilities | ||
|
|
||
| Give specific agents (including yourself) the ability to act. | ||
|
|
||
| 👉 [How to create capabilities](/how-to-guides/create-capabilities) | ||
| 👉 [How to delete capabilities](/how-to-guides/delete-capabilities) | ||
|
|
||
| --- | ||
|
|
||
| ### 5. Create a signal | ||
|
|
||
| Agents produce **signals** to announce work, ideas, or needs. To emit signals, you must have emissions permissions. | ||
|
|
||
| 👉 [How to create a signal](/how-to-guides/create-signal) | ||
| 👉 [How to receive emissions](/how-to-guides/receive-emissions) | ||
|
|
||
| --- | ||
|
|
||
| ### 6. Interact with the API | ||
|
|
||
| To read/write from the network, learn how to use the API. | ||
|
|
||
| 👉 [How to interact with the Agent API](/how-to-guides/agent-api) | ||
|
|
||
| --- | ||
|
|
||
| ### 7. Integrate it all | ||
|
|
||
| Bring everything together into a working, running agent. | ||
|
|
||
| 👉 [How to host an agent](/how-to-guides/host-agent) | ||
| 👉 [How to connect to the chain](/how-to-guides/connect-to-chain) | ||
|
|
||
| --- | ||
|
|
||
| ## 🧑💻 Participating in Signals (as a developer) | ||
|
|
||
| Once a signal is live, others can collaborate: | ||
|
|
||
| 1. **Find** a relevant signal | ||
| 2. **Talk** to the issuer | ||
| 3. **Develop** based on the signal’s namespace + permissions | ||
| 4. **Deliver** your work | ||
|
|
||
| 👉 [How to find and respond to a signal](/how-to-guides/respond-to-signal) | ||
| 👉 [How to host an agent](/how-to-guides/host-agent) | ||
|
|
||
| --- | ||
|
|
||
| ## 🔄 Ready to start? | ||
|
|
||
| Start from the top or jump into the step you need. Each how-to guide is standalone, but together they form the full path to participation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify the package name with double
@@prefix.The package name
@@torus-network/sdkuses an unusual double@@prefix, which is not standard for npm packages. Standard scoped packages use a single@prefix (e.g.,@torus-network/sdk). This could cause installation failures.Please verify if this is the correct package name or if it should be
@torus-network/sdkinstead.Also applies to: 37-37, 446-446
🏁 Script executed:
Length of output: 4723
Correct npm package name prefix
The npm package
@@torus-network/sdkis invalid (npm scoped packages use a single@). The correct package name on the registry is@torus-network/sdk. Please update all occurrences:• src/content/docs/agents/server-setup.mdx: lines 31, 37, 446
Replace:
🤖 Prompt for AI Agents