Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
ichibot-client-app
ichibot-client-app
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • Ichimikichiki
  • ichibot-client-appichibot-client-app
  • Wiki
    • Home
  • Alias Commands

Last edited by Ichimikichiki Apr 07, 2021
Page history

Alias Commands

Aliases are shortcuts / hotkeys to your commands. You simply press the up arrow on an order you just made, go to the start, and put alias x at the start. Then the next time you want to execute that command - you simply type "x" and hit enter.

Global Aliases - instrument *

  • You can set a global alias that can be called in any instrument.
  • It will only affect the instrument you're in.
  • Stick it under instrument * in your initrun.txt file or type instrument * and save the alias from the [global *] > prompt.
  • Executing a global alias under a specific instrument such as [BTC-PERP] > will only affect BTC-PERP.
  • Warning: If you execute a close all or cancel all while actually in instrument * it will close all your positions / cancel all your orders for any contract / order you have open on all instruments.
  • Just a reminder: don't use numbers as aliases... it's going to be pretty awkward when you go buy 2 and it does something unexpected because you saved an alias as "2".

Planning your keyboard layout (hotkeys assignments)

  • I set all my buy orders on the left half of keyboard
  • All my sell aliases on the right half of keyboard
  • Sometimes I'll use things like [ for buy and ] for sell
  • I set up extra aliases for double and triple presses of the same key to execute larger sizes

Example Contract Specific Aliases (in this case for BTC-PERP) and Global Aliases at the end with instrument *

###### Careful - all commands here run as raw commands upon startup. One line = one command.
###### BTC-PERP ALIASES HERE
instrument btc-perp
alias [ buy 1
alias [[ buy 2
alias [[[ buy 3
alias ] sell 1
alias ]] sell 2
alias ]]] sell 3
alias a bump +0.5
alias aa bump +2.5
alias aaa bump +5
alias z bump -0.5
alias zz bump -2.5
alias zzz bump -5

instrument eth-perp
#### ETH-PERP ALIASES HERE
alias [ buy 10
alias ] sell 10
  
instrument ada-perp
#### ADA-PERP ALIASES HERE
alias [ buy 100
alias ] sell 100
  
##### IF TRADING SIZE, YOU DON'T WANT TO MARKET SELL HUGE AMOUNTS IN ONE GO. USE SOMETHING LIKE THESE.
alias cx set ro, split sell 100%possize into 20
alias cxx set ro, split sell 50%possize into 10
alias cv set ro, chase sell 100%possize
alias cvv set ro, chase sell 50%possize

instrument *
#### GLOBAL ALIASES HERE
alias c cancel limits
alias cc cancel all
alias ca close all
alias cs cancel stops
alias ccc cancel chase, wait 0.8, cancel limits
alias ls position list; order list; cmd list
alias pos position list
alias ol order list
alias fk terminate
alias cm cmd list
alias cas close spots
alias * instrument *
alias btc instrument btc-perp
alias eth instrument eth-perp
alias al alias list

If you still have ichibot running and you made changes directly to the initrun.txt file, once you hit save - you can then type reload init on ichibot to reload the initrun.txt file on the fly.

Added set PO to the start of those 10 order serial strings which makes the orders "Post Only". You don't have to, but too many ppl accidentally pressed the wrong way and machine gunned into the order book.

Example of setting and using an alias in video here

Relative Sizes & Best Practices when making an Alias

The first time a base price is set, it will not be set again in the series. So if you set the price in an alias call, that's the base price for the whole series. If you do not set the base price in an alias call then the base price will be looked up from the result of the first order, providing a comma has been used to separate the orders. ,

Subsequent orders in an alias using , in between can all use the % and +5 or +10 and so on.

  • Each parallel command series (separated with ;) has their own individual base prices specified. However if these are inside an alias then the alias call may "force" set the base price once for all.

The same rules apply to relative order sizes.

  • If you are making an alias of 10 orders - best to make each order 10%, so you will end up specifying the TOTAL position you want to end up with. If you put 100% for each one, you will end up with x10 times the position size you specified, and it makes it less fun.

Example

buy 1 @8500, sell 1 @8600 - place two orders to execute one after the other
buy 1 @8500; sell 1 @8600 - place two orders to execute together at the same time

  1. So you can make an alias with amount and price (or equiv parameter) specified. (Fast to execute, requires a lot of different aliases with various amounts) - Use ; between orders.
  2. Make one where you only have to specify the amount. (Using say 10% in place of amount) - Use , between orders
  3. Make one where you only have to specify the price. (Using say +0 in place of price) - Use , between orders
  4. Make one where you have to specify the amount and the price. - Use , between orders

Note: If setting Reduce or Post Only orders, they will affect all orders in a serial up to the ;, as the ; break is considered an isolated trade. You will need to set ro, again after the ; if you require.

set ro, buy 150 @17.36; set ro, buy 100 @17.54

GO TO TRIGGER SYSTEM WIKI PAGE

Tip Jar:

  • BTC - 3L95ETWP3F8HLqUY4FD5CS8rkkFdpYjqKR
  • ETH - 0x6eb9A84CE93Cd61db02302f39B824AB155b69601
Clone repository

Get App:

  • MacOS
  • Linux
  • Windows
  • Web Console
  • Source Code

Instructions:

  1. Intro
  2. Setting up ichibot
  3. Overview
    -- General Commands
    -- Trigger / Wait Orders
    -- Variable System
    -- Alias System
    -- Replace Feature
    -- Ratelimit Overrides
  4. Advanced Examples
  5. Trigger Examples
  6. Variable Examples
  7. Stream Deck Integration
  8. AlphaBot Integration

  • Wiki Changelog

  • Discord Server
  • ichibot twitter
  • ichi's twitter
  • FTX Ref link
  • Bybit Ref Link