Graphene Blockchain Government and Development Discussion

Graphene blockchain community forum built on top of the <a href="https://golos.id" target="_new">Golos Blockchain</a>.

Welcome to the Graphene telegram group <a href="https://t.me/graphene_dex" target="_new">@graphene_dex</a>

Graphene Forum

<img style="margin: -13px -17px -16px -18px;padding: 0 10px;" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPoAAAA4CAYAAADUzOWCAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAA0ZSURBVHgB7Z1Rcts4EkAblORsTZyMcoKhTxDlBJFOEMuZ3ar9svy9cWyfwPIJbMfZ2k/bX1u1O46UE5g5gZ0ThPO7P9EkzuxsJBHbTYIKBQIUScuxJtOviuUIBAGQRAON7gYDwDAMwzAMwzAMwzAMwzAMwzDMAiKlrNMBDMN8eygB35dfuMDDBYZhvh1QqI9lmnc8uzPMN4S0swoMw9w6VduJ/eP3dbhfWa05zkMZCBccnJ0DMQggeBsE4O38+Z5H+XjWZpjFR5gSj3qfdlGCt/GfdfuFwh+OZHvnL8uXKOznmNQ0ZFsRQvjAMMytMiXo+/9879buLPUkyAbkRYjus9XvTvFfJOyuSh3gsYNCfgIMw9w6E0FXQn6OQu5CUVDYN9t399SanLSAPgr5ABiGWQgma/TaUm23lJATUnaPfvrwFoW7DwzDLBzhjP7i7KojBBzD9RiMfhmu7Gw84JmcYRaMcEYXDqyDzMx3iUPCQEpwxZd1uE69cr/Wwb8HwGSigoncRNIAtaFLYEpBHiLqe44j0EMEddRMXz9/unwCzITqfg/daNJoMcdkORBjaG8qVxpxdPaxi2vyXWNpQjaBBT0PHTySz9DDowVMYY56v26BDLr4T4rODHVU/PsWmCkcGFWtFnZHir2kkBObT++hoINnLsx5CAzzlYjcwAFNLBzLMQOn4tgNcEPHLNBBIN+Y0ksb8ximIOQlIiMwMLlwsk7Wlu6+B4ZZQKq1ik0T9RzpsL1DoyokDMzxcQDj36428E9XT68IZ12arXdscWe+CoEQDX2Wwr688+zpMtuIDFRHlbFXleaJ3UGjG7reBs/Vw1PWzX2bio7pb6AEygq9hQcF3Lgq2cPjlKLraHecdslOHJCD53Zh2oL9mvz5mN7Bf6/j4ePvDa2+JkTGMJoVaH3nq/r2VNqTRHaKDzhQ11Hefb0tqt3rifIu1bGXNwTY8AwGqozDWfEJ6n62VP2uSg6vpfsytUE9n8eJJHp3nqEN/Tz3kXje8TOI2386zwjJo39/bIqqQ16ihj7ZSBCPX/Y+PZRjeL35492pZ7aP19Wq4kkgYTXhObpEt/Ll8Lfh3s5fH/im+rC8qb5Hy1ay6FN5VcfZoj0gm+3lVlbeqfa/+ngghPN9Is/biXyhYbwGS/t6GePPQ6+6hOmRsbtO4ef47/5wgO1Gd7Zyj0/3P+wzo8Hnw9jdHc7lR72rc5vlXUGZfYgekNXwgUbPjaJuDewg1LGyRmE6t62ludh5flbX63H2JKw/QGTZJqijt1Reaju9jKxdddQ5k2ph8noX/7zT8vdnlNfF6/eSCTJaWyat7r766+YtI9Eeup8m2PEhGhj72rUnEAlmjAdfOooJ7Ezi1NKGZPizrQ2teex7eHH2AdvhZMZ8BFLubZHROL6md7WPs/121jVxdKeefPTqSk5nw4mH7kfZB0jonq3dXbHlfda+OzXJvHh19W7KRY2G7XigQEF3q7Km9y8P7O/lEmWOBqsOmG6J9qP873OLBrFoKh/JPcimDtmdgMZWv4SQU2c/mJFtG4pBnbdjOdeDbKEkGlCMWeV1ZbRBKAsXsgWlq2btCQkBa8Lssnv69QbofD3j/IH+MZGcQh634VY+RoKz3fFMIScoupOs+DOzya9tBGyC/b00bEJOkOZd/VMtHBRDQQ9daNcMXxWB2CmSX730ruW0D+VxwVxfB2YLxU2xW2A778BWhuG3a7g2XjboHOdswwDMbaBrdYE5t7TBg/Q7jLWprwYJbpYgpEABJjV4Rq4m/J5ATZ2W3JPF+Qg+k4pxCWVAVUlfE+XANHrSmvIBqjykCj2AaP17HXz40mn1+ih9T9VHS5gWlB9gqN0rqpxHeOgqrklITGVQW+i+VwxtmWgaapDsWNrwiA6I7icpsKZrdPZUGXEbdIF/kmhDvI6fup6upaWOeof6+2tmaRbUIVHQtg/PPloFjozHpD1SMJd+LkpHmwyIAbnfMG8nnYeuk/isglNpeN/4Bvdh8fBoOUJtNp2M7ynKkx6k0a62OhH0nfaDwUgM27JgZydL52ZiPVSApvb7BDvHdmxko7/KCDZrWWGCBp1wwMCjrTqXq+WhdWs3UZ8HaeHIQ9xuX5WDaybRAUjFIKxnlOFr9+5DWkiSs3En63pVhgeR8Cd5Atlt6Gpt2Mtog14W2TK6yQTL+zM+h3D35PdLFyRoZASmvRe45r0IP4CSYPPH+/3na8srFOaql+Hcudukc2TcqizVmgaj8eVYjFY21+5tb67d74zFsGXo73Uy+MEMsH1oJA42hJBtuEGofZtryy2yOVCbjcFqUuzQPVEeXLOnbTn4HKbM7SjsvuXmTXg4MDwq485QKqSrJR9ashctnzpsW9sm62p5BiZLsOrcxlEzA1t+/YG7YMc3pGVpV3oEomv6jhektRg3o0wPZrernlFWM2cbGmDAsnuyofZPFEYKwzcVxnKHJrT4J/V3kEFaMByRaacJ3XjtZTQ83z/5W3u5nBacEycasCcEMvhZzzP+MJxo0+NAGtuT8qvRzVcE0CiVPbNhAzBv2Zs0rRXfm6spvK/dJHiu9tsHO0Xre2dJ9/UE7Pc/wHzIs9Y24UIxBnMsK8bYdvTwuqZ02qgCpUjbI8R3y6l3NQ4MrkfItGVcLpqvPs+OUaMDnUYpVEuy18eR4WIbSqBmTr1xbXM1M63FefC1325G3qLCuGJJd/WE2CU4B8qWU3QQu4myfGNqII3ljWXwC5QiPUHIX69S76riCDd1JdgnFxwErvUOxS3F5VtDYEktQcUrU9hpPXX004dVKIeuDWxZ3DfzsNTqddFOp9RaUdXXhGJs5Uyfp4qnl0UdkwxwKzOORzA/3kC6TSs5jg1jaUF66UZGpkCMSs2eQhpU2IrYT675yS7gGHZiCov6SzjCyR0WTgbLZH3KwHj7gk5b/sLNAoowYkfO8LE7zvHf/3WVuaaxoL9YF493+HDI59tV0XAXUF5FnKD2euujNEXc7eLRIAFXmkMen7DOqoy+az8ph+4B0v71NzA/PO03dZ6ww5K2lNCYttSRTJ8Xfe13w1AXtYGs2Otxmq0NoYt3LFtkbFI2Ig8NZ61wHV2CsTPuQ/qdN8jgd3T2qUdRbNU7tQvdLhAav7QdmwUYaL/rVB95EV5S0M4tWvQngq729R7Qd+OSwh5Z1OVhRhl1WRW95DV5UJFanuEUCQh12g7Md/QzDVhdiAYTWruVEfKYjlaOLuQ+zHGfvhq4dFsE1UkDZXhAZPPYVse5iiOYG8qq72nJ24Y2ULu6Kq2TVSYJGEWJkeWcLM3XsAGFXiSbBRqn+1XVlnT/kqW8POpa6ZnqI61BRkE7tzKbE6GgR1v+ws37UTTNnVovqXKQ6R6CwGqNTkbgFITW5f6MPLPO50K5eopa1OfF3pxnU4I6jm9IdyE9YNHvIkE7edko2AbbMudGCDXSjH6bArXXa32ZJoBDWFBCQSfXBkyPNo1qvdZLZhxVxtSx7COshGYe/2MS5SundRuNor4hiwdz/PKK8m9nvYwBmLWMLE5nlLchbuCz18ob0YJ8g5cHUaz5PI1xsVG1Bfme2Sncwld00O/embn8hGvFg3ypi1T+7Lou5ZwmrqJEX4EVogn6tlMU3JdnV8foSgiNJ6QK7ffetyqydiEsKm5QCdU0DwqiAi26WmALBWD4llkoaYmlDpRc/3qQXdc2lknLhi2Y3qRDARgHKi1Zng/Z7Ko6KYCkobXrwCJcnvbbN+SJI/esKEHrqA0qHYj863WtnlOh+WIVfa1e0yDu52xDS727jtYGugd6ln1LG0rjBNAPhPSTacF/BkYLPQkw9t2Tqqx08cqH8bo83AUm5euRMzrZWTPbAgJNcJ0gyFxOUF1ooL5Ec/4WfWOR3HyJeg4qQa0TJNx3Qk5peoNZ9Znue4rRyA+cqlYGylK43a4izk3XUPQPBQYk09QOG1qPpv2UiZ08RYi3WVKgi+GcvrttoEI0vzqW3WvuHN1mDHMjOFVhX7cNDWouWUFxRDKqi0U/JaUs1TTIhAYsZbBZVdbrhmV3Wx8YhilEVQrayG7G+impjK/SFITsAG7it6vSsihvFWWYPyiZ34wzRRIRFRDzCuUk44xfIP/GDVivGeabxxk7Y892UlScY90/TpFw0rbHVxQzxCWstrMsxx5EVuMTYBimMKECfvTqilT0ujmD8McyOMV1uV8D57HM2MiPeQ63yOdeAmXoaqiDNAayoPoQWWx9WACUByBpWYd5W5MZ5iYIBZ1C9Bzb/75SgJEYrpQNWWQY5uYI1+gB+veu78iXhyzkDLOYhIJOwTBiLDegJDRIjMSoCwzDLCQTqzuF79GncaAgJOT0VZrklzsYhlksptxrtAed1tn51Xh5iEL+iFV2hllsrGEv4f/+4IgnOMs30fI+schHX9mUr1FVP2ABZ5hvCPqvYv7R+68LDMMwDMMwDMMwDMMwDMMwDMMwDPOH5v/Slj7TcOdbkgAAAABJRU5ErkJggg==">

Community Forum with token rewards that operates on the basis of a decentralized blockchain.

Graphene Forum - Graphene blockchain community forum

Graphene blockchain community forum

Обсуждение управления и развития блокчейна Graphene

Graphene Forum — форум сообщества Graphene на платформе <a href="https://golos.id" target="_new">блокчейна Голос</a>

Присоединяйтесь к чату Graphene в Telegram <a href="https://t.me/graphene_dex" target="_new">@graphene_dex</a>

Форум сообщества Graphene с вознаграждениями токенами, работающий на базе децентрализованного блокчейна.

Graphene Forum - форум сообщества блокчейна Graphene

Форум о Graphene

Форум сообщества блокчейна Graphene

![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/lVGSYsJ.png)

This guide is aimed to be comprehensive and easy enough for the newbies to run a DEXbot in docker on their own server, with local config and its operation log.

This approach allows you to move those two folders to another server, and launch the bot there, without consulting the wiki to find out where the configs and data is stored.

It also allows skipping the configuration of the server and preserve dependencies, as well as avoid conflicts if other applications require different server configuration.

## 1. Server purchase and configuration

If you already have a server, then you can skip this step, but if not here is my ref link to Hetzner: https://hetzner.cloud/?ref=wsKdGpzXMlWr

![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/CMy14ez.png)
This link gives you 10 Euro

![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/UBP0QRp.png)
Click add:
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/cBcvR44.png)

Here is the server config:
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/sICkyvm.png)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/cBdiEma.png)
A config like this costing 4.19 euro/month will be enough:
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/najhF4R.png)

Then click
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/DcJLBuw.png)

Server will be created and you will receive an email like this:
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/kdOOclG.png)

If you are using Windows, you will require PuTTy, add your server’s IP address and use standard SSH port 22
![](https://i.imgur.com/AXqUsRH.jpg)
Save the connection so you can connect quicker in the future.

Then launch the saved connection like this
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/bnbqTlR.png)

You can enable auto login so you do not have to enter **root** username in the console
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/6ffGLkQ.png)
after you will have to go to the Session tab which is located top left, and save the current connection with updated configuration (please note, that first you have to connect to it so you can save it)

Then lets connect
![](https://i.imgur.com/Hw2sRDS.jpg)

if you made an autologin at the previous step, then you do not have to enter your credentials, alternatively if you clicked OPEN, then you will have to enter username in the console. Type root, then press ENTER, and use the password that you received in an email. Copy it with CTRL-C, and paste it into the console, after making sure that it has entry focus after switching from email. It is usual that a right click will paste the password, which will be hidden due to security considerations, afterwards press ENTER.

After changing the password you will have a clean ready Ubuntu 20 server.

## 2. Docker installation

```
sudo apt update

sudo apt install apt-transport-https ca-certificates curl software-properties-common

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable"

sudo apt update

apt-cache policy docker-ce

sudo apt install docker-ce
```
_**Do you want to continue? [Y/n] Y**_
If you see such prompt enter Y, to agree to continue.

`sudo systemctl status docker`

If you need a step by step guide, then follow this link: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04-ru

Here is the docker repository with assembled DEXbot: https://hub.docker.com/r/blckchnd/dexbot

Just use this line to download it to your local server:
`docker pull blckchnd/dexbot`

##   3. Account set up and key import

By default the local data is stored inside docker. To avoid losing configuration and data, it is recommended mounting user directories inside the container as shown below.

First of all, you need to create directories that will contain your configuration and data:
```
mkdir ~/dexbot-data ~/dexbot-config ~/dexbot-data/bitshares ~/dexbot-data/dexbot
touch ~/dexbot-data/dexbot/history.csv
```
Now set the access rights:
`chmod -R 777 ~/dexbot-data/ ~/dexbot-config/`

If you do not have a Graphene DEX account now would be the time to create it. You can follow my referral link below: https://market.rudex.org/?r=xnxt

Please make sure that you’ve created a backup of your wallet keys, and/or saved your password. **Do not ignore the backup suggestion, it is very important**.

It is impossible to restore keys and passwords later. After creating a user account you need to write down WIF active keys, to add them later. Here is the guide on how to export your WIF active key.

Follow the steps:
![](https://i.imgur.com/f1VNhRF.jpg)

next
![](https://i.imgur.com/ITQgT6h.jpg)

![](https://i.imgur.com/ZyVhkAT.jpg)

Here is your WIF active key, that you need for next steps, you have to write it down:
![](https://i.imgur.com/jz42eBp.jpg)

After creating local storage you can add your keys by executing the following script:
`docker run -it --rm -v ~/dexbot-data:/home/dexbot/.local/share blckchnd/dexbot:latest uptick addkey`

![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/yJVZBX3.png)

The console will ask to create a password (passphrase) for encrypting your keys in the local storage and then repeat it. Afterwards import your keys and press ENTER after each key if there are several keys. After you’ve entered all keys press ENTER instead of the key, and you will see something similar to the screenshot above, the accounts that had their keys imported will be detected.

## 4. Configuring DEXbot using CLI

After all your active trading keys have been imported (keys for all Graphene accounts that you plan to use for trading) you can continue setting up trading bots. Execute **CONFIGURE** as the next step:
`docker run -it --rm -v ~/dexbot-config:/home/dexbot/.config/dexbot -v ~/dexbot-data:/home/dexbot/.local/share blckchnd/dexbot:latest dexbot-cli configure`
And enter the **_passphrase_** to continue.

Here you enter the worker name (so you can easily distinguish them in the common list)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/Wl6tMXD.png)

navigate around the buttons with TAB, press OK or ENTER
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/eubUcAA.png)
Here you can pick a strategy for the bot from 3 standard ones.
In this article we will look at the **Relative (Relative order strategy)**

Enter a Graphene account name
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/13KZFkv.png)

import an _active key_ which begins with 5…. (you’ve saved it earlier when you were making backup)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/OJhWah5.png)

You will see a message about successful key import
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/rrwJ8HO.png)

Here you enter the trading pair, that the current worker will operate on, press OK
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/JiICsg7.png)

Leave this part as is, it is the asset that the blockchain “order create” fees are paid with (don’t forget that orders in the blockchain aren’t free). I recommend having some GPH on all the bots for paying the blockchain fees, as it is cheaper than pay from the asset pool, which can also unexpectedly run out. Press OK
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/R2qpFo8.png)

Here in % we set the amount of traded (QUOTE) asset, and the next screen an amount of base asset (BASE) that will be taken into the account by the bot for its operation.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/9ZcifVN.png)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/yh8rbq2.png)

As this example the trading pair is GPH/USDT and as GPH isn’t traded on external markets, I will not specify an external quote feed (NO).
This setting is needed so the bot would understand the current price from another source, which is very handy when you’re trading an illiquid market, and allows the bot to follow the market price, always making sure it keeps its orders above and below that feed price.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/2HuCfDI.png)

next screen will ask for an external quote feed address, which we in our case will leave as is, since from the last setting it is not used, but this step is part of the bot setup via CLI.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/GrnIi0h.png)

here we set the amount of QUOTE asset in the order, and can specify either absolute numbers, as well as %, if in % you will still have to write 10 here. On the next screen we will specify the relative marker for the order.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/YjjqKQ7.png)
YES — is the relative size of the order, from the previous screen. It means that orders will be 10% from the total amount participating in the bot operation (in our case it is 100%),
If we set this to NO, then number 10 from the previous screen would mean 10 of the QUOTE asset, in our case GPH.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/CI53l5N.png)

Spread is the % difference between buy and sell orders
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/lKsPhh9.png)

We will not use dynamic spread, as it requires good understanding for effective use on the market (it is not advised to use for the newbies, and without a good understanding of specifics of the market that you’re setting up a bot for)
https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/YilNi3x.png

Market depth that will be used to change market spread. I am specifying 1000 GPH. In essence this is sensitivity for the dynamic spread. Which is not used in our case, as our spread is a constant.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/pitBEQy.png)

Leave as is, our spread is constant, and this setting is for dynamic spread.
How many percent will the own spread be in comparison to the market spread. Press OK.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/fAjc3Bq.png)

Here we’re specifying the central price, in this case I’ll set a price of 3 cents per GPH (price in BASE asset, USDT).
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/NWNftiQ.png)

Measure the central price by market orders — the valuation is based on closest opposite orders or by depth, in this example we specify NO, let's say we want the central price to be fixed.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/pQt22DD.png)

Depth change — total sum of QUOTE asset (in our case 1000 GPH) by order book depth, that will be measured in central price. In our case this parameter is not used, as in the previous step we’ve specified NO.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/FmEuBFB.png)

Last deal price will be the next central price, this will force the bot to move half a spread each time an order is filled.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/XGT4dqy.png)

Offset of the central price based on asset balances moves the calculated central price up or down, to try and keep the portfolio balanced, so as not to have only one asset on hand, as well as maximizing profits.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/OSvWQOh.png)

Manual center price adjustment allows you to manually correct the orders up or down. Works independently from other offsets and does not negate them. As far as my understanding goes it is an extra setting that allows to set a tolerance on certain markets not to move center price. A deviation during certain market conditions, to make the bot more effective.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/iIJXAEo.png)

Order recreation on partial fill, when a buy or sell order is partially filled.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/RMQYG8B.png)

An order fill threshold in percent, for activation of order recreation (see previous step). Press OK.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/EsmR3vE.png)

Reset orders when the central price changes by more than threshold value (set to False when using external quote sources)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/tYWTKXD.png)

Price change threshold — set central threshold price value, that requires action (from the previous step).
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/FohjMeF.png)

Activation of order expiration override to reset orders in set intervals
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/jw6XPG6.png)

Order lifetime is expressed in seconds and allows resetting orders in desired intervals
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/18d6TaT.png)

Would you like to set up another worker? Reply No.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/6Tougqz.png)

Should it run in the background as a daemon, reply No. We will run it explicitly in the docker.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/D3LKV9e.png)

After successfully completing configuration and saving it, you’ll see a New configuration saved message.

You can launch **CONFIGURE** again to check the list of configured workers and their parameters, or edit previously created worker if you have decided to change it. 

![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/lVGSYsJ.png)
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/5JZkPoB.png)

Here is how you exit the menu:
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/3yccVZS.png)

## 5. Start. Stop. Checking the logs.

To start the bot use the following commands (_passphrase_ here is the password that you set at step 3 for encrypting the keys):

`docker run -d --name dexbot -e UNLOCK=passphrase -v pwd/dexbot-config:/home/dexbot/.config/dexbot -v pwd/dexbot-data:/home/dexbot/.local/share blckchnd/dexbot:latest dexbot-cli run`

To check the logs:
`docker logs -f dexbot`

In the logs we can see what is happening, that the bot has canceled the orders if there were any on the market prior to starting it, as well as created bot BUY and SELL orders.
![](https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/58OMV0G.png)

to exit the log viewing mode press CTRL+C

And this is how it looks in the Rudex trading GUI:
https://images.golos.today/0x0/https://steemitimages.com/0x0/https://i.imgur.com/Zz7ohwq.png

To stop the bot:
```
docker stop dexbot
docker rm dexbot
```

Now you’ve learned how to configure the bot to run in the docker, to launch it as well as to check the logs.

If you need to change the configuration or add a new worker on other markets, first you have to stop and delete the docker using the code above. Then add new workers or edit existing ones and launch them.

You can now disconnect from the server, the bot will operate in the docker on its own.

And going forward, only experience, observation and effectiveness comparison for the setups on different markets will allow you to deeply understand the settings and increase the profits that the bots operation can generate.






























🤖 DEXBot simple VPS guide

Useful articles

![](https://i.imgur.com/OMXItxE.png)

Updated [Google Play](https://play.google.com/store/apps/details?id=org.rudex.app) app (v6.31):

- Added MPA for EUR, RUB  also to defaults markets
- Fixed default select days for APPROVE(3d) and REVIEW(4d) for create Proposals
- Fixed default options for create new gpAsset
- Fixed GUI styles for view Asset Managements
- Changed precisions for some markets
- Changed kline period default to 1D (for graphs)

Updated RuDEX android app (v6.31)

News

Today we've sent CMC next request to add Graphene Blockchain (GPH) token

**ID 441531**



GPH & CMC 

General Discussion

Предлагаются следующие предложения для членов комитета:

**1. Proposal 1.10.35.**
Вывести 165 625,00000 GPH с вестингового баланса, после отработанного воркера


**2. Proposal 1.10.36.**
Востребовать 15 005,00000 GPH из пула комиссий gpGOLD

Востребования части пула комиссий в комитет.

**3-4. Proposals 1.10.38 (gpEUR ) и 1.10.39 (gpRUB)**
Создание gpEUR и gpRUB от комитета. После востребовования вестинга из п.1 на балансе хватит средств для создания этих 2 монет


Предлагаю проголосовать за эти 4 предложений. Обратите внимание, там есть 2 не совсем корректных предложения, в одном я проверял создание из мобильного предложения (1.10.34), чтобы понять и убедиться в его работоспособности и корректности, особено со сроками истечения и принятия, в другом не точная информация для предпочтительного рынка по умолчанию (1.10.37), они дублируются после с исправлениями, за эти 2 голосовать не нужно.

The following suggestions are made for committee members:

**1. Proposal 1.10.35.**
Withdraw 165,625.00000 GPH from the vesting balance, after the spent worker


**2. Proposal 1.10.36.**
Claim 15,005,00000 GPH from the gpGOLD fee pool

Claiming part of the pool of commissions to the committee.

**3-4. Proposals 1.10.38 (gpEUR) and 1.10.39 (gpRUB)**
Creation of gpEUR and gpRUB from the committee. After claiming the vesting from point 1, there will be enough funds on the balance to create these 2 gp-actives


I propose to vote for these 4 proposals. Please note that there are 2 proposals that are not entirely correct, in one I tested the creation from a mobile proposal (1.10.34) to understand and make sure that it works and is correct, especially with expiration and acceptance dates, in the other there is not accurate information for the preferred market by default (1.10.37), they are duplicated after with fixes, you don't need to vote for these 2.

Stakeholder Proposals

Proposals 1.10.35, 1.10.36, 1.10.38, 1.10.39 (RU/EN)

**Предлагаются следующие предложения для членов комитета:**


**1. Proposal 1.10.27.**
Уменьшить комиссию на создание монет
 3 знак - 100k GPH (для большей доступности, а также уменьшения сроков при создании их комитетом, но в то же время сохраняя заградительный барьер от скамеров)

 4 знак - 40k GPH (мотивация как и для 3 знака, только немного бОльшая доступность, может кому то понадобится для своих нужд, чтобы и сделать доступнее и в то же время был заградительный предел от спам-монет)

 5 знак - 6k (тут повышение на 1000 GPH от текущих 5000, но 50% от общей суммы обычно идёт в пул комиссий монеты, которые можно изъять обратно и они не тратятся, таким образом создание простой монеты с кол-вом символов 5 и более будет стоить в районе 100$)


**2. Proposal 1.10.29.**
Востребования остатка пулы комиссий (с gpUSD в комитет - около 70k GPH. Т.к. она почти не нужна, ведь нас gp ассеты без комиссий текущие (gpUSD), а комиссии в GPH за транзакции незначительны, то большую часть считаю нужным вывести, со следующими gp-монетами буду предлагать аналогичный подход.


**3-4. Proposals 1.10.30 (gpSILVER ) и 1.10.31 (gpGOLD )**
Создание gpSILVER и gpGOLD от комитета. После вступления в силу изменений по п.1 и после вступления в силу п.2, на балансе хватит средств для создания этих 2 монет


**5. Proposal - 1.10.32**
Создать воркера на финансирование gpEUR и gpRUB (200k GPH), по моим подсчётам на балансе комитета сейчас около 16k GPH, после востребования баланса остатка комиссий gpUSD там станет около 86k GPH, 46k будут потрачены на создание этих 2 монет. Около 40k останется на балансе комитета.

Воркер предлагаю зафинансировать на сумму 165k GPH.

Время работы воркера
с 1 мая по 11 мая 2022 года, 11 дней,сумма выйдет 165k GPH.

В итоге к тем оставшимся 40k добавится 165k и станет около 205k GPH, после финансирования gpEUR и gpRUB останется незначительная сумма около 5k GPH в комитете.

(после того как воркер будет принят и отработает, будет новое предложение чтобы забрать с вестинга средства на баланс комитета и создать gpEUR и gpRUB)

В итоге 5 предложений. Обратите внимание что предложение 1.10.28 вышло ошибочным, вместо него 1.10.29 (незначительную сумму имеет смысл оставлять для уплаты комиссий в gpUSD, и если они закончатся, периодически финансировать пул)



**The following proposals are made to committee members:**


**1. Proposal 1.10.27.**
Reduce the fee for creating coins
Symbols with 3 Characters - 100k GPH (for greater accessibility, as well as reducing the time frame when creating them by the committee, but at the same time maintaining a protective barrier from scammers)

Symbols with 4 Characters - 40k GPH (motivation as for 3 , only slightly more accessible, maybe someone will need it for their needs to make it more accessible and at the same time there was a barrage limit from spam coins)

Longer Symbols - 6k (here is a 1k GPH increase from the current 5k, but 50% of the total usually goes into the coin's commission pool, which can be withdrawn back and they are not spent, so creating a simple coin with 5 symbols or more will be cost around $100)


**2. Proposal 1.10.29.**
Claiming the rest of fee pool balance (from gpUSD to the committee - about 70k GPH. Since it is almost not needed, because we have gp assets without commissions current (gpUSD), and commissions in GPH for transactions are insignificant, I consider it necessary to withdraw most of it, the next gp-coins will offer a similar approach.


**3. Proposals 1.10.30 (gpSILVER ) and 1.10.31 (gpGOLD )**
Creation of gpSILVER and gpGOLD by committee. After the changes under p.1 come into force and after the entry into force of p.2, there will be enough funds on the balance sheet to create these 2 coins


**4. Proposal - 1.10.32**
Create a worker to finance gpEUR and gpRUB (200k GPH), according to my calculations, the committee balance is now about 16k GPH, after claiming rest of fee pool balance gpUSD, there will be about 86k GPH, 46k will be spent on creating these 2 coins. About 40k will remain on the committee's balance sheet.

Worker proposes funding in the amount of 165k GPH.

Worker time
from May 1 to May 11, 2022, 11 days, the amount will be 165k GPH.

As a result, 165k will be added to those remaining 40k and become about 205k GPH, after financing gpEUR and gpRUB, an insignificant amount of about 5k GPH will remain in the committee.

(after the worker is accepted and worked out, there will be a new proposal to take funds from the vesting to the balance of the committee and create gpEUR and gpRUB)

As a result, 5 proposals. Please note that sentence 1.10.28 turned out to be erroneous, instead of it 1.10.29




Proposals  1.10.27,  1.10.29,  1.10.30,  1.10.31,  1.10.32 (RU/EN)

Create SILVER smartcoin by committee-account

SmartCoin Settings - SILVER

Maintenance collateral ratio 2000
Maximum short squeeze ratio 1100
Feed lifetime 48h
Minimum feeds 7
Force settlement delay 24h
Force settlement offset 2%
Max force settle vol 5%
Short backing asset GPH

Permissions

Allow witnesses to provide feeds: ON
all the rest OFF

Flags

Allow witnesses to provide feeds: ON

all the rest OFF

Market fee 0%

You can cast your vote until 13:00 Moscow time April 7, 2022
Changes take place from 13:00 Moscow time April 11, 2022 if the quorum is reached

Voting can be observed here:
https://market.rudex.org/#/account/committee-account

Committee proposal 1.10.26 (create gpSILVER)

WORKER-REFUND-10years

The previous worker is about to expire on a refund to the budget from the worker budget, so I propose to create a new worker for 10 years with the same parameters as the previous one

Voting can be observed here:
[https://market.rudex.org/#/account/committee-account/voting/workers](https://market.rudex.org/#/account/committee-account/voting/workers)

Worker

WORKER-REFUND-10years

**Suggested parameters:**

membership_annual_fee / membership_lifetime_fee : **3000 GPH**

You can cast your vote until 13:00 Moscow time April 7, 2022
Changes take place from 13:00 Moscow time April 11, 2022 if the quorum is reached

Voting can be observed here:
https://market.rudex.org/#/account/committee-account

Committee proposal 1.10.25

Полезные статьи  

🤖 Запуск DEXbot на VPS в докере

Proposal for committee, changing global parameters:

current:

 "cashback_vesting_period_seconds": 31536000,
 "committee_proposal_review_period": 1209600,


new:

"cashback_vesting_period_seconds": 7776000, 
"committee_proposal_review_period": 604800

Summary:
**Committee proposal review period** decrease by 1 week to 1 week.
**Cashback vesting period** from 365 days to 90

Proposal for committee, changing global parameters, vesting (1.11.1234

Graphene enthusiast from 2016.

I  stand for decentralisation and privacy, without KYC, for private money!

Vote for my committee!

Contact me https://t.me/serdrdoor

GitHub: https://github.com/serdrdoor

Committee Member

alex-pu committee

**Servers specs:**

8 × Intel Xeon Processor (Skylake, IBRS)
31 GB RAM / 236 GB disk space
Germany
Benchmark results summary:
UnixBench - 4517.2
Disk Read - 5246 MB/s
Disk Write - 1696 MB/s
Bandwidth - 947.42 MB/s

**Seed-node:**
116.203.0.169:1666

GitHub: https://github.com/serdrdoor

Contact me  https://t.me/serdrdoor



Witness

alex-pu

![](https://i.imgur.com/nLJzskt.png)

Today we've sent request to add Graphene (GPH) to coinmarketcap (CMC)

![](https://i.imgur.com/f6Rgplx.jpg)

New GPH tracking thanks to [Coinpaprika.com](https://coinpaprika.com/coin/gph-graphene-blockchain/)!

GPH & Coinpaprika.com 


![](https://i.imgur.com/CREmiME.png)


New GPH tracking thanks to [coinranking.com](https://coinranking.com/coin/He0kZRl3Z+grapheneblockchain-gph)!

GPH & coinranking.com 

Recently BLCKCHND donated to the friendly project [Blocktivity](https://blocktivity.info) and now Graphene has become the official sponsor of this statistical site.

![](https://i.imgur.com/7lSIY21.png)

Also, statistics of the activity of the Graphene blockchain in the service itself [became available](https://blocktivity.info/coin/gph_0)

![](https://i.imgur.com/LfDskEH.png)



The Graphene community has become an official sponsor of Blocktivity



Whats new: 

- add link to explorer
- add lex api node
- enable borrow for gpUSD
- enable rank/feeds for smartcoins
- add markets for gpUSD (gpUSD/GPH, gpUSD/USDT)


You can download android app from [**here**](https://play.google.com/store/apps/details?id=org.rudex.app)

Updated Google Play app

Witnesses please setup your price feed for gpUSD here is an open source public script down below 

https://github.com/graphene-blockchain/graphene-pricefeed

1. docker pull blckchnd/graphene-pricefeed
2. copy `examples/default.yaml` to `path_to/config.yml`
3. change _producer_:  `your_witness_name`
4. command:
`docker run --rm -v /path_to/config.yml:/usr/src/app/config.yml blckchnd/graphene-pricefeed graphene-pricefeed update --active-key 5xxxxxxxxxxx`
5. for autoupdate, add command to cron

there are 3 pricing sources for GPH:
RUDEX.USDT
RUDEX.BTC
RUDEX.BTS
(by default all 3 are active)

You can observe and remove/add them as liquidity increases, so that there is no strong disproportion of influence.

Price Feed Script for Graphene

Updated Graphene UI:
https://github.com/graphene-blockchain/graphene-ui/releases/tag/3.3.210901

- fixed a bug when adding a base market
- fixed bug with bots
- fixed bug with scrolling of histories, orders in windows (only in the web version)
- membership statistics from Elastic
- added the ability to download the account history report
- trollbox functioning only in RU-version for all languages
- added notifications at the top
- added ES and another API point from Lex
- icons for gateways instead of individual coins.

At the moment there are 3 categories:

- gp assets (MPA) and core asset GPH – icons by default
- gateway assets – united by the gateway icon/logo (if you want to add your own gateway icon, send pr to rep)
- assets without icon

**New tools:**

**Elastic-api-wrapper**
https://es-wrapper.gph.ai/apidocs/
API wrapper for requests to the Graphene blockchain via Elasticsearch (may be useful for obtaining additional information).

**Explorer**
https://explorer.gph.ai/

**Graphene Account History Exporter**
https://history.gph.ai
Added a separate service for exporting account history to CSV/Excel with the ability to filter by operations.

Update of Graphene services

**Updated RuDEX UI:**
https://github.com/blckchnd/rudex-ui/releases/tag/3.3.210901

- fixed a bug when adding a base market
- fixed bug with bots
- fixed bug with scrolling of histories, orders in windows (only in the web version)
- membership statistics from Elastic
- added the ability to download the account history report
- trollbox functioning only in RU-version for all languages
- added notifications at the top
- added ES and another API point from Lex
- 3 coins have been removed from the listing.

**Updated old RuDEX GUI:**
https://old.rudex.org/

Update of RuDEX

- Added Raven token for crowdfunding, 
- Changed orderbook for donation tokens 
- Fixes

https://github.com/blckchnd/rudex-ui/releases/tag/3.3.210724


New release of the RUDEX desktop version

New release of graphene core wallet with RuDEX gateway and other fixes

https://github.com/graphene-blockchain/graphene-ui/releases/tag/3.3.210724



New release of graphene core wallet

![](https://i.imgur.com/ybSHgrC.jpg)


## **Now you can download updated [mobile version from Google Play ](https://play.google.com/store/apps/details?id=org.rudex.app)**

Rudex mobile app updated to Graphene version

Bitshares Drama

Dear RuDEX users!
On July 15, 2021 due to the low trading volumes and constant problems with the network SMOKE coins will be permanently removed from RuDEX. From June 14, 2021, SMOKE deposits will be unavailable.

We kindly ask you to withdraw all SMOKE funds from your RuDEX accounts till July 15.

SMOKE tokens trades will be stopped forever on July 15, 2021.

Please complete all the necessary operations with your SMOKE tokens prior to July 15, 2021. The support of these tokens will be no longer available starting from that date.

Best regards,
RuDEX Support Team

‼️ SMOKE Delisting Announcement ‼️

Hello everyone!

We congratulate everyone with succesful migration of [RuDEX](https://market.rudex.org/) to **Graphene blockchain**! Starting today, all gateways are operating normally, and all deposits and withdrawals are available to users in full.

As we’ve already mentioned in the previous post, the **USDT (ERC20)** gateway was switched to the **TRC20 **protocol during the gateway migration.

We also like to announce that today we are adding to our range a gateway for the **Tron project token - TRX**.



The following markets have been launched:

[TRX/GPH](https://market.rudex.org/#/market/RUDEX.TRX_GPH)
[TRX/BTC](https://market.rudex.org/#/market/RUDEX.TRX_RUDEX.BTC)
[TRX/USDT](https://market.rudex.org/#/market/RUDEX.TRX_RUDEX.USDT)
[TRX/BTS](https://market.rudex.org/#/market/RUDEX.TRX_RUDEX.BTS)

During the design of the gateway we were aiming to ensure the following parameters:

- Security
- Independency
- Transparency and ease of audit
- Public trading bots
- Strict correlation between amount of tokens in the wallet and on the DEX
- Minimization of the fees
- Ease of use
- Stability
- No KYC, no max. limits

AUDIT: https://audit.rudex.org

Telegram: https://t.me/graphene_dex
Web: https://market.rudex.org
Desctop: https://github.com/blckchnd/rudex-ui/releases



Tron (TRX) gateway on decentralized trading platform RuDEX launched

Good news, everyone!

The time has come! As we have repeatedly declared in our public chats and on the forum, RuDEX is migrating from Bitshares blockchain to [Graphene](https://gph.ai/)

 Migration is planned starting from 12:00 MSK 24.05.2021 (Mon) to 12:00 MSK 27.05.2021 (Thu). Please note that it will take THREE FULL DAYS! During this time all RuDEX gateways will be disabled for deposit/withdrawal, as well as transfer will be disabled for all RuDEX assets on Bitshares.

Such duration is due to the necessity to scan Bitshares blockchain to gather required data to swap RuDEX UIA assets from Bitshares blockchain to RuDEX UIA assets on Graphene blockchain.

After migration the deposits/withdrawals will be restored in full but using Graphene blockchain.

Most public services provided by RuDEX for Bitshares blockchain will be disabled, and there are no plans to enable them in the future.

Assets on RuDEX accounts are eligible for swap if their amount is equal or greater than the minimum amount for gateway withdrawal, information about the minimum limits is available [here](https://audit.rudex.org/).

P.S. To access Bitshares using our platform we will keep [old.rudex.org](https://old.rudex.org/#/) domain, you will be able to use it to access your tokens on Bitshares platform that are not issued by RuDEX. We would like to note that this DNS address will work only as an access point and registration faucet, all other services for Bitshares blockchain will be disabled.

Thank you for your time, and we’ll see you on the other side!
Team RuDEX

Announcement of Rudex migration from Bitshares to Graphene 


Hey everyone!

Today we‘ve officially released Graphene blockchain code to the public on [GtHub](https://github.com/graphene-blockchain). As of this post all lottery participants can access their liquid GPH tokens. You can use the desktop client, located at [GitHub](https://github.com/graphene-blockchain/graphene-ui/releases), or assemble your own build from the sources.

![]( https://i.imgur.com/FFy7ibc.jpg)


Please note: to claim your GPH, you need to do a claim procedure, short instruction is located below.

![]( https://i.imgur.com/qxBVllq.gif)

Everyone who wants to announce their candidacy for witness or committee position is advised to create an announcement thread on the forum and use the link to the thread during witness/committee launch.

The next step in our planned migration to Graphene blockchain would be relocation of RuDEX exchange and gateway to the Graphene blockchain, which we will announce separately.
 
 Happy launch, everyone!



12/04/2021 Graphene (GPH) blockchain launch 

Today we would like to announce our plans on further distribution of GPH tokens. 
 
We'll start with the genesis block, lottery participant list, and their stake in the future blockchain. 
 
Lottery participant:


**№** | **Account name** | **Ticket count** | **GPH drop** | **Lifetime membership (LTM)** | **Public owner key**
------------- |------------- | ------------- |------------- | ------------- | -------------
1 | bot-1 | 776 | 100000 | yes | BTS8JCFpaCgyGjaSWKiKi9g92CVm1pdh4yrXMUwLWFvYCGrqWcpnS
2 | larik007 | 411 | 100000 | yes | BTS5MPmoYxiAyV5L3hYDRtbvnNYjfcyqE5dwsL6iVWASrPi4mCYhC
3 | dima-shares | 306 | 100000 | yes | BTS6VwSf8bfEtJusYUiqgUYUoFGJs4PEyWJ2QTgGHsCCc7qvya9uM
4 | dimsis-p | 284 | 100000 | yes | BTS8e2yD2vDwDv5pUWH5SdyzqhByX6ZaxU5YkobbRpzefjMfa5H4Z
5 | losos-wallet | 233 | 100000 | yes | BTS5Z3Z1B1W1DSceYa7nPTcK5MtuMB3sZsjAKUHXqkHn3LtTEX1wV
6 | dog-a | 171 | 100000 | yes | BTS5LLUhu48MEW3Po8uSN1HQt2j352dC1dprEvcEHERDzcaHTJNKZ
7 | tzehbp3x | 157 | 100000 | yes | BTS81GjvqkUysBGQpSdaM9DUWveF66uHcjTPBoveUdgCHzAQMLk2D
8 | dex-29 | 154 | 100000 | yes | BTS6Gayxr8Edu6acQTDPSq2W1dXATMh1TLMdw3LDVNJryMx319cuS
9 | xnxt | 130 | 100000 | yes | BTS7wNgGQbyCejbRfM4wtYCr45SjWptVa3Pha1x37PUTXncXDKQMe
10 | alex-pu | 124 | 100000 | yes | BTS8JyFVq4dzQnPB7coV9uH8ZKpWh7KDPjcPjgsToQKXdwNkrESXx
11 | onotole | 114 | 100000 | yes | BTS4uz9LpA8LgKuE6UokLmTbKd1UWPvQAGBvx3ZMUvwTWfpyyDwFd
12 | hornedpanda | 104 | 100000 | yes | BTS7t2dGYt81gKzLzWj9KDTwmwaw7b37BgLCZiBLGfFfZrunUN3ii
13 | tnam0rken | 101 | 100000 | yes | BTS7MaCPpqT2M2yBZCwi8jiHshEkpxGMUSB3BxhfbMKw3kTxEHbe7
14 | zhenek | 100 | 100000 | yes | BTS6eiBZoeuzuNnkegr5pm4Qqdg5Ru19kMkiWJZ7iG9rJCihhXr1o
15 | xchng | 100 | 100000 | yes | BTS7nbqZUsEcc6adqB8VFYsLZmfMgJvCEaB1rjgXRipDF47414EaL
16 | dex17 | 100 | 100000 | yes | BTS8bzFsoeX2icJ4WC5ycTVVz4dBLVjJH7UVbyZCNEEAbZNpaMYaN
17 | allforyou1 | 100 | 100000 | yes | BTS4zCymqCphHr4wqmz29wWDxy643xfQ5MgvEKcNc33ZCcSki4hx6
18 | smailer | 99 | 99000 | yes | BTS5K6LvbcgCghGUCqySkkFVpYvGopuW6oqXuB6ytZakECbPwAMCd
19 | ru-dex | 95 | 95000 | yes | BTS7QkckauYLKDjfd3phAPeG6rLCWTNhQ5HEt2hbaYTfRdkTk8CRp
20 | mountart-nsk | 86 | 86000 | yes | BTS8AjM3SemcCdX8KNz66iwfyyFwtRaHRG53sW2VXTWEzWmN5V2Zf
~~21~~ | ~~dusja-1~~ | ~~82~~ | ~~82000~~| ~~yes~~ | ~~BTS7ZQmL44GdN6WH9oraVjr4dWjgkMKRq3gjETNGC4LhgBNcmeJ1w~~
22 | gord1 | 79 | 79000 | yes | BTS6sh6LtwJpnG4mLb4RFr2AttSRX7uR52DQNVAG6viZyTdAbwMaD
23 | zuruk33 | 61 | 61000 | no | BTS5GtydtGzi7LCLcsu926fZf2kjx24tGUKvVhN6mDJ5EHJ2ugKEQ
24 | on1x | 52 | 52000 | no | BTS7dnZfaKRG4N2SNxfAXv9sNYxzAravKuCyTtLJS5kbS2rWYKGET
25 | associate-one | 48 | 48000 | no | BTS6yQWKnNwpQGDmg7P4rsPZBBWJ1NWsvLYenH5XRDWGZMU8GEjWa
26 | captain-different | 45 | 45000 | no | BTS76cSc59LBKNj97HyexaxrTwp9hDquH2qBv95ogcjhj7pj3n1aH
27 | x-captain | 35 | 35000 | no | BTS67tKoDNvo9J7HJnVPqtruv9qxNU3KBqDbs5KPr3UR85ERb5Jep
28 | en1gma | 24 | 24000 | no | BTS62pvcvKSSNRfEC4P5JdQX64HYvizRqkYyFw1ukHraAnxs41f3P
29 | lindsay-golos | 23 | 23000 | no | BTS7MNwQKaybZrBA9z4gurX3PwGUQACUnmDojX34NWxD7QBjbWoZw
30 | lady-nazgool | 18 | 18000 | no | BTS5sDTaBsTjQZtTSmyaPaYmfD9cqrcDL58V8S3KqZ5U46TEPUZ4E
31 | i633 | 14 | 14000 | no | BTS78AJhphpXuBwzq6uXCt6co1FniX6hJTSmFNQrrb5DaEPQPMia9
32 | qq-user | 13 | 13000 | no | BTS5jJz6GiMEEPamPW36AENQkvzeiNyuDSLZt9GL7P28azM9uFXk9
33 | mavrodi-s-p | 13 | 13000 | no | BTS5eeXgeAjGJSAKubYkT8uPSTiCQhxDRHmMvgJGypPEexaGEpAGS
34 | ru-dexorg | 7 | 7000 | no | BTS6n71kiFGtGnygiP6hKeh87sRkEqsdGMyVBgNzYGpc36UZvSyPJ
35 | i-l-i | 7 | 7000 | no | BTS53anj3p5d2ztcnZTh7msUb59qKxYiGPnp69Z48YbTMRjKrzu73
36 | ilicoin | 6 | 6000 | no | BTS5iKtw48EGsYmhaN3bU1M2c9uCvSCjbBzf2wsoMmouXtnRuRAbc
37 | ili-coin | 6 | 6000 | no | BTS6FQtdpneJjcnFYLJkCMu3igfrcAeazPNdzMvU72fPqP5PB6tS5
38 | megasapiens | 5 | 5000 | no | BTS4unUP4bk8nhasA9wFqpMw3ARVadWusbLYNHgg6pkxDYkGqp47S
39 | xchng-mm | 4 | 4000 | no | BTS7DNVyYFw8aaRexuGx9QePhEoxxBbA6bwkxs1A9iCDFW3pAgvjM
40 | sh-ev | 4 | 4000 | no | BTS68rWNWjqyCkMimh5qEKTuVBS2LLhvMSkDtSroXmVXJ4YyTyDbC
41 | loke-e | 4 | 4000 | no | BTS6LxbYVwaFkSTFmfjWrRviufBeXM2TQz57vQCYFgvsjxh4S5kbS
42 | san4ik | 3 | 3000 | no | BTS7feYEg4FUXm6DSG6VqJdwSsYG1n6C4ZgN8ZEEDsejUoqiGYeXH
43 | pmaster555 | 3 | 3000 | no | BTS7SSeBg2DhAHPHxMsxvhpFDXVxcDksGz8cUq8Zn2Y6x87DqwSM3
44 | ilic0in | 3 | 3000 | no | BTS5czxtWL57ruGmSHBheRyyN5YcTTuyc68ocsvBUuoN8C4XNR16V
45 | vnc7 | 2 | 2000 | no | BTS7j2auJ7fFpNb7cznPw43QyjviANyRj2XYFKwmbmBqZK1jVph7U

 
As you noticed all lottery participants, who registered more than 100 tickets were hard capped at 100k tokens. Those, who registered less than 100 tickets their token amount is proportional to the number of tickets bought. 
 

As a bonus ALL who registered more than&nbsp; 75 tickets receive the LTM (lifetime membership), which gives lifetime 80% Graphene network fee rebate.

We would like to invite everyone to join the preliminary discussions, and we would welcome any feedback!

---
**UPD 01.04.21:**

Today it was decided to exclude the **dusja-1** account from the drop, since this account is [confirmed](https://bts.ai/block/51144189), the scammer's account

According to the statement above the final numbers:

Max blockchain supply: 100 000 000 GPH 

Total drop for lottery participants: 2 459 000 GPH 

Therefore the reserve pool will contain 97 541 000 GPH,

Присоединяйтесь к чату Graphene в Telegram @graphene_dex