Use createAsset util function from ocean.js.

[mariacarmina]

Fixes #11 .

Changes proposed in this PR:

• Use createAsset util function from ocean.js.
• Change params order
• Update to latest version of ocean.js

[mariacarmina]

@jamiehewitt15 should we create a separate issue for integrating support for sapphire, meaning datatoken template id 4 and accesslist factory? I wouldn't include the oasis integration in this PR.

[jamiehewitt15]

@jamiehewitt15 should we create a separate issue for integrating support for sapphire, meaning datatoken template id 4 and accesslist factory? I wouldn't include the oasis integration in this PR.

Yeah, let's do it seperately

[jamiehewitt15]

I tested it locally barge and got this error. Do you know what might be causing this?

[mariacarmina]

I tested it locally barge and got this error. Do you know what might be causing this?

That error comes from latest release of ocean.js, make sure that the chain ID from the json sample matches the network configured (8996).

[jamiehewitt15]

I updated the metadata to have the right chainId, but now I'm getting another error. Have you seen this before?

[mariacarmina]

I updated the metadata to have the right chainId, but now I'm getting another error. Have you seen this before?

We have a separate issue for this where accesslists will be integrated https://github.com/oceanprotocol/vscode-extension/issues/16, let me double check why that address error is popping up.

[jamiehewitt15]

We have a separate issue for this where accesslists will be integrated https://github.com/oceanprotocol/vscode-extension/issues/16, let me double check why that address error is popping up.

Ok, we should still be able to publish assets on barge though?

[mariacarmina]

We have a separate issue for this where accesslists will be integrated #16, let me double check why that address error is popping up.

Ok, we should still be able to publish assets on barge though?

Yes, of course, I think the way that we retrive the contract addresses makes that error occur.

[jamiehewitt15]

Yes, of course, I think the way that we retrive the contract addresses makes that error occur.

Ok, so we need to fix that first then...

[mariacarmina]

Hello @jamiehewitt15:

extensionHostProcess.js:162
Finding the service endpoints failed: FetchError {message: 'request to https://node5.oceanprotocol.com:8…on: connect ECONNREFUSED 34.122.123.116:8000', type: 'system', errno: 'ECONNREFUSED', code: 'ECONNREFUSED', stack: 'FetchError: request to https://node5.oceanpro…ons (node:internal/process/task_queues:82:21)'}
extensionHostProcess.js:162
Error details: Error: HTTP request failed calling Provider {stack: 'Error: HTTP request failed calling Provider
    …vscode-extension/dist/extension.js:122:48789)', message: 'HTTP request failed calling Provider'}

I did not receive the error with accessListFactory address, I used ocean-lib v3.4.4., used remote node on sepolia

[jamiehewitt15]

Still getting the same error:

Testing locally with barge, which is working fine on the main branch.

[mariacarmina]

I think it is coming from some setup error w barge, on optimism sepolia, I could've published without problems the asset.

DID published on op. sepolia: did:op:ba6518f6d3b7b6e41293bdf57a02aed11dbbf0c7a51272dd77e4cf246447321a