You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently blob-daddy allows posting arbitrary blobs to Celestia and Avail. We want to update the UI to allow users to verify the availability of their posted blobs.
Approach:
Posting and verification are currently separate processes. You cannot immediately verify the availability of a blob on L1 right after posting it to DA (not yet). The time gap is a couple hours. So its best to keep them on separate pages or tabs.
The flow would go like this:
Choose DA
Enter txHash for Celestia or (block height, extrinsic index) for Avail
Click Verify button
Show some blob data associated with the txHash
Show Verified message alongwith:
link to contract
decoded data sent to our verifier contract
Profit?
Bonus
We could also have them upload blob data to check its availability. It'd be pretty cool.
Live demo this and send this out on socials.
On the UX of this, if we are building this.
We can have this:
A page where all jobs are listed and user's own jobs are shown with highlighting as we can store their job IDs in the localStorage and show it to them later. [Requires -> API for fetching all Jobs with DA and time submitted]
In the list there is a button (enables 2 hours after submission) in each row for "Verify", clicking on which opens a modal where you can fetch the inputs (share pointers and info) for proof verification [Requires -> API for fetching proof input by Job ID]
After you have the inputs, we show a button for "Verify the Proof" and we do RPC call on DA Contract from user's browser only and verify it, also show them the bridge transaction it was included in.
Currently
blob-daddy
allows posting arbitrary blobs to Celestia and Avail. We want to update the UI to allow users to verify the availability of their posted blobs.Approach:
Posting and verification are currently separate processes. You cannot immediately verify the availability of a blob on L1 right after posting it to DA (not yet). The time gap is a couple hours. So its best to keep them on separate pages or tabs.
The flow would go like this:
txHash
for Celestia or (block height, extrinsic index) for AvailtxHash
Verified
message alongwith:Bonus
We could also have them upload blob data to check its availability. It'd be pretty cool.
Live demo this and send this out on socials.
cc @kautukkundan
The text was updated successfully, but these errors were encountered: