Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
For a new add-on we are planning where the gateway operator can store and allow historical data to be sold. For this, we need to use a concept called proxy re-encryption. There is some work out there on this, but we need a practical NodeJS implementation.
Some questions and answers:
**Is the proxy re-encryption desired for data flow from Sensor generated (Stored / stream) to gateway operator ( proxy ) to data buyers?**
I would suggest we encrypt the data streaming in from the sensor where only the sensor owner can access it. On Purchase, the server re-encrypts for the buyer.
**If gateway operator is storing data, should we consider some design similar to a historian? If so what are the specifications for it?**
Not sure what you mean
**Any specific algorithm planned for the whole process of encryption?**
We currently use ECIES for most encryption. Something ellipic curve so we can use the ethereum public and private keys would be cool.
**For added safety, does this process require any validation of certification during initial exchange?**
Not at this time