In the spirit of continued transparency, the ANON community admin and Development teams have begun regularly cadenced conference calls to stay abreast of development news, address questions and share community feedback. This consistent feedback loop aims to provide an aggregate platform for 2-way communication with the community. Meetings will spotlight current development focus, next tasks in queue, technical updates, Q&A, and community feedback.
Notes / Recap
Nov 16th, Nov 30th, & Dec 14th Conference Calls
Week of Nov 16th:
The team had made significant progress on the co-pay wallet solution. Ability to show list of governance proposals was incorporated, and masternode visibility feature nearly complete. Work had begun on proposal creation from within the wallet. The developers encountered a significant roadblock in trying to make or start masternodes from within the copay wallet. This became a largely complicated task that would require substantial delay to the deliverables to work through. A pivot was made to move forward with one wallet that allowed two versions — a default “light mode” that would have basic functionality and an optional “full mode” on desktop where users could option full node and gain additional features. (similar to fork supporting multi-asset wallet, ZelCore) The team also worked through scenarios to compile resource and time estimates for core upgrade options. With governance proposals slated to be brought forth for consideration at months end and the coin burn approaching, the team looked to discuss project pathing as it relates to the community feedback and how to forge the best path forward.
Week of Nov 30th:
Continued efforts on transitioning to a full node co-pay wallet solution for governance functionality. The team had made significant progress on the coding. The wallet has been updated with the option to take it full node. This automated process downloads the full node for users and is very easy to use. Code progression was estimated at 50% with Z transactions. The code was near complete with the ability to send from Z addresses. Good progress was made with regards to masternode functionality. Masternode and Proposal visibility was made fully functional. Work persisted on the ability to generate proposals. The team continued careful deliberation of how the project parameters and development should be delineated.
Week of Dec 14th:
Focus for the week had been further development of the co-pay wallet solution. Release ready ALPHA client was completed and published for testing. Coding progressed so that Z transactions have full functionality with the exception of T to Z which is still in progress. Tasks remaining include some UI functionality such as storing and tagging your own masternode, searching for specific values, etc. Full node implementation within the wallet was completed and is now in testing phase.
Work continues on incorporating proposal creation within the light wallet, as well as creating and starting masternodes with full node in co-pay. Continued work resolving bugs and UI fixes on beta and alpha release clients. Additional time was spent carefully re-reviewing the recent co-pay vulnerability to once again verify there was no risk to ANON.
After nuanced discussion and careful consideration — final direction was decided regarding core upgrades and development pathing to best position ANON for the future.
Governance Model Change:
ANON Masternode Governance scope to be constrained to the propagation of tertiary budget proposals and the subsequent deployment of funding only. Core consensus, team and fundamental code base changes are out of scope for governance voting.
The ANON Governance model was intended to mimic DASH in that the community of masternode holders would determine the initiatives of the project via budget deployment for partnerships, advertising, exchange listings and the like. While core consensus changes were not delineated as off limits initially, it became apparent that there were fundamental flaws in leaving such breadth of project principals in the hands of a select community vote. By clearly defining the scope of governance, we can leave the core mission and objective of ANON to the tech oriented decision-making process of the development team. This will achieve a streamlining of the proposal process so that initiatives brought forth are incremental and less iterative.
Masternode Collateral Change:
Collateral required for Masternodes to be raised to 10,000 ANON.
After careful consideration of the community concerns and developer opinion — the decision has been made to raise the collateral requirement for ANON masternodes by a ratio of 20:1. This in turn will allow for efficiencies driven by consolidation to reduce the outlay required of both maintenance tasks and costs associated for upkeep. The parsed masternode quantity will significantly increase the rate of block reward distribution. This combined with a reduced cost of maintenance will put ANON in a favorable profitability disposition for the foreseeable future. Though a smaller collateral may have been possible to address the current market conditions — the team believes 20:1 allows for further price volatility while maintaining significant positive ROI.
Additionally, with the implementation of Superblocks paying out live funds — the team sought to ensure that the weight of the masternode responsibility and vote were significant enough to warrant careful consideration and respect of the process. It helps to ensure that proposals brought forth are sponsored by holders with vested interest in the project progressing forward. This raises the stakes and seriousness of the proposal and voting process, yet at the same time dilutes the power of select individuals leveraging hundreds of votes as the consolidation will help to equivalize voting power.
Proposal Cost Change:
ANON required to submit governance proposal to be raised to 100 ANON.
In conjunction with the masternode collateral requirements increasing 20:1, the cost to submit proposals on the network will increase by the same ratio. This reinforces efforts to ensure the weight and significance of governance works to streamline the process, and have carefully vetted quality proposals brought forward for vote.
Governance Approval Change:
Differential verses negating votes required to pass to be raised from 10% to 25%.
(YES votes — NO votes) TOTAL MASTERNODES * 25%
The final net positive vote differential of a governance proposal must exceed 25% of the total number of masternodes in order to become approved. This combined with the collateral and proposal cost changes help reinforce efforts to ensure the weight and significance of the governance process work streamline and filter proposals brought forward.
Block Reward Split Change:
50% Miners / 35% Masternodes / 5% Superblocks / 5% Development / 5% Administrative Cost
- The reward split equivalization was a strongly supported proposal brought forth by the community. The ANON team strongly believes 50% is a threshold that should not be breached for block reward split allocated to the miners. The preservation of this level combined with raising the inherent value of the currency should put ANON firmly in the scope of the mining community and build our hashrate.
- The masternode holders currently make up the largest contingent of our active community and have taken much of the risk and burden in securing the network. By increasing the payout frequency exponentially via the collateral raise and subsequent consolidation, we are able to increase returns while maintaining the 35% block reward. This compromise allows us to bolster earnings, retain miner prioritization and also allocate funding for development. The enhanced reward economics afforded by the faster reward queue put the masternode community in a position for positive growth both near and long term.
- Funding for extended development support of ANON was secured at the fork via the allocation of 500,000 ANON. However, market fluctuations have significantly devalued the currency leaving the development team faced with potentially exhausting funding in the near future. By allocating a portion of each block reward towards development and administrative costs; we ensure that we retain active development and support for ANON infrastructure going forward.
- Budget allocation via masternode governance for community advocated initiatives is a core tenant of ANON. Seeded with 1 million ANON at the time of the fork, the masternode trust was established so that governance would have resources at the onset to judiciously utilize. By creating a perpetual ANON feed to augment and be used in conjunction with the trust, the project ensures that the community will have the ability to continuously re-accumulate funding to deploy.
ANON Development Path:
The development team has mapped out a multifaceted development path to make ANON feature rich and primed for utility, usecase and partnerships in the coming year. Community concerns were taken into consideration along with technical perspective and a desire to build synergistic features that would optimize both time and resources. The pathing would allow for significant major upgrades to ANON in rapid succession; with progressive phases completing every 2 months and culminating in cycle completion in JULY 2019.
The team felt strongly that they wanted to optimize governance and implement Superblocks for utilization. The addition of Sporks provides a feature set that allows upgrades to the network moving forward to be safer and done in a manner in which there is less disruption to the network itself. The implementation of DASH Masternode+ features of InstantSend and PrivateSend would provide more utility of the masternodes and transaction speed on the network. This allows ZCash Sapling to be the focus of the next core upgrade providing speed to private transactions as well as private transactions on mobile. And DASH Evo will add features further optimizing ANON with a deterministic masternode list, a secondary layer on the network (not hardcoded) where the list is part of each block providing a safer and more secure network.
Answers to Community Questions
Will these changes occur at the time of the COIN BURN?
Yes, the objective is to have the collateral change, reward split change and foundational superblock implementation occur at the time of the coin burn (block 37,000).
What comprises the two-part Superblock implementation?
So that the reward split change can be implemented in totality in one update at the coin burn, the superblock parsing of the block reward will be initially set to allocate to a dedicated wallet. The automation of disbursement as tied to governance voting will be added in the subsequent Phase 2 update.
Is there a need to limit the # of proposals that could potentially split the Superblock?
There is a coded mechanism that helps manage allocation and proposals so that it does not become an issue. If winning proposals exceed the superblock disbursement available, there is a prioritization structure that gets applied.
With the Superblock methodology being automated retention and disbursement of ANON; how can the proposals utilize the 1M (million) ANON in the trust previously established?
An additional methodology for manual disbursement will be created. I.e. a specific type of proposal / wording so that if passed, it triggers human intervention for utilization of trust funding.
How will the “fork” at the coin burn happen logistically?
The changes will technically be a “hard fork”. Every asset will require an update. At least 51% of the network will need to be running the update.
Will Lightning Network be part of the upcoming upgrades?
Because speed will be obtained via the Masternode+ features, ZCash Sapling will be the focus for the core code upgrade (in lieu of BTC Lightning) to allow for speed via private transactions and private transactions on mobile.
Will the new full node wallet be a QT release?
QT not needed — the new full node copay wallet will also by an executable file similar to current copay beta wallet ( with an option to run full node ). Alpha has been released and is currently in testing.
When will Masternode and Governance viewing capabilities be added to the co-pay light solution?
The dev team has released an updated test client with viewing functionality included.
Does the team have additional utility planned for masternodes?
As of right now, PrivateSend / InstaSend are the additional features in scope.
Was there any impact on the ANON wallet development caused by the recent co-pay compromise?
There was no impact on ANON development. The exploit was very targeted and did not involve the assets used by ANON.
When do lapsed governance proposals get removed from UI?
Expired proposal removal from the GUI is not a current feature. However, the process can occur by programming the proposals to be filtered on the front end. Community admins have advocated this as a request to the developers and recommend it be added. The dev team have noted it as a feature to be implemented, however it is not prioritized at this time.
Does Github have the production code on it?
Yes — Github houses the production code.
Community Request — can the masternode trust / funding wallet be made public via a visible address?
Clarification — what is the halving cycle timing?
134,000 x 10 min / 60 min (1 hour) / 24 hours (1 day ) / 365 days = approx 2.5 years
The ANON Development and Admin teams are also active in open communication within the ANON socials. We encourage all community members to participate, debate and foster dialogue that will continue to propel the project forward. #WeAreANON