Please Vote For The Latest Community Superblock: 1209600

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 1209600 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 1209600

Proposal Name: 86b-1209600 Owner: 86b

Cost: 8020 BLOCK

Proposal: Operations

One goal this next month among other ongoing items detailed below will be producing setup guides for the community so they can get various custom chains (EOS, ETH, etc.) setup properly on their Service Nodes and be properly staged for the upcoming base code rollout.

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-1209600, type the following command:

mnbudget vote 0494db2f9c15de461f4176b5ba37d0ef58890a6a127f699d092ef884d7b464c1 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 0494db2f9c15de461f4176b5ba37d0ef58890a6a127f699d092ef884d7b464c1 yes/no

— — — —

Proposal Name: aderks-ops-1209600 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.

November Work:

• Block DX QA:
• Market pricing default on
• Wallet setting text update
• Custom data directory support
• Data directory remembering
• Conf loading error notification
• Clear cancelled order button
• Active/Inactive ? tool-tip
• DX 1.5.0 Release
• 1st iteration of localization for Block DX
• Created a list of all items missing for localization
• Market pricing name update
• Blocknet Core / V18 upgrade QA:
• Re-design integration QA
• V18 Data dir and executable name changes
• V18 Classic/Re-design re-naming
• Created list of remaining items needing name changes
• Checked the fixes
• V18 wallet sending error
• V18 segwit testing
• V18 re-design governance
• V18 governance started edge-cases/battle testing
• 3.14.1 Release
• Relaying between 3.14.1 and V18
• Block DX website QA:
• General QA checks on different devices for Hanni
• New Service Node and Governance documentation
• V18 Service Node setup documentation for classic and re-design
• V18 Governance setup documentation for classic and re-design
• XRproxy Docker container QA:
• Fattox and myself found a bug on sending XCloud data parameters
• Testing and setup working HTTP requests from the internet
• Ethereum web-server updated
• Built Ethereum web-server for the sole purpose of running through the XRproxy Docker container (https://github.com/Aderks/ethereum-webserver)
• Created Dockerfile and template configuration files
• Created setup instructions
• Updated setup info to allow public HTTP access
• Updated Dockerfile and script to support Ethereum RPC endpoint changes (including Infura) on docker build or docker run
• Discord Blocknet-API bot
• Updated discord.py to v1.2.5 to fix a bug causing crashes
• General maintenance
• Other
• Getting setup on a Kubernetes cluster for my ETH web-server/XRproxy

Cost:

• 1667 BLOCK
• 20% pay reduction due to unforeseen circumstances where I was out of town for 6 days
• 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-1209600, type the following command:

mnbudget vote 8b4276b0613388ca6bdc052450148c155717307cb8027554f5c55d9517a8e90e 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   8b4276b0613388ca6bdc052450148c155717307cb8027554f5c55d9517a8e90e yes/no

— — — —

Proposal Name: atc-dec-sb1209600 Owner: atcsecure

Cost: 1000 BLOCK

Proposal: Support Infrastructure

Previous Work: hosting/support for gitian, forum, related s3 buckets, blockdx services

Overview: Covers infrastructure related costs for this sb period.

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-dec-sb1209600, type the following command:

mnbudget vote   5671d68fcf3788d6b75f4b1cc4de1a8cf3f7ba8cc24146ddd8a4d96f89bb66d2 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   5671d68fcf3788d6b75f4b1cc4de1a8cf3f7ba8cc24146ddd8a4d96f89bb66d2 yes/no

— — — —

Proposal Name: blockdx-amcharts-lic Owner: atcsecure

Cost: 1850 BLOCK

Proposal: License

Previous Work: n/a

Overview: This license is required for the charting feature used in blockdx

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-amcharts-lic, type the following command:

mnbudget vote    a1789c000cf5ab7ce0e740bcc22c949c2f7f69304fce1b8ccbb4cbe8f091fafb 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    a1789c000cf5ab7ce0e740bcc22c949c2f7f69304fce1b8ccbb4cbe8f091fafb yes/no

— — — —

Proposal Name: blockdx-dev-dec-19 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:

• Complete localization
• dxGetNewTokenAddress integration
• 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-dec-19, type the following command:

mnbudget vote  ddac3a062c4b1a6c4a45d5aa7ba665ff4dafd8e93d82c7f9001f3b85e7eee59c 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  ddac3a062c4b1a6c4a45d5aa7ba665ff4dafd8e93d82c7f9001f3b85e7eee59c yes/no

— — — —

Proposal Name: buildserver-cost-dec Owner: michael

Cost: 960 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/bitcoin/pipelines (new wallet, Blocknet 4.0)
https://gitlab.com/blocknetdx/blocknet/pipelines (legacy wallet)

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-dec, type the following command:

mnbudget vote  90d86998df4b0366b2c5a9b27f3f592fd8e109373ec201d40b9f7717bf2a7d10 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  90d86998df4b0366b2c5a9b27f3f592fd8e109373ec201d40b9f7717bf2a7d10 yes/no

— — — —

Proposal Name: corgi-dec Owner: Crypto Corgi

Cost: 690BLOCK

Proposal: Crypto Corgi

Overview: Turn up the volume on the Block DX twitter.

Previous Work:

Generally: creating content for and growing the @BlockDXExchange Twitter account.

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

My last proposal (i.e. October) passed, but did not pay out due to insufficient funds in the Super Block to cover all the passed proposals.

I continued to do some occasional tweeting in November, despite the fact that last month’s proposal did not pass, but not at the same level as I had been over the previous months.

The Twitter stats for November are, as expected, down:

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-dec, type the following command:

mnbudget vote  2bc7b0812d5a6e90c41440a14bc902f5294b5c6226f571f2863a6631c66d11eb 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  2bc7b0812d5a6e90c41440a14bc902f5294b5c6226f571f2863a6631c66d11eb yes/no

— — — —

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

Cost: 250 BLOCK

Proposal: Block DX Maker Bot

Introduction:
Again sorry for my English.

Previous Work:
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

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
• 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 support this dxmakerbot update 002.
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-002, type the following command:

mnbudget vote 34ad43224e44be66e19c209125b907ce7d289ab690fbfa588a2ffc5ec70ac4ec 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 34ad43224e44be66e19c209125b907ce7d289ab690fbfa588a2ffc5ec70ac4ec yes/no

— — — —

Proposal Name: hanniabu-1209600 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 QA (MacOS)
• Block DX development
• Block DX task management
• 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 development, content, publishing
• 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
• Continued wallet and Block DX 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-1209600, type the following command:

mnbudget vote  e9689a0ba81f1823785e420bfb8ad61e53126555d567197cea9bf217158696f0 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  e9689a0ba81f1823785e420bfb8ad61e53126555d567197cea9bf217158696f0 yes/no

— — — —

Proposal Name: infinity7592–1209600 Owner: Infinity7592

Cost: 385 BLOCK

Proposal: Debugging

• Deployment tests: done on netlify.
  Removed dependencies which caused the deployment to fail on netlify.
• u2f status on Windows: Windows Update 1903 broke the communication channel.
• u2f test on Linux: working
• u2f test on Mac: not doable as I don’t have a Mac machine.
• WebUSB tests: performed some tests but not usable, as is.
  Very little documentation about it anyway.
• reached another ledger dev : no answer back.
• follow up of ledger dev channels: no specific milestone from them.

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–1209600, type the following command:

mnbudget vote  b6074ab2011e4b6e0be1ba4f23b1000dc75d7ebd34f5048857d7d2f0a66a4fa5 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  b6074ab2011e4b6e0be1ba4f23b1000dc75d7ebd34f5048857d7d2f0a66a4fa5 yes/no

— — — —

Proposal Name: michael-dev-dec Owner: michael

Cost: 16500 BLOCK

Proposal: Core Development

November recap
In November I completed the wallet redesign integration effort on the new basechain (upcoming Blocknet 4.0 release). I combined the redesign and classic wallets into the same codebase. The classic= flag in the blocknet.conf can be used to easily switch between them. I also added support for Segwit in the new basechain, which will be enabled when the majority of the stakers adopt the new protocol. This latest work can be reviewed here: https://github.com/blocknetdx/bitcoin/commits/blocknet. Also in November, I code reviewed and helped release Block DX 1.5.0. Testnet builds for the upcoming Blocknet 4.0.0 release can be obtained here: https://gitlab.com/blocknetdx/bitcoin/pipelines/

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)

December Development Overview
The plan for the month of December is to support the final development and release Blocknet 4.0.0, including working on bug fixes and related optimizations (specifically on the Governance system). The new Governance system is on-chain, as a result I’m working on a vote-on-stake feature that will cast votes on new utxos automatically. The team is also working on a new roadmap outlining the goals for 2020.

Current tasks

• Blocknet 4.0 release
• Vote-on-stake feature
• Blocknet 4.0 bug fixes and ptimizations

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-dec, type the following command:

mnbudget vote  007662c7372a312cbf70070d01c6291831c5cfb0a21cf111d1d9ec6e020e73c2 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  007662c7372a312cbf70070d01c6291831c5cfb0a21cf111d1d9ec6e020e73c2 yes/no

— — — —

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

Cost: 1080 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-1209600 type the following command:

mnbudget vote  b6fa1cdf181ab00e02df8993dfb5b63376e68afff3c762ae57bf2028ce1a2d29 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  b6fa1cdf181ab00e02df8993dfb5b63376e68afff3c762ae57bf2028ce1a2d29 yes/no

— — — —

Proposal Name: Social_Philip_Dec Owner: Philip

Cost: 1100 BLOCK

Proposal: Copywriter, Social media Admin

Previous, Recent and forthcoming tasks:

• A new article on Block DX was published on our website blog and Medium: 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
• A new article on the Hackernoon website was commissioned and published for which I wrote the outline: A Decentralized “Internet of Blockchains:” Blocknet Protocol
• 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:
• 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.67 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: Social_Philip_Dec, type the following command:

mnbudget vote 262820795be2d75079e24de75de0ec0ddc64b5cc1bbe944e08e8ae9d36e75dc6 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 262820795be2d75079e24de75de0ec0ddc64b5cc1bbe944e08e8ae9d36e75dc6 yes/no

— — — —

Proposal Name: TheVoice-1209600 Owner: TheVoice

Cost: 1600 BLOCK

Proposal: Support, Telegram, and Discord, Real Use Videos, Blocknet Crew media

Previous Work:
Support, Telegram, and Discord, Real Use Videos, Blocknet Crew media, Twitter

Overview:

Ive been on a short vacation for a month. Superblock was full last month but thank you for last months VOTES.

Focus on Blocknet Project through support and core team assistance along with regular involvement on any needed core projects. Broaden the use and creation of tools to simplify user ease of use — real use videos for the community. Also, building internal community participation in outside media, like but not limited to Twitter and Medium where we have the opportunity to reach people that have little or no knowledge yet of the Blocknet and Blocknet protocols. Encouraging new engagement and adoption organically.

Encouraging growth and opportunity with the development of teams on other communities to build usage of Block DX.

Building up external chain relations through the current set of blockchain peers — ie helping facilitate OTC trading groups.

Podcast Interview with Cigars and Crypto:

The Blocknet (The_Blocknet)

Check out this interview with Blocknet community member The Voice on the Cigars & Crypto podcast where they discuss #blocknet & #divi & #interoperability and how to make a difference to your #crypto community. https://t.co/0hoCOuYYdc @DiviProject @CigarsAndCrypto @knowcryptoshow

1 Group has formed in the DIVI community, this is a purely community-run initiative by the community members facilitated by myself and another key community member.

Divi Community > can use the original BlockDX quick setup.

Building Blocknet Fee faucet for new communities to trade on DX — first-time users. This will be available on Telegram Groups — Bot is complete will continue updated as users inquire and it benefits trading. It is an admin-only distribution bot. Admins are community or core. Community admin already installing and testing bot and DX. We will be moving the bot to Digital Ocean for hosting. A minimal amount of block will be used for OTC training and trading for newcomers. Est .016 block for training and first few buy trades. No more than 10 trials per user. The distribution will be manual to prevent fraudulent trading or training.

First Bot is in Divi Unofficial OTC, the next fork of the bot will be made for Digibyte community for an unofficial OTC trading channel with the BLOCK DX.

DigiByte community was used for the latest Block DX setup video and will be used in the soon to be created DigiByte OTC Telegram trading channel.

Block DX First Time Setup

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: TheVoice-1209600, type the following command:

mnbudget vote   338886fd1b68991db6409bde015085d84655829159f7343fa690bc152a521764 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   338886fd1b68991db6409bde015085d84655829159f7343fa690bc152a521764 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!

— — — — — —