A signed append only log, distributed with webtorrent would provide provenance and distribution. This would allow for not having to have dedicated infrastructure for collection.
One could also use USENET and get rid of the garbage will killfiles.
One could also use USENET and get rid of the garbage will killfiles.
You can't just "create a blockchain". Blockchains depend on hashing power for security. A new niche chain provides very little security, and a rich person like Elon could set up a hash cluster to out-hash everyone else and block updates for his jets.
In order to fund hashing power and security, there has to be economic incentive for the miners. That requires some token, which ultimately requires everyone who submits updates to pay a fee.
The reasons I and many other people provide ADS-B data to aggregation sites is that it's free (minus the one-time cost of the hardware) and I get something in return: a free upgraded account which, depending on the site, enables historical flight searches. If I lost money every time I provided data, it wouldn't make any sense to continue.
I also wouldn't want to have to download an entire (or a good chunk of a) blockchain or raw data ledger to check history for a tail number. That's what I'd have to do if it were truly decentralized. Ledgers do not provide efficient indexing.
EDIT: Regardless, the point I'm making is this is just way more work for something that really doesn't need a blockchain.
I'm genuinely curious but isn't Webtorrent just using WebRTC to join a Torrent Swarm? Torrents are fundamentally immutable, the identifier is a static hash of the content of the torrent. That would mean producing a new torrent for each new data point or chunk of data points only to then submit that hash to a WebRTC based connection to again fetch torrent content?
Genuinely curious, I'm interested in how torrent swarms can be used for novell applications.
If you are going to log, I'd look into CF offerings.