Rules, Limits & FAQs
This section covers platform rules, known limitations, and answers to common questions. Read this to avoid avoidable mistakes.
Rules
OctaBot only responds to public tweets or replies
Commands must follow the exact supported format
Only one deployment command per tweet is processed
Misformatted or ambiguous commands are ignored
OctaBot does not respond to DMs
OctaBot does not manually intervene or correct commands. If it fails, fix the format and repost.
Limits
Only one token can be deployed per command
Token names and symbols must meet platform constraints
Multiple token transfers in a single command are not supported
Transfers cannot be edited or reversed once executed
Rate limits may apply during high network or platform load
These limits exist to keep deployments fast, predictable, and abuse-resistant.
FAQs
Q: Do I need a wallet to use OctaBot? No. OctaBot abstracts the deployment process. No wallet connection is required from the user.
Q: How long does deployment take? Typically a few seconds after the tweet is posted.
Q: What happens if my command fails? Nothing is deployed. Simply fix the format and post again.
Q: Can I delete the tweet after deployment? Yes. Deleting the tweet does not affect the deployed token.
Q: Can I redeploy the same name or symbol? That depends on platform availability. OctaBot does not override existing tokens.
Q: Is deployment reversible? No. Token deployment is permanent once executed.
Last updated