Please Vote For The Latest Community Superblock: 1382400

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 1382400 can be viewed below or on the FORUM forum here. 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.

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

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 1382400

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

Cost: 6500 BLOCK

Proposal: ARBIT-Market-Making-1382400

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)

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 (https://global.bittrex.com/Market/Index?MarketName=BTC-BLOCK )
2. Digifinex BLOCK/USDT (https://www.digifinex.com/en-ww/trade/USDT/BLOCK)
3. Digifinex BLOCK/BTC (https://www.digifinex.com/en-ww/trade/BTC/BLOCK)
4. BlockDX LTC/BLOCK
5. BlockDX BLOCK/BTC
6. BlockDX LTC/BTC
7. BlockDX DASH/BLOCK
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–02–08 17:18:53 through 2020–03–12 20:21:56

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

BLOCKDX:

total_volume_base_currency
BLOCK/BTC 1384.57229
BLOCK/DGB 4.70595
DASH/BLOCK 2.50000
DASH/LTC 0.60000
LTC/BLOCK 280.62524
LTC/BTC 1.50000

total_volume_quote_currency
BLOCK/BTC 0.28358087
BLOCK/DGB 1370.00000001
DASH/BLOCK 142.41599700
DASH/LTC 0.89708800
LTC/BLOCK 10503.99284468
LTC/BTC 0.01049600

Bittrex and Digifinex:

total_volume_base_currency
BLOCK/BTC 18926.586
BLOCK/USDT 2475.090

total_volume_quote_currency
BLOCK/BTC 3.6690015
BLOCK/USDT 3002.5079071

2. Trade counts by trading pair

BLOCKDX:

trade_counts_by_pair
BLOCK/BTC 34 BLOCK/DGB 1
DASH/BLOCK 9
DASH/LTC 6
LTC/BLOCK 484
LTC/BTC 6

Bittrex and Digifinex:

trade_counts_by_pair
BLOCK/BTC 504
BLOCK/USDT 83

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

bittrex 440
digifinex 147
blockdx 540

4. Error counts on BlockDX

19

BLOCKNET address for deposit:
BZvcgfhGazLpYXN8Nag2RkH124T9Wmic2P

— — — —

Proposal Name: blockdx-dev-1382400 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
• Updating electron version
• Partial order tasks
• App zooming
• Start looking into supporting partial orders
• Various bug fixing

— — — —

Proposal Name: buildserver-cost-apr Owner: michael

Cost: 900 BLOCK

Proposal: Build Server

Overview
This 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:
https://gitlab.com/blocknetdx/blocknet/pipelines 2 (new wallet, Blocknet Comet v4)

— — — —

Proposal Name: corgi-april Owner: Crypto Corgi

Cost: 825 BLOCK

Proposal: Crypto Corgi

Overview: Continue managing and growing the Block DX and XRouter 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 ~700–800 followers. We have also had several “viral” tweets (ex. tweet 700+ and 1000+ likes)

Last month was also our best month yet for “Profile visits” at 13,300 and we are on pace for another great month for March.

Our “Profile visit” numbers have been trending upwards ever since inception:

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: 5,205* (as of March 15th)

Block DX Twitter Analytics:

— — — —

Proposal Name: Fazer-dxmbot-005 Owner: Fazer

Cost: 550 BLOCK

Proposal: DX Bot

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
  — research, development, testing, bugfixing, support, code refactoring, repeat
  — stage still in progress

PLEASE READ
As we all know superblock budget is not enough so i considered => costs lowering => longer term development over unknown months.
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 (yyyy.mm)

Overview:

• rolling up dxmakerbot research & development & testing & bugfixing & readme update & examples & info-graphics & support & repeat
• there will be probably two dxmakerbots dxmakerbot.py and dxmakerbot_ng.py to stay with compatibility, than code can be merged into official blocknet git repository
  — (2019.12) updated readme for both versions v1 as dxmakerbot.py and v2 as dxmakerbot_v2.py merged at https://github.com/nnmfnwl7/dxmakerbot/tree/fazer_dxmakerbot_latest
• 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
• update configuration verification
  — (2020.01) added add more validations and help messages https://github.com/nnmfnwl7/dxmakerbot/commit/3397670521c511a585beb5d329ab3935d4dec9a0
• 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}}

“name”:
“sellstart”:
“sellend”:
“selltype”: <float number between -1 and 1. -1 means maximum exponential to 0 means normal to 1 means maxium logarithmic>
“slidestart”:
“slideend”:
“slidetype”: <float number between -1 and 1. -1 means maximum exponential to 0 means normal to 1 means maxium logarithmic>
“maxopen”:
“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

[strategy]
[[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_1382400 Owner: Infinity7592

Cost: 385 BLOCK

Proposal: Ledger

• Can now communicate normally with the ledger with WebHID.
• Added Xrouter support (thanks to adersk)
• 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-apr Owner: michael

Cost: 14500 BLOCK

Proposal: Core Development

March recap
Released Blocknet Comet 4.1 on March 13th! The first half of March has been dedicated to completing the many bug fixes and improvements included in the 4.1 release. Here’s a summary of what I worked on during the past several weeks:

• Service node list protocol
• Improved staking (including new staking protocol)
• Improved service node registration
• New service node screen
• New proposal voting screen (vote on multiple proposals at once)
• Added voting input to servicenodecreateinputs rpc
• Unlock wallet from the top menu
• Fixed headers syncing screen and top progress bar
• Support casting votes from a specific address
• Add proposal status to listproposals rpc
• Improved XRouter ETH calls and Enterprise XRouter Proxy
• New lowmemoryload=1 config option for RPi devices (swap may be required)
• XBridge trading bug fixes, including improved locktime checks (New XBridge protocol version 52)

Review progress in these branches:

• https://github.com/blocknetdx/blocknet/commits/4.1.0

Test builds for the Blocknet 4.1 release can be obtained here:

• https://gitlab.com/blocknetdx/blocknet/pipelines/

April Development Overview
I will be dedicating time to several large development efforts in March/April. First, I have added the service node list protocol upgrade that will allow XRouter libraries to pull the services list on demand. I’m continuing to build out the C++ and GoLang libraries. I have been continuing development on the Enterprise XRouter Proxy (v0.6.2). This will support high traffic service node operators. Second, I will be improving XBridge and Block DX trading. There’s currently some important features that are needed, e.g. supporting persistent storage of orders. This will allow clients to better recover orders after crashes or inadvertently shutdowns. Regarding task priorities, the core team will be providing insight on priorities, especially XBridge and Block DX related. As a result some of my listed tasks may change accordingly.

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-1382400 Owners: hanniabu, 86b, aderks, fattox

Cost: 11510 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
• 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
• https://docs.blocknet.co
• https://blocknet.co
• https://api.blocknet.co
• https://blockdx.com
• https://forum.blocknet.co
• blocknet-blockchain-bootstrap repo
• blockchain-configuration-files repo
• Development
• Partake in XBridge locktime drift discussions and analysis
• XCloud API Documentation Portal updates (DM for more details)
• Ongoing Docker updates
• Investigating and staging decentralized mining pools over XRouter
• Test and dev environment overhauls and rebuilding for expansion
• Test automation staging and building
• Support
• All things v4.0, v4.1, and Block DX support
• Block DX QA:
• Bug fix: Clicking generate new address wasn’t retaining order form fields
• Bug fix: BTC Price showing N/A on active status steps 1/5
• Order form functionality: Retain last price in order form after order goes through
• Warning if asset found with ticker not found in manifest
• App zoom in/out functionality
• Ensure file re-name did not break any DX screens
• Blocknet Core QA:
• New features:
• v6 Staking protocol upgrade
• servicenodestatus ability on collateral client
• lock/unlock menu option
• Service node screen
• new proposal voting screen
• support casting vote from addresses
• xrUpdateNetworkServices
• proposal status to listproposals
• -lowmemoryload starting parameter for low RAM devices (Eg. RPi)
• Failed trade investigating and fixing
• Locktime drift battle testing
• Proposal state testing
• Bugs:
• Prevent vote submission if 5000 BLOCK or less in wallet
• Mac staking crashes
• Vote count discrepancy testing
• Proposal submission character count
• Classic wallet sending funds on cancel when unlocked for staking only
• Re-design headers sync progress bar issues
• Proposal screen sorting and count issues
• Votes pulling in from non-5k addresses
• XRouter issue with setting domain= with domain name and not IP
• XRouter responses with XRproxy hex
• XBridge protocol update to improve locktime drift on slower chains (BTC)
• Improvements:
• servicenodecreateinputs
• Service Node registration
• Re-design dashboard balances updating
• XBridge improvements and edgecases
• Blocknet v4.1.0 RC sanity checks
• XRproxy QA:
• ETH XRouter fixes
• SPV Node XRouter fixes
• Adding tls certs into nginx.conf
• Successfully have XRproxy operating under a domain name
• IP and Domain name http support is working through the Blocknet network
• Domain name https endpoint is available through cURL

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 blocknet.co 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.

Any questions or concerns, feel free to ping me 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-1382400 Owner: 86b

Cost: 1040 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_APR20 Owner: Philip

Cost: 900 BLOCK

Previous, Recent and forthcoming tasks:

• A new article will be published on crypto news sites within 48 hours of this proposal.
• I worked with BeInCrypto to choose BLOCK as the token to watch for March (https://twitter.com/beincrypto/status/1235476438557523968).
• I outlined and commissioned an article for Hackernoon which has now been published here: https://hackernoon.com/cross-blockchain-implementation-on-a-decentralized-service-node-network-8zbp372g
• A new article for the Comet update was published on The Capital here: https://medium.com/the-capital/new-blocknet-governance-is-a-first-for-crypto-and-a-boon-for-blockchain-enterprise-introducing-5975f27eab0e
• I have started work on a comparison of XRouter with other similar projects. This will take the form of a comparison graphic in a similar vain to the DX graphic: https://cdn-images-1.medium.com/max/1600/1*T8KscI52HFjCSe52h6YRhg.png 1
• I have started an accompanying article for the above comparison that examines Blockchain 3.0 projects. Both of these items will be ongoing as they require in-depth analysis and research.
• 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

XRouter — The Biggest Advancement Since Ethereum

Blocknet makes Sia Storage available on the Internet of Blockchains

XROUTER: AN INTERNET OF BLOCKCHAINS VS. AN INTRANET OF BLOCKCHAINS 2

The Evolution of the Decentralized Exchange: A Brief History

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

BLOCKNET RELEASES XROUTER: THE INTERNET OF BLOCKCHAINS EXPANDS

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

Block DX: Saving time, maintaining privacy

BLOCK DX: ULTIMATE TRUSTLESS TRADING OR: HOW I LEARNED TO STOP WORRYING AND LOVE THE DX

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 900 BLOCK from the Superblock (Plus 10 BLOCK fee) @ $0.77 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).

PLEASE VOTE ASAP. MANY THANKS!

— — — — — —