Community Superblock: 1425600 Please vote!

It’s time to vote for the latest proposals! 

Please note: Voting has changed with the release of Blocknet Comet. Please view the updated requirements regarding voting here.

There is a great responsibility for the community to vote either “yes,” or “no,” on the proposals. It cannot be emphasised enough how much the proposal authors and the Blocknet team relies on the community to vote on project proposals to ensure continued funding for development of the Blocknet.

The proposals for superblock 1425600 can be viewed below or on the forumhere . Please note, proposals are being submitted individually so please make sure you scroll down and take your time to look over each proposal. For any late proposals please check the forum above. 

In the latest wallet voting is now much easier. Navigate to the proposal area:

Open the wallet and in the side menu, go to Proposals. The wallet needs to be unlocked to cast votes. The Proposals screen shows all the proposals submitted to the network. Above the list of proposals there is an option to filter by Upcoming, which displays the proposals that can currently be voted on. Select this filter to view all proposals currently open for voting.

Review the proposals and the amount requested. It’s a good idea to consider the total Superblock budget, the other proposals amounts requested, the priorities of the project, and if the proposal aligns with those priorities and greater vision of the project. The link for each proposal should lead to a description of what the proposal is for with some background information and objectives. The voting system will automatically calculate how many votes you have available according to your balance (1 vote per 5000 BLOCK) and cast your full vote weight when voting (5562 BLOCK balance = 1 vote, 49635 BLOCK balance = 9 votes.

When ready to vote on a proposal, select the Vote button. A popup will appear that will be used to vote from. Select whether you’d like to approve the proposal (Yes) or vote against the proposal (No). After you have selected how you wish to vote, select the Vote button. This registers your vote to the network after the vote transaction has 1 confirmation (about 1 minute). Once you have voted you can change your vote by selecting the Change Vote button and selecting you new vote.

Voting Complete!

  1. Repeat this process for every proposal you are voting for.
  2. Your vote is not counted until the voting transaction fee has 1 confirmation (typically 1 minute), after which your votes will be accounted for.
  3. If you spend any of your 5000 BLOCK inputs after you vote, the vote is marked invalid and you will need to cast your vote(s) again.
  4. If you are staking, your vote will automatically re-cast.

The latest Superblock details are below in alphabetical order:

Superblock 1425600

Proposal Name: ARBIT-Market-Making-1425600 Owner: Arbit

Cost: 6200 BLOCK

Proposal: ARBIT-Market-Making-1425600

Previous Work :
ARBIT Corporation is a Canadian market maker in business since 2015 that has provided $220 Million of trading volume across 9 ALTCOINS to date. We have been providing services to the BLOCKNET community since 2016. We became an early investor in BLOCKNET and have a vested interest in the success and usage of BLOCKNET. We are most excited about the potential of BLOCKDX and are eager to increase liquidity and trade volume on the major cryptocurrency tokens on the BLOCKDX platform.

  1. January 2020 our total trade volume was $21,497 USD equivalent . (Using 2020–02–01 spot prices)
  2. February 2020 our total trade volume was $32,659 USD equivalent . (Using 2020–03–17 spot prices)
  3. March 2020 our total trade volume was $83,115 USD equivalent. (Using 2020–04–14 spot prices)

Overview :
To provide robotic API 24/7 market making services with human supervision and up to $100,000 of our own capital consisting of BLOCKNET, BTC, LTC, DASH, DGB and USDT. Our goal is to increase liquidity and trading volume of BLOCKNET across both Centralized Exchanges and BLOCKDX totalling 9 order books:

Continue Market Making on:

  1. Bittrex BTC-BLOCK ( 1)
  2. Digifinex BLOCK/USDT (
  3. Digifinex BLOCK/BTC (
  4. BlockDX LTC/BLOCK
  5. BlockDX BLOCK/BTC
  6. BlockDX LTC/BTC
  8. BlockDX DASH/LTC
  9. BlockDX DGB/BLOCK

Capital Requirements :
ARBIT will devote a minimum of $20,000 of capital to keep orders up 24/7 across all order books above. The BLOCK cost we are asking for above would cover both human resources to monitor market making as well as any losses incurred to maintain reasonable spreads of 5% or less.

Deliverable for Reporting Period : 2020–03–12 20:21:56 through 2020–04–13 18:36:34

1. Trade volume by trading pair (base and quote currency)


BLOCK/BTC 4915.20553
BLOCK/DGB 0.00000
DASH/BLOCK 0.50000
DASH/LTC 0.00000
LTC/BLOCK 690.67525
LTC/BTC 0.00000

BLOCK/BTC 0.62795375
BLOCK/DGB 0.00000000
DASH/BLOCK 36.24540000
DASH/LTC 0.00000000
LTC/BLOCK 34706.11906429
LTC/BTC 0.00000000

Bittrex and Digifinex :

BLOCK/BTC 53671.509
BLOCK/USDT 2966.780


BLOCK/BTC 6.9227715
BLOCK/USDT 2031.7325799

2. Trade counts by trading pair



Bittrex and Digifinex:


3. Total trade counts by exchange (currently: blockdx, bittrex, digifinex)

blockdx 265
bittrex 224
digifinex 139

4. Error counts on BlockDX


BLOCKNET address for deposit :

— — — — 

Proposal Name: atc-infra-sb1425600 Owner: atcsecure

Cost: 410 BLOCK

Proposal: Infrastructure

Previous Work: blocknet infra hosting, blockdx backend, forum, seed nodes, s3 costs,gitian build server

Overview: Month to Month cost for blocknet related infrastructure, includes s3, blockdx backend, forum, seed nodes, gitian build server

— — — — 

Proposal Name: blockdx-dev-1425600 Owner: 86b

Cost: 2500 BLOCK

Proposal: Block DX Development

Overview :
Block DX requires continued javascript development, maintenance, and bug fixing. This work is being completed by a js developer that has been working with the team on Block DX since January 2018.

Tasks :

  • v1.7 tasks ongoing
  • Electron update bug fixing
  • Partial order tasks
  • App zooming bug fixing
  • Start looking into supporting partial orders
  • Various bug fixing and other DX UI-related tasks as needed

— — — — 

Proposal Name: buildserver-cost-may Owner: michael

Cost: 875 BLOCK

Proposal: Build Server

This CI/CD build and test server is responsible for auto-generating all of the dev builds for Linux, Mac, Windows and is important for QA testing as well as for validating Blocknet’s code on github. It also allows the community to beta test our upcoming releases.

Builds can be reviewed here: 1 (new wallet, Blocknet Comet v4)

— — — — 

Proposal Name: corgi-may Owner: Crypto Corgi

Cost: 840 BLOCK

Proposal: Crypto Corgi Twitter

Overview : Continue managing and growing the Block DX, XRouter and XCloud twitter accounts. This includes drafting engaging tweets, creating images/content, replying the tweets, staying up to date on crypto twitter, etc.

Previous Work :

Since the last Superblock the number of followers of the Block DX twitter account has increased by 646 new followers. We also had a widespread viral tweet with 4,700+ likes and 12,000+ shares.

Last month tied our best month for profile visits, which have been generally trending upwards:

July: 2,992
August: 3,703
September: 2,964
October: 8,834
November 2,272* (proposal was not funded, tweeted occasionally on volunteer basis)
December: 9,435
January: 5,897
February: 13,300
March: 13,300

Block DX Twitter Analytics:

(*to date, April 13th)

— — — — 

Proposal Name: fazer-dxmbot-006 Owner: Fazer

Cost: 2000 BLOCK

Proposal: DX Bot

Previous Work:

All next followed features list will be prioritized on the fly by research and development of dxmakerbot.
Updates of this “rolling up” proposal are market as (


  • rolling up dxmakerbot research & development & testing & bugfixing & readme update & examples & info-graphics & support & repeat
  • there will be probably two dxmakerbots and to stay with compatibility, than code can be merged into official blocknet git repository
     — (2019.12) updated readme for both versions v1 as and v2 as merged at
  • add save and restore orders from file
  • save orders to db before exit, dxmakerbot session will be able to cancel only session specified orders on reconfig/exit/crash
  • add more dxmakerbot events(exit bot events, reset order events, reopen order events)
     — add trading boundaries, relative by % dxmakerbot session
     — (2020.02) added to alfa
     — add trading boundaries, by static value
     — (2020.02) added to alfa
     — add exit bot at events and cancel/notcancel orders on exit…
     — (2020.02) added to alfa as part of config of trading boundaries exit/noexit, cancel/notcancel orders
     — add — reopenafterfinishdelay, reopen finished orders after delay of last filled order
     — (2020.01 003) added to alfa
     — add — reopenafterfinishnum reopen finished orders after specific number of orders finished
     — (2020.01 003) added to alfa
     — (2020.04) all above in pre-beta and manual testing
  • update configuration verification
     — (2020.01) added add more validations and help messages
  • analyze update_balances_unspent() and update_balances_left() possibility
  • update dxmakerbot and XBridge API to handle UTXOs:
     — update XBridge API to work with UTXOs than update dxmakerbot to be more effective to uses whole UTXO with coop of “–sellstart” and “–sellend”
     — We are not sure about if exactly this API calls need, or something like that API calls, this needs more discussion in before proposal:
     First needed XBridge API update is, to dxMakeOrder() be able to create order only from funds specified by dxMakeOrder(…makeraddress…) or THE BEST solution to use funds only from specified UTXO txid like this API call: dxMakeOrder(…makeraddress… txidlist[‘txid1’,‘txid2’]). For this case also new XBridge API call is needed to get ‘listunspent’ from specified coin. This call can be added for example as dxGetTokenBalancesUnspentList(maker, makeraddress) or only maker parameter. Because if dxmakerbot wanna use specific UTXO from XXX-COIN wallet to create order it needs to know UTXOs first. By this API can dxmakerbot be updated to be more specific and also effective by using always whole UTXO values. Also there are more reasons, that you can read in draft of planned proposal below.
     As long as you want to run multiple makerbots with same maker and you wanna save hardware resource by running only one full-wallet from pair, coin addresses needs to be specified separated by makerbot-instance.
  • add configuration argument — strategy {{},{}}
     — dxmakerbot argument “–strategy” is json-style formated argument specifying sequence of orders.
     — This configuration way strategy can be specified like this:

–strategy {{pump and dump orders place first}, { than push some normal orders}, {at the end strategy with some small orders}}

 “selltype”: <float number between -1 and 1. -1 means maximum exponential to 0 means normal to 1 means maxium logarithmic>
 “slidetype”: <float number between -1 and 1. -1 means maximum exponential to 0 means normal to 1 means maxium logarithmic>
 “reopenfinished”: <True/False, reopen finished orders or must wait for any reset event>
 “slide_dyn_enable”: <True/False, include dynamic slide or not, very useful when not applied on pump orders>
 example of config arg — strategy{{“name”:‘normal’, “sellstart”:3, “sellend”:5, “selltype”:-0.5, “slidestart”:1.02, “slideend”:1.25, “slidetype”:0.6, “maxopen”:10, “reopenfinished”:True, “slide_dyn_enable”:True}, {“name”:‘pump’, “sellstart”:20, “sellend”:50, “selltype”:-0.2, “slidestart”:1.3, “slideend”:10, “slidetype”:0, “maxopen”:10, “reopenfinished”:False, “slide_dyn_enable”:False}}

  • add configuration file per dxmakerbot instance by — cfg argument
     — Configuration file per bot is more useful
     — configuration files can have private permissions vs. running process arguments are by OS public
     — example of config file representing strategy argument

 [[push some normal orders]]
 sellstart = 10 # first order in sequence with amount
 sellend = 1 # last order in sequence with amount
 sellstartlimit = 10 # first made order in sequence can accept this amount
 sellendlimit = 1 # last made order in sequence can accept this amount
 selltype = 0 # orders amounts are evenly rising

slidestart = 1.10 # first order placed at 1.1 times more than actual price means +10%
 slideend”: 1.03 # last order placed at 1.03 times more than actual price means +3%
 slidetype”: 0 # orders prices are evenly rising

maxopen = 10 # including borders and range there will be placed this number of orders. <sell-start, sell-end> <slide-start, slide-end>

reopenfinished = false # <True/False, reopen finished orders or must wait for any reset event>
 slide_dyn_enable= false # <True/False, include dynamic slide or not, very useful when not applied on pump orders>
 [[push some big orders]]
 [[push some pump orders]]

by having parallel staggered orders sequences, it will fix discord discussed “PROBLEM (2)” and also increases parallel market liquidity
PROBLEM (2) Problem related to partial order filing. For example someone have 100 BLOCK for sale, and he creates orders at 33+33+33 or 25 25 50 or he do not think about and creates one order at 100. Problem is that most of time here are thousands of people who are interested in to take that order but are not able to accept it because individuals have funds to buy only 10 10 10 20 20 20 and nobody of them can accept one whole order

  • save and restore orders from file
     — In case of bot quit/crash to be able to restore
  • PUMP/DUMP auto management
  • autodetect and precompute possible next pump
  • dxtakerbot/dxmakerbot automatically selling all coins of wallet which is detected as going to dump…
  • feature is to automatically compute top price of next pump and cover it.
  • feature to opposite dxbot side to detect pump/dump to disable dxbot to not make a loss.
  • add log exp normal staggered mods
     — add logarithmic/exponential/normal staggered size of orders
     — add logarithmic/exponential/normal staggered price of orders
  • educational examples & info-graphics & video tutorials how to use dxmakerbot

Possible Next Work Expectations:
 — Purpose of this proposal is to continue with dxmakerbot research, development, testing, bugfixing, support, code refactoring to finish all above features

I believe that i gives you many reasons to vote up this proposal to continue dxmakerbot development and all stuff around.
Thanks for your time & MTFBWY
Hopefully see you later on upcoming dxmakerbot development.

— — — — 

Proposal Name: infinity7592_1425600 Owner: Infinity7592

Cost: 385 BLOCK

Proposal: Ledger

  • Can now communicate normally with the ledger with WebHID.
  • Currently adding code so that the website detects the platform and use the appropriate protocol.


Useful reminders:

  • This new communication protocol is still experimental. So I advise not to release anything until this thing is more mature.
  • The protocol will be available only for Chrome, because it is not a Web standard (W3C).

— — — — 

Proposal Name: michael-dev-may Owner: michael

Cost: 15250 BLOCK

Proposal: Core Development

April recap
This month completed a working alpha version of the C++ XRouter library. This library allows C++ developers to query the XRouter network without having any blockchains installed locally.

Review C++ XRouter library progress in this branch:

Other wallet updates include:

  • Stake to address option
  • Split balance rpc/cli command that allows consolidating and splitting wallet amounts
  • Fixed the service node tab filtering
  • Fixed stake rewards (full 1.0 BLOCK reward, no more network fee)

Review wallet fixes in 4.1.1 branch:

Code sample to get started with C++ XRouter library:

#include <xrouter/xrouterclient.h>#include <cstdlib>#include <iostream>int main(int argc, char* argv[]) {    // Create and start the xrouter client    xrouter::XRouterClient client(xrouter::XRouterClient::defaultOptions());    if (!client.start()) {        std::cout << "Failed to find service" << std::endl;        std::exit(EXIT_FAILURE);    }    // Wait up to 10 seconds for the service to be found    if (!client.waitForService(10000, "xr::BLOCK")) {        std::cout << "Failed to find service" << std::endl;        client.stop();        std::exit(EXIT_FAILURE);    }    // Get the block count for the xr::BLOCK SPV service    auto res = client.getBlockCount("BLOCK");    std::cout << res.write(2) << std::endl;    client.stop();    std::exit(EXIT_SUCCESS);}

April/May Development Overview
I am working to complete the beta version of the C++ XRouter library. I’m also working to finish the alpha version of the GoLang XRouter library. The GoLand XRouter library will allow ETH developers to integrate XRouter into their applications. I’m continuing to improve the Enterprise XRouter Proxy (EXR) and getting that ready for open beta, where community members can run and install EXR servers. Developers leveraging the XRouter libraries will only be able to connect to EXR capable service nodes, so we’ll need community snode operators to get involved with this when we’re ready to release the beta.

Current tasks

  • XRouter C++/GoLang libraries
  • XBridge persistent storage
  • Enterprise XRouter Proxy
  • Bug fixes and optimizations

Other tasks

  • Maintenance and bug fixes on Blocknet products (XBridge, XRouter, XCloud, Block DX)

Upcoming XRouter tasks:

  • Blocknet Name Service (XRouter DNS)

— — — — 

Proposal Name: Operations-team-1425600 Owners: hanniabu, 86b, aderks, fattox

Cost: 9560 BLOCK

Proposal: Operations

We (hanniabu, 86b, aderks, fattox) have decided to submit our proposals as a single group considering how much we rely on each other due to how closely we work together.

Previous Work :

We began contributing to Blocknet in 2017 and are the silent contributors that keep the project running smoothly by working on a range of items from administrative tasks, to documentation, to support and QA. Below is a summary list of items we have worked on in the past Superblock period.

  • Admin, project forecasting, & strategy
  • Core team strategic discussions
  • Review/finalize the newsletter
  • Submitted newsletter and release emails
  • Coordinate with potential partners to be named later
  • Exchange applications submitted
  • Ongoing reaching out to various sites featuring Blocknet content that needs updating
  • Maintain Blocknet email
  • Organize and send payments for articles
  • CFA voting and spending sheet updates
  • Review release posts and articles
  • Publish Blockfolio posts for new releases and news
  • Sharing and analyzing competitor research
  • Block DX task management
  • Release announcements

Documentation & site maintenance


  • Blockchain maintenance scripting
  • Test automation building ongoing
  • EOS chain management tweaks
  • XCloud API Documentation Portal updates (DM for more details)
  • Ongoing Docker updates
  • XRproxy staging
  • Test and dev environment overhauls and rebuilding for expansion


  • All things v4.1 and Block DX support

Block DX QA:

  • Electron Update testing
  • App zoom in/out functionality feature testing

Blocknet Core QA:

New features:

  • Staking protocol upgrade monitoring
  • Battle test new splitbalance feature
  • Verify vote-on-orphan fix working correctly
  • Testing -staketoaddress= feature


  • Mac staking crashes
  • Investigating and addressing various DX canceled trade issues
  • XRouter responses with XRproxy hex


  • Block DX ongoing improvements
  • Blocknet wallet ongoing improvements
  • Redesign wallet UX improvement documenting
  • Block DX UX improvement documenting

Blocknet v4.1.0 sanity checks

XRproxy QA:

  • ETH XRouter fixes
  • SPV Node XRouter fixes
  • XRproxy under domain name troubleshooting

Overview :

The following list are main items we plan to be working on in the following Superblock period. Keep in mind that some of these may not be completed this upcoming Superblock period, may be pushed back due to a change in priority, or may be ongoing long term items.

  • Continue the ongoing tasks mentioned in the “Admin, project forecasting, & strategy” above
  • Continue the ongoing tasks mentioned in the “Documentation & site maintenance” above
  • Complete setup for XR Proxy for ETH nodes to continue discussions with interested parties
  • Setup snode groups behind a domain
  • Continued XBridge, XRouter, and XCloud testing and QA
  • Continued Block DX QA
  • Continued wallet release QA
  • Complete Block DX localization support
  • Organize discussions on roadmap refinement
  • Continue to work on the new content
  • Testing environments — Installation/config/maintenance/expansion of all relevant systems.
  • Auto configuration (wizard) updates testing and QA.
  • Other bug reporting, error tracking, and logging + any other relevant QA tasks with UAT/devs.
  • Partake in any BizDev/partnership discussions with potential partners.
  • Integration strategy — Including future platform investigation/testing within UAT (ETH, EOS and beyond).
  • Product analysis — Related to the areas both the above (external products) and below (our products). Discussions within the team on technical considerations.
  • Assisting in any efforts we make towards pushing awareness of Blocknet throughout the communities of our supported projects and partners, as well as towards fresh eyes, by working with new partners and influencers where advantageous. Co-marketing efforts may be taken up when deemed to be beneficial.
  • Collaborating on content creation for Blocknet’s Social Media, to aid in driving traffic to our site and community channels.
  • Collaborating on other developmental/marketing strategies and initiatives, with both the Strategy group and the team as a whole.
  • Collaborating on the creation and maintenance of documentation: EG Tutorials, resources, informative articles and other content, for both our community and a wider audience.
  • Collaboration and communication with current partners, delegates and other teams we work with.
  • Dealing with any necessary discussions and negotiations undertaken with any other potential partners and third-parties who would like to work with us. EG: Exchanges, dev teams and any other interested parties.
  • Communicating closely with content creators to arrange the creation of works (videos, podcasts, articles), focused on promoting Blocknet to the masses.
  • Coin Announcements lifecycle: from initial integration/QA to community/partner outreach and coordination of announcements/support. Creating ANN media.
  • Helping to support and promote the use of Block DX to communities that are integrated in to our protocol, both old and new. Using raffles, airdrops, tips (etc) as a way to enable people to try the DX using these small portions of BLOCK as trade-fees.
  • Support — Both within the community and also helping out partners who are interested in testing our products.
  • Improved Service Node operator communication
  • Service Node operator tools

Any questions or concerns, feel free to ping us at any time!

The amount requested for this Superblock is a retainer for hanniabu, 86b, aderks, and fattox to continue contributing to this project.

— — — — 

Proposal Name: proj-costs-1425600 Owner: 86b

Cost: 850 BLOCK

Overview :

This proposal is to cover our AWS, cloud services, and MailChimp project costs for this Superblock period. Services include:

  • S3 Data Transfer
  • S3 Storage
  • EC2 costs
  • Various AWS fees and utilities
  • VPS addnode support + testing servers
  • E-mail subscription services

— — — — 

Proposal Name: SocialPhilip_MAY20 Owner: Philip

Cost: 1100 BLOCK

Previous, Recent and forthcoming tasks:

  • I completed a new article ; “The Blocknet Protocol: This Is What A Decentralized Infura Looks Like” which was published on multiple Crypto sites. A partial list includes The Merkle, Blockmanity, Nulltx 1 and thebitcoinnews. It was also published in various languages including Italian, Spanish and Indonesian.
  • I completed and published a much longer full length version of the article on our blog and website that included more details, more links and more sources which can be seen here .
  • The in-depth article comparison of XRouter with other similar Blockchain 3.0 projects is progressing well. Word count currently stands at over 4700.
  • An accompanying graphic in a similar vain to the DX graphic (*T8KscI52HFjCSe52h6YRhg.png 1 ) will also be produced.
  • I published the regular newsletter and proposal summary updates and will continue to do so.

A selection of previous articles and press releases I have written:

It’s time to stop learning lessons the hard way: Leave centralized exchange hacks behind and enter a world of security and peace of mind with Block DX 1

XRouter — The Biggest Advancement Since Ethereum

Blocknet makes Sia Storage available on the Internet of Blockchains


The Evolution of the Decentralized Exchange: A Brief History

Exchange Hackings, Security and Freedom: Why Would Traditional Exchanges Embrace a Decentralized Exchange?


Introducing XRouter. Developers Can Now Mix And Match Any Blockchain Via The World’s First Blockchain Router

Block DX: Saving time, maintaining privacy


Overview :

  • Maintain and manage the social media profile of Blocknet on our main website blog pages, Facebook, Twitter, Reddit, BTCTalk, Youtube, Medium and other platforms.
  • Ensure communications from the developers and marketing team can be transmitted in a clear and timely manner to the community.
  • Respond to the community.
  • Compile and write regular newsletter and proposal summary.
  • Contribute to various marketing materials and initiatives.
  • Write press releases and news updates.
  • Write and create articles for specific initiatives.
  • Manage, source, correspond and coordinate payments to news and media outlets.
  • Maintain various internal spreadsheets.
  • Participate in strategy discussions as part of the strategy group.

Cost Assessment:

A fixed amount of 1100 BLOCK from the Superblock (Plus 10 BLOCK fee) @ $0.80 per BLOCK. I work between 1 hour and 5 hours on BLOCK items every day.

— — — — 

We have created a separate proposal notification email alert reminder that snode owners can sign up for here so they do not forget to vote.(This email is separate to the Word on the BLOCK newsletter email).


— — — — — — 

Download Blocknet

Wallet (4.3.1)
Block DX (1.8.0)

Setup Guides