Skip to content

Instantly share code, notes, and snippets.

@nnmfnwl7
Last active July 17, 2021 22:06
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nnmfnwl7/62ad76031767c16f95b2f4b4f199bc91 to your computer and use it in GitHub Desktop.
Save nnmfnwl7/62ad76031767c16f95b2f4b4f199bc91 to your computer and use it in GitHub Desktop.
fazer dxmakerbot previous work
* fazer-dxmbot-001
-- discussion and development dxmakerbot 001 has been already done.
-- dxmakerbot 001 can be found at https://github.com/nnmfnwl7/dxmakerbot/tree/fazer_dxmakerbot_update_001
* fazer-dxmbot-002
-- working on slow development of upcoming features
-- doing support for ppl who are interested in dxmakerbot
-- div by zero bug fix
* fazer-dxmbot-003
-- working on slow development of upcoming features
-- added add more validations and help messages https://github.com/nnmfnwl7/dxmakerbot/commit/3397670521c511a585beb5d329ab3935d4dec9a0
-- fix dxmakerbot exeption caused by balance-get in case when wallet disconnected https://github.com/nnmfnwl7/dxmakerbot/commit/3397670521c511a585beb5d329ab3935d4dec9a0
-- doing support for ppl who are interested in dxmakerbot
-- merging changes for upcoming dxmakerbot_v3
-- you can find latest version here: https://github.com/nnmfnwl7/dxmakerbot/tree/fazer_dxmakerbot_latest
-- you can find latest beta version here: https://github.com/nnmfnwl7/dxmakerbot/tree/fazer_dxmakerbot_latest_beta
-- dev add reopenfinishednum and reopenfinisheddelay config feature
-- dev add trading boundary config features boundary_*
-- dev upt delayinternal default value from 9 to 3 to increase timers accuracy
* fazer-dxmbot-004 and fazer-dxmbot-005
-- research, development, testing, bugfixing, support, code refactoring, repeat
-- updated reopenfinished to reopenfinisheddelay and reopenfinishednum - finished orders will be reopened after specific number of filled orders or in specific timeout
-- added static/relative and asset-relative trading price boundaries
-- as easiest explanation, boundary features are very useful when you wanna from dxmakerbot to stop working when price of configured asset goes out of boundary (maximum minimum). Like to prevent selling BLOCK under specific or relative price.
-- all new stuff already in community testing pre-beta, details in commit https://github.com/nnmfnwl7/dxmakerbot/commit/7e164021d6a517b1825f49eb150601f4d4ff0e80
* fazer-dxmbot-006
-- research, development, testing, bugfixing, support, code refactoring, repeat, 24/7 bot running and analysis, block dx liquidity support
-- working on dynamic spread(slide) feature fix and update. New params --slidedyntype 'relative'/'static' and --slidedynzero for asymetric dynamic spread(slide) balance. Dynamic slide is functionality which can dynamically update slide when market center price still have no action but one side selling/buying already started. As bot detect unbalanced sells/buys it automatically move order price with dynamic slide as is it configured from +0 dynamic slide up to +max dynamic slide at specified amount.
-- updated internal balance measurement as total, reserved=locked by orders, available=left.
* fazer-dxmbot-007
-- working on <--sellstartmin> and <--sellendmin> which are dynamic order size/dynamic taker size/partial orders.
-- Dynamic order size means, if there is not enough funds to add order with default size by <sellstart (size of first order)> <sellend (size of last order)>, bot will recompute highest size which is available to create and also must meets required minimum order size provided by <--sellstartmin> and <--sellendmin> For example if your bot is configured like <sellstart 300> <sellend 100> <sellstartmin 100> <sellendmin 50> <maxopen 3>. By default will bot try to create 3 orders: 1# maker with size 300, 2# maker with size 150 and 3# maker with size 100. If orders are somehow done, and there is not enough funds to create order ie. 1# at size 300, but available only 51, bot will not create 1# also 2# but last order which is at <sellend 100> <sellendmin 50> and maker size meets minium 50, so order at maker size 51-txfee will be created.
-- Partial orders means, to cooperate with upcoming BlockDX partial orders feature.
-- Dynamic taker size is to cooperate with upcoming makerbot <--takerbot> feature.
-- working on <--takerbot> feature. to "Keep checking for possible partial orders which meets requirements(size, price) and accept that orders."
'If this feature is enabled, takerbot is automatically searching for orders at size between <sellstart-sellend>...<sellstartmin-sellendmin> and at price <slidestart-slideend>+<dynamic slide>*<price> and higher.'
'This feature can be also understood as higher layer implementation of limit order feature on top of atomic swaps on BlockDX exchange, because Takerbot can possible cancel multiple opened orders to autotake orders which meets requirements'
'(I.e. value 30 means check every 30 seconds)'
'By default this feature is disabled.'
-- as always research, development, testing, bugfixing, support, code refactoring, repeat, 24/7 bot running and analysis, block dx liquidity support
* fazer-dxmbot-008
-- at summary: research, development, testing, bugfixing, support, code refactoring, repeat, 24/7 bot running and analysis, block dx liquidity support
-- what consumes lots if time was manual testing upcoming features
-- added <sellstartmin>, <sellendmin>, <takerbot>, <delayinternalerror>, <delayinternalcycle>
-- added dxmakerbot v2 commented configuration examples as howto/examples/bot_v2_sell_block_buy_ltc.py and howto/examples/bot_v2_sell_ltc_buy_block.py
-- refactoring and fixing <boundary> feature
-- fixed bug which was causing dxmakerbot crash when no virtual orders created when takerbot enabled
* fazer-dxmbot-009
-- as long term discussion about xBridge API(handling UTXOs, addresses, left vs reserved balances) i think it was updated as it was needed and new API is already in use by dxmakerbot
-- working on, almost done:
-- component <pricing_storage> which is pricing storage and price update manager, saving bandwidth/data/source-code
-- <sell_size_asset> to be able to set size of orders in specific asset instead of maker
-- updated boundary feature having <boundary_asset> <boundary_asset_track> and <boundary_reversed_pricing>
-- <boundary_start_price> to manually set price of which are boundaries computed
-- <address_only> to limit bot to use and compute funds only from maker and taker address, so users will be able to run parallel bots of multiple pairs on same wallets with separated funds.
-- <partial_orders> which enable/disable partial orders creating with minimum is set by <sellstartmin> <sellendmin>
-- <make_next_on_hit> which enable/disable creating next orders when previous was not able to create because some failed conditions, like not enough funds to to place order.
-- <sell_type>, exp/linear/log orders size distribution type, number between <-1 and 1>. >-1 means maximum exponential to 0 means linear to <1 means maximum logarithmic
* fazer-dxmbot-010
-- mostly finding way to how xBridge API is needed to be updated to system be unified for all layers it will be used by.
-- found some issues why code still not been published as beta
-- for those who are interested in latest biggest dxmakerbot upcoming update:
-- here is last alfa repository commit https://github.com/nnmfnwl7/dxmakerbot/commit/b2b1429abc15ad12bfe7c4b5f5896e9ba9db4164
-- here is alfa repository to watch https://github.com/nnmfnwl7/dxmakerbot/commits/fazer_dxmakerbot_latest_alfa
* fazer-dxmbot-011
-- mostly Testing/debugging/fixing/ dxmakerbot alfa version configured with full 3 wallets(BLOCK/BTC/LTC) to run 3 trading pairs and separated coin resources. Unfortunately without partial orders enabled, but takerbot can do the job.
-- By latest testing dxmakerbot alfa version https://github.com/nnmfnwl7/dxmakerbot/tree/fazer_dxmakerbot_latest_alfa source code has been updated about few fixes and few new debug logs https://github.com/nnmfnwl7/dxmakerbot/commit/d2977532e5829f705d84c0716e6d7ca810e44e78 :
-- fix loop bug when zero balance
-- fix config error when boundary_max_relative is disabled and boundary_min_relative is enabled
-- add more logs for better debugging
* fazer-dxmbot-012
-- debugging and looking for hard to find corner case bug, fixed critical bug causing internal error when order is still in progress but virtual orders hit reset was causing wrong counters, internal checks of bot exit bot
-- commit in https://github.com/nnmfnwl7/dxmakerbot/commit/b1bd86f72b632b8020349f3e332904ba16e8c157
-- runscript helper has been added to clear orders and restart dxmakerbot in case of any exception, corner cases
-- updated configuration examples to correspond runscript usage
-- fix bug to cancel orders with <open> and also <new> status which can cause unpredictible errors/exceptions
-- commit in https://github.com/nnmfnwl7/dxmakerbot/commit/a3f459a47dd2e00b5f376d51cab0258ec4d250ab
-- added <--balance_save_asset> to specify save asset, ie USDT or BTC
-- added <--balance_save_asset_track> to track custom balance save asset price vs maker
-- added <--slide_dyn_zero_asset> to specify in which assset will be dynamic slide zero set.
-- added <--slide_dyn_zero_asset_track> to specify to track slide_dyn_zero_asset vs maker
-- refactoring dynamic slide and balance save feature code and config variables
-- runscript refactoring, addded more logs, updated configuration examples and readme file to match this update
-- commit in https://github.com/nnmfnwl7/dxmakerbot/commit/9b965a00edafb2a8436d1b34d7043432ef3f1b3d
* fazer-dxmbot-013
-- was mostly stuck on burned linux node to be restored and working and be managed over tor. Little bit dxbot code development was done but still not pushed. Previous work was mostly postponed to this month(dep hidden orders >> dep save and restore >> dep staggered >> dep mirroring)
-- research on tor, onion, secure remote ssh management vps/NATed linux nodes over hidden service v3, good practices, screen and output general summed tutorial: https://github.com/nnmfnwl7/documents/blob/master/linux.tor.onion.ssh.blockchain.nodes.gnu.screen.howto.txt
-- ref runscript helper code refactoring https://github.com/nnmfnwl7/dxmakerbot/commit/c580a3728404b564d37b701b3646bf903869347e
-- runscript helper was not able to cancell orders direcly by request so <cancelall> and <cancelmarket> were added https://github.com/nnmfnwl7/dxmakerbot/commit/64993ab9512395b8a18f42e55b704722358a2ae8
-- fixed config verify false error on <slide_dyn_zero_asset> https://github.com/nnmfnwl7/dxmakerbot/commit/d546213696410d17f79511cf17e40c954a4fe8bd
-- running dxbot on BTC/LTC pair with latest alfa version to get results and provide liquidity
* fazer-dxmbot-014
>> mainly two months been researching, developing and testing dxbot and dxbot-setup
>> dxbot-setup in summary >> read dxbot setup readme file >> download dxbotsetup >> edit configuration file >> run dxbot setup on client machine(client and node can be same machines) to remotelly setup your dxbot node like:
>> >> install all needed software packages on destination node
>> >> configure ssh
>> >> generate and export private keys for ssh access without password
>> >> also ability to access your server without having public IP address accessible by private key tor hidden service V3
>> >> also checkout BLOCk LTC BTC PIVX XVG DOGE wallets and build em from source code
>> >> also configure wallets, as clearnet or also tor or also as tor hsv2 node
>> >> also checkout dxbot source code
>> >> also configure all wallets with blocknet dxbot
>> >> also generate scripts to speed up blockchain sync by adding some initial onetry nodes
>> >> also generate scripts to open all software in gui terminal
>> >> also generate scripts to open all software in screen session as daemons
>> >> also autostart dxbot ecosystem in screen session
>> >> also optinally build and running wallets in separated sandboxes to prevent data leaks, hack or prevent badnwidth consuming wallet by download/upload limits
>> >> more features on the fly by development...
>> dxbotsetup initial commit has been pushed: https://github.com/nnmfnwl7/dxbotsetup/commit/69b6b4d13aa1eac066858b00206080c31eeedf50
>> dxbot commits has still not been pushed.
* fazer-dxmbot-015
>> mainly researching, developing and testing dxbot and dxbot-setup
>> more details in commit diff https://github.com/nnmfnwl7/dxbotsetup/commit/f534b690f1fb20decc89b8a58862b1f84f00e2d1
* fazer-dxmbot-017
>> research, development, testing dxbot-auto-setup/dxbot, help/support/QA discord/DM, partial orders and LBC related discussions
>> for more details about RAD, please read last commit here >> https://github.com/nnmfnwl7/dxbotsetup/commit/89912bb20a3ec34d777b599f113eaf3b094590e5
* fazer-dxmbot-018
>> research, development, testing dxbot-auto-setup/dxbot, help/support/QA discord/DM, partial orders and LBC related discussions
>> for more details about RAD, please read last commit here >> https://github.com/nnmfnwl7/dxbotsetup/commit/556b12db43ca86c4c1401abacf1b98314e5963ab
* fazer-dxbot-dxbotautosetup-019+020
>> testing, dxbot-dev, dxsetup-dev, qa, LBC, xbrigde-api optional params....
>> im not sure if i remember all to be reported
>> dxmakerbot https://github.com/nnmfnwl7/dxmakerbot/commit/2daf3847b0637f0b0188a85cb76e66024353fc62
mainly fixing error handling when wallet with high response time causing timeout while xbridge is waiting for RPC answer, was possible causing restored but unhandled open orders + added some code as preparing for multi-bot xbridge API
>> dxbotsetup https://github.com/nnmfnwl7/dxbotsetup/commit/03a1006ab8273771b83934e42cbb9e224a5e5d6d
wallet dat to be restored from client machine where setup was started from
>> dxbotsetup https://github.com/nnmfnwl7/dxbotsetup/commit/8e9d9ae0a8cbec6c7e67dd8712fafa5146e4a693
added deps + autodetect and optionally install GUI dependency packages
>> dxbotsetup https://github.com/nnmfnwl7/dxbotsetup/commit/038b76e61270744a25cce353d7e69a00c2a07e3e
update related to prevent xbridge timeouts on heavy chains
>> dxbotsetup https://github.com/nnmfnwl7/dxbotsetup/commit/ec4efd88e95c07f5e18d0bdba39c30708e05210e
added BTC dxbotsetup, updated deps, added optional debug, updated with proxychains to also setup of your trading environment be anonymous
>> last investigated bug summary for internal xbridge disappearing utxos when orders are created and canceled, details here https://discord.com/channels/819650867807780893/819875302620659712/865163833068617738
https://discord.com/channels/819650867807780893/819875302620659712/865164044658540544
https://discord.com/channels/819650867807780893/819875302620659712/865164414726832130
>> more details in links above
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment