Desired outcome: What needs to be done to make gaia hubs deployable by users?
STACKs token inside the Atlas network
Owner: @jude Background
Users earn STACKs by operating subdomain registrars, and can set a STACKs price for including a subdomain creation TXT record. Users mine STACKs by burning BTC in the OP_RETURN of a NAME_UPDATE; the allocation of STACKs is spread across all NAME_UPDATE burns across a wide interval (as described in the paper). At the same time, the server-side subdomain indexing logic only accepts the subdomain creation record if the user’s address has enough STACKs in it (at which point is is debited the cost of the subdomain, and the NAME_UPDATE sender is credited it). Since the new subdomain code allows any NAME_UPDATE to update/transfer a subdomain, the user isn’t beholden to a specific subdomain registrar to manage their subdomain (they only need to find one to buy). The PoC would have a sunset date at the time of the next hard fork (November 2018).
Pros:
can run on the production network without breaking consensus, and can be ready before Berlin
easy to implement (server-side subdomain indexing is in pretty good shape in the feature/blockstackd-subdomain-indexing branch)
architecturally speaking, this is very similar to what we had been planning
we encourage users to mine “blocks” (really zone files) and aggregate “transactions” (really subdomain updates/transfers and a new token transfer TXT record we’d add for the PoC)
Desired outcome: Should we do this before the berlin event?
Community Questions/Comments
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.
I’ll turn proposed items into an agenda prior to the the meeting.
Desired outcome: Can we use blockchain to store the files even if it’s slow, may be have the file can be uploaded fast to S3 while they’re being uploaded to the blockchain then when that’s done uploading switch the files link from S3 to the blockchain link so we can access it (download or view it) possible encryption too?
There would be little to no cost uploading to S3 since the actual file would take 6 to 8 minutes to be uploaded to the blockchain then the files on S3 get deleted and only stored on the blockchain which will offer unlimitted space but limited size per file (8MB according to Jack?)
Desired: users can deploy their own gaia hub and the instructions are well tested
Blockstack Core API Deployment:
Background: Currently the core api (core.) indexing operation relies heavily on the filesystem to write temporary data and keep its place. It also keeps all indexing data in memory until the index is complete leading to data loss issues if a restart or other is needed.
Desired: The indexer uses mongodb to store the list of names and as new profiles fetched they are immediately inserted into the DB. The indexer should rely on Mongo for state instead of files on disk.
@aaron is there a way we can have a tool to simply run a few commands and voila! regtest is installed and ready? This would be the most optimal tool. Quite important for developers. Thanks.
@aaron is there a way we can have a tool to simply run a few commands and voila! regtest is installed and ready? This would be the most optimal tool. Quite important for developers. Thanks.
This is ideally what the docker images are, right now. If they don’t behave that way, then that’s a problem that should be fixed. Longer term, there should be easier options (likely, a testnet).
