rdk publish:* and rdk index:*
Add content to the network directly, outside the vault indexing flow.
Two commands for adding content to the network without going through the vault file pipeline. Both accept raw text and create a single chunk.
rdk index:chunk
rdk index:chunk "<text>" --title "<title>"Index text as a PRIVATE encrypted chunk on the network. Same effect as if the text were a file in your local vault that just got indexed. Visible only to you and team members with vault access.
Example:
rdk index:chunk "Our API rate limit is 1,000 req/min per key." --title "api-rate-limits"rdk publish:chunk
rdk publish:chunk "<text>" --title "<title>"Publish text as a PUBLIC chunk on the network. Plaintext, retrievable by any node, earns USDC tips when retrieved.
Example:
rdk publish:chunk "GDPR Article 17 grants the right to erasure..." --title "gdpr-article-17"Public chunks are immutable. Other nodes may cache them after retrieval. Cannot be made private again.
Choosing between them
| Command | Visibility | Encrypted | Earns tips | Reversible |
|---|---|---|---|---|
index:chunk | PRIVATE | Yes | No | Yes — delete removes it |
publish:chunk | PUBLIC | No | Yes | No — immutable |