/help
Shows the full command list. Works without approval — anyone can run it.
Welcome to Confetti
This is your reference for everything you need as a user — how to set up your Telegram bots, get approved, deploy sites, and configure them. Built to be short and useful.
Setting up your Telegram group
Confetti uses two bots working together. Both must be in the same Telegram group before you can use any commands.
-
1
Create a new Telegram group
Open Telegram → New Group → name it whatever you like (e.g.
My Confetti). -
2
Add
@confettipartybotThis is the bot you'll talk to — it handles all commands like
/launch,/host,/sites.When added alone, it'll ask you to add the second bot.
-
3
Add
@confettimanagerbotThis is the silent partner — it keeps the owners in the loop on what you do. It never takes commands from you, but it must be in the group.
As soon as both bots are present, you'll automatically see the command list.
Why two bots?
It's a safety net. The Manager Bot ensures the owners are always aware of what's happening,
which keeps payouts honest and removes any "did this deploy?" ambiguity.
Getting approved
Before you can run any command (other than /help), an owner has to approve your
Telegram username and set your commission rate.
-
1
Make sure you have a Telegram username
Telegram → Settings → Username. If you don't have one, set one now — approval works by username.
-
2
Reach out to
@CarnivalSupportSend your Telegram
@username. The owners will agree on commission terms with you. -
3
Wait for confirmation
Once approved, run
/launchin your Confetti group to set up your payout wallet and start hosting.
Not approved yet?
If you run a command before approval, the bot will reply with
"Carnival access required. Reach out to @CarnivalSupport to get your ticket."
That's the signal to contact us first.
Confetti Party Bot — all commands
Every command lives in @confettipartybot. Run them in your group (with both
bots present) or in a private chat with the bot.
/launch
One-time, run this first. Asks for your Solana payout wallet, confirms it, and optionally lets you build your starter config.
Can only be run once. To change your wallet later, use /wallet.
/wallet
View your current payout wallet, or update it. Owners are notified of any changes.
/config
Opens the live configurator pre-loaded with the team standard. Tweak modal style,
brand name, button text, etc., then download config.json and use it during
/host.
/host
Deploy a new site. The bot walks you through:
- Enter the domain
- Upload your
config.json - Upload the website .zip (Telegram up to 20 MB, or browser drag-drop up to 50 MB)
- Point the domain's nameservers to Cloudflare (the bot tells you which two)
- Reply
OKwhen nameservers are updated — site goes live within ~1 minute
An intermediate wallet is auto-generated per site. You'll only see its public address — the private key goes straight to the owners.
/sites
Lists every site you've deployed. Tap one to manage it:
- 🎢 Update files — re-upload the website zip and redeploy
- 🎭 Reconfigure — edit the live config in the configurator
- 🍭 Delete site — tear down everything (Cloudflare zone, project, stored zip, bot tracking)
/update
Quick path to update either the config, the files, or both on an existing site. Pick the site, pick what to change — the bot walks the rest.
/standard
Shows the team's standard config in a read-only view. Useful as a reference when building your own config.
/cancel
Abort whatever multi-step flow you're currently in (e.g., halfway through /host).
Always works.
Payouts
Commission payouts are calculated and distributed automatically based on the rate set when you were approved. Your registered payout wallet receives them.
To verify or update your payout wallet, run /wallet in the bot.
Configurator options
Every field that's visible in the configurator.
Branding
- Modal title
- The headline shown at the top of the wallet modal (default: Connect Wallet).
- Trigger button text
- Bot will bind to any button or link on your site whose text matches this string. Useful when your page has a "Connect Wallet" or "Recover SOL" CTA.
- Apply to all buttons
- When on, every button/link on the page opens the modal (skips form submits and real navigation links). Convenient for landing pages with multiple CTAs.
- Open modal when user clicks anywhere on the page
- Most aggressive option. A single click anywhere on the page opens the modal. Form fields and the modal itself are still skipped so users can type normally.
Modal style
- Style
- 23 visual presets to choose from — pure dark, gradients in red/blue/purple/orange/teal, light theme, plus carnival-inspired duotones (Black & pink, Bronze, Rosé gold, Silver, etc).
State texts
- Loading
- Shown while the widget is preparing the wallet prompt.
- Success
- Shown after a successful operation.
- Failure
- Shown when something goes wrong (e.g., user rejects the prompt).
Transaction
- SOL fee reserve
- Lamports left in the user's wallet to cover the on-chain transaction fee. Default is fine for most cases.
- Assets per wallet prompt
- Caps how many SPL token transfers get bundled per wallet signing prompt. Lower = more prompts but simpler review; higher = fewer prompts but a longer asset list to review.
Live preview.
Every change you make in the configurator updates the live preview on the right immediately.
Use it to verify your styling before downloading and shipping.