Issue Summaries - Aug 24, 2018


#1

Like most open source projects, Blockstack has created many channels to interact with the community both asynchronously (the forum, github, etc) and in realtime (slack, telegram, meetups, hackathons, etc). We’re experimenting with a practice of posting bi-weekly issue summaries. With this, we wanted to assess a periodic, comprehensive snapshot of reported issues, as a starting point to optimize our engineering cycles by prioritizing the most critical and impactful issues in the community.

We decided to kick this off by first accumulating user feedback through the numerous venues we interact with the community in an open source environment.

Currently, we are categorizing issues in three broad categories:

  • bugs and errors under investigation
  • prohibitively difficult for users and/or developers
  • feature requests

We currently report issues by both developers, users who host blockstack-core nodes and users who do not host nodes, together. Many of the issues currently overlap.

We then decided to address these issues in sprints, reporting on the issues we tackle in each sprint in a public kanban here: https://github.com/orgs/blockstack/projects/29

We always recommend checking the kanban to see what Engineers are working on in regards to user reported issues. The current process for how issues end up in the kanban is as follows:

  • A report of the issues, both outstanding and new from the previous two weeks, will be posted every other week, before the beginning of a new sprint on the forum by Friday 11:59pm EST.

    • The goal of this is that it can be read by Engineers before the Monday engineering meetings.
  • Engineers will respond in the forum with issues they are working on. If these are new issues not mentioned previously in the thread, they should elaborate on those issues.

  • After the meeting, the topics posted on in the forum, and any changes based on conversation in the open meetings will be posted in the kanban https://github.com/orgs/blockstack/projects/29, where you can keep track of issues throughout the sprint.

  • A summary of issues fixed in each sprint will be posted the Wednesday after each sprint. Issues resolved in the previous sprint are listed here: Blockstack Bug Fix Sprint in Review - August 15, 2018

As we are focused on addressing the most impactful issues, we anticipate some issues will be addressed across multiple sprints, with the kanban providing support for dedicating Engineering cycles to prioritizing these issues.

We welcome your feedback and review.


#2

Bugs and Errors outstanding or reported during this sprint

Sending bitcoin has strange error messages and behavior

App private keys should use longer derivation paths

Automatically restore all IDs on restore

Mobile SDKs don’t work with React Native

Transit private key change

  • blockstack/blockstack.js#331
  • People have reported this issue both on this github issue, and someone brought it up on our slack as well
  • Basically — the transit private key changes between when the authRequest was generated and when the application tried to validate and log the user in.
  • The most common cases where this happen are (1) trying to sign into a blockstack app in incognito mode, and (2) a different default browser is set on your computer than the one you tried to log in with.

Requesting email scope doesn’t return email

Blockstack.js storage routines difficult to use outside of logged in web app

Old profile location in zonefile would cause login to fail or hang

Non-standard treatment of TLDs in search endpoint

Method for searching pending subdomains, directly querying a specific registrar

Github gist proofs should fail if the gist is a fork

iOS App ends up with different Gaia address for same app private key

Sponsored name copy on the “More IDs” page

  • This needs to say “usable immediately” when registered from the more IDs page, rather than the normal on-boarding flow.

Setting up gaia is hard

Connecting to regtest/testnet from browser is not trivial

Hosting blockstack-core nodes is difficult for non power users

  • This is feedback from enthusiasts on #engineering
  • Potential solutions:
    • re-instate apt package installs
    • improved dockerfiles (images could be much smaller, instructions could be better)

New CLI is hard to install

Legacy wallet transfers

  • There’s a whole host of legacy wallet formats (e.g., the scrypted wallet.json files, old derivation paths from the browser, the older, improper key-lengthened encrypted wallet.jsons) that people occasional need to deal with — we should have a utility to help with that
  • Forum:

Confusing or non-existent error codes in blockstack.js

Magic recovery code validation fails when there’s a return character at the end

Email screen copy in restore flow is inaccurate

Social level 0 after updating Blockstack browser

Async registration test times out some times

Non-square Avatars don’t render correctly

Wallet buttons not rendered in sync on mobile

Noscript regression in browser

Uploading large photo fails silently


listed #3