Binary Bot on Deriv

Visual automation for binary bot on deriv - bot.deriv.com

Binary Bot on Deriv uses Google Blockly to provide a puzzle like automation environment to trade using binary.com API version 3.

Pre-installation

Ensure that your environment contains the following packages.

 - node >= 12.18.0
 - npm >= 6.14.4
 - git (for contribution)

Getting Started

Recommended extensions to start contributing to the project:

 - Prettier
 - ESLint

You can simply search for these extensions on VS Code and install them to start using.

Note: node -v and sudo node -v should be the same version.

Installation

1. Setup the project on local machine

You will need to perform the following on your development machine:

In order to work with Deriv-Bot application, you must create your own version of this project. Please fork the project - https://github.com/deriv-com/binary-bot to your git account.
Change the current working directory to the location where you want the cloned directory.
Clone using SSH. Clone the forked repo using git clone [URL for the forked repo]
Enter project directory cd binary-bot
Run npm install

Note: - issue with installing packages

2. Configuring Hosts file

In order to run our application for the first time, you need to configure your hosts file:

If you are using a UNIX based system (Mac or Linux), Do the following:

Open terminal.
Open hosts file in your preferred text editor using sudo vim /etc/hosts.
Add a new entry pointing to 127.0.0.1 localbot.binary.sx
Save the file

For Windows:

Run Microsoft Notepad as an administrator.
From Notepad, open the file: c:\Windows\System32\Drivers\etc\hosts
Add a new entry pointing to 127.0.0.1 localbot.binary.sx
Save the file

3. Preparing environment variables

If you want to use Google Drive features in the project (to Save/Load strategies) you need to create a file called .env at the project root with the following content:

GD_CLIENT_ID=GOOGLE_DRIVE_CLIENT_ID
GD_API_KEY=GOOGLE_DRIVE_API_KEY
GD_APP_ID=GOOGLE_DRIVE_APP_ID

Here comes useful links for more information on how to confgure your project with Google Drive integration:

4. Starting a Development Server

Make sure to set the endpoint for running the application on the localhost

Run sudo npm start on the binarybot directory. This will open the application in your default browser.

Note: - Getting Permission Denied Error
Navigate to http://localbot.binary.sx (Note that the protocol is http and not https)

Note: - Getting error "This site can’t be reached" on localhost
And now you are ready with your setup. Login to the binary account using the Binary.com account credentials. Run the bot

Pushing changes to github

Create a feature branch from master - git checkout -b [branchName]
Make your changes to the source code
Run test command to make sure your changes are correct npm run test
Run git fetch upstream master and git merge upstream/master to update your branch and avoid conflicts
Push your changes to your forked repo:

git add .
git commit -m "describe your changes"
git push origin BRANCH_NAME

Test link deployment

The deployment for test link is done automatically:

Upon creating PR, Vercel will auto-generate a test link inside the PR. you can use that to preview the test link for the changes you have made.

PR Guidelines

Use the developer 1|developer 2/task_name format for PR titles. (e.g.: dev1|dev2/fixed_emoji_issue, dev1/added_superfast_jellyfish)
- Optional square bracket tag (e.g. [WIP]) can be at the end.
Use the appropriate package labels available on the repo to indicate which packages your PR modifies.
Use Draft PRs if you don't mean to request for reviews yet. Read more here.

Release

Release to production: 1. git tag production_v20191205 -m 'release production' 2. git push origin production_v20191205

To update to the latest version

git fetch upstream master
git merge upstream/master

Optional Branding

Go to app.config.js file inside the src/directory of the project folder.
All the important branding settings are implemented in this file.
User can make changes to Deriv branding related logo, text and their visibility.

Running with a specific endpoint Use only if you know what you're doing

ENDPOINT='wss://ws.binaryws.com/websockets/v3?l=en&app_id=1169' bot bot-example.js

To set the endpoint for running the application on the localhost. For this, Go to http://localbot.binary.sx/endpoint.html. Make sure the Server is set to blue.binaryws.com and O Auth App ID is 16014 Click submit

Think you found a bug?

There's a chance that we already know about it and doing our best to fix it. To find out you can search our GitHub issues

Not satisfied yet? Please create a new issue, and explain to us what is the nature of the problem and how to reproduce here

We'd love to hear from you

Please send us your inquiries through marketing@binary.com

Sample Blocks

You can find some example blocks in the Examples folder.

Disclaimer: All the files and codes in the above links are intended for educational and informational purposes only. They should not be construed as giving investment advice, and you should not rely on them as your singular factor in making or refraining from making any investment decisions. Binary.com accepts no liability whatsoever for any losses incurred by users in their trading. Binary options trading may incur losses as well as gains.

FAQ

1. Issue with installing packages

If you couldnt install binary bot with a different node version, try cleaning npm cache.

To clear a cache in npm, we need to run the npm cache clean --force command in our terminal.
Delete cache directory. The default cache directory is ~/.npm on Posix (mac or linux), or %AppData%/npm-cache on Windows.
Run rm -rf ~/.npm
Run npm install

2. Getting Permission Denied Error on localhost

Try sudo npm startinstead of npm start

3. Cannot access the site

Make sure to use HTTP instead of HTTPS: https://localbot.binary.sx => http://localbot.binary.sx

oleglr/com-binary-bot