@martijnbolt while barge is mainly optimized for local development, there is a
--exposeip option flag exactly for the use case of a remote deployment https://github.com/oceanprotocol/barge#all-options
As far as system requirements go, the most consume hungry resource out of all components is running a full Parity node which usually requires at least 4GB of RAM, a SSD, and multi-core CPU. https://wiki.parity.io/FAQ#what-are-the-parity-ethereum-disk-space-needs-and-overall-hardware-requirements
You could also look into using Windows' WSL and run Docker in there. Or did you actually try running Barge on Windows? There was a technical restriction in Docker for Windows back when we created Barge so we decided to not support Windows at that time, which just means we do not test it on there. But by now it might just work
this.web3.eth.personal.sign(text, publicKey, password)where text is the did, publicKey is the eth address
fileslist from the ddo.metadata.main section
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:
Beth and the Ocean Team
If you have any questions about the hackathon or survey, please reach out in one of the following ways:
@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.
" 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.