The risks, in plain Australian English
Automated tools change how trading is done, not what trading is. This page sets out the ten risk categories every Southern Ledger user should understand before depositing funds. Read it once before you start and once after your first month — different sentences will matter the second time.
1. Introduction and general warning
Trading cryptoassets and other financial instruments involves substantial risk. Prices can move violently in minutes, overnight, or over a weekend when no support desk is open. You can lose some or all of the money you deposit, and automated execution can make losses accrue faster than manual trading would, because the system follows its rules without pausing to worry.
Nothing on this platform is a savings product. There is no capital guarantee, no deposit insurance for trading balances, and no mechanism that converts a losing strategy into a winning one over time. The balanced view is that automation changes the workload of trading, not its physics.
This disclosure is not fine print to skip; it is the operating manual's most important chapter. Each section below explains a category of risk and, where one exists, gives a practical step that reduces — never removes — it.
2. Market risk: volatility and sharp price moves
Market risk is the plainest one: the price of what you hold moves against you. Cryptoassets in particular can fall by double-digit percentages in a day, and share indices can gap down between sessions. A position that was comfortably profitable at breakfast can be materially negative by dinner, and leveraged or highly volatile instruments amplify both directions.
Practical step: decide the maximum drawdown you are willing to sit through before you set a strategy, and encode it as a stop level rather than an intention. Intentions fail at 2 am; stops do not.
3. Liquidity risk: execution and slippage
Liquidity risk appears when there is not enough trading interest on the other side of your order. In thin markets, the price you see is not always the price you get: orders fill partially, or fill at levels away from the quoted price (slippage). During news events, spreads — the gap between buy and sell prices — widen suddenly, so the same trade costs more to enter and exits at worse levels.
Practical step: prefer instruments and venues with deep order books for any strategy that trades quickly, and review your filled orders against their intended prices in the ledger view. A pattern of consistent slippage is information about where that strategy belongs.
4. APIs and integrations: connection and key security
The automation runs through API connections to liquidity venues, and those connections can fail precisely when markets are most interesting: rate limits under load, maintenance windows, or an interrupted link between the platform and an exchange. When that happens, a strategy may miss an entry, hold a position it intended to exit, or trade on stale prices until the connection restores.
API keys themselves are a risk category: a key with more permission than its job requires is a liability. Our defaults are read-only and trading scopes, with withdrawal scope issued only on explicit request (see the Security page, section 7).
Practical step: audit the API keys connected to your account each quarter, revoke anything unused, and check the connection status panel after any period of unusual market action.
5. Counterparty and custody risk
Funds and positions sit with third parties: liquidity venues, payment processors and banking partners. If one of them suffers an outage, an insolvency event or a security breach, your assets can be frozen or affected through no fault of the strategy or the platform. Crypto venues in particular vary widely in governance, proof-of-reserves practices and jurisdictional protections.
Practical step: keep your trading balance sized as working capital, not as your savings. Funds you cannot afford to have temporarily inaccessible belong in your bank account, where they can neither be lost to markets nor trapped by an intermediary.
6. Operational risk: software, infrastructure and connectivity
Software has defects, infrastructure has outages, and networks drop packets at inconvenient moments. A platform bug can mis-render a report; a server restart can delay an order; your own home internet can fail during the one hour that mattered. Scheduled maintenance is announced, but emergency maintenance is by definition not.
Practical step: before assuming a bug, check the status panel and your own connection. Keep your manager's contact details somewhere offline, and know in advance which actions (closing a position, pausing a strategy) you would take first if the platform were briefly unreachable.
7. Cybersecurity and phishing: protecting your account
The most common compromise path is not a break-in; it is an invitation. Phishing sites copy the login page, fraudulent "support agents" ask for one-time codes, and malware records what you type. From there, an attacker does not need to beat the platform's security — you handed them the session. Account takeover of this kind usually ends in a rushed withdrawal to a destination you have never used.
Practical step: bookmark the sign-in page, enable 2FA, and treat any message combining urgency and secrecy as hostile. The full toolkit — session revocation, login alerts, withdrawal freezes on suspicious activity — is described on the Security page.
8. Models and automation: the limits of algorithms
The analysis engine looks for repeating micro-trends and probabilities, and probability has an uncomfortable property: it is right only often enough to matter, not always. Models are trained on history, and history — including a back-test — does not bind the future. A pattern that paid for a year can stop working in a fortnight, and an automated system will keep following its rules while that happens, which is why strategy monitoring is part of the product rather than an optional extra.
Be direct with yourself about what automation is not: it is not a guarantee of results, it is not immune to drawdowns, and it does not know that this particular trade was supposed to be the safe one. The platform's volatility controls can pause trading in extreme conditions, but that is a brake, not a shield.
Practical step: review each strategy's actual performance against its expectation monthly, and treat a widening gap as a reason to reduce size or stop, not as a reason to hope louder.
9. Service availability
The platform undergoes maintenance, and outages happen despite redundancy: upgrades overrun, providers fail, extreme market traffic exceeds capacity. During an outage you may be unable to view positions, adjust settings or request a withdrawal until service returns. Availability risk compounds with market risk when the outage coincides with violent price action.
Practical step: strategies with hard stops set in advance behave better through an outage than positions awaiting a manual decision. If being unreachable for an hour would be intolerable, size your exposure so it is not.
10. Before you start: a checklist, not a slogan
Understand the strategy you are switching on — what it trades, how it sizes positions, and what its worst historical drawdown looked like, not just its best month. Write down the loss level at which you will stop; a number decided in advance is a plan, and a number decided during a drawdown is a negotiation you will lose.
Protect the account itself: 2FA on, sessions reviewed, API keys minimal. Then keep watching what the automation does — weekly at first, monthly once it is boring. Boring is the goal; surprises belong at the cinema.
Finally, only deposit money whose total loss would not change your life. If a loss of the full amount would threaten your home, your family or your sleep, the correct position size is zero. Questions about any of this go to [email protected] — we would rather answer a basic question early than a hard one late.