BitShares Core Team Budget Worker Proposal - 2018

<ul> <li>Author: Ryan R. Fox (<code>"fox") <li><a href="https://mandarin_translation.md" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">国语翻译 Mandarin Translation: 招木 (<code>"Zhaomu") <h1>Intent <ul> <li>Establish a <strong>budget to sustain the development efforts of the BitShares Core Team <li>Define a <strong>framework for the Core Team to collaborate within <li>Provide transparent <strong>delivery of BitShares development efforts to the community <h1>Background <p dir="auto">BitShares Core software is currently maintained by individuals either volunteering their time or<br /> receiving funding through distinct short-term worker proposals. The BitShares Community has<br /> recognized the need for organized development efforts to increase the utility of our platform.<br /> There is a large backlog of ideas and requirements lacking prioritization, including feature<br /> enhancements, bug fixes, and BSIPs. Therefore, proposed is the establishment of a long-term,<br /> professional, global team dedicated to cohesive and comprehensive development efforts delivered<br /> transparently. <h1>Worker <p dir="auto">This is a Budget Worker Proposal which provides <strong>partial funding through calendar year 2018 for: <ul> <li>BitShares Core Team Roles <li>Collaboration Tools <li>Development Initiatives <p dir="auto">This Worker funds an <em>initial Core Team at <strong>reduced hours to mitigate draw on the reserve pool<br /> and support <strong>bootstrapping efforts. Subsequent Worker(s) will be offered to fund the team as it<br /> scales up. This Worker intends to work in concert with the existing development resources including<br /> Abit, Alfredo Garcia, and the UI Team, led by Bill Butler. <p dir="auto">BTS are collected into the <code>"workers.bitshares.foundation" account which is a multi-sig account<br /> controlled by <code>"BitShares Blockchain Foundation" and owned by <code>"committee-account" using the<br /> Budget Worker Model [5]: <ul> <li>Transparent accounting provided by the BitShares Blockchain Foundation [6] <li>Submitted invoices reviewed, approved and remitted within 5 business days <li>Compensation paid in bitUSD (according to the rules set forth in [5]) <li>All unused accumulated BTS returned to the Reserve Pool at the conclusion of the Worker [5] <h1><em>Initial BitShares Core Team <p dir="auto">The initial Core Team is comprised of community members who have demonstrated their ability to work<br /> with Graphene-based code, contribute to this community with thoughtful leadership and share a<br /> dedication to the BitShares ethos. Initially, the team is a skeleton, with many contributing to<br /> multiple roles and at reduced weekly hours as represented in <em>Table 1 Each team member is focused<br /> on returning more value to the BitShares platform than is drawn from the reserve pool. <p dir="auto">The initial team is estimating 54 hours of weekly effort. This Worker proposes to <strong>budget $15,000<br /> for a team delivering approximately 100 hours weekly to support conservative growth. Demonstrated<br /> results will warrant subsequent Worker(s) to budget for additional team members and weekly hours. <p dir="auto"><strong>Table 1. Initial BitShares Core Team <div class="table-responsive"><table> <thead> <tr><th style="text-align:left">Roles (described below)<th style="text-align:right">Rate Range (Hourly USD)<th style="text-align:left">Team Members<th style="text-align:left">Estimated Hours <tbody> <tr><td style="text-align:left">Core Developer<td style="text-align:right">$150<td style="text-align:left">Peter Conrad<td style="text-align:left">10 hours weekly <tr><td style="text-align:left">Core Developer<td style="text-align:right">$150<td style="text-align:left">Abit<td style="text-align:left">5 hours weekly* <tr><td style="text-align:left">Core Developer<td style="text-align:right">$150<td style="text-align:left">Alfredo Garcia<td style="text-align:left">2 hours weekly* <tr><td style="text-align:left">Junior Core Developer, BA<td style="text-align:right">$125<td style="text-align:left">Taconator<td style="text-align:left">10 hours weekly <tr><td style="text-align:left">Business Analyst, Coordinator, QA<td style="text-align:right">$125<td style="text-align:left">Ryan R. Fox<td style="text-align:left">15 hours weekly <tr><td style="text-align:left">Lead Documentation Specialist, QA<td style="text-align:right">$ 90<td style="text-align:left">Tamami Sugimoto<td style="text-align:left">10 hours weekly <tr><td style="text-align:left">UI/UX Liaison<td style="text-align:right">$125<td style="text-align:left">Bill Butler<td style="text-align:left">2 hours weekly <tr><td style="text-align:left">Core Developers<td style="text-align:right">$125 - $200<td style="text-align:left">-open-<td style="text-align:left">- <tr><td style="text-align:left">Business Analysts<td style="text-align:right">$ 75 - $125<td style="text-align:left">-open-<td style="text-align:left">- <tr><td style="text-align:left">Documentation Specialists<td style="text-align:right">$ 60 - $ 90<td style="text-align:left">-open-<td style="text-align:left">- <tr><td style="text-align:left">QA/Testers<td style="text-align:right">$ 75 - $125<td style="text-align:left">-open-<td style="text-align:left">- <tr><td style="text-align:left"><strong>TOTALS INITIAL CORE TEAM<td style="text-align:right">$ 90 - $150<td style="text-align:left">-all-<td style="text-align:left">54 hours weekly** <tr><td style="text-align:left"><strong>$6,825 WEEKLY (EST.)<td style="text-align:right"><td style="text-align:left"><td style="text-align:left"> <tr><td style="text-align:left">-<td style="text-align:right"><td style="text-align:left"><td style="text-align:left"> <tr><td style="text-align:left"><strong>BUDGET FOR THIS WORKER<td style="text-align:right"><td style="text-align:left"><td style="text-align:left"> <tr><td style="text-align:left"><strong>$15,000<td style="text-align:right"><td style="text-align:left"><td style="text-align:left">≈100 hours weekly <p dir="auto"><em>*Abit and Alfredo intend to complete their existing Workers. Their contributions as part of the<br /> Core Team will initially be at the reduced hours above, then expected to increase similar to their<br /> existing Worker.<br /> **Additional hours for all roles remain available at this time. Please contact<br /> fox@bitshares.boston for additional information. <h1>BitShares Core Team <p dir="auto">The BitShares Core Team is a self-organizing agile-principled team focused on delivering regularly<br /> scheduled releases and ad hoc bug fixes for the BitShares Core software. The actual number of<br /> contributors and roles <strong>may vary within each development cycle (described below), leading to<br /> variations in weekly compensation per contributor. The team has discretion in allocating resources<br /> to meet the needs of each development cycle. <p dir="auto">Producing reliable and secure software at scale requires ideation, organization, definition,<br /> prioritization, development, testing and documentation. The ideal team composition includes roles<br /> specializing in each of these functions and capable of contributing to many. The goal of a highly<br /> functioning team is to fully utilize each individual's effort and together maximize their<br /> collective output. <h1>Development Cycles* <ul> <li>Feature Release (non-hard fork): <ul> <li>Three-week sprints <li>Core Release (Hard Fork): <ul> <li>Twice annually: first Thursday of June & December <p dir="auto"><em>*Subject to change upon consensus of Core Team Members <p dir="auto">A typical Feature Release will likely span three weeks from planning thru tested and delivered<br /> software, called a sprint. Many agile principals will be adopted by the Core Team, but do not<br /> expect a strict scrum practice. This is a global team, so a formal daily standup is unlikely. One<br /> should expect asynchronous communication within various collaboration tools keeping the team<br /> informed of progress, plans and problems. The community are our stakeholders; we look to them for<br /> ideas, enhancements and identifying bugs, then organize these into a backlog for future<br /> development. The Coordinator facilitates the prioritization of the backlog items based on feedback<br /> from the stakeholders and the Core Team. The team will keep the stakeholders informed of<br /> development progress throughout the sprint. <p dir="auto">At the beginning of a sprint cycle the Core Team meets to review the prioritized backlog and<br /> identify the highest value items that each can contribute to, within the established time block.<br /> Many features have dependencies and cannot be implemented within a single sprint. Therefore, the<br /> team will create tasks, a subset of the feature, that can be delivered on time. A task may be<br /> researching and defining requirements to be implemented later. A task may be writing a test case,<br /> or perhaps implementing only a subset of a given requirement, or even documenting how existing code<br /> functions. The team will maintain a sprint backlog comprised of the tasks selected from the project<br /> backlog. Completing each of these tasks results in incremental value added to the project. Testing<br /> is performed throughout the sprint to ensure functioning code from each increment. <p dir="auto">As the sprint nears completion, the Core Team will begin release planning. They will select which<br /> tested increments are ready to be included in a release candidate. This will be deployed to a<br /> staging network for final validation. A release will be tagged within the bitshares-core GitHub<br /> repo along with release notes. The team also produce stakeholder documentation detailing resource<br /> allocations and budget consumption. <p dir="auto">The final steps of the sprint include a retrospective look at how the team performed. Here we<br /> reflect on our original estimates, the delivered increments and what contributed to our successes<br /> and shortcomings. We will use insights gained from the retrospective to improve in the next sprint.<br /> The following day we immediately begin our next sprint cycle. <h1>Bounty Process (Implicit Budget) <p dir="auto">The BitShares Core Team maintain a prioritized project backlog of ideas, enhancements, bugs and<br /> BSIPs which they select from for their development sprint. The community is encouraged to comment<br /> on the items to aid in refining requirements and guide prioritization. Effort estimates are first<br /> assigned to the highest value backlog items. Unassigned <strong>and estimated project backlog items are<br /> available for ad hoc <em>bounty development. Successfully completing ad hoc bounty items is a primary<br /> consideration for an invitation to join the Core Team on a future sprint. <p dir="auto">The Core Team encourages ad hoc code contributions of estimated project backlog items from<br /> community members and will compensate successfully merged code based on those estimates. The<br /> Coordinator will facilitate onboarding new community contributors to <em>claim a backlog item and<br /> implement a solution that fits within the broader architecture design defined by the Lead<br /> Developer. Care must be taken to ensure effort is not duplicated and can easily be merged within a<br /> future sprint. Claimed items that become a dependency of a sprint may be recalled by the Core Team<br /> to facilitate feature delivery. Compensation for a partially completed increment will be evaluated<br /> by the Lead Developer. <p dir="auto">Compensation for a successfully merged <em>bounty item is drawn from the excess <em>implicit budget<br /> capacity within <em>Table 1 when any Core Team Role is not fully allocated. The specifics for the<br /> bounty process is still being revised (note: it is largely based on the process in use by the UI<br /> Team). <h1>BitShares Core Team Framework: <p dir="auto">Accountability <ul> <li>Maintain timely collaborative communications with each BitShares Core Team Member <li>Participate in at least two of three weekly Collaboration Sessions (see Coordinator description) <li>Target a majority of your weekly hours between Tuesday - Thursday <ul> <li>Facilitates ad hoc collaboration <li>Facilitates healthy work/life balance <p dir="auto">Transparency <ul> <li>Maintain working increments within Community facing collaboration tools <li>Maintain timely updates within Community facing collaboration tools of work in progress and development priorities <p dir="auto">Delivery <ul> <li>Deliver the highest value work first <li>Favor release schedule over feature completeness (see Development Cycles) <h1>BitShares Core Team Member 'Contract Work' Guidance: <p dir="auto">This section is to be considered guidance, not a legal statement. The BitShares<br /> Decentralized Autonomous Community (BitShares DAC) controls the funds collected<br /> by this Budget Worker and are issued as compensation to individuals performing<br /> agreed work as described elsewhere in this document. Effort contributed by<br /> individuals is considered by personal commitment as no formal employment<br /> contract is intended or able to be formed between BitShares DAC and the<br /> individual worker. Neither the BitShares Blockchain Foundation (BBF) nor the<br /> BitShares Committee or any individual serving those entities are to be<br /> considered employers of any agreed contribution. No BitShares Core Team Member<br /> or Role is considered the manager or the employer of any individual person. Any<br /> compensation received from the BitShares DAC might be considered earned income<br /> for individual persons involved in their individual situation and may be<br /> subject to tax reporting by the recipient. Neither BitShares DAC, nor the<br /> BitShares Blockchain Foundation, nor BitShares Committee, nor the Coordinator,<br /> or any Core Team Member will neither carry responsibility, nor command, nor<br /> issue, nor prepare any document, including tax documents, to any entity or<br /> natural person. All effort performed is a contribution to the BitShares DAC<br /> adhering to its MIT license. <p dir="auto">Each Core Team Member is encouraged to contribute in a responsible way with<br /> respect to a work/life balance and legal employee engagements he or she might<br /> have entered into, or enter, with an employer. <p dir="auto"><strong>Table 2. Core Team Roles and Rates <div class="table-responsive"><table> <thead> <tr><th style="text-align:left">Roles (described below)<th style="text-align:right">Hourly Rate (USD) <tbody> <tr><td style="text-align:left">Lead Core Developer<td style="text-align:right">$200 <tr><td style="text-align:left">Senior Core Developer<td style="text-align:right">$175 <tr><td style="text-align:left">Core Developer<td style="text-align:right">$150 <tr><td style="text-align:left">Junior Core Developer<td style="text-align:right">$125 <tr><td style="text-align:left">Lead Business Analyst<td style="text-align:right">$125 <tr><td style="text-align:left">Senior Business Analyst<td style="text-align:right">$100 <tr><td style="text-align:left">Junior Business Analyst<td style="text-align:right">$75 <tr><td style="text-align:left">Lead QA/Tester<td style="text-align:right">$125 <tr><td style="text-align:left">Senior QA/Tester<td style="text-align:right">$100 <tr><td style="text-align:left">Junior QA/Tester<td style="text-align:right">$75 <tr><td style="text-align:left">Lead Documentation Specialist<td style="text-align:right">$90 <tr><td style="text-align:left">Senior Documentation Specialist<td style="text-align:right">$75 <tr><td style="text-align:left">Junior Documentation Specialist<td style="text-align:right">$60 <tr><td style="text-align:left">UI/UX Liaison<td style="text-align:right">$125 <tr><td style="text-align:left">Coordinator<td style="text-align:right">$150 <h1>Core Developer <p dir="auto">The Core Developer is a seasoned C++ developer primarily tasked with writing and documenting the<br /> source code. Secondarily, the Core Developer is tasked with refining user stories, requirements<br /> and process models prior to development as well as resolving bugs during testing. <p dir="auto">Core Developer Key Performance Indicators <ul> <li>Collaborate with Business Analyst to refine user stories, requirements and process models <li>Collaborate with QA/Tester on bug identification and resolution <li>Collaborate with the Documentation Specialist to review documentation and ensure it matches<br /> the source code intent and implementation <li>Maintain code repositories within GitHub using GitFlow principles [7] <li>Contribute to Code Review of peers and provide approval for Release <li>Document code for the benefit of future development efforts <h1>Business Analyst <p dir="auto">The Business Analyst is a key role in a highly functioning team. They review the prioritized list<br /> of enhancements and refine them into requirements prior to the Developer beginning their design.<br /> Creating requirements documents often include user stories which narrate how the end user and/or<br /> system behaves. Process models are another tool for conveying the requirements in a visual flow<br /> diagram. Attention to detail and the ability to research and document are desired characteristics<br /> During development the Developer will often collaborate with the Business Analyst to clarify and<br /> refine requirements to ensure the implementation meets the desired behavior. The Business Analyst<br /> will assist the QA/Tester with writing test cases as well as executing and documenting results<br /> thereof. The Business Analyst will review and refine documentation produced by the Documentation<br /> Specialist to ensure it accurately reflects the requirements. <p dir="auto">Business Analyst Key Performance Indicators <ul> <li>Maintain user stories, requirements and process models <li>Collaborate with Core Developers to refine user stories, requirements and process models <li>Collaborate with Documentation Specialist to revise developer documentation matches the intent<br /> of the user stories, requirements and process models. <h1>Documentation Specialist <p dir="auto">The Documentation Specialist is technical writer able to interpret test cases, user stories,<br /> requirements, process models and C++ source code. Primarily the Documentation Specialist will<br /> write documentation for the development community on the GitHub Wiki and docs.bitshares.org<br /> website. Secondarily, the Documentation Specialist will work with Core Developers to revise<br /> developer documentation based on the intent of the user stories, requirements and process models<br /> to ensure they match the intent and function of the source code. <p dir="auto">Documentation Specialist Key Performance Indicators <ul> <li>Collaborate with the development community to ensure documentation supports their efforts <li>Collaborate with the Core Developers to review documentation and ensure it matches the source<br /> code intent and implementation <li>Collaborate with the QA/Tester and Business Analyst to enhance documentation including user<br /> stories, requirements, process models and test cases <h1>QA/Tester <p dir="auto">The QA/Tester is primarily tasked with writing test cases based on user stories, requirements and<br /> process models, then executing the tests and documenting the results. Secondarily, the QA/Tester is<br /> tasked with revising developer documentation with the Documentation Specialist. <p dir="auto">QA/Tester Key Performance Indicators <ul> <li>Maintain test cases within Aha! <li>Collaborate with Core Developers to identify and document bugs in GitHub <li>Collaborate with Documentation Specialist to revise developer documentation, ensuring it matches<br /> the intended workflow <h1>UI/UX Liaison <p dir="auto">The UI/UX Liaison is the primary point of contact for planning, prioritizing, defining and testing<br /> UI/UX elements impacted by the implementation of the Core software. The UI Team function<br /> independently of the Core Team, but their combined efforts are interdependent. Therefore, the UI/UX<br /> Liaison is integral to delivering our feature rich Core platform. <p dir="auto">UI/UX Liaison Key Performance Indicators <ul> <li>Maintain Feature Requests related to UI/UX <li>Collaborate with Business Analyst and Core Developers to refine user stories, requirements and<br /> process models <h1>Coordinator <p dir="auto">The Coordinator is an experienced agile project manager or scrum master with deep knowledge of<br /> distributed ledger technology. Primarily, the Coordinator is tasked with general facilitation,<br /> organization and prioritization of development efforts. <p dir="auto">Coordinator Key Performance Indicators <ul> <li>Maintain transparent communications with BitShares Community <li>Maintain transparent communications with BitShares UI Project Manager <li>Maintain transparent communications with Chinese Spokesperson <li>Maintain transparent communications with BitShares Spokesperson <li>Maintain prioritized backlog of issues/feature requests <li>Maintain project roadmap <li>Facilitate release cycles <ul> <li>Facilitate communication to centralized exchanges listing BitShares tokens <li>Maintain physical presence for BitShares within co-working space <li>Maintain a pool of candidates to select from to fulfill open roles <ul> <li>Contingency: If both a backlog of effort and an empty candidate pool for an open role exist,<br /> the accumulated budget funds may be allocated to a recruitment effort to fill the open role <li>Onboard and mentor Core Team Members <li>Facilitate standing collaboration sessions (Thrice weekly 2-hour blocks dispersed for<br /> international participation) <ul> <li>02:00 - 04:00 UTC Tuesday <li>19:00 - 21:00 UTC Wednesday <li>11:00 - 13:00 UTC Thursday <li>Approve invoices submitted by Core Team Members, forward to BitShares Blockchain Foundation<br /> for remittance <li>Maintain vendor relationships for collaboration tools <li>Facilitate Developer Conference attendance <h1>Initial Core Team Member Introductions <h1>Abit - Core Developer <p dir="auto">Draft: I have contributed to the BitShares code base for many years [11]. <h1>Alfredo Garcia - Core Developer <p dir="auto">I recently began my second 6-month Worker as a BitShares Core Developer [12]. Mainly I focus on the<br /> bitshares-core software by implementing features, fixing bugs, testing, maintenance, etc. [13]. I<br /> also develop outside the core tools for other developers and final applications for the BitShares<br /> community. [14] <h1>Bill Butler - UX/UI Liaison <p dir="auto">I lead the BitShares UI team and have extensive industry experience: Founded an ISP in 1993,<br /> NodeJS, Angular, PHP, CouchDB, SQL. UX/UI Experience [16]. I am currently VP Engineering for a<br /> healthcare software development firm and have eight years’ experience managing development teams. <h1>Peter Conrad - Core Developer <p dir="auto">I am a knowledgeable and long-standing member of the BitShares community (@pc) and an active<br /> developer for many years [9-10]. <h1>Ryan R. Fox - Coordinator, Business Analyst, QA/Tester <p dir="auto">I have actively contributed to BitShares development from its inception [1-4]. I have extensive<br /> professional background in project management with software development teams and am a professional<br /> scrum master (PSM-1) with multi-national experience in financial services, mortgage banking and<br /> manufacturing. <h1>Taconator - Core Developer, Business Analyst <p dir="auto">I began participating in the BitShares Hangout in early 2017 after submitting a patch and<br /> associated unit tests related to the recurring withdrawals capability that already existed in<br /> BitShares Core [8]. I also began publishing monthly reports on the fees collected by the BitShares<br /> blockchain in April 2017. I have experience within various industries identifying problems of<br /> non-technical end-users, designing technical products for solving those problems, and leading teams<br /> to successfully build those technical products. (Just because one might have a "hammer" does not<br /> mean that every problem is a "nail".) These solutions span from augmented reality applications on<br /> mobile devices to global distributed software systems. <h1>Tamami Sugimoto - Documentation Specialist, QA/Tester <p dir="auto">I have created and revised documentation for BitShares over the past year [15]. I hold a Masters in<br /> MIS and have held professional titles including Systems Analyst & Programmer, Web Designer and<br /> Database Administrator. I have experience using Content Management Systems to re-organize multiple<br /> websites. I am proficient analyzing system code in many programming languages and have created many<br /> web applications and websites. <h1>Collaboration Tools <p dir="auto">The BitShares Core Team use various collaboration tools to organize their work, convey ideas and<br /> aid development efforts. Transparency of development efforts to the community is a key requirement.<br /> Tools selected by the team generally provide read/reviewer access for the community to observe<br /> progress, track our time and provide feedback. Write/contributor access may be limited to a<br /> specific Core Team role(s). License quantities and types will vary monthly, therefore $2,000 is<br /> budgeted for tools. A non-exhaustive list is provided in <em>Table 3 below. <p dir="auto"><strong>Table 3. Collaboration Tools (Monthly) <div class="table-responsive"><table> <thead> <tr><th style="text-align:left">Description<th style="text-align:right">Amount (USD) <tbody> <tr><td style="text-align:left">Software Tools<td style="text-align:right">$2,000 <tr><td style="text-align:left">--Code Repository<td style="text-align:right">-- <tr><td style="text-align:left">--Continuous Integration<td style="text-align:right">-- <tr><td style="text-align:left">--Continuous Code Quality<td style="text-align:right">-- <tr><td style="text-align:left">--Product Roadmap<td style="text-align:right">-- <tr><td style="text-align:left">--Process Models<td style="text-align:right">-- <tr><td style="text-align:left">--Time Tracking/Auditing<td style="text-align:right">-- <tr><td style="text-align:left">--Infrastructure Environment<td style="text-align:right">-- <tr><td style="text-align:left">Escrow and Remittance (BBF)<td style="text-align:right">$3,000 <tr><td style="text-align:left"><strong>TOTAL TOOLS BUDGET (MONTHLY)<td style="text-align:right"><strong>$5,000 <p dir="auto">Select Core Team will meet prior to each of the scheduled DevCon events for team building,<br /> in person collaboration and presentation preparation. The Core Team will participate in conference<br /> events in constructive ways. A budget for Conference participation is provided in <em>Table 4 below. <p dir="auto"><strong>Table 4. Conference Budget (One-Time) <div class="table-responsive"><table> <thead> <tr><th style="text-align:left">Description<th style="text-align:left">Accommodations<th style="text-align:right">Amount (USD) <tbody> <tr><td style="text-align:left">DevCon Spring 2018 - Shanghai, China<td style="text-align:left"><td style="text-align:right"> <tr><td style="text-align:left">Travel round trip (up to $2000)<td style="text-align:left">5 FTE<td style="text-align:right">$10,000 <tr><td style="text-align:left">Lodging (up to $150)<td style="text-align:left">5 nights<td style="text-align:right">$3,750 <tr><td style="text-align:left">Meals (up to $60)<td style="text-align:left">5 days<td style="text-align:right">$1,500 <tr><td style="text-align:left">DevCon Autumn 2018 - TBD, Europe<td style="text-align:left"><td style="text-align:right"> <tr><td style="text-align:left">Travel round trip (up to $2000)<td style="text-align:left">5 FTE<td style="text-align:right">$10,000 <tr><td style="text-align:left">Lodging (up to $200)<td style="text-align:left">5 nights<td style="text-align:right">$5,000 <tr><td style="text-align:left">Meals (up to $80)<td style="text-align:left">5 days<td style="text-align:right">$2,000 <tr><td style="text-align:left"><strong>TOTAL TOOLS BUDGET (ONE-TIME)<td style="text-align:left"><td style="text-align:right"><strong>$32,250 <h1>Development Initiatives <p dir="auto">The Initial Core Team has identified in <em>Chart 1 a set of Initiatives to research, define and<br /> develop as part of their 2018 Roadmap. A detailed Roadmap will be a deliverable of this Worker for<br /> Community review. An 'Ideas Portal' will also be maintained to incorporate Community priorities<br /> into the Roadmap. <p dir="auto"><strong>Caveat: The Core Team cannot commit to deliver fully implemented solutions for all identified<br /> Initiatives. The intent here is to provide guidance at the outset, realizing the Core Team<br /> continuously evaluates and prioritizes new issues ongoing. <ul> <li>Interchain Communication <ul> <li>Atomic Cross Chain Transactions (ACCT) <li>EOS.IO Integration Report <li>Trustless Gateway <li>Market Mechanics <ul> <li>Market Engine Improvements <li>Maker/Taker Model <li>Bancor Protocol <li>Consensus & witness_node Enhancements <ul> <li>Database Storage Options <li>Installation scripts / environments <li>Confidential Transactions / Confidential Assets <li>Hardware Wallet Integrations <li>API & cli_wallet Enhancements <li>Community Engagement <ul> <li>Vote Decay <li>Fee Schedule based on Market Pegged Assets <li>Refine/Prioritize Existing BSIPs <p dir="auto"><strong>Chart 1. Initiatives - 2018 <p dir="auto"><img src="https://images.hive.blog/768x0/https://steemitimages.com/DQmWf2xvJuo3nWYHM7yJoQNMMPDNehCxUtXjKFuhurCwyAq/initiatives.png" alt="BitShares Core Initiatives - 2018" srcset="https://images.hive.blog/768x0/https://steemitimages.com/DQmWf2xvJuo3nWYHM7yJoQNMMPDNehCxUtXjKFuhurCwyAq/initiatives.png 1x, https://images.hive.blog/1536x0/https://steemitimages.com/DQmWf2xvJuo3nWYHM7yJoQNMMPDNehCxUtXjKFuhurCwyAq/initiatives.png 2x" /> <h1>Budget <p dir="auto">The items listed in the tables below represent an <strong>upper bound on expenditures. All funds<br /> collected and unused at the conclusion of this Worker Proposal will be returned to the Reserve<br /> Pool [5-6]. <p dir="auto"><strong>Table 5. Core Team Budget <div class="table-responsive"><table> <thead> <tr><th style="text-align:left">Description<th style="text-align:right">Amount (USD)<th style="text-align:right">Daily<th style="text-align:right">TOTAL BUDGET <tbody> <tr><td style="text-align:left">Total Core Team Roles (Table 1)<td style="text-align:right">$15,000<td style="text-align:right"><td style="text-align:right"> <tr><td style="text-align:left">++ Convert to daily (/7 days)<td style="text-align:right"><td style="text-align:right">$2,143<td style="text-align:right"> <tr><td style="text-align:left">Total Collaboration Tools (Table 3)<td style="text-align:right">$5,000<td style="text-align:right"><td style="text-align:right"> <tr><td style="text-align:left">++ Convert to daily (/30 days)<td style="text-align:right"><td style="text-align:right">$167<td style="text-align:right"> <tr><td style="text-align:left">Total Conference Budget (Table 4)<td style="text-align:right">$32,250<td style="text-align:right"><td style="text-align:right"> <tr><td style="text-align:left">++ Convert to daily (/44 weeks /7 days)<td style="text-align:right"><td style="text-align:right">$106<td style="text-align:right"> <tr><td style="text-align:left">≈≈ TOTAL DAILY BUDGET ITEMS<td style="text-align:right"><td style="text-align:right">$2,416<td style="text-align:right"> <tr><td style="text-align:left"><strong>≈≈ ≈≈ TOTAL 44 WEEK BUDGET<td style="text-align:right"><td style="text-align:right"><td style="text-align:right"><strong>$744,128 <h1>Duration and Pay <p dir="auto">This proposal will last for roughly 44 weeks, starting from 1st March 2018. <p dir="auto">Payments: <ul> <li>Invoices from Core Team Members will be submitted to the Coordinator by Monday 12:00 UTC for work<br /> performed thru Sunday 23:59 UTC of the previous period <li>Coordinator will review and approve submitted time sheets, then forward an invoice to BitShares<br /> Blockchain Foundation for release of funds from escrow to <code>"bitsharesdev" account for remittance to<br /> contributors <li>Coordinator will review and approve vendor invoices, then forward to BitShares Blockchain<br /> Foundation for direct payment to vendor <p dir="auto">Calculation: <ul> <li>3.9761 BTS/bitUSD = Settlement price of bitUSD at the moment of writing (2018-02-16) <li>2.5 = Collateral multiplier to cover market fluctuations and borrow with 2.5x collateral, as needed <li>$2,416 USD/day * 3.9761 BTS/USD * 2.5 collateral multiplier ≈24,016 BTS/day <p dir="auto">USD payment will be in bitUSD with method developed by the BitShares Blockchain Foundation [5]. <h1>References <ul> <li>[1] <a href="https://bitsharestalk.org/index.php?action=profile;u=5333" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">BitShares Talk Profile, Ryan R. Fox <li>[2] <a href="https://github.com/ryanRfox" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">GitHub Repository, Ryan R. Fox <li>[3] <a href="https://linkedin.com/in/ryanRfox" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">LinkedIn Profile, Ryan R. Fox <li>[4] <a href="https://twitter.com/ryanRfox" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Twitter Profile, Ryan R. Fox <li>[5] <a href="http://www.bitshares.foundation/worker/" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Budget Worker Template, BitShares Blockchain Foundation <li>[6] <a href="http://www.bitshares.foundation/accounting" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Transparent Accounting, BitShares Blockchain Foundation <li>[7] <a href="https://github.com/bitshares/bitshares-core/wiki/Git-Flow" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">GitFlow, BitShares <li>[8] <a href="https://github.com/TheTaconator" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">GitHub Repository, Taconator <li>[9] <a href="http://bts.quisquis.de/delegate/about.html" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Professional Background, Peter Conrad <li>[10] <a href="http://www.bitshares.foundation/worker/escrow/2017-07-peter-conrad" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Implementation of BSIP-18, Peter Conrad <li>[11] <a href="https://github.com/abitmore/bts-worker-proposals/blob/master/abit-worker-201712-201803.md" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Core Dev Worker, Abit <li>[12] <a href="https://github.com/oxarbitrage/worker-proposals/blob/master/bitshares2018_1.md" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Core Dev Worker, Alfredo Garcia <li>[13] <a href="https://github.com/bitshares/bitshares-core/commits?author=oxarbitrage" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">BitShares Core Contributions, Alfredo Garcia <li>[14] <a href="https://github.com/oxarbitrage" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">GitHub Repository, Alfredo Garcia <li>[15] <a href="#" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">BitShares Documentation, Tamami Sugimoto <li>[16] <a href="https://steemit.com/bitshares/@billbutler/bitshares-gui-worker-proposal-renewal" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">BitShares GUI Worker, Bill Butler![initiatives.png]