How twoke copy trading works

twoke is a non-custodial copy-trading platform for crypto perpetual futures. It runs three automated trading engines — called masters — named Scalping, Intraday and Swing. You subscribe to one master, connect your own Bybit or Binance API key, and that master's trades are mirrored into your own exchange account, scaled to your balance and your risk settings.

Non-custodial means twoke never holds your money. Your funds stay in your own exchange account the entire time, and the API key you connect is restricted to trading and reading — it cannot withdraw.

Copy trading automatically mirrors another trader's positions into your own account. When the trader you follow opens, adjusts or closes a position, the same action is placed on your account without you doing anything.

On twoke the trader you follow is an automated master engine rather than a person, and the copy is not a one-to-one clone: every trade is re-sized to your account balance and re-checked against your own risk limits before it is placed. A trade the master takes with 2% of its equity is taken with your configured percentage of yours.

They differ by the timeframe they think on, which changes how often they trade and how long a position stays open.

• Scalping reads 3-minute candles for execution and 15-minute candles for structure. It trades inside fixed intraday sessions and holds positions for minutes.
• Intraday reads 15-minute candles for execution and 1-hour candles for structure, over a single trading day from 03:00 to 23:00 New York time.
• Swing reads 1-hour candles for execution and 4-hour candles for structure, over one crypto trading day beginning at 20:00 New York time. Positions can stay open across days.

Each master is a separate subscription. One exchange account can follow exactly one master at a time.

You do not need to know how to analyse a chart, but you do need to understand what leveraged futures trading can do to an account. Copy trading does not remove risk — it automates a strategy that can and does lose money.

Before you can subscribe or connect a key, twoke requires you to accept a risk disclosure and the Terms of Service, both recorded with a version against your account. If the disclosure text changes, you are asked to accept it again.

The safest way to start is demo: every exchange key you connect carries a demo/live flag, and demo is the default. You can run a master against Bybit demo funds for as long as you like before deciding whether to point it at real money.

No. twoke is execution software, not an advisor. It mirrors a master engine's decisions into your account; it does not assess whether trading suits your circumstances, and past performance of any master does not indicate future results.

You are responsible for your own decisions and for complying with the law where you live. Trading digital-asset derivatives carries a substantial risk of loss, and you can lose some or all of the capital in the account you connect.

Four things:

• An email address, to create your twoke account.
• A Bybit or Binance account, with an API key scoped to trade and read only — no withdrawal permission.
• A crypto wallet holding USDC on the Polygon network, plus a small amount of POL for gas, to pay for a subscription.
• Funds in the exchange account you connect. twoke never holds them; it places orders on your account.

The order matters: you connect the exchange key first, then subscribe. A subscription is bought for one specific exchange account, so that account has to exist before it can be paid for.

Bybit and Binance, both on USDT-margined perpetual futures. Each supports a demo/testnet account and a live account, and you choose which one a key points at when you connect it.

Bybit uses its Demo Trading environment, where balances persist indefinitely and can be topped up on request. Binance uses its Futures testnet, which the exchange resets periodically without notice — so treat Binance testnet history as temporary.

Trade and read only. Do not enable withdrawal on a key you connect to twoke — the platform never needs it, and a key that cannot withdraw cannot be used to move your funds even if it were compromised.

On Bybit, create the key under API Management with Contract trading and read permissions, and leave Withdraw off. On Binance, enable Reading and Futures, and leave Enable Withdrawals off. Binance also lets you restrict a key to specific IP addresses, which is worth doing once you know the address twoke connects from.

Your API secret is encrypted with AES-256-GCM the moment it arrives and is only ever stored as ciphertext. The key that encrypts it is itself held by a cloud key-management service and unwrapped into process memory at startup, so a copy of the database or the configuration files does not decrypt anything on its own.

The secret never leaves the database in readable form. Screens that show a connected account display a truncated API key only, and no part of the platform logs a secret.

Yes, and it is the default. Every exchange key you connect carries a demo/live flag, and connecting without choosing gives you demo.

Demo and live accounts run side by side on the same platform — a demo follower gets exactly the same copied trades, sizing and stop-loss handling as a live one, against the exchange's paper balance. When you want to switch an account from demo to live you replace the key on that same account, which keeps your subscription, your risk settings and your history attached. That account must be flat (no open positions) at the moment you switch.

No. One exchange account can follow exactly one master, and this is enforced both when you subscribe and by the database itself.

The reason is mechanical, not commercial. Exchanges net positions per symbol in one-way mode, so two masters trading the same account would merge into one position when they agree and close or flip each other when they disagree — leaving the first master's stop-loss orders attached to a position that no longer exists. To follow a second master, connect a second exchange account. A Bybit or Binance sub-account works for this and is the usual way to do it.

As many as you subscribe. The only limit is on idle accounts: you can hold one connected account without an active subscription, and a second one is refused until the first is subscribed.

This exists because every connected account opens a private WebSocket to the exchange, and exchanges cap how many connections can be opened from one address. Accounts that are actually paying for a subscription do not count toward the limit, so someone running three subscribed accounts can still add a fourth in order to subscribe it.

Remove the key from the Accounts section of your dashboard. Three conditions have to hold: you must have verified a fresh emailed step-up code, the account must not have an active subscription, and the account must be flat — no open positions.

The flat check asks the exchange directly. If the stored key no longer authenticates at all, removal is allowed anyway: at that point twoke can neither see nor manage anything on that account, so refusing would only trap you. If the exchange is merely unreachable, removal is refused until it answers, because 'no response' is not evidence that you are flat.

Removing a key stops all copying for that account immediately. It does not close positions that are already open — flatten those on the exchange first, which the flat precondition requires anyway.

Yes. Rotating replaces the key and secret on the same connected account, so your subscription, your per-account risk settings and any open positions stay attached to it. Use this whenever you regenerate a key on the exchange.

The same rotation flow moves an account between demo and live, in which case the key must change too — a demo-scoped key cannot authenticate against the live venue. Moving between demo and live requires the account to be flat. The exchange itself cannot be changed: a Bybit key and a Binance key are different accounts, so point a new connection at the other exchange instead.

Three, all per master: quarterly (3 months), semi-annual (6 months) and annual (12 months). There is deliberately no monthly plan — quarterly is the minimum commitment, because a strategy needs more than a few weeks before its results mean anything.

Prices are set at runtime and shown live on the twoke pricing section and again at checkout, so the amount you are quoted is always the current one. A subscription covers one master on one exchange account; following a second master is a second subscription.

One: USDC on the Polygon PoS network, paid from your own crypto wallet. twoke does not accept credit or debit cards, bank transfers, PayPal, Apple Pay, or a transfer from an exchange account.

Specifically it accepts native USDC — the token issued by Circle, contract 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359 on Polygon. The older bridged token that many wallets also label simply USDC, whose real name is USDC.e, is a different contract and is rejected. USDT is not currently accepted on Polygon or anywhere else, so check which token your wallet actually holds before starting.

The reason for a single crypto payment path is the same reason twoke never holds your trading funds: payment goes from your wallet straight to a smart contract, so there is no merchant account, no stored card and no balance held on your behalf. It also means nothing can charge you again without your signature.

Paying takes two wallet confirmations and about a minute. From the subscribe dialog, choose the master, the plan and which of your connected exchange accounts the subscription is for, then:

• Connect your wallet. twoke asks it to switch to Polygon PoS (chain ID 137) and offers to add the network if it is missing.
• Approve the USDC amount. This first transaction lets the subscription contract move exactly that amount — it does not send anything yet.
• Confirm the subscription. This second transaction transfers the USDC and records your subscription on-chain.

You need a small amount of POL, Polygon's native token, to pay gas on both transactions. Polygon gas has been paid in POL rather than MATIC since the 2024 migration, so a wallet still funded with the old token cannot pay fees.

Your subscription activates when the payment service observes the confirmed transaction, not when the browser returns. A slow confirmation is therefore not a failed payment — leave the page open or come back to your dashboard shortly.

Nothing renews automatically and no payment method is stored, because there is nothing to store: each payment is a signature from your own wallet. A subscription simply expires unless you renew it.

Any browser wallet that injects a standard EIP-1193 provider into the page. MetaMask is the one twoke names in its error messages and the safest default; Rabby, Coinbase Wallet's extension, Brave Wallet and similar extensions work the same way.

Your wallet must be able to reach Polygon PoS, chain ID 137. If it is on another network, twoke asks it to switch and offers to add Polygon if it is not configured — you approve that prompt in the wallet, not on the page.

There is no WalletConnect QR flow and no mobile deep link at the moment, so paying from a phone means using a wallet app's built-in browser rather than a desktop pairing. A hardware wallet works if it is connected through one of those browser extensions.

Nothing is lost if the transaction never confirmed — a rejected or failed transaction moves no USDC, and you can simply try again. The common causes are, in rough order of frequency:

• The wallet prompt was dismissed. twoke reports this as a rejection rather than an error; start the subscribe flow again.
• The wallet is on the wrong network. It must be Polygon PoS, chain ID 137. Approve the switch prompt, or add the network in your wallet.
• Not enough POL for gas. The USDC balance can be sufficient while the transaction still fails, because fees are paid in POL.
• The wallet holds bridged USDC.e rather than native USDC. These are different contracts and only native USDC is accepted — swap or bridge to native USDC first.
• Only the first transaction was confirmed. Approving the amount does not pay; the second confirmation is what transfers it. An approval left on its own costs nothing but grants nothing.

If a transaction did confirm on-chain and your subscription has not appeared, do not pay again. Check your dashboard first — a payment that cannot be routed to an account, most often because that account already follows another master, is held for you as a pending subscription to attach rather than rejected. If it is not there either, email enfo@twoke.io with the transaction hash from Polygonscan.

No. Subscriptions are non-refundable — not partial, not pro-rated, and not for downtime. You confirm this at the point of payment as well as in the Terms of Service.

This is why quarterly is the minimum plan rather than monthly, and why every exchange key defaults to demo: twoke would rather you spend a few weeks on paper funds before committing than ask for money back afterwards.

It is preserved, not discarded. Upgrading sets your new expiry to whichever is later — today or your current expiry — plus the full duration of the new plan. Upgrading a quarterly plan with 5 weeks left to an annual plan gives you those 5 weeks plus 12 months.

Upgrades move you to a longer plan on the same master. Downgrading to a shorter plan is not supported.

Renewal is manual — nothing charges you automatically, because payment comes from your own wallet and twoke stores no payment method.

Renewing extends your expiry by the plan's duration from whichever is later, today or your current expiry. So renewing early does not waste the time you have left, and renewing after a lapse does not backdate to when it expired.

New trades stop being copied to that account immediately. The copy allocator only fans a trade out to subscriptions that are active and unexpired, so an expired account is simply absent from the list — it is not queued and it does not catch up later.

Positions already open on your account are not abandoned. The stop-loss and take-profit already live on the exchange stay in place, and twoke keeps watching an account that still has an open position even after its subscription lapses, so protection is not dropped underneath a live trade. Closing or managing that position remains available to you on the exchange at any time.

It is held for you as a pending subscription, and your dashboard shows it with a prompt to attach it to one of your exchange accounts. Nothing is lost.

This happens when a payment lands for an account that cannot receive it — most often because that account already follows a different master. Rather than reject money that has already moved on-chain, twoke parks the subscription until you point it at an eligible account. A parked subscription copies nothing while it waits.

Four steps, in a fixed order:

• The master engine produces a trade idea, including a required stop-loss and take-profit. It can also decline to trade, which is a normal outcome rather than a failure.
• A deterministic risk engine checks the idea. A model output is never the last step before an exchange — this check always runs, and it is ordinary code, not a model.
• The trade is sized to your account: your live balance is fetched fresh from the exchange, and the quantity is derived from your configured risk percentage and the distance to the stop.
• The order is placed on your account through your own API key, with the stop-loss and take-profit attached, and tagged so you can trace the position back to the exact master decision that produced it.

By default from a percentage of your own equity, never from a fixed quantity. twoke fetches your live balance from the exchange immediately before sizing, multiplies it by your configured risk percentage to get the amount you are risking, and divides that by the distance between the entry and the stop-loss. That gives a quantity where being stopped out costs approximately what you configured.

The result is then rounded DOWN to the exchange's lot size, never up, because rounding up would silently risk more than you asked for. It is also checked against your available margin rather than just your equity, so a trade can be shrunk or skipped if other positions are already using your margin.

Two other modes exist if you prefer them: an equity-ratio mirror, which scales the master's quantity by the ratio of your balance to the master's, and a fixed lot, which uses the same quantity every time. All three pass the same rounding, minimum-size and margin checks.

Yes — a stop-loss and a take-profit are mandatory on every position, and this is enforced at three independent layers rather than trusted to one.

• The master engine's decision type requires both prices, so a trade idea missing either cannot be produced at all.
• The database rejects any position record whose stop-loss or take-profit is missing, or is on the wrong side of the entry price for the direction.
• The order management system confirms the protective orders are actually live at the exchange, which is the only layer that knows what the exchange really holds.

If protection cannot be placed within a short window, the position is closed at market rather than left running unprotected, and a watchdog forces the same outcome for a position that is left unprotected too long. An unprotected position is treated as worse than no position.

All of them. When a master moves its stop, takes partial profit or exits, the same action is applied to the position that master opened on your account, keyed to the original decision so the two stay linked.

Management actions only ever touch positions that twoke opened for you on behalf of that master. A position you opened yourself on the same exchange account is never moved, closed or re-stopped by the platform — it is yours.

The same decisions, but not always the same fills, and sometimes fewer trades. Several checks can legitimately skip a trade for your account while another follower takes it.

• The price moved too far between the master's entry and your copy. If it moved beyond your deviation limit — 0.5% by default — the copy is skipped rather than placed at a worse price, because the same stop-loss at a worse entry is more risk than you configured.
• The size that matched your risk percentage came out below the exchange's minimum order size. The trade is skipped rather than rounded up, since rounding up would exceed the risk you set.
• Your own limits stopped it — your maximum concurrent positions, your daily loss limit, or your kill switch.

Each skip is recorded with its reason, so a missing trade can always be explained rather than guessed at.

USDT-margined perpetual futures. The specific symbols depend on the master you follow — the current engines trade major pairs such as BTCUSDT and ETHUSDT, plus GOLD (the XAUTUSDT contract) on some styles.

Trading is one-way rather than hedged, meaning one position per symbol per account. This is also why one exchange account can follow only one master.

No. The masters read a published economic calendar and stand down around high-impact releases — a blackout around red-flagged events and a shorter one around medium-impact events. The window covers US releases and Bank of Japan rate decisions, which are the events that move crypto hardest.

The gate fails closed: if the calendar cannot be fetched or its coverage has lapsed, the engine waits instead of trading. Being blind to the schedule is treated as a reason not to trade, not a reason to proceed.

Five, from the risk panel in your dashboard, applied per master or as a default across them:

• Risk per trade — the share of your equity risked if a trade hits its stop. The default is 0.5% and the maximum accepted is 5%.
• Maximum concurrent positions — how many copied positions can be open at once. The default is 3.
• Maximum daily loss — trading stops for the day once realised losses reach this share of your account. The default is 3%.
• Maximum copy deviation — how far price may move between the master's entry and yours before the copy is skipped instead of placed. The default is 0.5%.
• Kill switch — an immediate stop on new copied trades for that master.

Your settings can only ever shrink or veto a trade. They cannot make a copied trade larger or riskier than the master's own boundaries allow.

Turn on the kill switch in your dashboard's risk panel. It stops new copied trades for that master straight away and needs no confirmation code, because a control that stops trading must never wait on an email.

The kill switch does not close positions that are already open, and it does not remove their stop-loss or take-profit — those stay live at the exchange. To exit an open position, close it on the exchange or wait for the master's own exit. To stop copying permanently, let the subscription lapse or remove the key from that account.

twoke can only place orders on the account you connect, so it cannot reach your other funds, your wallet or your bank. What happens inside that account is governed by your exchange's own rules for margin and liquidation, not by twoke.

Within that account you can lose the entire balance. Every position carries a stop-loss, but a stop reduces risk rather than removing it: gaps, slippage and fast markets can all fill a stop worse than its price, and leverage magnifies both directions. Only fund a connected account with money you can afford to lose.

It stops new copied trades for the rest of the day once your realised losses since midnight UTC reach the share of your account you configured — 3% by default.

The figure is read from your exchange's own booked profit-and-loss record, not estimated by twoke, so it reflects what actually happened on your account including fees. If that figure cannot be read, copying stops rather than continuing on an unknown loss total.

With your email address and a password of at least 8 characters. Ticking remember-me keeps you signed in for 30 days; leaving it unticked ends the session when you close the browser.

If you cannot use your password, you can request a 6-digit code by email and sign in with that instead. Forgotten passwords are reset through a link emailed to you.

Yes, on the actions that matter. Connecting or replacing an exchange API key, and exporting your data, each require a fresh 6-digit code sent to your email at the moment you perform the action — on top of already being signed in with your password.

That code is stored only as a hash, expires after 5 minutes, works once, and fails closed: if the service that verifies it is unavailable, the action is refused rather than allowed through. Connecting an exchange key is additionally blocked at the database level unless the second factor was satisfied, so the check cannot be bypassed by reaching the API directly.

No. Your money stays in your own exchange account and your own wallet at all times. twoke places orders through a trade-only API key and is paid directly from your wallet to a smart contract — there is no deposit, no pooled account and no balance held on the platform.

This is a deliberate design constraint rather than a feature that might change: the platform holds no customer funds and asks for no wallet private key, and nothing in the product ever needs one.

Yes, both from the Privacy section of your settings page. Export returns your complete record — account, subscriptions, connected accounts, trade history and the security audit trail — and requires a fresh emailed code, because silently downloading everything about an account is exactly the kind of action a victim would never notice.

Deletion anonymises your account and removes your connected exchange credentials, while retaining the trade and payment records with your identity stripped from them. A complete erasure of financial records is not offered, because keeping them is a legal obligation; separating them from your identity is the honest way to satisfy both.

No. A master administrator sees aggregate performance for the master they manage, not individual followers' balances, positions or personal details beyond what support requires.

Administrative actions that do touch a user account — a role change, an impersonation for support, adding or rotating an exchange credential — each write a permanent entry to an append-only audit log, so who did what and when is always answerable.

The most common cause is that the account has no active subscription. A connected key with no subscription is inert by design — the copy allocator only selects accounts with an active, unexpired subscription, so an unsubscribed account receives nothing at all. Your dashboard says so per account.

If the account is subscribed and still quiet, check in this order: whether your kill switch is on, whether the master has actually traded (all three masters stand down for long stretches — no trade is a normal output), whether your daily loss limit has already been hit today, and whether your API key still authenticates and has trading permission enabled.

Because copies are checked per account, so two followers of the same master can legitimately get different results from the same decision. Four checks skip a trade for one account and not another: price moved beyond your deviation limit before your copy could be placed; the size matching your risk percentage fell below the exchange's minimum order size; your available margin was already committed to other positions; or one of your own limits — concurrent positions, daily loss, kill switch — refused it.

Every skip is recorded with its reason and attributed to the master decision it came from, so it can be looked up rather than inferred.

It can be, and twoke will tell you rather than quietly compensating. If your configured risk percentage produces a quantity below the exchange's minimum order size for that symbol, the trade is skipped and the reason is logged — the size is never rounded up to meet the minimum, because that would risk more than you configured.

If this happens on most trades, the account is too small for that master's stop distances at your risk setting. The honest options are to fund the account further or to follow a master whose typical stop distance suits it. Raising your risk percentage until trades squeeze through works mechanically but is the wrong reason to change it.

A subscription is bound to one specific exchange account, so it does not move on its own — but you rarely need it to. If you want that account to point at a different exchange key, rotate the key on the account instead: the subscription, risk settings and history stay attached to the account, and only the credential behind it changes.

If the subscription genuinely landed on the wrong account, contact support at enfo@twoke.io before removing anything. Removing a key is refused while an active subscription is bound to that account, precisely so that money already paid cannot be stranded by a deletion.