Getting started with SixStar for projects

Your first 30 minutes, from a new account to a tested alert. Everything here is read only: you never send funds from your project, connect a wallet, or share a key.

1. Create your account and choose a plan

1. Open For projects and choose a plan.
2. Under "Create your team account", enter your work email, a password of at least 12 characters, and your project or team name.
3. On "Save your recovery code", press "Copy the code" and keep it somewhere safe. It is the only way back in if you forget your password, and it is shown once.
4. Choose your plan and period. You pay once, upfront, and nothing renews by itself.
5. Fill in "Who the invoice is for".
6. On "Send exactly this amount", pay from any wallet. The page shows the token contract for each network and token, so you can check it in your wallet first. You pay the network fee.

When the payment is seen, your period starts and you land on your team's Account page.

If you were invited, open the invite link instead. Your free months start as soon as you create the account, and no payment is needed.

2. Tell us where alerts should go (5 minutes)

Do this first, so the next steps have somewhere to send their alerts.

On the Account page, under alert channels, add at least one:

• Slack: a Slack incoming webhook URL.
• PagerDuty: an integration key. Urgent alerts are sent as critical, the rest as info.
• Your own webhook: an HTTPS address you run. Copy the signing secret when it is shown, because it is shown only once. The API and webhooks page shows how to check each message came from us.
• Email: an address. It gets nothing until you confirm it from the email we send.

For each channel choose "All alerts" or "Urgent only". Then send a test message and check it arrived. A channel you have not tested is a channel you do not know works.

3. Add what you want watched (10 minutes)

Start with the few things that would hurt most if they changed without you knowing.

1. Security watch. Add your main contracts and their networks, and name the admin wallets that are allowed to change them. You are alerted when an owner, admin, role, upgrade or pause changes.
2. Address book. Name your addresses and give each a role, such as treasury, signer or deployer. Alerts then print the name instead of a long address, which matters at 3 a.m.
3. Safe queue. Add your Safes to get an alert for each new pending transaction, so nothing is proposed behind your back.
4. Takeover Watch. Add a wallet or Safe. If it, one of its signers, or your contract's owner starts running someone else's code (EIP-7702), you get an urgent alert.
5. Limits. Set how much may leave a wallet or contract before you are alerted, and a minimum balance where it matters.
6. Other networks. For Bitcoin and the XRP Ledger, add an address or account to hear when money leaves it. For Solana, watch a program, a token mint, a Squads multisig or a council key.

4. Set how loud each alert is (5 minutes)

Each kind of alert is Urgent or Notice. Leave the defaults, then raise the ones that would mean an emergency for your project. Use "Urgent only" channels, such as PagerDuty, for the alerts that should wake someone up.

After a drain alert, Chain Alarm checks every network your team watches on every cycle for an hour, and every alert in that hour is urgent.

5. Prepare for a bad day, before it happens (10 minutes)

These take minutes now and save the minutes that matter later.

• Emergency actions. Set up in advance what you would do: pause a contract, revoke a role or an allowance, cancel a queued Safe transaction, or move a Safe's funds to an address you name. When an alert fires, it links to the action, already built and checked against the chain. We prepare it. Your own signers decide and sign.
• Issuer request pack. Know where it is. If stablecoins are taken, you open a pack and get each transfer out, where the tokens went, and the issuer to ask. You send it.
• Read the "When an alert fires" playbook with whoever is on call.

6. Optional, when you are ready

• Team identity sources. Connect Okta, Zoom, Google Workspace, GitHub, Cloudflare, Telegram or a Discord server to hear about sign-in and admin changes.
• Your website, code and channels. Add your domain to watch its pages and lookalike domains.
• Open approvals. See which spenders can move a wallet's tokens.
• Governance. Watch a governor's proposals and settings.
• Bot heartbeat. Give each bot a check-in URL and hear when one goes quiet.
• Your own rules, from your repository. Keep a rules file in Git and deploy it with an API key. See the API and webhooks page.

Common questions

Can SixStar move our funds or sign anything? No. We read public chains. Emergency actions are prepared for your own Safe, and your own signers decide whether to sign.

What happens if our Slack or webhook is down? The alert waits and is tried again, about every 15 minutes at most, until it is delivered. After an hour of failures your other channels are told.

What happens when our period ends? Watching stops on the day it ends. Your account and past reports stay open to you for a month after that. Nothing renews by itself.

Who do we contact? contact@sixstarlab.com. Never send us a password, key, seed phrase or one-time code.