2018-01-18 Engineering Meeting

Community Meetings
#1

Date/Time: 2018-01-18 @ 14:00 UTC / 09:00 EST / 22:00 HKT
Meeting link: https://zoom.us/j/432646691

Attendees

@Jack Z
@Jude N
@Aaron B
@Larry S
@Muneeb A
@Ryan S
@Ken L
@Sebastian D
@Guy L

Agenda

Transaction Generation and blockstack.js API

Desired outcome: answer the following 3 questions

  1. Should we use WIFs or Secret Key hexes (which we use elsewhere, but are not a standard, and have resulted in a bunch of compressed vs. uncompressed issues, and will likely cause issues in the future as well as make integration with other wallet software more difficult)
  2. Should we coerce given addresses based on the provided network?
  3. Does the network object API make sense? This could be used for existent calls as well – like nameLookupUrl

Decisions:

  1. We decided to continue to use Secret Key hexes because it’s what we already do and seems to be more compatible with a wider range of software. WIFs are bitcoin-specific.
  2. No, we should stop coerce addresses into other network formats. Our whole stack should support multiple networks. This will require changes on the browser.
  3. Users shouldn’t have to configure core nodes on each call - we decided there should be the ability to configure the imported blockstack object and then optionally override any settings in the options object on any call.

Authentication

We think this portion of our platform should be among the first to turn into a spec. @larry will circulate a doc with action items and issues that should be addressed in authentication.
Update: the doc Review & Spec creation for Blockstack Authentication

Devops

We had a brief discussion about several dev ops tasks and services that we could potential deprecate.

Stacks Blockchain

  • We need more requirements before design of this can begin.
  • Jude is going to work on getting a blockstack testnet up and running.

Technical debt reporting

We’ll each circulate a document with the technical debt that we know about. From that we can figure out how we want to prioritize various items given our product roadmap.

3 Likes
#2

Hello Guys,

Awesome work by the way,

If you can please talk more about Documentation so we have advanced docs and more examples please!!!

and we need to know the limitations like how much max file can putFile upload? and what types… and so on! encryption type?
putFile upload progress in the promise?

Should we each time we GetFile send the whole content after we append to it or what?
what if the file gets bigger and bigger?

thank you

1 Like
#3

Something I’d like to discuss is the expected API and behavior of the blockstack.js transaction generation.

Issue here:

Namely, I want to answer the questions 1, 3, and 4 in the issue:

  1. Should we use WIFs or Secret Key hexes (which we use elsewhere, but are not a standard, and have resulted in a bunch of compressed vs. uncompressed issues, and will likely cause issues in the future as well as make integration with other wallet software more difficult)
  2. Should we coerce given addresses based on the provided network?
  3. Does the network object API make sense? This could be used for existent calls as well – like nameLookupUrl
#4

Might be able to join a bit later and would be cool to discuss the TypeScript declarations as @jackzampolin suggested :slight_smile:

More information:

Edit: Won’t be able to join. Feel free to discuss this anyway :slight_smile:

1 Like