2018-02-15 Engineering Meeting

Community Meetings
#1

Date/Time: 2018-02-15 @ 14:00 UTC / 09:00 EST / 22:00 HKT
Length: 45 minutes
Meeting link: https://zoom.us/j/416493133

#2

2018-02-15 Engineering Meeting Notes

Attendees

  • Larry
  • Ken
  • Martin
  • Jude
  • Chase
  • Shankarganesh PJ
  • Jack
  • Aaron
  • Dhaval Shah
  • chokha
  • mkdir

Process

In the future, we’ll create the post for next week’s engineering meeting immediately after posting the notes from the current week so that people can add potential agenda items as the week progresses.

Client-side transaction generation update

Ken: Running into some problems
Estimate: end of this week if we can fix the bugs

Subdomain update

  • For this sprint what is remaining is essentially to deploy the production registrar and then we will be ready for internal testing.
  • Aaron will update regtest mode to use the node subdomain production registrar

UTXO discussion

  • Do we want a driver model in blockstack.js?

Decision: Possibly, but not at this time. creating a driver model right now would be over-engineering.

Evangelist Question

  • Ethereum developers at a meet up in India asked about writing Blockstack apps - will they have to rewrite apps as things change?

Answer: No, we will soon have stable versions of developer libraries so that apps written will continue to work with minimal changes.

1 Like
#3

There was some additional discussion about the API(s) that should be supported now —

The current status of the feature/blockstack-operations branch’s network.js implementation is that it interacts with:

  • blockchain.info API in mainnet
  • bitcoind in regtest

The plan would be to use insight-api instead of blockchain.info in mainnet — @jackzampolin is working on deploying infrastructure for us which will implement the insight-api.

As far as regtest goes, in an ideal world, we have support for the insight-api in the regtest environment – then the difference between the mainnet and regtest networks in blockstack.js is just the default URLs. However implementing and testing that will probably take 1-2 days of engineering effort, so maybe we continue interacting directly with bitcoind in regtest for now?