A CKB-efficient and Anti-Collision xudt Transfer Scheme on CKB L1

could these issues be resolved by abstraction?

It sounds like this kind of system is already getting kind of complicated already, would tasking an application with structuring deposit/withdrawal proofs be reasonable?

1 Like