This meeting is for issues around our developer facing products such as blockstack.js and the mobile SDKs.
Agenda
Please reply to this forum post with items you would like included on the agenda.
Each item should include:
Item name Background information: Links to github issues, forum posts, etc with background information on the item Desired outcome: what decision or deliverable would you like from the discussion of this topic at the meeting?
We’ll save ~10 minutes or so for community questions or comments at the end of the meeting.
The new onboarding flow includes registration of a sponsored name. This leads to the expectation that the name will be immediately usable after onboarding. Currently, the sponsored name registration requests go into a queue on the registrar and also needs to go through the same number of confirmations as a full domain name in order to be usable.
Desired outcome:
Estimate the engineering resources needed to implement this and decide if we should prioritize this feature or change the onboarding flow.
I moved this immediately usable sponsored names issue to the Developer Products Engineering meeting agenda because this isn’t something that we can execute in one of the consumer products.
Background: Hank was great enough to open a PR that set up better logging in blockstack.js – it logs to the console, but the level is configurable via blockstack.config.
Outcome: Do we like this approach? Also, should we default to none or debug or info?
Interface for TX Signing
Background: We need to use different kinds of transaction signers than single-sig (e.g., multi-sig, segwit), even just in our blockstack-core integration tests. Furthermore, if we want to support hardware wallets, we need a different interface anyways, because they cannot pass the private key directly to blockstack.js.
Proposed interface:
Desired Outcome: feedback on that interface.
Subdomains in search results
Background: Our search endpoint doesn’t return subdomains – I have an indexer which will generate the JSON dumps required for search to work correctly with subdomains. It’s been tested, etc. I just need to deploy it.
Desired Outcome: I guess high fives? But seriously, I want to voice the concern that this endpoint is inherently batch-y. Right now, those batches are like every 12 hours, but with this new indexer, they can be roughly every 45 minutes. This could be rearchitected a little to make it less batch-y, but I need to know whether or not that’s an actual priority.