https://github.com/oceanprotocol/squid-js/blob/master/src/ocean/utils/SignatureUtils.ts#L9
and
https://github.com/oceanprotocol/squid-js/blob/master/src/brizo/Brizo.ts#L108
If I am correct, I (will) may have additional questions. I hope you won't mind if I contact you again about them.
Thanks
documentKeyId is the didsquid-java should already have a method to sign a message, maybe you don't need to implement this.
for the signature all you need is to do the equivalent of
this.web3.eth.personal.sign(text, publicKey, password) where text is the did, publicKey is the eth addressin the encrypt method, the
document is the files list from the ddo.metadata.main section
oceanprotocol/squid-java#151
I included what I though are the most relevant messages from our conversation to date.
Hello Data Economy Challenge participants,
Thank you so much for your diligent work and compelling contributions to the challenge! We're deep in the judging process now and thrilled with the creativity and quality of submissions so far, with winners emerging as we close in on Announcement Day (29 January)!
In the meantime, would you be willing to take a few minutes to fill out the Data Economy Challenge Participant Survey?
We hope to take your perspective into account as we learn from this pilot challenge to create the best possible hackathons, bounties and onboarding experiences for our developer ecosystem.
Please follow this link to the survey:
https://docs.google.com/forms/d/e/1FAIpQLSdFiTKarjVpK54PtMjC1dNHRF_kDY8o9fERjtedZDsX9LPa-g/viewform
Cheers,
Beth and the Ocean Team
Questions?
If you have any questions about the hackathon or survey, please reach out in one of the following ways:
- email beth@oceanprotocol.com
- message Beth on Telegram, Gitter or Discord @ontologymachine
- post on the discussion forum
The other one is that smart contracts don't run well in my deployment
@pallares6 when running under http://localhost:3000 to which network are you connected in MetaMask? You should choose Localhost:8545, and NOT Nile because the networks are all remote networks.
As for the red Contracts lamp, you can ignore that for now if the only warning message in browser console you see is Error on contract ComputeExecutionCondition. This is a known issue right now with Brizo loading v0.13.1 of keeper-contracts but squid-js already loads v0.13.2. This should not affect any existing live functionality, meaning publish & consume should still work
@kremalicious @ssallam I noticed that keeper contract releases are no longer on maven.
When I go to
https://www.npmjs.com/package/@oceanprotocol/keeper-contracts/v/0.13.2#packages
it states:
"To facilitate the integration of the Ocean Protocol's keeper-contracts there are Python, JavaScript and Java packages ready to be integrated. "
and
" Java Maven package - The Maven keeper-contracts package provides the same ABI's to be used from Java.
The packages contains all the content from the doc/ and artifacts/ folders."
Where can I get the latest release of keeper contracts?
If the jave version of keeper contracts is no longer available, and effectively, yuou are no longer supporting Java, please let me know. I will find an alternative solution for my application.
I would appreciate a response to this post. I do not want to keep bothering you, and wasting your and my time.
Thanks
1) Store detailed location information for access points (AP) (primarily WiFi)
2) For each AP with a record stored on the blockchain, update that record as needed (using CRAB approach)
3) Retrieve record of APs in the vicinity (as given by one GPS reading) of a user's current location to accurately estimate that user's indoor/outdoor location
The above three functions have been implemented and work using the bigchainDB testnet. Until last summer, using squid-java I was on my way to completing implementation to store, update and retrieve AP location information on Nile testnet (I was in the final pahse of testing/debugging).
Since the changes to squid-java (version 0.8.0), my work has stopped because of issues with squid-java which @ssallam is aware of.
With functions 1), 2) and 3) running, the next phase would include storing of user location and user mobility analytics information the blockchain for resale to third parties.
I hope this answers your question.
Again, thanks for your offer to help,
Alex Donnini
"what are the req for your app? maybe you can leverage some calls to the agent"
I answered his question:
"1) Store detailed location information for access points (AP) (primarily WiFi)
2) For each AP with a record stored on the blockchain, update that record as needed (using CRAB approach)
3) Retrieve record of APs in the vicinity (as given by one GPS reading) of a user's current location to accurately estimate that user's indoor/outdoor location
The above three functions have been implemented and work using the bigchainDB testnet. Until last summer, using squid-java I was on my way to completing implementation to store, update and retrieve AP location information on Nile testnet (I was in the final pahse of testing/debugging).
Since the changes to squid-java (version 0.8.0), my work has stopped because of issues with squid-java which @ssallam is aware of.
With functions 1), 2) and 3) running, the next phase would include storing of user location and user mobility analytics information the blockchain for resale to third parties.
I hope this answers your question.
Again, thanks for your offer to help,
Alex Donnini"
I am waiting for his or anyone's answer.