alternative

GDEX

alternative

RUDEX

alternative

SPARKDEX

alternative

GDEX

alternative

RUDEX

alternative

SPARKDEX

Contest Rules

Up to 60,000 BTS every day. Funding by the committee.

2019-10-25 0:00:00 UTC
End date not yet decided.

BTS / [gateways].BTC
BTS / [gateways].USDT
(30,000 BTS each)

Gateways who have interest in participating in the contest please reply to this thread.
Every gateway needs to prove that its gateway assets are fully backed by real assets.

(The lists below will be updated from time to time as the contest progresses)

Qualified gateway asset(s):

SPARKDEX.BTC https://audit.bitspark.io
RUDEX.BTC https://audit.rudex.org/
GDEX.BTC https://www.gdex.io/noticeAssets
GDEX.USDT https://www.gdex.io/noticeAssets

Gateway assets that are replied in this thread buy not yet qualified:
XBTSX.X

Brief

Market makers place orders onto the order book.
The bigger the orders and
the closer the orders to the opposite side of the order book and
the longer the orders lasting on the order book,
the more rewards the owner of the orders will earn.

Details

For each market:
98% of total reward will go to BTS buyers and the rest will go to BTS sellers.
(Note: The committee will have the right to update the percentages as the contest progresses. Updates will be announced in advance.)
After each block is produced, a snapshot of the order book will be captured. Every order on the markets will be scored.

The orders whose size is smaller than 100 BTS will be ignored when calculating.
Get the lowest ask price (LAP) and highest bid price (HBP) of the remaining order book.
For bids (orders buying BTS), order_distance = (LAP - order_price) / LAP
For asks (orders selling BTS), order_distance = (order_price - HBP) / order_price

Group 1: orders whose order_distance is within [0%, 1%] will share up to 53% of total reward;
Group 2: orders whose order_distance is within (1%, 2%] will share up to 25% of total reward;
Group 3: orders whose order_distance is within (2%, 3%] will share up to 12% of total reward;
Group 4: orders whose order_distance is within (3%, 5%] will share up to 6% of total reward;
Group 5: orders whose order_distance is within (5%, 7%] will share up to 3% of total reward;
Group 6: orders whose order_distance is within (7%, 10%] will share up to 1% of total reward.

For each group:
group_score = group_reward_percent * min(1, total_order_size / 1,000,000 BTS).

For each order within a group:
order_weight = order_size * ( 1 + (group_upper_bound - order_distance) / (group_upper_bound - group_lower_bound) )
order_score = group_score * order_weight / sum(order_weight)

For each day:
for each market group, specifically, BTS / [gateways].BTC or BTS / [gateways].USDT,
daily_bids_reward = 30,000 BTS * bids_reward_percent * sum(bids_group_score) / total_blocks_produced_in_that_day
daily_asks_reward = 30,000 BTS * asks_reward_percent * sum(asks_group_score) / total_blocks_produced_in_that_day

For traders:
account_bids_reward = daily_bids_reward * sum(bids_order_score) / sum(bids_group_score)
account_asks_reward = daily_asks_reward * sum(asks_order_score) / sum(asks_group_score)
account_daily_reward = account_bids_reward + account_asks_reward

https://bitsharestalk.org/index.php?topic=29693.75 and following pages.

Can also check blockchain explorers or web wallets:

https://bts.ai/details/account/committee-trade
https://cryptofresh.com/u/committee-trade
https://wallet.bitshares.org/#/account/committee-trade

How to verify the reward data

1. run a patched https://github.com/abitmore/bitshares-core/tree/ugly-3.0 delayed node https://github.com/bitshares/bitshares-core/wiki/Delayed-Node to generate snapshots (update "config.ini" as follows):


                                                # Ugly snapshot start block number
                                                ugly-snapshot-start-block = 42000000

                                                # Ugly snapshot markets
                                                ugly-snapshot-markets = [ ["1.3.0","1.3.861"], ["1.3.0","1.3.1570"], ["1.3.0","1.3.2241"],
                                                ["1.3.0","1.3.3926"], ["1.3.0","1.3.4157"], ["1.3.0","1.3.4198"], ["1.3.0","1.3.1042"],
                                                ["1.3.0","1.3.5144"], ["1.3.0","1.3.5286"] ]

                                                #  "id": "1.3.861", "symbol": "OPEN.BTC",
                                                #  "id": "1.3.1570", "symbol": "BRIDGE.BTC",
                                                #  "id": "1.3.2241", "symbol": "GDEX.BTC",
                                                #  "id": "1.3.3926", "symbol": "RUDEX.BTC",
                                                #  "id": "1.3.4157", "symbol": "XBTSX.BTC",
                                                #  "id": "1.3.4198", "symbol": "SPARKDEX.BTC",
                                                #
                                                #  "id": "1.3.1042", "symbol": "OPEN.USDT",
                                                #  "id": "1.3.5144", "symbol": "BRIDGE.USDT",
                                                #  "id": "1.3.5286", "symbol": "GDEX.USDT",

                                                p2p-endpoint = 127.0.0.1:0
                                                seed-nodes = []
                                                trusted-node = 127.0.0.1:8090

                                                #...
                                                plugins = delayed_node
                                              

2. Run the Ruby script https://github.com/abitmore/bts-mmcontest-scripts
to calculate rewards from the snapshot files.

以主流币交易为切入点,改善内盘的交易广度和深度。

2019年10月25号 北京时间早上 8 点整开始
结束时间待定.

每天奖励上限 6 万 BTS .

理事会账户现有资金,目前各子账户合计约 700 万BTS(不含债仓)。
外部赞助资金,待定。
第一期活动不需要申请 worker 。

BTS/[各网关].BTC
BTS/[各网关].USDT
其中, BTS/BTC 和 BTS/USDT 交易对各 3 万 BTS 奖励 .

第一阶段目的是建设内盘 BTS 与主流币的深度,争取更交易者进内盘买卖 BTS ,争取内盘的 BTS 定价主动权

网关主动报名.
对网关有两点基本要求:
1.保证充提,如果出现技术问题快速响应解决;
2.提供资产证明,确认没有发假币

目前报名并有资产证明的网关资产有: SPARKDEX.BTC https://audit.bitspark.io
RUDEX.BTC https://audit.rudex.org/
GDEX.BTC https://www.gdex.io/noticeAssets
GDEX.USDT https://www.gdex.io/noticeAssets

报名但没有提供资产证明的有:
XBTSX.X

理事会有权根据大赛进展情况调整参赛资产清单

0. 简单来说,就是挂买单有奖。如果买单成交,后果自负。参与者自控风险。
1. 原则:鼓励挂单、鼓励缩小买卖盘口挂单差价、鼓励大资金参与、不鼓励刷成交量,争取形成长效机制
2. 参与者自筹做市资金,实盘操作,自负盈亏,靠实力说话;资金量不限
2.1 越大资金挂单,奖励越高;
2.2 价格离对面盘口越近,奖励越高;
2.3 挂单持续时间越长,奖励越高。
注:只统计当前挂单,不统计成交量

* BTS/BTC 交易对 和 BTS/USDT 交易对各一半奖励 (各 30000 BTS)
 为防止恶意压盘,买盘奖励比例大于卖盘,初始比例 买盘:卖盘 = 98:2
 理事会有权根据大赛进展情况调整买卖盘奖励比例
 11月17日开始买卖盘奖励比例由98:2调整为90:10

* 单笔 100 BTS 及以上的挂单视为有效挂单, 100 BTS 以下的挂单不参与深度计算、奖励计算

* 按照当前挂单到对方盘面最近的“有效挂单”的距离,计算深度
 距离 = 【绝对值(本单价格 - 对方挂单价)】/ 【最大值(对方挂单价格,本单价格)】
 挂单深度分档 / 基准奖励比例
* 距离 1% 及以内的挂单分享最多 53% 的奖励
* 距离 2% 及以内的挂单分享最多 25% 的奖励
* 距离 3% 及以内的挂单分享最多 12% 的奖励
* 距离 5% 及以内的挂单分享最多 6% 的奖励
* 距离 7% 及以内的挂单分享最多 3% 的奖励
* 距离 10% 及以内的挂单分享最多 1% 的奖励

* 每一档内,
如果不到100万BTS的总深度,奖励额 = 基准奖励 * 实际深度 / 100万BTS
(也就是说,如果总深度不足100万BTS,总奖励按比例减少)
如果达到100万BTS的总深度,奖励额 = 基准奖励(也就是说封顶,超过不多奖

* 档内奖励分配
每档内部挂单,按挂单价格离档位边界的距离计算权重,
权重系数 = 1 + (档位上边界 - 挂单价格)/(档位上边界 - 档位下边界)
各挂单按(挂单金额*权重系数)汇总,加权平均,得出各挂单实际奖励金额

* 每天统计发奖。统计周期为格林尼治时间 0 点到 24 点(北京时间8点到次日8点)
发奖数据在英文贴
也可以查 committee-trade 的转账记录.

* 媒体宣传
* 活动期间,在其他渠道投放广告,吸引做市商的同时,也吸引普通交易者
* DEXBot 提供做市机器人技术支持
* 社区保证各水龙头、钱包App、API 节点使用正常
* 社区组织人力解答参与者提问,包括钱包使用、网关使用(充提)、交易返佣机制解释等

活动分阶段进行。 第一阶段,建设内盘 BTS 与主流币的深度,争取更交易者进内盘买卖 BTS ,争取内盘的 BTS 定价主动权
深度不够导致 BTS 价格容易被恶意操纵

现在外盘各大交易所的 BTS 交易对最多的是 BTC ,其次是 USDT ,
我大略看了一下,
有 BTC 交易对的交易所中, Poloniex 深度最好,盘口附近有大约4-5个BTC、150万BTS的深度;
USDT 交易对深度最好的是火币,盘口附近有大约 100 万 BTS 的深度

因此,为了吸引BTS回流内盘,内盘优先发展 BTS/BTC 和 BTS/USDT 交易对,目标是至少达到 Poloniex 的深度。活动奖励也以此目标来设定

第二阶段,考虑人民币/BTS交易对

由于中国交易者比较多,人民币交易对很重要
但 zb aex 刷量甚至发假币,无法参考,内盘 bitcny 因为喂价问题,争议也比较大,因此,需要另外的方案

目前没有完美方案。我个人想象中的备选方案,
1. 由做市商自筹资金,超额质押给受信任的中立机构,内盘发行IOU CNY 用于交易,并负责组织承兑;
2. 以BTC等强势币为抵押品,采用内盘机制抵押出 CNY 智能货币(比如采用GDEX的GCNY或者类似)。但是,内盘抵押机制不完善,特别是抵押线爆仓线没有分离、喂价不准等问题,如果投机者太多,会导致稳定币价格不够稳定,进而影响BTS喂价问题;而参与者太少的话,供应量又有问题

第三阶段,非BTS交易对,初步想法是 bitCNY bitUSD 为基础币种的主流币交易

第四阶段,其他币币交易对

Up to 60,000 BTS every day. Funding by the committee.

2019-10-25 0:00:00 UTC
End date not yet decided.

BTS / [gateways].BTC
BTS / [gateways].USDT
(30,000 BTS each)

Gateways who have interest in participating in the contest please reply to this thread.
Every gateway needs to prove that its gateway assets are fully backed by real assets.

(The lists below will be updated from time to time as the contest progresses)

Qualified gateway asset(s):

SPARKDEX.BTC https://audit.bitspark.io
RUDEX.BTC https://audit.rudex.org/
GDEX.BTC https://www.gdex.io/noticeAssets
GDEX.USDT https://www.gdex.io/noticeAssets

Gateway assets that are replied in this thread buy not yet qualified:
XBTSX.X

Brief

Market makers place orders onto the order book.
The bigger the orders and
the closer the orders to the opposite side of the order book and
the longer the orders lasting on the order book,
the more rewards the owner of the orders will earn.

Details

For each market:
98% of total reward will go to BTS buyers and the rest will go to BTS sellers.
(Note: The committee will have the right to update the percentages as the contest progresses. Updates will be announced in advance.)
After each block is produced, a snapshot of the order book will be captured. Every order on the markets will be scored.

The orders whose size is smaller than 100 BTS will be ignored when calculating.
Get the lowest ask price (LAP) and highest bid price (HBP) of the remaining order book.
For bids (orders buying BTS), order_distance = (LAP - order_price) / LAP
For asks (orders selling BTS), order_distance = (order_price - HBP) / order_price

Group 1: orders whose order_distance is within [0%, 1%] will share up to 53% of total reward;
Group 2: orders whose order_distance is within (1%, 2%] will share up to 25% of total reward;
Group 3: orders whose order_distance is within (2%, 3%] will share up to 12% of total reward;
Group 4: orders whose order_distance is within (3%, 5%] will share up to 6% of total reward;
Group 5: orders whose order_distance is within (5%, 7%] will share up to 3% of total reward;
Group 6: orders whose order_distance is within (7%, 10%] will share up to 1% of total reward.

For each group:
group_score = group_reward_percent * min(1, total_order_size / 1,000,000 BTS).

For each order within a group:
order_weight = order_size * ( 1 + (group_upper_bound - order_distance) / (group_upper_bound - group_lower_bound) )
order_score = group_score * order_weight / sum(order_weight)

For each day:
for each market group, specifically, BTS / [gateways].BTC or BTS / [gateways].USDT,
daily_bids_reward = 30,000 BTS * bids_reward_percent * sum(bids_group_score) / total_blocks_produced_in_that_day
daily_asks_reward = 30,000 BTS * asks_reward_percent * sum(asks_group_score) / total_blocks_produced_in_that_day

For traders:
account_bids_reward = daily_bids_reward * sum(bids_order_score) / sum(bids_group_score)
account_asks_reward = daily_asks_reward * sum(asks_order_score) / sum(asks_group_score)
account_daily_reward = account_bids_reward + account_asks_reward

https://bitsharestalk.org/index.php?topic=29693.75 and following pages.

Can also check blockchain explorers or web wallets:

https://bts.ai/details/account/committee-trade
https://cryptofresh.com/u/committee-trade
https://wallet.bitshares.org/#/account/committee-trade

How to verify the reward data

1. run a patched https://github.com/abitmore/bitshares-core/tree/ugly-3.0 delayed node https://github.com/bitshares/bitshares-core/wiki/Delayed-Node to generate snapshots (update "config.ini" as follows):


                                                # Ugly snapshot start block number
                                                ugly-snapshot-start-block = 42000000

                                                # Ugly snapshot markets
                                                ugly-snapshot-markets = [ ["1.3.0","1.3.861"], ["1.3.0","1.3.1570"], ["1.3.0","1.3.2241"],
                                                ["1.3.0","1.3.3926"], ["1.3.0","1.3.4157"], ["1.3.0","1.3.4198"], ["1.3.0","1.3.1042"],
                                                ["1.3.0","1.3.5144"], ["1.3.0","1.3.5286"] ]

                                                #  "id": "1.3.861", "symbol": "OPEN.BTC",
                                                #  "id": "1.3.1570", "symbol": "BRIDGE.BTC",
                                                #  "id": "1.3.2241", "symbol": "GDEX.BTC",
                                                #  "id": "1.3.3926", "symbol": "RUDEX.BTC",
                                                #  "id": "1.3.4157", "symbol": "XBTSX.BTC",
                                                #  "id": "1.3.4198", "symbol": "SPARKDEX.BTC",
                                                #
                                                #  "id": "1.3.1042", "symbol": "OPEN.USDT",
                                                #  "id": "1.3.5144", "symbol": "BRIDGE.USDT",
                                                #  "id": "1.3.5286", "symbol": "GDEX.USDT",

                                                p2p-endpoint = 127.0.0.1:0
                                                seed-nodes = []
                                                trusted-node = 127.0.0.1:8090

                                                #...
                                                plugins = delayed_node
                                              

2. Run the Ruby script https://github.com/abitmore/bts-mmcontest-scripts
to calculate rewards from the snapshot files.

DEXBot Features

While not necessary to use DEXBot to participate in the trading contest, we do encourage people to try it out. Below is a brief coverage of the main features one can employ to automate their trading strategy.
alternative

Relative Orders Strategy


Relative Orders places two simultaneous offers to both buy and sell at a spread and centre price configured by the user.

DEXBot requires a BitShares account, and encrypts the keys inside secure container software called Uptick.

DEXBot's relative orders strategy is configurable to account for market depth, external CEX feed prices and kill/cancel orders.

Relative orders performs best when in a low volatility market where the RO DEXBot worker satisfies demand to buy and sell at the current price, but are too impatient to wait for a better offer. Relative orders connects with instant buyers and sellers and services their requirement of quick trades.

In volatile times in a market speculators buying a dip or selling a rise are a different kind of trader to those most likely to benefit a Relative Orders strategy. Fast moving prices quickly result in a surplus of one asset vs another, and RO strategies suffer less predictable trades.

alternative
alternative

Staggered Orders Strategy

Staggered orders is a long term strategy that aims to benefit from a mean reversion price chart. It places many orders at a wide range of prices incrementally staggered apart. Staggered orders aims to stay in the market for as long as possible, betting that trading and compounding order-sizes on the up/down noise volatility on top of a long term trend accumulates to a more successful strategy than buying & holding both assets.There are 5 modes available: Mountain, Neutral, Valley, Buy Slope and Sell Slope. For simplicity will cover the 2 most popular ones:

Mountain Mode

alternative

Mountain mode concentrates order size to the centre. Aiming to compound profits from low volatility noise around the centre price. If the price stays the same for extended periods with frequent up/down noise before moving, mountain mode aims to build larger order sizes at prices moving gradually away from the centre. If the price slowly trends in a particular direction, mountain mode can be more effective.

Valley Mode

alternative

Valley mode is a strategy best suited to bootstrapping a new or "dead" marketplace. Valley mode puts more weight on buying very low and selling very high and so loves volatility. Plotted on a chart the order sizes at the extremes of the price range are much higher, falling to a valley of lower order sizes near the centre.

alternative

King Of the Hill

King Of The Hill aims to be the highest order on the books. If anyone at all buys or sells, KOTH aims to be involved. Traders looking to buy quickly but want to save a %, can instead use KOTH to slowly make the trade at the best possible price.

Buy + Sell Mode

Applying this mode with KOTH, DEXBot keeps the sell and buy orders constantly on top of the order books.

alternative

Buy Only Mode

This mode places a buy only order and keeps it on top of the buy order books.

Sell Only Mode

This mode places a sell only order and keeps it on top of the sell order books.

DEXBot Installation Instructions

A complete step-by-step video tutorial on how to install DEXBot on Ubuntu 18.04 (by Canonical) using Oracle VM VirtualBox.
alternative

Relative Orders Setting

Relative Orders settings consist of a series of 20 parameters which can be used to fine tune the behavior of your DEXBot; for an in depth explanation please join our Telegram channels listed at the bottom of this page.

PARAMETERS

Staggered Orders Settings

Staggered Orders settings consist of a series of 9 parameters needed to adjust the 5 strategies modes available; DEXBot can run multiple workers and each worker can run under a different strategy.

PARAMETERS
alternative

Download DEXBot

DEXBot is a FREE market making bot. It runs under Linux, OSX and Windows. Some users were also able to successfully compile it on Rasberry Pi. Just follow the link and download the version for your operating system.

GITHUB
alternative