You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/explanations/builders/demand-signaling.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Demand Signaling
3
-
description: Understanding how agents coordinate specialization through demand signals and emission delegation.
3
+
description: Understanding how agents coordinate specialization through demand signals and stream delegation.
4
4
---
5
5
6
6
import {
@@ -13,7 +13,7 @@ import {
13
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
14
14
their demand for specialized capabilities from other agents.
15
15
16
-
Standard agents are looking for opportunities to receive emission delegations by providing specialized capabilities.
16
+
Standard agents are looking for opportunities to receive stream delegations by providing specialized capabilities.
17
17
This means, you can define a problem and increase interest in solving it by proposing an allocation of your own emissions.
18
18
19
19
For example, if you have an agent specializing on finding predictions for the swarm memory and your accuracy and rewards suffer by failing to filter out irony,
Emission permissions are the core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of their incoming emission streams (token flows) to other agents with flexible control. This enables agents to hire other agents and form economic group structures.
12
+
Stream permissions are the core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of
13
+
their incoming emission streams (token flows) to other agents with flexible control.
14
+
This enables agents to hire other agents and form economic group structures.
13
15
14
-
## Emission Permission System
15
-
16
-
Emission permissions are core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of their incoming emission streams (token flows) to other agents with flexible control. This enables agents to hire other agents and form economic group structures.
16
+
## Stream Permission System
17
17
18
18
### Stream-Based Emission Model
19
19
20
-
The emission system preserves **stream identity** through delegation chains via unique `StreamId` identifiers. Each stream represents a distinct emission source (staking returns, delegation fees), enabling complete traceability of token flow from source to final recipients.
20
+
The emission system preserves **stream identity** through delegation chains via unique `StreamId` identifiers.
21
+
Each stream represents a distinct emission source (staking returns, delegation fees),
22
+
enabling complete traceability of token flow from source to final recipients.
21
23
22
24
### Allocation Mechanisms
23
25
24
-
Emission permissions support two distinct allocation paradigms:
26
+
Stream permissions support two distinct allocation paradigms:
25
27
26
28
#### Stream Allocations (Percentage-Based)
27
29
@@ -36,80 +38,45 @@ Stream allocations enable agents to delegate specific percentages of incoming em
36
38
37
39
#### Fixed Amount Allocations
38
40
39
-
Fixed amount allocations reserve specific token quantities from the delegator's account at permission creation:
40
-
41
-
```rust
42
-
FixedAmount(1000) // Reserve 1000 TORUS
43
-
```
41
+
Fixed amount allocations allow you to set aside specific token quantities for delegation:
44
42
45
43
**Fixed Amount Characteristics:**
46
-
-**Upfront Reservation**: Tokens are reserved using the Currency trait's reserve mechanism
44
+
-**Upfront Reservation**: Tokens are reserved from your account at permission creation
47
45
-**One-time Distribution**: Can only be executed once (manually or at a specific block)
48
-
-**Distribution Constraints**: Limited to `Manual`or `AtBlock` distribution controls
49
-
-**Safety Guarantee**: Uses the reserve/unreserve pattern to prevent double-spending
46
+
-**Distribution Constraints**: Limited to manual trigger or specific block execution
47
+
-**Safety Guarantee**: Reserved tokens cannot be double-spent or allocated elsewhere
50
48
51
49
### Distribution Control Mechanisms
52
50
53
51
The system provides four distribution control patterns that determine when and how delegated tokens are transferred:
54
52
55
-
```rust
56
-
pubenumDistributionControl {
57
-
Manual, // Recipient triggers distribution
58
-
Automatic(Balance), // Auto-trigger at threshold
59
-
AtBlock(BlockNumber), // Execute at specific block
60
-
Interval(BlockNumber), // Execute every N blocks
61
-
}
62
-
```
63
-
64
-
<Tabs>
65
-
<TabItemlabel="Manual Distribution">
53
+
##### Manual Distribution
66
54
**Manual Distribution** requires explicit execution by the recipient:
67
55
68
-
```rust
69
-
DistributionControl::Manual
70
-
```
71
-
72
56
-**Recipient Control**: Recipient determines when to claim accumulated tokens
73
57
-**Flexibility**: Allows strategic timing of token distribution
74
58
-**Gas Efficiency**: Batches multiple accumulations into single distribution
75
-
</TabItem>
76
59
77
-
<TabItemlabel="Automatic Distribution">
60
+
##### Automatic Distribution
78
61
**Automatic Distribution** triggers when accumulated amounts reach a threshold:
79
62
80
-
```rust
81
-
DistributionControl::Automatic(5000) // Auto-distribute at 5000 TORUS
82
-
```
83
-
84
63
-**Threshold-Based**: Automatically executes when accumulated amount exceeds threshold
85
64
-**Predictable**: Ensures regular distribution without manual intervention
86
65
-**Efficient**: Reduces the need for manual monitoring
87
-
</TabItem>
88
66
89
-
<TabItemlabel="Block-Based Distribution">
67
+
##### Block-Based Distribution
90
68
**AtBlock Distribution** executes once at a specific block:
91
69
92
-
```rust
93
-
DistributionControl::AtBlock(1_000_000) // Execute at block 1,000,000
94
-
```
95
-
96
70
-**Scheduled**: Executes at predetermined block height
97
71
-**One-time**: Single execution at specified block
98
72
-**Predictable**: Known execution timing
99
-
</TabItem>
100
73
101
-
<TabItemlabel="Interval Distribution">
74
+
##### Interval Distribution
102
75
**Interval Distribution** executes periodically at fixed intervals:
103
76
104
-
```rust
105
-
DistributionControl::Interval(10_800) // Execute every 10,800 blocks (~24 hours)
106
-
```
107
-
108
77
-**Periodic**: Regular execution at specified block intervals
109
78
-**Automated**: No manual intervention required
110
79
-**Consistent**: Predictable distribution schedule
0 commit comments