May 2017 - Dash Core Team Monthly Report

Status
Not open for further replies.

kot

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Dash Support Group
Mar 17, 2015
698
1,860
263

Dear Community members,

It is my pleasure to give you a status report of the Dash Core Team activities. Below, you will find our report covering activities performed through the end of May, grouped by the four strategic areas of focus for 2017.

  1. Software Development
    1. Dash core wallet - version 12.x (lead developer: UdjinM6; PM support: Robert Wiecko)

    2. Dash Evolution (lead developer: Nathan Marley; PM: Luba S.)
      • Detailed development roadmap for May-July was created. Milestones: Backend Pre-alpha (06 June), DashDrive Pre-Alpha(04 July), Frontend Pre-Alpha(17 June), Backend Alpha(15 August), Frontend Alpha(1 August).
      • New DevOps workflow was created and accepted by the team. It allows us to improve product quality assurance and deployment process, build CI&CD for Evolution.
      • Finished refinement of Evolution Whitepaper, Architecture Diagram was created.
      • We make some organizational changes that will help us to improve delivery process and increase development transparency:
      • Internal weekly reports(project status).
      • Improved structure of Evolution sub-projects in JIRA, now all team activities are tracked in JIRA, statistic is available.
      • Started more detailed planning of product versions/milestones.
      • Created documentation related to project planning and project management in Evo Confluence space
    3. Dash Evolution Backend (lead developer: Alex Werner; PM: Luba S.)
      1. Completed researches:
        • DAPI & JSON highjacking (Does DAPI need to integrate a JSON Hijicking solution while/before API response?)
        • Handle new user creation without any funds.
        • DashAuth: How we could use BitAuth2017 in a Dash Evolution perspective? Defined requirements for challenge building and resolving processes for authentication to interactive session with a MN quorum.
        • Probability of successfully attacking a quorum.
        • Seeding Evolution initial SubTx Costs from the Network
        • How we will use ZMQ and what is ZMQ.
      2. DashAuth: POC building finished, implemented Account/Create, Account/Login functionality.
      3. New development environment setup was finished:
        • Setup of server running with Evolution parts(Insight, Insight-API, dashd, dapi API, dapi WS) on testnet.
        • Setup of DAPI basic interface with others parts (Rest-interface, ZMQ interface with dashd, JSON-RPC interface with dashd).
        • Setup of evo-backend-installer with two differents install modes.
        • Updated requirements (install list + package) for Evo-backend-installer
        • Setup on npm (+grant access) : dapi, dapi-sdk
      4. AuthService was implemented in DAPI
      5. Decoupling Insight-API from Dashd management was finished
      6. In order to work-out for the later DashPay needs, we need to be able to make DashPay's dependencies (Bitcore-wallet-service) works on a decentralized way. Preparing Evo Backend for DashPay Wallet(Evolution Frontend) was done:
        • Implementation of Explorer routes
        • Inspection of DashPay calls and returns
        • BWS mock (added routes/wrappers +test for bws mock)
        • Additional signatures for DashPay were inspected and documented.
      7. Proposal Generator: verified proposal generator work, finished w/auto-deployment (CD).
      8. DAPI : Setup Main Tech Architecture (with tests, benchmarking, and basic connection interfaces - RPC...):
        • Prepare WebSocket interface
        • Prepare Rest interface
        • ZMQ interface with dashd
        • JSON-RPC with dashd
    4. Dash Evolution DashDrive (lead developer: Nathan Marley; PM: Luba S.)
      1. New developer was onboarded - Ian
      2. Started building of DashDrive prototype:
        • Mocked up DashDrive proof of concept User API calls and test JSON user account database
        • Contacts added
      3. Researching completed:
        • Backend storage
        • OOB data transfer with IPFS
        • GraphQL
        • IPNS with regards to pre-validated OOB. Matrix overview.
        • Factom
      4. Quorum integration research was done, quorum interaction stories with other system components were defined.
      5. Created internal documentation with detailed description of what is DashDrive and what is Quorum.
    5. Dash Evolution Frontend (lead developer: Chuck Williams; PM: Luba S.)
      1. Planned Alpha DashPay Wallet Release that will include DASH Account Setup, Basic DASH Transactions. Release date: 1 August 2017
      2. IBN Team(Contactors) was successfully onboarded and started work on Android build for DashPay Wallet.
      3. First version of UX Flow for DashPay Wallet (Account Setup) was delivered
      4. Documentation created: DashPay Wallet & Bitcore Playground DASH - How-To - How to get a private key for an address in the DashPay Wallet
      5. Initialized "Dash-UI" UI/UX Pattern Library Repository as home for discovered patterns and practice of Common Dash Interfaces & Interaction Styles.
    6. Dash wallet for Android - updated features (lead developer: @HashEngineering)
      1. Full report available here: https://www.dash.org/forum/threads/...-maintenance-and-support-1.14777/#post-128538
    7. Dash wallet for iOS - updated features (lead developer: @QuantumExplorer)
      1. Escalations with Apple management on Dash acceptance (Ryan Taylor is handling the communication)
    8. All Electrum versions updated https://electrum-dash.org
  2. Business Development
    1. Fernando @ Corks
      http://irishtechnews.ie/corks-first-blockchain-hackathon-and-conference/
    2. Daniel @ Blockchain 360
      https://www.dash.org/forum/threads/danie-dash-blockchain-360-san-francisco.14945/
    3. Dash Team @ Consensus NYC
      https://www.dash.org/forum/threads/consensus-2017-nyc-thread.15015/
    4. 2 Conferences (new leads)
    5. 2 new leads on Asian exchanges (Japan)
    6. Interesting opportunity with crypto-currency village in Asia
    7. Meeting with Bithumb to agree on promotion on Korea
    8. New project with BlockCypher
    9. New opportunity in China
    10. Coinapult Integration
  3. Marketing and Communication
    1. http://fintekneeks.com/the-cryptosphere-nears-40-billion/
    2. https://www.cryptocoinsnews.com/dash-accessibility-market-cap-rises/
    3. https://www.cryptoninjas.net/2017/05/03/dash-partners-coinapult-cryptocurrency-fiat-gateway/
    4. https://www.paymentssource.com/news/5417-your-morning-briefing
    5. https://cointelegraph.com/news/altcoin-dash-opens-regulated-fiat-purchases-with-coinapult-deal
    6. An interview with Evan Duffield:
    7. BCHGraz - Meetup #10 - DASH by Valentin Kalinov 1+2:
    8. https://cointelegraph.com/news/ethereum-vs-dash-in-race-for-100-mark-both-crossed-threshold
    9. Interview with Amanda B. Johnson:
    10. Other major publications:
      1. https://www.facebook.com/thecryptoshow/posts/1954301158126588
      2. https://letstalkbitcoin.com/blog/po...irez-of-alt36-a-pos-for-the-cannabis-industry
      3. http://www.banklesstimes.com/2017/05/11/dash-system-gives-window-to-blockchain-potential/
      4. https://cointelegraph.com/news/dash-to-ripple-gateways-heading-to-market-altcoin-watch
      5. https://www.dashforcenews.com/neocash-radio-dash-force-exclusive/
      6. https://www.dash.org/forum/threads/march-april-2017-dash-core-team-monthly-report.14919/#post-126744
      7. https://www.financemagnates.com/cry...ereum-dash-ripple-cryptocurrency-cfd-trading/
      8. http://www.newsbtc.com/2017/05/24/b...ow-includes-seven-different-cryptocurrencies/
    11. Dash.org Multi-language is live
  4. Project Organization
    1. Onboarding of 6 new developers completed
    2. JIRA and Confluence setup for the new team completed
    3. Assistance with the new project structure implementation
    4. Work on the internal core team processes
    5. Updates of Core Team Intranet
    6. Q1 Core Team call preparations
    7. Initiated first interviews for HR Director position and conducted first interviews
    8. Kicked-off American PM search
The original report could be found in this location: https://dashpay.atlassian.net/wiki/display/OC/May+2017+-+Dash+Core+Team+Monthly+Report?moved=true
 
Last edited:

Name3

Member
Jun 23, 2017
120
40
78
Awesome, I think everyone appreciates it when the community is kept in the loop like this.
 

xjones

Member
May 22, 2016
79
38
58
Is the code being developed already open source? Or is it being kept under wraps for now?
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
Is the code being developed already open source? Or is it being kept under wraps for now?
Evolution is being developed in a private repository. This gives us a competitive advantage to make it harder for our competitors to just copy/paste our feature set onto their token. Once ready and launched it will become open source. If any crypto product is not open source, you can never really trust it in the same way. Open source is critically important to differentiate ourselves from the legacy banking system.
 

kot

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Dash Support Group
Mar 17, 2015
698
1,860
263
I would not call the banking system "legacy". Lets be serious [emoji16]
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
I would not call the banking system "legacy". Lets be serious [emoji16]
Uhm.....not to disagree, but this term is widely used in cryptocurrency discussion. It just means the current banking system. Ask around....

Even in computer parlance, the legacy system is the old system. That's all it means.
 

xjones

Member
May 22, 2016
79
38
58
Evolution is being developed in a private repository. This gives us a competitive advantage to make it harder for our competitors to just copy/paste our feature set onto their token. Once ready and launched it will become open source. If any crypto product is not open source, you can never really trust it in the same way. Open source is critically important to differentiate ourselves from the legacy banking system.
How authoritative is this information? (Since you signed up on this forum only recently.)
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
Not authoritative at all. I own two masternodes and I primarily hang out over on the Slack channel. I don't even have my fancy masternode badge set up here. Anyway, DashNation slack is where the conversation occurred originally. I'll see if I can find it for a minute...steps away...hmmmm

The search function is not particularly good on the slack channel. But...if you go over there, and you go to the evolution channel and ask, I'm 100% confident that someone could give you an authoritative answer. If you're not a member already, here's an invitation:

https://dash-nation-invite.herokuapp.com/
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
Not authoritative at all. I own two masternodes and I primarily hang out over on the Slack channel. I don't even have my fancy masternode badge set up here. Anyway, DashNation slack is where the conversation occurred originally. I'll see if I can find it for a minute...steps away...hmmmm

The search function is not particularly good on the slack channel. But...if you go over there, and you go to the evolution channel and ask, I'm 100% confident that someone could give you an authoritative answer. If you're not a member already, here's an invitation:

https://dash-nation-invite.herokuapp.com/
Let me know what you find out. I would hate to pass around inaccurate information.
 

TheSingleton

Active Member
Masternode Owner/Operator
Mar 27, 2017
275
140
103
Evolution is being developed in a private repository. This gives us a competitive advantage to make it harder for our competitors to just copy/paste our feature set onto their token. Once ready and launched it will become open source. If any crypto product is not open source, you can never really trust it in the same way. Open source is critically important to differentiate ourselves from the legacy banking system.
I can confirm that.
 

xjones

Member
May 22, 2016
79
38
58
The authoritativeness of information depends on the people from whom you got it, not on the forum where you got it.
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
The authoritativeness of information depends on the people from whom you got it, not on the forum where you got it.
Ah, but I can assure you, people with first hand knowledge can answer your question over on the Slack channel. Who would you consider authoritative?
 

kot

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Dash Support Group
Mar 17, 2015
698
1,860
263
There is no reason to argue about authoritativeness :)
Evo is being developed as a confidential project and code is being stored in private repositories. It will be released and open-sourced together with the product.
 

xjones

Member
May 22, 2016
79
38
58
Ah, but I can assure you, people with first hand knowledge can answer your question over on the Slack channel. Who would you consider authoritative?
Generally, the most authoritative information comes from the combination:

credible person + credible physical evidence​

It's not a good idea to choose the person or the evidence ahead of time.
 

solarguy

Active Member
Mar 15, 2017
867
413
133
60
And you are satisfied now? And what's the question behind the question? Were you concerned that it wasn't really open source? Or some other concern?
 

xjones

Member
May 22, 2016
79
38
58
And you are satisfied now? And what's the question behind the question? Were you concerned that it wasn't really open source? Or some other concern?
What happened was that you made some assertions ("Evolution is being developed in a private repository....") that made you sound like an insider or a member of the core team. But you had only recently signed up on this forum, so that seemed like a contradiction to me. That's why I asked if your information was authoritative. You replied that it was not, and I was satisfied at that point.
 
  • Like
Reactions: solarguy
Status
Not open for further replies.