Provisioned data type is 'assertion', instead of 'asset'

[Aescwine]

Issue description

When resolving a previously provisioned asset, the data type is being returned as assertion and not asset. No errors or warnings are seen in the logs, but it looks as though no proofs are being found for the assertion. I've not gotten as far as working out if the proofs are failing to be created, or that they are just not being fetched correctly on /resolve.

Expected behavior

When provisioning an asset using the /provision/ API, the data type should be asset.

Actual behavior

Provisioned assets are being returned as having the data type assertion.

Steps to reproduce the problem

1. Provision an asset
2. Resolve a provisioned asset by id
3. Returned data has "type": "assertion"

Specifications

• Node version: v6.0.0-beta.1.23
• Platform: WSL Ubuntu
• Node wallet: 0x31c98399d3D162fC9bFBFe25C3fc1e41D19ed711
• Node libp2p identity: QmQcY1XgxvSALM8bRupeoVnRHVFv1FBPGrntY97X9w49oC

Contact details

• Email:

Error logs

Disclaimer

Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].

[Aescwine]

Upon further debugging, this appears to be a 'feature' rather than a bug. It wasn't obivious to me that to resolve an asset, you need to resolve using the UAL rather than the id.

In terms of API design, wouldn't it make more sense to have two separate endpoints for resolving assertions and assets? This would make the APIs easier to understand and use, as well as making any API contracts easier to manage and test.

[zeroxbt]

Hi @Aescwine. You can resolve both assertions and assets. Resolving an asset will return the latest public assertion linked to that asset.

[NZT48]

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you, OriginTrail Team