Please Vote For The Latest Community Superblock: 1252800

Hello Snode owners! It’s time to vote for the latest proposals!

There is a great responsibility for Service Node (Snode) owners to vote either “yes,” or “no,” on the proposals. It cannot be emphasised enough how much the community as well as the Blocknet team relies on Snodes to vote on project proposals to ensure continued funding for development of the Blocknet.

The proposals for superblock 1252800 can be viewed below or on the NEW 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.

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

Click the “Vote” button for a proposal you wish to vote on and choose “yes”, “no” or “abstain” to vote. (If voting for multiple nodes or a vps, check “Vote many”.)

If using an older wallet, follow the instructions on how to vote for each proposal below.

The latest Superblock details are below in alphabetical order:

Superblock 1252800

Proposal Name: 86b-1252800 Owner: 86b

Cost: 8120 BLOCK

Proposal: Operations

The base code update (and many other updates including the governance moving completely on-chain) is on the way! One focus this next month will be making sure all snode operators and the community alike are completely up to speed as this upcoming release will lay the foundation for an enterprise-level XRouter product. Because of this, dev support and XRouter integration efforts will be given priority this next quarter.

Overview :

• Bitcoin v18 codebase testing.
• XRouter/XCloud testing and QA.
• Block DX UI QA.
• Wallet/Client release QA.
• Auto configuration (wizard) testing and QA.
• Testing environments — Installation/config/maintenance/expansion of all relevant systems.
• 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!

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: 86b-1252800, type the following command:

mnbudget vote 64e52ad9d5410fb11710adcb3f2b8760238bac7acff614db888c17cefc386656 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote 64e52ad9d5410fb11710adcb3f2b8760238bac7acff614db888c17cefc386656 yes/no

— — — —

Proposal Name: aderks-ops-1252800 Owner: Aderks

Cost: 1667 BLOCK

Proposal: Operations

Background

I’ve been around since the inception of Blocknet in 2014 (Blocknet’s ITO) but did not start contributing until I saw a need in 2017. The first moment where I knew I was hooked on helping the project was when Dan asked for volunteers to help test a trade on the DX.

December Work:

• Block DX QA:
• Finished localization QA (except for Order Form window)
• dxGetNewTokenAddress integration (auto-create addresses)
• 1st QA run through of dxGetNewTokenAddress button
• 1st QA run through of CloudChains Litewallet config wizard support
• Blocknet Core / V18 upgrade QA:
• V18 governance edgecases/battle testing
• V18 main-net testing:
• Windows staking
• Staking edgecases
• Mainnet servicenode setup
• Servicenode registration fixes
• Feature to re-register snode on client restart
• Mainnet XRouter/XCloud/XBridge
• XRproxy container
• Win & Linux classic=1
• Fee rate estimation fixes
• General bug fixes for future RC
• Dev support gearing up for release
• Documentation
• Mainnet client screenshots for Service Node and Governance docs
• Finalizing some questions for Service Node and Governance docs
• Compiled screenshots for Hanni
• XCloud API Documentation Portal
• Progress can be viewed here: https://10f0776e.ngrok.io/ 6 (link is subject to change as this is still in the developing stage)
• Note: Blockchain and Oracle API calls will be separated on different pages
• Blockchain XCloud API calls
• Oracle XCloud API calls
• Rough implementation, still need to QA, proof read, re-organize pages.
• TO DO:
• Finish Blockchain API calls
• Intro page
• Setup page
• Paying for HTTP requests instructions
• GitHub README.md for 3rd party operators to submit their supported calls

Cost:

• 1667 BLOCK
• 20% pay reduction due to less time being online because of the holidays
• SB payout calculated using $1 USD/BLOCK
• Feel free to ask me publicly or in DM what I am currently working on

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: aderks-ops-1252800, type the following command:

mnbudget vote f734a5da3a58a7542046d9299a0d4e73603cc878bf40352ab6f1ae89558dcc2d yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote   f734a5da3a58a7542046d9299a0d4e73603cc878bf40352ab6f1ae89558dcc2d yes/no

— — — —

Proposal Name: atc-1252800-infra Owner: atcsecure

Cost: 1760 BLOCK

Proposal: Support Infrastructure

Previous Work: Atc-dec-sb1209600

Overview: Covers infrastructure costs for BlockDX, S3 Hosting, Forum and all other related items. This SB also includes costs for the gitian updates require for the v4.0 codebase, as well as the infra costs related to that effort (ec2 compute costs)

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: atc-1252800-infra, type the following command:

mnbudget vote   bc8b0e11f418803bf31b2e575a2f100491345a0f29e3c863f0047a5b98ee2afa yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote   bc8b0e11f418803bf31b2e575a2f100491345a0f29e3c863f0047a5b98ee2afa yes/no

— — — —

Proposal Name: blockdx-dev-jan-20 Owner: Hanniabu

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:

• Wrap up 1.6.0 release (contains updates for 4.0.0 wallet, localization integration, dxGetNewTokenAddress integration)
• Review work on Litewallet auto setup
• Additional misc bug fixes

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: blockdx-dev-jan-20, type the following command:

mnbudget vote  718ecd6845c927367b299c6b84723e021e26abcf29b98c6e13c7a59e926f28df yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  718ecd6845c927367b299c6b84723e021e26abcf29b98c6e13c7a59e926f28df yes/no

— — — —

Proposal Name: buildserver-cost-jan Owner: michael

Cost: 980 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 (new wallet, Blocknet 4.0)

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: buildserver-cost-jan, type the following command:

mnbudget vote  aeed5446267aa3d709805bc78d0a2d3fcfd2547507f3a72966e9b53c6b649f47 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  aeed5446267aa3d709805bc78d0a2d3fcfd2547507f3a72966e9b53c6b649f47 yes/no

— — — —

Proposal Name: corgi-jan Owner: Crypto Corgi

Cost: 690BLOCK

Proposal: Crypto Corgi

Overview: Continue growing and managing the @BlockDXExchange twitter.

This month (with 8 days still left to go) is well on track to be our best month yet:

Previous Work: Creating and growing the @BlockDXExchange Twitter account over the last 6 months into the recognizable and influential account that it is today.

See previous proposals for more information on previous work: October, July/August, September and December

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: corgi-jan, type the following command:

mnbudget vote  11fb0ee090455cc24a4d5642d39cde6099b0db0908463d9f3ff67e94edcc5708 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  11fb0ee090455cc24a4d5642d39cde6099b0db0908463d9f3ff67e94edcc5708 yes/no

— — — —

Proposal Name: fazer-dxmbot-003 Owner: Fazer (Discord)

Cost: 550 BLOCK

Proposal: Block DX Maker 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

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.

Overview:

• dxmakerbot.py code needs more research & development & features & testing & readme & examples & info-graphics
• 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 002) 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 1
• 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 “–sellmin” and “–sellmax”
• analyze update_balances_unspent() and update_balances_left() possibility
• add configuration argument — strategy {{},{}}
• add configuration file per dxmakerbot instance by <–cfg> argument
• 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 trading boundaries, relative by % dxmakerbot session
• add trading boundaries, by static value
• 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 more dxmakerbot events(exit bot events, reset order events, reopen order events)
• update configuration verification
• educational examples & info-graphics & video tutorials how to use dxmakerbot

More Details:

• 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.
• added 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
• add more dxmakerbot events(exit bot events, reset order events, reopen order events)
  — exit bot at events and cancel/notcancel orders on exit…
  — add — reopenafterfinishdelay, reopen finished orders after delay of last filled order
  — add — reopenafterfinishnum reopen finished orders after specific number of orders finished
• educational examples & info-graphics & video tutorials how to use dxmakerbot

Possible Next Work Expectations:
— Purpose of this proposal is to continue with dxmakerbot development and 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.

dxmakerbot 001 — non paralelized orders

dxmakerbot 002 — few strategies(orders sequence) parallelization examples

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: fazer-dxmbot-003, type the following command:

mnbudget vote 3c3d504ce9b3a9a1174ad15d714fc831f0f5be9a85e1c0c0d52adbb4397f6222 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote 3c3d504ce9b3a9a1174ad15d714fc831f0f5be9a85e1c0c0d52adbb4397f6222 yes/no

— — — —

Proposal Name: hanniabu-1252800 Owner: Hanni Abu

Cost: 4000 BLOCK

Proposal: Core Contributions

Previous Work:
I began contributing in August 2017 when I saw there were areas the project could use help in. The first thing I worked on was an informational website (blocknetprotocol.com) since informational resources we lacking. This led to submitting my first Superblock proposal that next month for further contribution.

Since then I have been responsible for multiple projects and tasks, as well have assisted in others. Some of these items are as follows:

• API documentation (https://api.blocknet.co/)
• New configurations file format: https://github.com/blocknetdx/blockchain-configuration-files
• Compose documentation (https://docs.blocknet.co)
• Block DX website (https://blockdx.com)
• Compose content
• Compose specifications
• Wallet QA (MacOS)
• Block DX task management, development, and QA (MacOS)
• Website development
• Participate in interviews
• Roadmap discussion
• Manage and organize files and documents
• Review announcements and publications
• Convention prep, attending convention, and followups
• Newsletter content, review, and submission
• Article reviews
• Release announcements, posts, and emails
• Respond to questions from the community
• Respond to emails
• Exchange communication
• Fill out applications and forms

Below is a list of items I have been working on the past Superblock period.

• Daily intra-team communication and coordination
• Reviewed/finalized the newsletter
• Submitted newsletter email
• Continued documentation
• Maintain existing documentation
• Maintain blockchain-configuration-files
• Maintain and update bootstrap files
• Maintain API documentation
• Block DX website maintenance
• Block DX QA, release, manage tasks
• Roadmap revision

Overview:
As a core contributor of Blocknet, I take part in many daily tasks that help keep the project running smoothly, as well as larger tasks that move Blocknet forward. Putting in an average 60 hours a week, I partake in projects that build Blocknet’s foundation and assist in other projects in order to help meet objectives. This proposal is for compensation to allow me to continue contributing to Blocknet for the next upcoming Superblock period.

I have a technical background with a degree in mechanical engineering, prior development experience, and have spent a few years a a few early stage startups (pre and post seed round). This experience helps in various aspects of the project including working in a fast-paced environment, wearing multiple ‘hats’, pivoting priorities and tasks, understanding the project technicals and vision, communicating the different components, conveying concepts into diagrams and text, and budgeting and financials.

Attention to detail is another useful trait. When reviewing interface UI and user experience, performing QA, writing specifications and documents, and communicating concepts, this attention to detail is important as it’s typically the intricacies that make a difference.

In addition to daily tasks, the following list are main items I 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.

• Manage Block DX tasks
• Continued documentation and tutorials
• Continued Block DX website development
• Roadmap revision

The amount requested for this Superblock is a retainer to continue contributing to this project.

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: hanniabu-1252800, type the following command:

mnbudget vote  15b325060ed8505d1df468f877b0ef3592f52ab69997a49fb23ce8902c142aa4 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  15b325060ed8505d1df468f877b0ef3592f52ab69997a49fb23ce8902c142aa4 yes/no

— — — —

Proposal Name: infinity7592–1252800 Owner: Infinity7592

Cost: 385 BLOCK

Proposal: Debugging

• Ledger issued a new communication protocol to fix the fact that the u2f communication
  protocol is broken.
• This new communication protocol is still experimental.
• Currently testing whether it works or not…
• Initial testing suggests I can exchange basic data at the very least.
  As for more complex communication, it still remains to be seen…

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: infinity7592–1252800, type the following command:

mnbudget vote  c43bb39713a3cfb84070997ce8acc2e18d5b0106ff9f3b631216cd6038f2fe75 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  c43bb39713a3cfb84070997ce8acc2e18d5b0106ff9f3b631216cd6038f2fe75 yes/no

— — — —

Proposal Name: michael-dev-jan Owner: michael

Cost: 16800 BLOCK

Proposal: Core Development

December recap
In December I’m continued working on the new Blocknet 4.0 release (formerly referred to as v18) that we are planning on releasing in January. This work includes fixing bugs discovered by the QA team as well as stability improvements and adding support for OSes including Windows, ARM, Raspberry Pi, Mac and Linux (Xenial, Bionic, Debian). I also implemented unlock for staking only feature on the 4.0 codebase. Blocknet 4.0 was also added to the main blocknet repository and can be reviewed here: https://github.com/blocknetdx/blocknet/commits/4.0.0 1 Test builds for the upcoming Blocknet 4.0 release can be obtained here: https://gitlab.com/blocknetdx/blocknet/pipelines/ 1

All Items in the Core Development task summary have been completed:

• New basechain implementation (COMPLETE)
• PoS upgrade (COMPLETE)
• Service Node system (COMPLETE)
• Governance system (COMPLETE)
• XBridge (COMPLETE)
• XRouter, XCloud (COMPLETE)
• Wallet Redesign integration (COMPLETE)

January Development Overview
Release Blocknet 4.0! Immediately after the new wallet release I plan to begin developing the XRouter libraries that will allow developers to query the network without any wallets installed locally. This will improve support for enterprise customers and server environments. I will also be working on bug fixes on the new 4.0 wallet pending issues reported by users.

Current tasks

• Blocknet 4.0 release
• Vote-on-stake feature
• Bug fixes and optimizations

Other tasks

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

Upcoming XRouter tasks:

• XRouter C++ library
• XRouter golang library
• Blocknet Name Service (XRouter DNS)
• Nginx support (COMPLETE)
• URL plugin type (COMPLETE)

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: michael-dev-jan, type the following command:

mnbudget vote  282d774b5dcdaab3a3a59faa12443b9b43f47b067f43cf0a47f1079c50063f09 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  282d774b5dcdaab3a3a59faa12443b9b43f47b067f43cf0a47f1079c50063f09 yes/no

— — — —

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

Cost: 1100 BLOCK

Proposal: Project Costs

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

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: proj-costs-1252800 type the following command:

mnbudget vote  5a81f62aee632d80c7061087a4d2ad785e622962c3a076e4bc5cfdcf571a8019 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote  5a81f62aee632d80c7061087a4d2ad785e622962c3a076e4bc5cfdcf571a8019 yes/no

— — — —

Proposal Name: SocialPhilip_JAN20 Owner: Philip

Cost: 1100 BLOCK

Proposal: Copywriter, Social media Admin

Previous, Recent and forthcoming tasks:

• 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.
• A new article on what a decentralized Infura might look is in the final editing stages. This will be published at the appropriate time to tie in with other events.
• A new article on the v18 BTC base chain update and governance is currently in the editing stages. This will be published at the appropriate time
• 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 this year:

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

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 1100 BLOCK from Superblock (Plus 10 BLOCK fee) @ $0.64 per BLOCK.

How to vote:

• If not voting via the proposal area in the wallet (as described above) you can instead vote using the following method:
• Open wallet and go to Tools > Debug Console. The debug console will open in a new window.
• To vote for Proposal: SocialPhilip_JAN20, type the following command:

mnbudget vote 30f1c450c92705b0a68e3c6639ff1f98ef73ae6313d3880afed00a14f5884df9 yes/no

• If voting with multiple node, you can use “mnbudget vote-many….”
• If voting from the terminal, type in the following:

blocknetdx-cli mnbudget vote 30f1c450c92705b0a68e3c6639ff1f98ef73ae6313d3880afed00a14f5884df9 yes/no

— — — —

For more detailed instructions see: http://blocknetdx.forumotion.com/t6-blocknet-proposal-introduction-guide

• An introduction to Superblocks and a guide to submitting and voting for proposals, can be found here.
• A proposal category was created in the Blocknet Discord for focused and specific discussion of proposals and ideas. Within this category, there is a channel called #anon-snode-feedback for Service Node owners to provide anonymous feedback on proposals.
• Votes in favor must be greater than votes against by at least 10% of the total number of Service Nodes.
• The proposals that pass are sorted in a descending order list by the sum of yes votes minus no votes. If multiple proposals have an equal sum of yes votes minus no votes, those are sorted randomly. If there are not enough funds remaining in the Superblock for a proposal to be paid out, it is skipped (not paid out), and the next proposal in the list is checked.
• Multi-month proposals are voted on each month and are treated in the same manner as normal proposals in the ordered list.
• There is also something called a ‘final budget,’ which needs to be submitted between 2880 blocks and 28 blocks before the Superblock. By default, Service Nodes automatically vote yes on final budgets. Moving forward, proposal voting will end 2880 blocks before the Superblock since the final budget locks in the proposal vote counts.
• An introduction to Superblocks and a guide to voting can be found here.
• In addition, 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!

— — — — — —