I'm exploring the potential of the blockchain technology as a distributed database for specific use in my profession. I'm looking for any thoughts/suggestions you might have on this idea and how I might approach such a problem. Ideally, if there is a similar altcoin that I could use to start my own project, that would be ideal. Here goes...
I work in a profession with very specific/specialized data. Currently, our data process goes as follows:
- Individuals/Agencies submit site survey data to a central organizational authority in my field - location data, input quantity data, output quantity data, date/time, etc.
- Overall this information is simple, not tons of information for every data point - integers, float, chars, short text, etc. No blobs or images required.
- The central authority indexes and correlates this data into manuals with trend lines and formulas based on predefined site classifications, but these manuals are only updated *gasp* every few years!
- If you want a rate/formula from the data that doesn't fall within the predefined categories, you're pooched, unless you do your own site surveys. What if you want a custom query? You can't.
What I had in mind was something along the lines of the following:
- The cohesiveness/validity of the data itself is paramount. There is nothing secret or sensitive here.
- The source of the data should be known (ie know a user is legit) or identifiable (ie can self identify who they are). Could this be something like every mined "coin" would be one data point, belonging to a "wallet" aka user?
- There should be a way to ensure nodes are spawned to maintain the network.
- Would be nice if the data were editable/deletable by the original user.
- I don't foresee this blockchain becoming huge, as the data is simple (see above).
- There would be a need to index and query the data points so that attributes could be collated/excluded, a rate generated, and applied in additional analysis.
- Private keys don't really have to be kept too secure, unless you want someone to steal your "data points"! LOL
- A standard set of agreed upon database fields would be a good starting point, but expandability would be helpful (always the unforeseen).
I think that's good for a start. Likely forgetting *something*, but will post more if ideas come.
Thank you for any help you can provide.
CHEERS!!
