Date/Time: 2018-01-11 @ 14:00 UTC / 09:00 EST / 22:00 HKT
Meeting link: https://zoom.us/j/799691635
Attendees
@jackzampolin
@jude
@larry
@ryan
@yukan.id
@guylepage3
@aaron
Agenda
Pick recurring timeslot for engineering meetings
- Proposed range: 9am to 11am EST start time Tuesday, Wednesday or Thursday
Desired outcome: A timeslot & general meeting policy
Azure rolling outage postmortem
- Everyone owns their own infra, but there is sometimes tragedy of commons with shared
- Discuss evolution of Blockstack hosted infrastructure
- What systems do we need to host going forward?
- Currently running:
utxo.blockstack.org
bitcoin.blockstack.org
core.blockstack.org
hub.blockstack.org
node.blockstack.org
browser.blockstack.org
explorer.blockstack.org
- +proofs.blockstack.org
- Currently running:
- How long do we see ourselves hosting them?
- What systems do we need to host going forward?
- Alerting system upgrades/improvements
- Consolidation
- Can we remove utxo.blockstack.org and defer to explorer.blockstack.org?
- Is explorer.blockstack.org whitelisting API calls and filtering long-requests? Does it have the protections that utxo.blockstack.org does?
New UTXO provider
- What UTXO services exist that we can deploy ourselves?
- How hard would it be to deploy our own?
- Full list of Insight API Queries needed
- Service could server backed by
btcd
nodes with nginx in front - Would be simple to scale each layer of the service
- Options
- Build with btcd
- See the implementation sections in this doc
- Build with libbitcoin
- Similar to btcd, perhaps a better maintained library, C++
- Use another index server with different api
- This has the advantage that it could run on the same hosts as the
bitcoind
nodes we have already. - https://github.com/CounterpartyXCP/indexd-server
- This has the advantage that it could run on the same hosts as the
- Implement a chain-reader to pump out UTXOs
- Already have the basics written in virtualchain
- Would allow us to pivot to the STACKS blockchain without breaking interfaces
- Build with btcd
- Further reading
Web-based Blockstack Browser
- Find way to implement protocol handlers for each browser
Drivers for Gaia Hub
- Question from #engineering
- Driver documentation? Porting existing drivers (including IPFS)?
STACKS blockchain R&D meetings
- When’s a good time to schedule this?
- What are the main questions we have?
- How do we ask questions? How do we answer them?
- Input from marketing and bizdev
- Timeline?
- Previews? Beta? Testnet?
- What do we need by the Summit?
Issue Tagging
Projects with good tagging:
- Kubernetes - 4,700 open
- Their system is to tag issues with
area/*
andkind/*
to allow sorting and thenpriority/*
once they have been prioritized - This gist gives a few examples
- The
category/instance
tagging is used in a number of projects similarly to how Kubernetes uses it. (see Hashicorp, Docker) - Lisk - 100 open
- No use of
category/
. - Each issue tagged with “kind” (standards, bug, test, etc…) and “difficulty” (easy, medium, hard)
- They also have a concept of “parent” and “child” issues. Child issues link back to parent and are marked as such
- React - 293 open
- They have
Component:
,Type:
,Status:
, andDifficulty:
- Most issues tagged with at least component and type
Meeting Notes
Pick recurring timeslot for engineering meetings
Decision: Thursday @ 14:00 UTC / 09:00 EST / 22:00 HKT
Azure rolling outage postmortem
- We plan to hire someone to do sysops
- Jack is going write some system d unit files
- We need repeatable deployments
- We need 3 shifts of people on call to handle issues
- Decision: We need to hire someone to do the creation of orchestration and then have people on duty that can solve issues if they come up
UTXO provider
- Larry: ask exchanges what they do
Web-based blockstack browser
- Aaron: we could use a cookie to remember that users had signed up on the hosted browser
- The right time to address this is when address on-boarding process
Drivers for Gaia Hub
- Jude: port Blockstack drivers and take notes on the experience
STACKS blockchain R&D meetings
- Jude: split between product meetings and engineering meetings
Issue tagging
- Jack has done some research on issue tagging which he will share on a forum post for discussion