Please Vote For The Latest Community Superblock: 1166400

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

Proposal Name: bizdev-1166400 Owner: Mastermind

Cost: 2500 BLOCK

Proposal: Business Development

October Business Development Summary
After exploring opportunities for Blocknet within the financial services and consulting sector over the past few months, my take (and I think general consensus within the dev team) is that our chance of success in this realm -at the current moment- is challenging. While a partnership at the Fortune 100 level would definitely move the needle for the project, it would be more effective to focus efforts on targeting companies within the crypto sector for initial partnerships rather and score a few goals instead of aiming to win the world cup right off the bat.

The consistent piece of feedback that I received from different banks was that they saw no urgent need to pursue. There are companies interested in Blocknet, but did not have an immediate pressing need to implement the technology and I would not expect them to think about these solutions for probably at least another 6 months / 1 year from now.

I will continue to keep feelers out in the banking sector, but focus my efforts on the low hanging fruit within the crypto sector going forward at this time.

Current pipeline:
Crypto/Tech Sector:
-App development company possibly interested in integrating Blocknet API (SF)

Banking Sector:
-3 Banks to follow up with in Q1/Q2 2020

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

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

— — — —

Proposal Name: blockdx-dev-nov-1 & blockdx-dev-nov-2 (2 -part proposal) Owner: Hanniabu

Cost: 2500 / 5000 BLOCK

Proposal: Block DX Development

Overview:
Cost are being broken up into 2 proposals (blockdx-dev-nov-1 & blockdx-dev-nov-2) of 2500 BLOCK each so Service Nodes have more variability over how much work they would like to have done.

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:

• Localization
• Bug with pulling in most recent configs
• 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-nov-1, type the following command:

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

• To vote for Proposal: blockdx-dev-nov-2, type the following command:

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

— — — —

Proposal Name: buildserver-cost-nov Owner: michael

Cost: 620 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 (current wallet)
https://gitlab.com/blocknetdx/bitcoin/pipelines (new wallet, v18 bitcoin fork)

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

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

— — — —

Proposal Name: corgi-oct Owner: Crypto Corgi

Cost: 972 BLOCK

Proposal: Crypto Corgi

Overview: This proposal is for past services provided for month of October

Previous Work:

• Creating regular content for the @BlockDXExchange Twitter account, including initiating the successful blank profile picture campaign.
• Authored educational Medium Article on atomic swaps and risk mitigation
• Increased @BlockDXExchange Twitter follower count to current 1,523 followers.
• @BlockDXExchange Twitter account stats for October (to date):

Screen Shot 2019–10–25 at 4.12.33 PM.png852×628 23.5 KB

Profile visits (over last 28 days) and mentions up significantly over previous months:

Screen Shot 2019–10–25 at 4.20.24 PM.png742×218 14.3 KB

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

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

— — — —

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

Cost: 1000 BLOCK

Proposal: Block DX Maker Bot

Introduction:
At first sorry for my English, probably some mistakes in text.

As you may already know, we spend some time with dxmakerbot research & development & also in development using some know how from previous bots. As long as bitshares network is going to be completely KYC’ed, we rather move bot development to project which have potential to grow. As you know we want to give this bot to Blocknet community and also continue with bot development later, implementing new features and also maybe development dxtakerbot. But as you know this takes our energy and time and this equals money and BlockDEX is now at low liquidity, and if there is someone who wants to increase liquidity or wanna just trade to make some profit he must use bots which have some logic and useful features. And here our ideas come.

If we continue with development, we had previous research that XBridge API is not enough compatible with logic we want to implement to dxmakerbot. This is our first proposal that is enough compatible with actual XBridge API, but in next proposal we need some more Blocknet dev cooperation.

Possible next development and next proposal needs XBridge api call update or new API calls. There only 2 needed:
We are not sure about if exactly this API calls need, or something like that API calls, this needs more discussion in next 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.

If you see this as possible please continue reading with proposal draft, otherwise thanks for your time

We are not sure but in draft we also marked atsecure, because previous communication, also nice from him would be to do some “code review” and “commit” into github.

As we already done some development and running/testing dxmakerbot,

Previous Work:
Some develppment/discussion has been already done.

Overview:
dxmakerbot.py code needs more research & development & testing:
-dxmakerbot refactoring to make code reusable and as easy to understand as it can be for next development.
-some new basic features implement
-manual testing new features
-readme file update
-dxmakerbot.py and other dependency python/readme files delivery to blocknet team.

All Features by arguments:

• –maker
• –taker
• –makeraddress (added to specify address by dxmakerbot session)
• –makeraddress (added to specify address by dxmakerbot session)
• –sellmin (using only this value of order size)
• –sellmax (temporary disabled)
• –slidestart (slide min and max were deleted and replaced by this)
• –slideend (slide min and max were deleted and replaced by this)
• –maxopen (just little bit updated)
• –reopenfinished (added)
• –balancesavenumber (added)
• –balancesavepercent (added)
• –slidedynpositive (added)
• –slidedynnegative (added)
• –slidedynzoneignore (added)
• –slidedynzonemax (added)
• –slidepump (added)
• –resetonpricechangepositive (added)
• –resetonpricechangenegative (added)
• –resetafterdelay (added)
• –resetafterorderfinishnumber (added)
• –resetafterorderfinishdelay (added)
• –delayinternal (added)
• –delaycheckprice (added)
• –usecb
• –usecg
• –usecustom
• –cancelall
• –cancelmarket

More Details:
Makerbot is just piece of simple source code now. It does not use logic, but only simple random generation of orders.

Let me explain case-by-case/feature-by-feature why this proposal is needed, why to update dxmakerbot as hybrid special featured bot.
By hybrid meaning staggered, static + dynamic spreads(slide), pump/dump covering, reset orders events and…

• 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.
  For example you wanna run BLOC->BTC and BLOCK-LTC bot, for this case there will be “–makeraddress” and “–takeraddress” config argument.
  For this case XBridge API must be somehow updated. First needed XBridge API update is, to dxMakeOrder() be able to create order only from funds specified by dxMakeOrder(…makeraddress…) or better solution to use funds only from specified UTXO txid like 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. Fully suport of this feature comes with Proposal to improve dxmakerbot #2
• As long as you wanna run multiple makerbots like in previous case (BLOC->BTC and BLOCK-LTC), there are many reasons why every bot instance must know which orders belong and not belong to running instance. To fix this, virtual orders internal database per dxbot is needed. This feature is also preparing bot for next features like to save running open orders in case of bot quit/crash.
• Bot previously uses “–slidemin” and “–slidemax” and was placing orders-price randomly in that range. For been bot more flexible this two parameters has been renamed to “–slidestart” and “–slideend”.
  Let me explain how this works. Start dna End can be used in conjunction if your bot have or not have enough funds to place all “–maxopen” orders count. As long as you specify slidestart higher value, bot will place higher orders first. For example “–slidemin 10 — slidemax 1 — maxopen 5”: first order placed at price 10, than middle equally spaced orders and last order at price 1.
• As long as you want or do not want to finished orders be reopened or not, there will be “–reopenfinished” config argument. This can be useful when uptrend is expected and staggered bot.
• As long as you want to always save same minimal specific amount of your coins, there will be “–balancesavenumber” config argument.
• As long as you want to save profit made by makerbot as percentual meaning of both pairs, there will be “–balancesavepercent” config argument.
• As long as makerbot needs to dynamically react on uptrend and downtrend of your pair, by selling with higher and more higher slide on price going up, with expectation that every uptrend is followed by at least small downtrend, there was special algorithm developed and previously privately long-term used on bitshares network by patched DEXBOT by us. And now coming to Blocknet makerbot. This features were called “custom dynamic parameters”, and one of these features was
  “custom dynamic spread”(or you want to call it custom dynamic slide) based on maker/taker balance. By this feature some new config arguments has been added to dxmakerbot: “slidedynpositive” “slidedynnegative” “slidedynzoneignore” “slidedynzonemax”. slidedynzoneignore parameter means is percent meaning when custom dynamic slide is not applied.
  slidedynzonemax parameter means is percent meaning when custom dynamic slide is applied at maximum slidedynpositive uptrend applied dynamic slide slidedynnegative oposite side bot applied dynamic slide, that expects following downtrend
  Be aware of: if you using this feature you need to start 1:1 value of your trading pair or you must be 100% sure what you are doing.
  Default parameters means this feature is disabled.
• As long as you want to cover price pumps/dumps, there will be “–slidepump” parameter which can be used to specify special “out of range slide” that can cover possible price pumps. Or opposite side bot dumps.
  Possible next development if this feature is to automatically compute top price of next pump and cover it. Also oposite side to disable bot to not make a loss.
• As long as you want to reset all orders when price changes in percentual meaning, there will be “–resetonpricechangepositive” and “–resetonpricechangenegative” config argument.
  Two asymmetric on price change configuration are very useful if you expect price goes only up or only down or very little corrections in price gonna happen.
• As long as you want to reset all orders on specific timeout, there will be “–resetafterdelay” config argument.
• As long as you want to reset all orders after bot reaching some finished orders, there will be “–resetafterorderfinishnumber” config argument. Very usefull if you have multiple staggered orders with conjunction with next “–resetafterorderfinishdelay”.
• As long as you want to run timer after last finished order and than reset all orders, there will be “–resetafterorderfinishdelay” config argument. If your staggered orders start to pass, you can set em timeout to wait for next pass or reset orders.
• As long as have internet connection or some other latency problems you want to wait for internal bot operations processing, there will be “–delayinternal” config argument.
• As long as you wanna specify how often to check pricing also case to price provider not thread you like spammer, there will be “–delaycheckprice” config argument.
• All this new features makes dxmakerbot less limited to be configured as your many wishes are.
  Example of dxmakerbot usecases:
  liquidity/trading bots -> to increate liquidity of blockdx decentralized exchnage and earn some coins
  automatically selling all staked/mined coins
  custom bots configured by external financial analysis systems…

I believe that i gives you many reasons for vote up this proposal to support this new dxmakerbot update.

Possible Next Work Expectations:

Possible next development:

• as this is research&development do more code refactoring
• configuration file per dxmakerbot instance implementation
• save orders to db before exit, dxmakerbot session will be able to cancel only session specified orders on reconfig/exit/crash
• update XBridge API to work with UTXOs than update dxmakerbot to be more effective to uses whole UTXO with coop of “–sellmin” and “–sellmax”
• 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.
• staggered hill/valley mods
• educational video tutorials how to use dxmakerbot.
• exit bot at events and cancel/notcancel orders on exit…

Thanks for your time & MTFBWY
Hopefully see you later on upcoming dxmakerbot development.

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

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

— — — —

Proposal Name: hanniabu-1166400 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)
• 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 QA and manage tasks
• Website planning, content, and development
• Exchange applications
• Forum updates

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 website development

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

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

— — — —

Proposal Name: hardware-1166400 Owner: Ops Team

Cost: 1075 BLOCK

Proposal: Hardware upgrade

Overview:
Due to the growth of the ETH chain, a new dedicated 8TB SSD is required for one of our systems which is being used to syncronise the (newly synced) Geth v1.9 data for XRouter staging. This system will also be the source used to transfer data to our AWS S3 bucket, so that other team members have access to Geth’s datafiles.

This is a required upgrade as the growth of the ETH chain means that the current (4TB) SSD used on this particular system will no longer be sufficient approximately 6 weeks from now, as the ETH archival state grows by ~4.5GB/day on average:
https://etherscan.io/chartsync/chainarchive

This upgrade is required ahead of time to allow time for installation and migration before these limits are reached.

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

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

— — — —

Proposal Name: infinity7592-nov19 Owner: Infinity7592

Cost: 375 BLOCK

Proposal: Debugging

@ledger:

• Transitioned previous web client from React to Vue.js.
• During testing of this web client, I discovered that the signing process is currently broken due to a Windows Update (1903) breaking
  the ledger communication channel.

Open Github issues are here:

• https://github.com/LedgerHQ/ledgerjs/issues/402
• https://github.com/cosmos/ledger-cosmos-js/issues/13

The Ledger team seems to be looking into the issue, but a Windows Update will be required.

An alternate solution, which I will test, consists in using the WebUSB, another communication protocol.

• Most code of the web client is written. The work consists mainly in 1) fixing the above issue, 2) making the web client look good.

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

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

— — — —

Proposal Name: michael-dev-nov Owner: michael

Cost: 13000 BLOCK

Proposal: Core Development

October recap
In October I completed the XRouter integration into the new basechain. Additionally, I improved XRouter and added support for external servers and data oracles paving the way for enterprises to build on top of the XRouter protocol without having the blockchain installed locally. This lastest work can be reviewed here: https://github.com/blocknetdx/bitcoin/commits/blocknet. Wallet redesign integration is currently in progress, this is the final milestone in the base chain migration. The goal is to complete the redesign integration next week and begin final testing of the new chain in November. Testnet builds can be obtained here: https://gitlab.com/blocknetdx/bitcoin/pipelines/

November Development Overview
The plan for the month of November is to release Blocknet 3.14.1 (legacy) and Blocknet 4.0.0 (new chain), release Block DX 1.5.0 and finish testing XBridge, XRouter, and general wallet functions.

Core Development task summary:

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

Other tasks

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

Upcoming XRouter tasks:

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

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

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

— — — —

Proposal Name: ops-team-1166400 Owner: 86b/Fattox/aderks

Cost: 16020 BLOCK

Proposal: Operation Team

Note:
2 of our 3 members worked on a voluntary basis last month (as did Hanni) to make room for other contributors, but of course this is not sustainable. Our team is now back to a regular proposal of 3, though we are currently still continuing with a reduced rate of pay.

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.

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: ops-team-1166400, type the following command:

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

— — — —

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

Cost: 1360 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

Note: This includes the month of October + November. If this proposal fails to make the Superblock cutoff priority but passes within the normal rules of the Superblock design, it will be paid out of the Development community fund.

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

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

— — — —

Proposal Name: TheVoice-1166400 Owner: TheVoice

Cost: 1600 BLOCK

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

Overview:
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.

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. Image: https://forum.blocknet.co/uploads/default/original/1X/51e5184f4d37a0de0cbb2073e8abe2d8dffe9c15.png

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. Images:

https://forum.blocknet.co/uploads/default/original/1X/4b9de17042a026a0b16db9333d235756e45fcf48.png

https://forum.blocknet.co/uploads/default/original/1X/ffd4bd7a335163a9cca4180828716e27ed42eb83.png

https://forum.blocknet.co/uploads/default/original/1X/d8dae7031b6950e3564c4ef02c2c01c0fd9d2d35.png

https://forum.blocknet.co/uploads/default/original/1X/53d9ca38aaf3676801d551194794741b463eb7e4.png

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.

New video:

Block DX First Time Setup

https://forum.blocknet.co/uploads/default/original/1X/a832017cad1b56701cea27f3b3980dcc1ec337c5.png

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

mnbudget vote  3bb431f29bad25ffa49db5416efbf2824164e079855866d5c34d99a0c6368ff7 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  3bb431f29bad25ffa49db5416efbf2824164e079855866d5c34d99a0c6368ff7 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!

— — — — — —