“First place went to XCarbon, a father and son team, Kaushik, and Soham Ashodiya! They delivered an outstanding presentation which can be viewed below. It was very well organized and the solution has great promise. The solution they provided, was for Carbon detection in large cities. The data would be captured by iOT devices, and stored on the Algorand Blockchain. It provides an immutable ledger so the data can not be tampered with.”
WOULD BE STORED – but how much data? I couldn’t find any trace of storing any data in GitHub.
I think that a separate file storage solution WOULD be necessary.
It looks like they are using Assets to represent carbon. Another option could be to upload sensor data to the note field, which can be 1kb of data per transaction.
As I saw, they distribute Carbon asset for uploading data, but the data is NOT YET uploaded.
Take a medium city like Budapest, with 100 sensors, 10 measurements/hour, 1 Kbyte data block,
that would mean a daily 24 MB of data. Not so bad. But to write the note field has additional costs.
I don’t know the exact value, lets assume: 0.01 Algo/byte, then the daily operating cost of this system would be: 240000 Algos!
That’s why I think that a saparate file storage is necessary.
If they are dealing with large amounts of data, they can always use an external source and use the note field or an asset to point to the external location. That said, currently, most transactions cost 0.001 Algos. This may go up based on congestion but as it stands now that would be 2400 transactions per day or 2.4 Algos for 1 transaction per hour. If they did 10 transactions per hour, that would be 24.