TWM Wiki

Description

TWM - Orders Time in Force

GTC (Good ‘Til Cancelled)

(sometimes shortened to “GTC” instead of “GDC” — double-check your platform, but they mean the same)

  1. Behavior: Your order sits on the book until it’s either fully filled or you manually cancel it.
  2. Use Case: When you want to patiently wait for your price without worrying about a time limit.
  3. Example: Place a buy limit at $50,000 for BTC. It may sit there for hours or days until matched.

IOC (Immediate or Cancel)

  1. Behavior: The order must be matched immediately against the book.
  2. Any unfilled portion is cancelled right away.
  3. Use Case: When you want to take liquidity immediately but don’t want leftover “hanging” orders on the book.
  4. Example: Place an IOC buy for 10 BTC at $50,000. If only 7 BTC is available, you get 7, and the rest (3) is cancelled instantly.

FOK (Fill or Kill)

  1. Behavior: Either the entire order is filled immediately at your price (or better), or the whole thing is cancelled.
  2. Use Case: When you need the full size executed, no partials.
  3. Example: Place a FOK buy for 10 BTC at $50,000. If only 9.9 BTC is available, you get nothing — order is cancelled.

Post-Only

  1. Behavior: Ensures your order only adds liquidity (posts on the book).
  2. If placing it would instantly match against an existing order, the exchange cancels it instead.
  3. Use Case: For maker orders where you want to avoid taker fees (or earn maker rebates).
  4. Example: Place a Post-Only buy at $50,000. If the best ask is $50,000, it would match immediately → exchange rejects/cancels it. If you enter at $49,999, it stays on the book.

In short:

  1. GTC = Stays until filled or cancelled
  2. IOC = Fill what you can now, cancel the rest
  3. FOK = Fill all immediately or cancel entirely
  4. Post-Only = Must rest on the book, never take liquidity


Post-Only is not really a "time in force"

  1. GTC, IOC, and FOK are time in force instructions (they tell the exchange how long the order should live and under what conditions).
  2. Post-Only is more of an execution constraint (it tells the exchange how to handle the order when placing it on the book).

So they are in different "categories."

Does Post-Only override the others?

  1. On most exchanges, yes: if you check Post-Only, the system will ignore IOC/FOK logic because those conflict.
  2. Post-Only + IOC/FOK makes no sense → IOC/FOK want immediate fills, Post-Only forbids immediate fills.
  3. So if you try to combine them, the exchange usually rejects the order outright or defaults to Post-Only behavior.
  4. Post-Only + GTC does make sense → it will sit on the book until filled or cancelled, but never execute immediately.

Typical Exchange Behavior

  1. Binance / Bybit / OKX: If you enable Post-Only and your price would cause an instant match, the order is cancelled automatically.
  2. Coinbase Pro: If you tick Post-Only and it conflicts with IOC/FOK, you’ll get an error message saying “Invalid combination.”

In short:

  1. Post-Only overrides IOC/FOK (or makes the order invalid).
  2. Post-Only works fine with GTC (most common setup).


What is Reduce-Only?

  1. Definition: A Reduce-Only order can only decrease or close an existing position.
  2. If placing it would increase your position size, the exchange cancels or adjusts it.
  3. Mainly used in derivatives trading (futures, perpetuals, margin).

🔹 How It Works in Practice

  1. Example 1 (Closing a long):
  2. You’re long 5 BTC. You place a Reduce-Only sell for 3 BTC.
  3. → If it executes, your position shrinks to 2 BTC long. ✅
  4. Example 2 (Conflict):
  5. You’re long 5 BTC. You place a Reduce-Only buy for 3 BTC.
  6. → This would increase your long to 8 BTC, which violates Reduce-Only.
  7. → Exchange rejects or ignores it. ❌
  8. Example 3 (Closing with exact size):
  9. You’re short 2 BTC. You place a Reduce-Only buy for 2 BTC.
  10. → If it fills, position goes to flat (0). ✅

🔹 Why Use It?

  1. Prevents mistakes where a stop order or TP order accidentally flips your position.
  2. Useful when running multiple exit orders (e.g., several take-profits) and you don’t want overfills to create a reverse position.
  3. Common in hedged strategies where risk management requires that certain orders never add exposure.




This website uses cookies to enhance your browsing experience. By continuing to use our website, you agree to our Privacy Policy

Necessary cookies help make a website usable by enabling basic functions such as page navigation and access to protected areas of the site.

  • Necessary cookies

    .AspNet.Consent

    Indicates whether the user has consented to the use of necessary cookies.

    Maximum storage duration: 1 Year | Type:Necessary cookies
    .AspNetCore.Antiforgery

    Used to prevent CSRF attacks and protect user data.

    Maximum storage duration: Session | Type: Necessary cookies
    .AspNetCore.Cookies

    Used to manage authentication information and the user's session.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    .AspNetCore.Culture

    Used to store user's language preferences.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    __Secure-OSID

    Security cookie set by Google to authenticate users and prevent fraudulent use of login credentials.


    Maximum storage duration: 6 Months | Type: Necessary cookies
    __Host-3PLSID

    Ensures you stay connected to your Google accounts across various services.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    AEC

    Used to verify your Google account and ensure that requests in sessions come from you.

    Maximum storage duration: 6 Months | Type: Necessary cookies
    HSID

    Security cookie used by Google to authenticate users and prevent fraudulent use of login credentials, protecting user data.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    SEARCH_SAMESITE

    This cookie prevents the browser from sending the cookie along with cross-site requests, helping to mitigate the risk of cross-origin information leakage.

    Maximum storage duration: 6 Months | Type: Necessary cookies
    SID

    Important for Google's security and to ensure that Google can authenticate the account and block fraudulent access attempts.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    SIDCC

    Security cookie to protect user data from unauthorized access.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    __Host-1PLSID, __Host-3PLSID

    Crucial cookies to ensure that you remain securely logged into your Google accounts while accessing various Google services.

    Maximum storage duration: 2 Years | Type: Necessary cookies

Functional cookies allow the website to provide enhanced functionality and personalization. They may be set by the website owner or by third parties whose services have been added to the pages.

  • Functional Cookies

    LSOLH

    Used by Google to store session information and enhance the user's experience on Google services.


    Maximum storage duration: Session | Type: Functional Cookies
    COMPASS

    Used by Google to improve user navigation by remembering preferences and information, such as preferred language.

    Maximum storage duration: 6 Months | Type: Functional Cookies
    ACCOUNT_CHOOSER

    Remembers which accounts have been used to log into Google services on the device.

    Maximum storage duration: 1 Year | Type: Functional Cookies
    APISID

    Used by Google to store user preferences and information when viewing pages with Google maps.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    LSID

    Used by Google to store user preferences while viewing pages that incorporate Google services.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    NID

    Used by Google to remember user preferences, such as preferred language, to provide a more personalized experience.

    Maximum storage duration: 6 Months | Type: Functional Cookies
    SAPISID

    Used by Google to collect information about visitors for videos hosted on YouTube or maps integrated with Google Maps.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    __Host-GAPS

    Used by Google to store user preferences and information when pages containing maps or Google services are viewed.

    Maximum storage duration: 2 Years | Type: Functional Cookies

Statistical cookies help website owners understand how visitors interact with the site by collecting and transmitting information anonymously.

  • Statistical Cookies

    CLID

    Unique identifier used to track user interactions and maintain unique sessions.


    Maximum storage duration: 1 Year | Type: Statistical Cookies
    MR

    Microsoft cookie that collects data on user interactions to improve services.

    Maximum storage duration: 7 days | Type: Statistical Cookies
    SM

    Used by the Microsoft Clarity analytics suite to maintain the user's session.

    Maximum storage duration: Session | Type: Statistical Cookies

Marketing cookies are used to track visitors on websites. The intent is to display relevant and engaging ads for the individual user.

  • Marketing Cookies

    AID

    Used by Google to link your activity across devices if you have logged in with the same Google account.


    Maximum storage duration: 1 Year | Type: Marketing Cookies
    ANONCHK

    Used by Microsoft Advertising to check the anonymity of data sent by tracking cookies.

    Maximum storage duration: 10 minutes | Type: Marketing Cookies
    MUID

    Microsoft cookie used to track user interactions across Microsoft domains.

    Maximum storage duration: 13 Months | Type: Marketing Cookies
    __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDTS, __Secure-3PSIDCC

    Google cookies designed to build a profile of your preferences and show you relevant ads on other sites, protecting the Google account.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    ADS_VISITOR_ID

    Used by Google to identify and track visitors across various websites to display personalized advertising.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    OTZ

    Used by Google to personalize ads on Google properties, like Google Search.

    Maximum storage duration: 1 Month | Type: Marketing Cookies
    __Secure-1PAPISID, __Secure-1PSID

    Used by Google to deliver more relevant ads and protect the security of your preferences and Google account information.

    Maximum storage duration: 2 Years | Type: Marketing Cookies

Cookies are small text files that can be used by websites to make the user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This means that cookies classified as necessary are processed under Article 6(1)(f) of the GDPR. All other cookies, namely those belonging to the categories of preferences and marketing, are processed under Article 6(1)(a) of the GDPR.

This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages.

You can change or revoke your consent at any time from the Cookie Statement on our website.

Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.

Specify your consent ID and the date you contacted us regarding your consent.