The channel was long. Twenty minutes later it calls a short on the same contract. Three accounts following the same two posts end up in three different places, and the difference is a dropdown most followers have never opened.
What actually happens when the second call lands?
Picture the ordinary version of this. At 03:41 the channel posts a short on the same contract it called long two hours earlier. No explanation, no "close the long first" — just the new direction, an entry, a stop and a target.
Three people follow that post with the same balance and the same size. One wakes up flat, the long closed at a small loss by the new order. One wakes up short, because the new size was bigger than the long and the remainder became a position in the other direction. One wakes up holding both a long and a short on the same contract, each with its own margin and its own liquidation price, and neither of them is the flat position they assumed they had.
None of the three did anything wrong at the order ticket. The difference is a single account setting called position mode, and it was decided long before that post appeared.
What is position mode, in the plainest terms?
It is the rule your exchange uses to answer one question: can this account hold a long and a short on the same contract at the same time?
Binance's futures FAQ on hedge mode puts both halves in one place. In one-way mode, Binance states, "In One-way Mode, you can only hold positions in one direction under one Futures contract." In hedge mode, "In Hedge Mode, you can simultaneously hold positions in both long and short directions under the same Futures contract."
Bybit's API documentation describes the same split for its own venue: "If you are in one-way Mode, you can only open one position on Buy or Sell side. If you are in hedge mode, you can open both Buy and Sell side positions simultaneously," with one-way recorded as mode 0 and hedge as mode 3 in Bybit's switch position mode reference.
That is the whole mechanic. Everything below is a consequence of it.
One thing it is not: this is a different setting from isolated versus cross margin. Margin mode decides how much of your money stands behind a position; position mode decides how many positions can exist on that contract at once. They are set in different places, they fail in different ways, and having a strong opinion about one tells you nothing about the other. If the margin side is the part you are unsure about, that has its own explanation of isolated and cross margin.
Why does a short call close a long in one-way mode?
Because in one-way mode there is nowhere else for the order to go.
The account is allowed exactly one direction on that contract. An order on the opposite side cannot become a second position, so the exchange applies it against the one you have. Sell into an open long and the long gets smaller. Sell the same size as the long and the long is gone.
Sell more than the long and the arithmetic keeps going. The first part of the order closes what you had; the remainder has nothing left to reduce, and a market that will happily fill it. You are now short a coin you were long twenty minutes ago, at a size you never chose, having read a post that never told you to close anything.
This is not a hypothetical edge case — it is the reason the reduce-only flag exists at all. Binance's page on failed futures orders lists two cases where a reduce-only order gets rejected — "The order is in the same direction as the open position", and "The order is in the opposite direction and the order size exceeds the open position and fails the margin check" (Binance, summary of failed orders). The exchange refuses to let a reduce-only order overshoot into a new position. Which tells you plainly what an ordinary order without that flag is permitted to do.
So in one-way mode, the follower-specific risk is not that the channel is wrong about direction. It is that a directional call arrives as an instruction to your open trade, whether or not the channel meant it that way. A long you intended to keep for another day can be closed by a post about a completely separate idea, and a size mismatch turns "closed" into "reversed."
And in hedge mode, why is "flat" the wrong word?
Because in hedge mode nothing was closed at all.
The short call opens a short. The long stays exactly where it was. You now have two live positions on one contract, and Bybit's API returns them as separate records — each with its own positionIdx (1 for the hedge-mode Buy side, 2 for the Sell side), its own initial and maintenance margin fields, and its own liqPrice, documented as "Position liquidation price" in Bybit's position info reference.
Two liquidation prices, one above and one below — though how solid those two numbers are depends on your margin setting, and Bybit's own reference notes that under cross margin the figure is an estimate rather than a fixed level, and that it is not returned at all under Portfolio Margin. A move large enough in either direction can take out the side facing it while the other side is still open — so a market that goes nowhere on net can still cost you a position. The reason this is so easy to miss is that your unrealised profit and loss can look almost still, the two sides moving against each other, while the margin behind each one is doing something quite different. What a liquidation actually is and how it gets triggered is worth having straight before you hold two of them at once.
The carry cost deserves an honest description rather than a scary one. Funding is charged on position value: Binance gives the formula as Funding Amount = Nominal Value of Positions x Funding Rate, settling by default "every 8 hours at 00:00 (UTC), 08:00 (UTC), and 16:00 (UTC)," and notes that "You are only liable for funding payments in either direction if you have open positions at the pre-specified funding times" (Binance funding rate introduction). With a long and a short of equal size on the same contract, one side pays and the other receives, so funding largely offsets rather than doubling. What does not offset is everything else: you paid fees to open two positions and you will pay fees to close two positions, margin is locked in two places instead of one, and the day you want out you have two exits to manage, not one. A hedged pair is a bill, not a shelter.
Does "close" from a channel mean the same thing in both modes?
No, and this is the sentence worth re-reading.
A post saying "close the long" is one instruction to a human and two different instructions to an exchange. In one-way mode there is only one position, so a same-size opposite order does the job. In hedge mode the order has to name which side it is closing, or the exchange will read it as opening the other one. Bybit's create-order documentation makes the requirement explicit: positionIdx is "Used to identify positions in different position modes. Under hedge-mode, this param is required," and reduceOnly means "true means your position can only reduce in size if this order is triggered" (Bybit, create order). The same page notes that "When reduceOnly is true, take profit/stop loss cannot be set" — so the protective flag and the attached exit levels are not a combination you get for free.
The practical translation: reduce-only is not one behaviour with one meaning. In one-way mode it is a guardrail against accidentally flipping. In hedge mode it is a guardrail plus an answer to "which of my two positions?" — and if the answer is missing or wrong, the flag protects nothing. Anyone typing orders by hand should know how their own ticket expresses that choice, which is the same class of detail as knowing which order type turns a published entry into a position.
Why can you not just fix this mid-trade?
Because the setting is locked exactly when you most want to change it.
Binance states it directly: "Position Mode cannot be adjusted while you have open positions or open orders" (Binance, What Is Hedge Mode and How to Use It?). Bybit's documentation applies the same constraint per trading pair — a pair with a live position or a resting order will not switch — and describes a scope that is worth knowing before you assume anything: "Priority for configuration to take effect: symbol > coin > system default," with the system default being one-way (Bybit API, Set Position Mode). Setting the mode by settlement coin, that page adds, batch-switches every symbol on that settlement coin which has no position and no open order, and puts newly listed symbols on the same coin into the mode you chose.
Two things follow. First, the scope is a per-venue fact, not a universal one: one exchange may hang the setting off the futures account, another off the symbol with a coin-level fallback, and any of it can change with a release. Read your own exchange's current page rather than a number you remember from a different venue. Second, the moment a flipped call lands is the one moment the switch is unavailable to you — you have a position open, which is the condition that blocks it. Whatever mode you are in at 03:41 is the mode you are trading.
What does an automation do with all of this?
Exactly what you configured, at full speed, with no one awake to object.
A bot subscribed to a channel receives "short" as an order to place, not as a change of view to think about. In one-way mode it will reduce or reverse your open trade. In hedge mode it will stack a second position beside the first. Some tools have their own position-mode field that must match the exchange account, and a mismatch produces either a rejected order or a filled one that lands on the wrong side of the book. If you are running anything unattended, the mode is part of the configuration, not a background detail — the same category of setting as the ones covered in running a bot on someone else's signals.
What is genuinely in your control here?
Not whether the channel flips. Channels flip; that is a view changing, and sometimes it is the right call. What is in your control is whether the flip lands on your account as something you understood in advance.
Four things, all of which can be settled before you subscribe to anything:
- Know which mode your futures account is in right now. Open the setting and look. Do not infer it from how a past trade behaved.
- Know what your exchange's mode setting covers — one contract, all contracts settled in one coin, or the whole futures account — and know that it is locked while positions or orders are open.
- Decide in advance how you will treat a direction call on a contract you already hold. Close first and then enter, or skip the second call entirely. Both are defensible. Discovering the answer at 3 a.m. is not.
- If a channel's instructions are ambiguous about closing, treat the ambiguity as the finding. A service that publishes entries and reversals on the same contract without saying which existing position they act on has left the most expensive part of the trade to your dropdown settings.
The setting is dull, it is one click, and it changes what a single post can do to money you already have on the table.