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.
vsund
commented
7 years ago
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.