Incident Response
This is Orion's public incident response plan. It tells users, managers, and researchers where to look, what to do, and what we will (and will not) say while an incident is active.
It is not a complete internal playbook. It does not promise recovery timing, restoration of funds, or compensation. Binding limitations are in the Terms of Service.
What counts as an incident
An incident is any situation that may lead to a considerable loss of funds for users, the protocol, or contracts deployed by Orion. Examples include:
- A bug or exploit in vault, orchestrator, adapter, or related protocol code
- A bug or exploit in an underlying protocol that Orion vaults or adapters rely on
- Loss or compromise of a privileged key (for example Admin, Guardian, or a vault manager/strategist key)
- A credible vulnerability report that requires emergency action
- An active exploit in progress
Routine app bugs, wallet support issues, and strategy underperformance are not incidents. Use Troubleshooting or community channels for those.
Official channels
During an incident, treat only the following as official. Ignore direct messages, unofficial Telegram/Discord accounts, and lookalike websites.
| Channel | Role |
|---|---|
X / Twitter (@OrionFinanceAI) | Primary public status updates |
| Discord | Community updates from Orion-operated accounts |
| Telegram | Same, from the official Orion channel |
| Company-level notices when used | |
| App (app.orionfinance.ai) | In-app notices when we can show them safely |
| Docs (docs.orionfinance.ai) | Standing security pages; incident notes when published |
| security@orionfinance.ai | Private reports and researcher contact |
The official app URL is app.orionfinance.ai. Bookmark it. Do not follow links from DMs or search ads.
If official channels disagree, prefer a later post on X from @OrionFinanceAI and the app URL above.
What Users and Managers Should Do
- Watch the official channels above. Do not rely on screenshots or forwarded messages.
- Follow any interaction guidance we publish (for example: do not deposit, do not sign unexpected transactions, wait for settlement).
- Do not sign transactions you do not understand. "Support" accounts that ask you to "validate," "sync," or "claim" are not Orion.
- Do not discuss suspected exploits in public if doing so could help an attacker. Email security@orionfinance.ai instead.
- Verify the URL before connecting a wallet. See User Security.
If the protocol is paused, epoch execution (rebalancing and settlement) stops until Admin unpauses. Pending deposits or redemptions may remain pending. Pause is a protective measure.
How we Respond
The objective is to limit loss of funds, then to inform users as soon as we can do so without making the situation worse.
| Phase | What you can expect |
|---|---|
| Assess | We confirm the report, identify affected surfaces, and decide whether funds are at risk. Early information may be incomplete. |
| Contain | We may pause the Liquidity Orchestrator (Guardian or Admin), restrict the app, or take other onchain steps already described in Roles and Permissions. We will not publish a live exploit write-up while funds remain at risk. |
| Communicate | We post on official channels: that we are aware, whether users should stop interacting, and whether pause or similar controls are in use. First notices can be short. |
| Remediate | We work a fix or operational path. Admin, not Guardian, unpauses. Timing is not guaranteed. |
| Disclose | After it is safe, we publish a summary of what happened, what we did, and what changes as a result. We may withhold exploit details that would help copycats. |
We may skip or compress phases when speed matters. We may also stay quiet for a short period if a public post would increase harm (for example, while a pause transaction is still being signed).
Emergency Controls
These onchain controls are already documented.
- Guardian or Admin may call
LiquidityOrchestrator.pause(), which stops epoch upkeep. - Admin only may unpause.
- Guardian may also retune the emergency parameters listed in Roles and Permissions. Guardian cannot unpause, upgrade contracts, or move protocol admin.
Onchain pause does not by itself disable every wallet interaction with every contract. Any extra app or operational restrictions will be stated on official channels.
After an Incident
When it is safe, we intend to publish a public summary: timeline at a high level, user impact as we understand it, containment steps, and follow-up work. That summary is informational. It is not an admission of liability and does not create an entitlement to compensation.
To report a vulnerability, see Security.