Verifying ZCash Equihash on CKB

[BuildUnion]

Thanks for creating this.

[DIS] CKB Integration for Rosen Bridge

Too much multi-tasking for me these days, I should have mentioned. RGB++ only allows for creation and movement of new user-generated assets. It won’t be able to lock $ZEC on ZCash. I don’t know the exact terminology, but I think Guard-controlled multi-sig will be closest. Proof of reserve would be visible on-chain.

As confirmed, RGB++ is off the table for native ZEC — so direct Zcash integration on Rosen Bridge is the path worth exploring.

@matt_ckb

Started looking into this a bit based on this post. It seems possible that CKB could verify ZCash proof of work. ZCash uses Blake2b for hash function, we need 512 hashes to verify a header. Blake2b is roughly 20,000 cycles, so this is a reasonable number.

ZCash implements FlyClient, so with 1 header verification we could have certainty around chain history (would require verifying the FlyClient sampled headers as well)

I appreciate you digging into this, the FlyClient point is interesting. To confirm my understanding: this means CKB could trustlessly verify that a ZEC transaction actually happened on the Zcash chain, which would be the foundation for any kind of Zcash integration whether that’s Rosen Bridge or otherwise?