TWM Wiki

Description

Instruments

Understanding Instruments



TWM locally stores instruments in its own database. For users to be able to combine these instruments into their custom instrument lists, the instruments need to be downloaded from their respective providers. Please take a look at the illustration to understand how it works.

Image



As the illustration shows, the above process has 2 steps:

  1. Connect to the provider, and download the desired instrument using the instruments window.
  2. Add the downloaded instrument to your custom instrument list, using the Instrument List Window.

Upon connecting for the first time to any provider, TWM will create a default instrument list, supplied with a number of instruments. Depending on your internet connection speed please allow up to 60 seconds for default instruments to appear in the instrument lists window.

Loading Instruments

Use this interface to download instruments from your provider into the local TWM database. On the right, you can browse instruments available on the provider server. On the left, you will see instruments that have already been loaded into the local database.

User can:

  1. Add a single instrument from the provider server to the local TWM symbols database by selecting it and clicking the Add button (bottom center-right).
  2. Add all instruments in bulk by clicking the Add All button (next to Add).
  3. Remove one or more instruments from the local database using the Remove and Remove All buttons (bottom left).
  4. View detailed data for any instrument by double-clicking it.
  5. Filter instruments by type using the filter dropdown.
  6. Select a provider from the provider dropdown menu at the top.
Image


When you connect to an exchange, the TWM engine will automatically add any instruments with open positions that aren’t already in your local database. This ensures that all positions appear correctly in the Positions tab.

Instrument Lists

The instrument lists window is used to create custom user instrument lists. TWM comes with Default instrument lists that cannot be deleted. The instrument lists window is subdivided into 3 sections.

Window part 1 is used to show created instrument lists. Use the Add Remove buttons at the bottom below the section to add and remove custom instrument lists. When creating an instrument list it has to be assigned to a specific connection and instrument type, cross connection and cross type lists are not supported.

Window part 2 is used to show the instruments that have been added to a specificly selected list from the local instruments database. Use the Remove button below the section to remove the instument from the selected list.

Window part 3 demonstrates all instruments that are available locally and can be added to any list from the blue section. Use the Add button below the section to add instument to the selected list.

Image


After you have created your custom instrument list and added an instrument to this list it will appear in the data series window. Please see illustration below.

Image


Min Lot Size

When accessing instrument parameters you will see a field called min lot size which is very important to understand to place your trades successfully. For example min lot size for BTCUSDT future contract on Binance is 0.001 which means you cannot buy/sell less than that when you trade. Some future contracts also have a notional field which means that even if you do use the min lot size when you trade it cannot convert to less than the notional value of the quote asset using the current price. You can access individual instrument information by double clicking on any instrument in the local database list in Instruments window (left hand side) or Instrument Lists window (bottom right section 3).

For example, if BTCUSDT min lot size is 0.001 and the current price is 59600 the converted value is 59.6 which is less than the notional which is usually 100. As a result an order placed at this value can be ignored. Please check with providers for more information on this issue.

Below is an example with BNBUSDT futures contract where minimum lot size is 0.01 and notional is 5,00. If we trade min lot size here at current price of about 617USD you will be ok because the notional will be 6,17USDT. However if price falls below 500 you will need to increase this value to open a minimal position.


Image


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.