Jakub Smékal

I think I'm looking for an alternative to `getAddresses`, because I think that requires all the contracts being deployed locally with barge running, although I think that's separate to the...

@miquelcabot I have managed to solve the above error, but have been getting a JSON RPC error, which I traced back to my web3 provider, I changed it to the...

Update: I got up to ProviderInstance.computeStart in the compute flow, there it crashes with a Compute start failed: 400 from the post request to https://v4.provider.rinkeby.oceanprotocol.com/api/services/compute. I'm not sure whether this...

**Update** I tried sending the datatokens & algorithm tokens manually from a test wallet in ocean.py to my MetaMask test wallet, that meant my script was not attempting to buy...

Hi @bogdanfazakas, thanks a lot for the reply! I tried making the changes you proposed, but the error still persists. Removing the check of datatokens and just going straight to...

@bogdanfazakas Yes, the issue is still relevant, the C2D does not work when I attempt to buy datatokens with the `buyAndOrder` function, do you have any resources where datatoken buying...

Hey @AbhinavTuli! Thanks a lot! I am still working on the final implementation of `copy` and `delete` functions & their corresponding unit tests. I will push the updates to this...

Hi @tatevikh. I signed the CLA but then I accidentally pushed a commit with incorrect credentials. I tried to git rebase that commit but it seems it hasn't been updated...

@jasongrout Thank you for the reply. I have tried adding that to my package.json so it now looks like this: ``` "browser": { "stream": "stream-browserify", "http": "stream-http", "https": "https-browserify" },...

Thank you @jasongrout. Do you think changing the web3.js package.json should solve the issue for web3-providers-http as well? I tried adding the line proposed in https://github.com/ChainSafe/web3.js/pull/5274 to the web3js package.json,...