ionic side (Order of ai commit)

[sync-by-unito]

Expectation

Every asset when it is register from Capture Cam, it should have two commits.

1. initial registration
2. commit(miningPreference...)
3. For miningPreference value, please refer gitbook
4. the default should be "notAllowed"

┆Issue is synchronized with this Asana task by Unito
┆Created By: Kenny Hung

[sync-by-unito]

➤ Sam commented:

Kenny Hung, (cc: Ethan Wu) want to clarify.

Capture cam should not care about commits, right?

Capture cam should only care about

1. Making sure user can capture image/video asset from camera or gallery.
2. Calling backend to register asset (aka Create an asset ( https://dia-backend-dev.numbersprotocol.io/api/v3/redoc/#operation/assets_create ) handled from ionic side)
3. Calling backend to mintAndShare (currently is handled from bubble iframe side)

So it' not clear what is expected form ionic side?

Should I set miningPreference to notAllowed from capture cam?

[sync-by-unito]

➤ Kenny Hung commented:

Sam (cc Tammy YangEthan WuScott Yan)

No, we want every asset from Capture service(including Cam, dashboard) to have consistent experience.

So when user takes a photo or upload from gallery, the asset should have 2 commits.

The first one(initial registration) should be the same now.

The second one should be like the asset from dashboard, the commit will show the "miningPreference" is "notAllowed"

1. sample asset: https://nftsearch.site/asset-profile?nid=bafkreibze5ybkaceei3awt6cmttix3sq7g2ctldj4arjfolacxg7jc3nem ( https://nftsearch.site/asset-profile?nid=bafkreibze5ybkaceei3awt6cmttix3sq7g2ctldj4arjfolacxg7jc3nem )
2. sample assetTree: ipfs-pin.numbersprotocol.io/ipfs/bafkreihkxk2soz242fxgyyqmghpmbt7prc4buo7ffrxg5jinsoqz4a6qri ( https://ipfs-pin.numbersprotocol.io/ipfs/bafkreihkxk2soz242fxgyyqmghpmbt7prc4buo7ffrxg5jinsoqz4a6qri )
3. detail format please refer https://docs.numbersprotocol.io/introduction/numbers-protocol/defining-web3-assets/assettree ( https://docs.numbersprotocol.io/introduction/numbers-protocol/defining-web3-assets/assettree )

[sync-by-unito]

➤ Sam commented:

Kenny Hung, thank you for clarification.

[sync-by-unito]

➤ Sam commented:

Ethan Wu, I have no access to bubble dashboard. So I need to clarify the following.

What API is called from Capture Dashboard during creation ( https://dashboard.captureapp.xyz/version-test/main?tab=createnft ).

Tammy Yang, would be nice to have access to Capture Dashboard so I could inspect the API call or the logic so I can keep ionic implementation as close as possible to bubble implementation to keep experiences as consistent as possible.

[sync-by-unito]

➤ Ethan Wu commented:

Sam

we are calling the following:

1. Create An Asset: https://dia-backend.numbersprotocol.io/api/v3/assets/ ( https://dia-backend.numbersprotocol.io/api/v3/assets/ )
2. Commit : https://docs.numbersprotocol.io/developers/commit-asset-history/commit-via-api ( https://docs.numbersprotocol.io/developers/commit-asset-history/commit-via-api )

[sync-by-unito]

➤ Ethan Wu commented:

Sam

what we do is

(1) create an asset

(2) after 5 minute delay create commit

[sync-by-unito]

➤ Sam commented:

Ethan Wu, thank you for clarification. The screenshot is very helpful. 🙏

[sync-by-unito]

➤ Sam commented:

Ethan Wu, is it a requirement (or a limitation) to call create commit after 5 minute or it's okay to do create commit after asset registration immediately?

[sync-by-unito]

➤ Ethan Wu commented:

Sam there needs to a delay because what happens is if you call the immediately what you get is the commit appearing before initial registration

[sync-by-unito]

➤ Ethan Wu commented:

Sam i have tested this many times. the 5 minute duration can maybe reduced maybe.

most of the time people don't look at the asset profile immediately so its ok if the commit appears a little later.

[sync-by-unito]

➤ Sam commented:

Kenny Hung, (cc: Tammy Yang).

I would suggest to move ionic side (Order of ai commit) (Implement on 0731 sprint) ( https://app.asana.com/0/0/1205120894428797 ) to next milestone.

Because bubble side has built in scheduler that can trigger certain actions after certain time. However on ionic side we need to implement it manually and test it carefully. Also ionic side should consider offline cases.

Since v230808-capture-app-ionic-launch ( https://app.asana.com/0/inbox/1202182817452381/1205132295508392/1205217942354076 ) release is tomorrow I don't think this task can be implemented and test in one day.

Please let me know what you think.

[sync-by-unito]

➤ Kenny Hung commented:

Sam (cc Tammy YangScott Yan )

Okay, Shall we exchange [FR] Remove options from list on ionic asset page ( https://app.asana.com/0/1201083422707776/1205200411494663/f ) with this task?

If not, it's also fine.

[sync-by-unito]

➤ Sam commented:

Kenny Hung, I would suggest not to exchange.

[sync-by-unito]

➤ Kenny Hung commented:

Wait, I notice this task is in our roadmap ( https://docs.google.com/spreadsheets/d/14xP-HuGdiS5UExmn3ebMKpjGEqqbTPEa5GJCOLM0WSU/edit?pli=1#gid=1112418286 ), we need Tammy Yang's confirmation. (Push this item into next sprint.) (cc Sam)