December 25, 2024

Table of Links Abstract and Introduction Preliminaries Overview Protocol 4.1 Efficient Option Transfer Protocol 4.2 Holder Collateral-Free Cross-Chain Options Security Analysis 5.1 Option Transfer Properties 5.2 Option Properties Implementation Related Work Conclusion and Discussion, and References A. Codes B. Proofs 5 SECURITY ANALYSIS We analyze and prove the properties satisfied by our proposed protocol. Recall from the previous illustration that Alice/Carol is called the holder, and Bob/Dave is the writer, and Carol or Dave is

Table of Links Abstract and Introduction Preliminaries Overview Protocol 4.1 Efficient Option Transfer Protocol 4.2 Holder Collateral-Free Cross-Chain Options Security Analysis 5.1 Option Transfer Properties 5.2 Option Properties Implementation Related Work Conclusion and Discussion, and References A. Codes B. Proofs 4.2 Holder Collateral-Free Cross-Chain Options We want to remove the need for upfront collateral from Alice without using a cross-chain bridge. Allowing Alice direct access to the exercise secret risks Bob’s asset since Alice has

Table of Links Abstract and Introduction Preliminaries Overview Protocol 4.1 Efficient Option Transfer Protocol 4.2 Holder Collateral-Free Cross-Chain Options Security Analysis 5.1 Option Transfer Properties 5.2 Option Properties Implementation Related Work Conclusion and Discussion, and References A. Codes B. Proofs 4 PROTOCOL Due to the complexity of efficient holder collateral-free options, we elaborate on the protocol gradually. We first introduce the efficient transfer of an option in Section 4.1. Next, we outline how to achieve

Authors: (1) Xueying Mao, School of Computer Science, Fudan University, China (xymao22@[email protected]); (2) Xiaoxiao Hu, School of Computer Science, Fudan University, China ([email protected]); (3) Wanli Peng, School of Computer Science, Fudan University, China ([email protected]); (4) Zhenliang Gan, School of Computer Science, Fudan University, China (zlgan23@[email protected]); (5) Qichao Ying, School of Computer Science, Fudan University, China ([email protected]); (6) Zhenxing Qian, School of Computer Science, Fudan University, China and a Corresponding Author ([email protected]); (7) Sheng Li, School