You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 14, 2023. It is now read-only.
Votes need to be highly available (DDoS resistant) and immutable. Probably a case for Atlas.
@jcnelson said that Atlas can store arbitrary data. It needs a NAME_UPDATE to initiate storage, which prevents DDoS but costs a transaction. Also he said that Atlas doesn't throw away any older data and stores all revisions. Seems like a good fit.
This needs a way to interact with raw zone file data. Blockstack's RPC has a /v1/names/{name}/zonefile/{zoneFileHash} for retrieving raw zone files. This also needs a way to get all relevant zone files (belonging to a poll) and a way to write raw zone file data. Since I need to interact with the RPC either way, a PR for blockstack.js would be the way to go with.
Votes need to be highly available (DDoS resistant) and immutable. Probably a case for Atlas.
@jcnelson said that Atlas can store arbitrary data. It needs a
NAME_UPDATEto initiate storage, which prevents DDoS but costs a transaction. Also he said that Atlas doesn't throw away any older data and stores all revisions. Seems like a good fit.This needs a way to interact with raw zone file data. Blockstack's RPC has a
/v1/names/{name}/zonefile/{zoneFileHash}for retrieving raw zone files. This also needs a way to get all relevant zone files (belonging to a poll) and a way to write raw zone file data. Since I need to interact with the RPC either way, a PR forblockstack.jswould be the way to go with.