這裡將詳細地對示例性實施例進行說明，其示例表示在圖式中。下面的描述涉及圖式時，除非另有表示，不同圖式中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本說明書一個或多個實施例相一致的所有實施方式。相反地，它們僅是與如所附申請專利範圍中所詳述的、本說明書一個或多個實施例的一些態樣相一致的裝置和方法的例子。
需要說明的是：在其他實施例中並不一定按照本說明書示出和描述的順序來執行相應方法的步驟。在一些其他實施例中，其方法所包括的步驟可以比本說明書所描述的更多或更少。此外，本說明書中所描述的單個步驟，在其他實施例中可能被分解為多個步驟進行描述；而本說明書中所描述的多個步驟，在其他實施例中也可能被合併為單個步驟進行描述。
圖1是一示例性實施例提供的一種跨鏈互動的示意圖。以如圖1所示的區塊鏈1與區塊鏈2之間的跨鏈互動為例，該區塊鏈1與區塊鏈2可以透過跨鏈互動系統實現跨鏈互動，該跨鏈互動系統可以包括：可信錨定器和可信證明轉化中繼器；可信錨定器中可以配置區塊鏈1的客戶端，使得該可信錨定器與區塊鏈1之間建立連接，而可信證明轉化中繼器中可以配置區塊鏈2的客戶端，使得可信證明轉化中繼器與區塊鏈2之間建立連接。
在一實施例中，可信錨定器、可信證明轉化中繼器上分別配置的客戶端可以為SPV(Simplified Payment Verification，簡單支付驗證)客戶端，可使可信錨定器、可信證明轉化中繼器的配置輕量化。當然，透過配置其他類型的客戶端，同樣可以實現相關跨鏈互動功能，本說明書並不對此進行限制。
在一實施例中，當區塊鏈1需要向區塊鏈2調取跨鏈資料時，可以在區塊鏈1上創建跨鏈請求，且該跨鏈請求的請求對象為區塊鏈2。而透過已配置的區塊鏈1的客戶端，可信錨定器能夠監聽區塊鏈1上創建的跨鏈請求，並基於該跨鏈請求所指示的請求對象為區塊鏈2以及區塊鏈2與可信證明轉化中繼器之間存在連接關係，將跨鏈請求傳輸至可信證明轉化中繼器，並由可信證明轉化中繼器進一步將跨鏈請求傳輸至區塊鏈2。
進一步地，透過已配置的區塊鏈2的客戶端，可信證明轉化中繼器可以調取區塊鏈2針對上述跨鏈請求形成的回應資料，並將該回應資料返回至可信錨定器，而可信錨定器可以將該回應資料進一步返回至區塊鏈1，從而完成區塊鏈1與區塊鏈2之間的跨鏈互動。
除了回應資料之外，可信證明轉化中繼器還從區塊鏈2調取相應的鏈上證明，且可信證明轉化中繼器可以根據該鏈上證明對回應資料進行驗證，比如確定該回應資料存在於區塊鏈2的區塊鏈帳本中等，本說明書並不對此進行限制。同時，可信證明轉化中繼器配置有可信證明轉化技術，使得根據鏈上證明對回應資料實施驗證操作後，如果驗證結果為通過驗證，該可信證明轉化中繼器可以基於可信證明轉化技術產生中繼器證明，相當於將鏈上證明轉化為中繼器證明。然後，可信證明轉化中繼器將回應資料與中繼器證明返回至可信錨定器，並由可信錨定器進一步返回至區塊鏈1，其中，可信證明轉化中繼器可以預先發布信任根，而區塊鏈1可以預先獲取並部署該信任根，使得該區塊鏈1在獲得上述的回應資料和中繼器證明後，可以基於該信任根對回應資料和中繼器證明進行驗證，以確定可信證明轉化中繼器針對所提供的回應資料實施過驗證且驗證通過。
可見，透過採用上述的跨鏈互動系統，使得可信錨定器、可信證明轉化中繼器均只需要配置存在存取需求的區塊鏈的客戶端，而無需配置所有參與跨鏈互動的區塊鏈的客戶端，使得可信錨定器與可信證明轉化中繼器均十分輕量化。同時，透過在可信證明轉化中繼器上配置可信證明轉化技術，可以透過該中繼器實現對回應資料可靠性的單點證明，區別於相關技術中基於共識演算法的中繼鏈，由於對中繼器證明的轉化過程相比於共識過程更為高效、便捷，使得在確保回應資料可靠性的情況下，能夠提升跨鏈互動效率。並且，由於可信證明轉化中繼器得到的證明資訊僅為一份(即中繼器證明)，區別於相關技術中的中繼鏈內的眾多驗證者所提供的多份證明資訊(每一驗證者提供一份證明資訊)，能夠極大地簡化區塊鏈1對於證明資訊的驗證過程、有助於提升驗證效率。
基於上述結構的跨鏈互動系統，可以根據實際的流量、容量需求進行伸縮部署，具有極強的部署彈性。例如，圖2是一示例性實施例提供的一種跨鏈互動系統的結構示意圖。如圖2所示，跨鏈互動系統中可以部署多個可信證明轉化中繼器，比如可信證明轉化中繼器1至4等，一方面可以增加可信證明轉化中繼器的數量、以擴展可支持的區塊鏈數量，另一方面可以為各個可信證明轉化中繼器配置多種類型的可信證明轉化技術，比如TEE(Trusted Execution Environment，可信執行環節技術)技術、POA (Proof of Authority，權威證明共識)技術、MPC(Secure Multi-Party Computation，安全多方計算)技術、零知識證明(Zero—Knowledge Proof)技術等，本說明書並不對此進行限制。由於不同的可信證明轉化技術所實現的性能模型、安全邊界等均不同，因而可以滿足不同場景下的應用需求。
在一實施例中，可以在可信證明轉化中繼器1中配置TEE技術、在可信證明轉化中繼器2中配置POA技術、在可信證明轉化中繼器3中配置MPC技術、在可信證明轉化中繼器4中配置零知識證明技術，而區塊鏈2、區塊鏈4至6可以根據實際需求選用特定的可信證明轉化中繼器，以用於對自身提供的鏈上證明進行可信證明轉化。例如，區塊鏈2可以選用可信證明轉化中繼器1至3，則可信證明轉化中繼器1至3中需要分別配置區塊鏈2的客戶端；區塊鏈4可以選用可信證明轉化中繼器1，則可信證明轉化中繼器1中需要配置區塊鏈4的客戶端；區塊鏈5可以選用可信證明轉化中繼器2、4，則可信證明轉化中繼器2、4中需要配置區塊鏈5的客戶端；區塊鏈6可以選用可信證明轉化中繼器2、4，則可信證明轉化中繼器2、4中需要配置區塊鏈6的客戶端。
在一實施例中，區塊鏈2、區塊鏈4至6等可以對可信證明轉化中繼器1至4進行共用，即可信證明轉化中繼器1至4為公共類型，這樣可以減少跨鏈互動系統中相同的可信證明轉化中繼器(即配置有相同的可信證明轉化技術)的數量，有助於簡化系統複雜度。當然，本說明書並不限制在跨鏈互動系統中配置相同的可信證明轉化中繼器，比如當需要調用的區塊鏈數量較多時，由於同一個可信證明轉化中繼器的性能有限，可以配置多個相同的可信證明轉化中繼器，以實現性能需求的分流。再比如，可以基於資料隱私需求而配置相同的可信證明轉化中繼器；例如，圖3是一示例性實施例提供的另一種跨鏈互動系統的結構示意圖，假定可信證明轉化中繼器1為公共中繼器、配置有TEE技術，而區塊鏈2雖然希望採用TEE技術實現可信證明轉化，但是不希望自身提供的回應資料被記錄至可信證明轉化中繼器1中、避免發生外泄，那麼區塊鏈2可以配置專用的私有可信證明轉化中繼器，該私有可信證明轉化中繼器配置有TEE技術，且該私有可信證明轉化中繼器僅設有區塊鏈2的客戶端、其他區塊鏈無法(如沒有操作權限)在該私有可信證明轉化中繼器中設置自身的客戶端，使得僅區塊鏈2能夠使用該私有可信證明轉化中繼器。
在一實施例中，與中繼器相類似地，可信錨定器也可以具有公共類型和私有類型，以滿足不同的應用需求。比如圖3所示，區塊鏈3可以與公共可信錨定器相連，該公共可信錨定器中可以配置區塊鏈3的客戶端，使其能夠監控區塊鏈3上的跨鏈請求，並協助區塊鏈3獲得其他區塊鏈提供的回應資料，這與圖1所示的實施例相似，此處不再贅述。類似地，其他區塊鏈也可以與該公共可信錨定器相連，使得該公共可信錨定器可以配置這些區塊鏈的客戶端、協助這些區塊鏈完成跨鏈互動，此處不再贅述。再比如，區塊鏈1可以配置私有可信錨定器，該私有可信錨定器上配置有區塊鏈1的客戶端，且其他區塊鏈無法(如沒有操作權限)在該私有可信錨定器上配置自身的客戶端，使得該私有可信錨定器僅用於監控區塊鏈1上的跨鏈請求，並協助區塊鏈1完成跨鏈互動。
可見，基於如圖3所示的跨鏈互動系統，作為調用方的區塊鏈可以根據實際需求選用私有可信錨定器或公共可信錨定器、作為被調用方的區塊鏈可以根據實際需求選用私有可信證明轉化中繼器或公共可信證明轉化中繼器，從而滿足作為調用方或被調用方的區塊鏈的隱私需求。
需要指出的是：本說明書中的每一個可信證明轉化中繼器在邏輯上可以視為“一個設備”，使得每一個可信證明轉化中繼器在獲取被調用方的區塊鏈返回的跨鏈資料和鏈上證明後，可以基於對跨鏈資料和鏈上證明的驗證結果，將鏈上證明轉化為可信的中繼器證明，且該中繼器證明的數量僅為一份，區別於相關技術中的中繼鏈內的多個驗證者分別提供的多份證明。當然，每一個可信證明轉化中繼器實際上可以運行於單台電子設備上，比如包含一獨立主機的物理伺服器、PC、筆記型電腦、手機等；或者，每一個可信證明轉化中繼器可以運行於多台電子設備構成的設備集群上，比如主機集群承載的虛擬伺服器等；本說明書並不對此進行限制。
圖4是一示例性實施例提供的又一種跨鏈互動系統的結構示意圖。如圖4所示，當區塊鏈1選用私有可信錨定器時，該私有可信錨定器可以連接至公共類型的可信證明轉化中繼器1，而並不一定與如圖3所示的私有可信證明轉化中繼器相連。實際上，如果作為調用方的區塊鏈1存在隱私需求、作為被調用方的區塊鏈2不存在隱私需求，那麼區塊鏈1可以選用私有可信錨定器、區塊鏈2可以選用公共類型的可信證明轉化中繼器1，從而分別滿足各個區塊鏈的實際需求。
在如圖1至4所示的實施例中，跨鏈互動系統中的可信錨定器和可信證明轉化中繼器之間直接建立連接；而在其他實施例中，比如圖5是一示例性實施例提供的一種提供橋接功能的跨鏈互動系統的結構示意圖，可以透過設置橋接器，使得該橋接器分別連接至可信錨定器和可信證明轉化中繼器，實現可信錨定器與可信證明轉化中繼器之間的橋接功能。
例如，透過設置公共橋接器，以連接至公共可信證明轉化中繼器1至4等公共可信證明轉化中繼器。其中，公共橋接器可以連接至公共可信錨定器，比如該公共可信錨定器可以直接配置於該公共橋接器處，當然本說明書並不對此進行限制；或者，該公共橋接器可以連接至私有可信錨定器1或其他的私有可信錨定器。那麼，當區塊鏈A1連接至公共可信錨定器、區塊鏈B1至B4分別連接至各個公共可信證明轉化中繼器時，該區塊鏈A1可以針對區塊鏈B1至B4實現跨鏈互動；而當區塊鏈A2連接至私有可信錨定器1、區塊鏈B1至B4分別連接至各個公共可信證明轉化中繼器時，該區塊鏈A2可以針對區塊鏈B1至B4實現跨鏈互動。
再例如，透過設置私有橋接器，可以分別連接至私有可信錨定器2和私有可信證明轉化中繼器1至2，當區塊鏈A3連接至私有可信錨定器2、區塊鏈B5連接至私有可信證明轉化中繼器1至2時，該區塊鏈A3可以針對區塊鏈B5實現跨鏈互動。
當然，正如上文所述，公共橋接器、私有橋接器等橋接器並非必須，比如私有可信錨定器1可以直接連接至公共可信證明轉化中繼器4、私有可信錨定器2可以直接連接至私有可信證明轉化中繼器2，公共可信錨定器也可以直接連接至指定的公共或私有類型的可信證明轉化中繼器，從而實現相關區塊鏈的跨鏈互動。
雖然上述實施例中將橋接器劃分為公共橋接器、私有橋接器，但實際上也可以不予以區分，比如可以透過同一個橋接器分別連接至公共可信錨定器、私有可信錨定器、公共可信證明轉化中繼器、私有可信證明轉化中繼器，只要能夠實現相應的橋接功能即可。當然，對於存在較高的資料隱私需求的區塊鏈而言，可以選擇採用專門的橋接器，即相當於上述的私有橋接器。
綜上所述，本說明書透過提出一種新型的跨鏈互動系統，不需要中心化的中繼鏈，而是採用單機形式的可信證明轉化中繼器與區塊鏈連接，不僅相對更加輕量化，並且可以根據流量、容量需求而對採用的可信證明轉化中繼器進行靈活部署，還可以根據實際需求選擇配置特定的可信證明轉化技術、不限於採用諸如共識演算法等方式。同時，區塊鏈可以根據需求配置公共類型或私有類型的可信錨定器、可信證明轉化中繼器和橋接器，該公共類型的相關節點可以滿足諸如公有鏈下的快捷配置，而私有類型的相關節點可以避免隱私資料被其他區塊鏈獲得，能夠滿足部分區塊鏈的隱私需求，支持有存取權限的私有鏈或聯盟鏈的應用需求。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦芯片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
在一個典型的配置中，電腦包括一個或多個處理器(CPU)、輸入/輸出介面、網路介面和記憶體。
記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體(RAM)和/或非易失性記憶體等形式，如唯讀記憶體(ROM)或快閃記憶體(flash RAM)。記憶體是電腦可讀媒體的示例。
電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可擦除可編程唯讀記憶體(EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存器、磁盒式磁帶、磁碟儲存器、量子記憶體、基於石墨烯的儲存媒體或其他磁性儲存設備或任何其他非傳輸媒體，可用於儲存可以被計算設備存取的資訊。按照本文中的界定，電腦可讀媒體不包括暫態性電腦可讀媒體(transitory media)，如調變的資料信號和載波。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範疇內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在圖式中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多工處理和並行處理也是可以的或者可能是有利的。
在本說明書一個或多個實施例使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本說明書一個或多個實施例。在本說明書一個或多個實施例和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出專案的任何或所有可能組合。
應當理解，儘管在本說明書一個或多個實施例可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本說明書一個或多個實施例範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“回應於確定”。
以上所述僅為本說明書一個或多個實施例的較佳實施例而已，並不用來限制本說明書一個或多個實施例，凡在本說明書一個或多個實施例的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本說明書一個或多個實施例保護的範圍之內。The exemplary embodiments will be described in detail here, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with one or more embodiments of this specification. On the contrary, they are only examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the scope of the appended application.
It should be noted that in other embodiments, the steps of the corresponding method may not be executed in the order shown and described in this specification. In some other embodiments, the method includes more or fewer steps than described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. description.
Fig. 1 is a schematic diagram of a cross-chain interaction provided by an exemplary embodiment. Take the cross-chain interaction between Blockchain 1 and Blockchain 2 as shown in Figure 1 as an example. The Blockchain 1 and Blockchain 2 can achieve cross-chain interaction through a cross-chain interaction system. The system may include: a trusted anchor and a trusted certification conversion repeater; a client of blockchain 1 can be configured in the trusted anchor to establish a connection between the trusted anchor and blockchain 1. , And the trusted certification conversion repeater can be configured with the blockchain 2 client, so that the trusted certification conversion repeater can establish a connection with the blockchain 2.
In one embodiment, the clients respectively configured on the trusted anchor and the trusted certification conversion repeater may be SPV (Simplified Payment Verification) clients, so that the trusted anchor and the trusted Prove that the configuration of the conversion repeater is lightweight. Of course, by configuring other types of clients, related cross-chain interaction functions can also be realized, and this manual does not limit this.
In an embodiment, when the blockchain 1 needs to retrieve cross-chain data from the blockchain 2, a cross-chain request can be created on the blockchain 1, and the request object of the cross-chain request is the blockchain 2. Through the configured client of blockchain 1, the trusted anchor can monitor the cross-chain request created on blockchain 1, and based on the request object indicated by the cross-chain request is blockchain 2 and block There is a connection relationship between chain 2 and the trusted certification conversion repeater, and the cross-chain request is transmitted to the trusted certification conversion repeater, and the trusted certification conversion repeater further transmits the cross-chain request to the blockchain 2 .
Further, through the configured client of the blockchain 2, the trusted certification conversion repeater can retrieve the response data formed by the blockchain 2 for the above cross-chain request, and return the response data to the trusted anchor The trusted anchor can further return the response data to Blockchain 1, thereby completing the cross-chain interaction between Blockchain 1 and Blockchain 2.
In addition to the response data, the trusted certification conversion repeater also retrieves the corresponding on-chain certification from Blockchain 2, and the trusted certification conversion repeater can verify the response data based on the on-chain certification, such as determining the The response data exists in the blockchain ledger of blockchain 2, and this manual does not restrict it. At the same time, the trusted certification conversion repeater is equipped with trusted certification conversion technology, so that after the verification operation is performed on the response data based on the on-chain certification, if the verification result is passed, the trusted certification conversion repeater can be based on the trusted certification The conversion technology produces a repeater certificate, which is equivalent to converting the on-chain certificate into a repeater certificate. Then, the trusted certification conversion repeater returns the response data and the repeater certification to the trusted anchor, and the trusted anchor further returns to the blockchain 1, where the trusted certification conversion repeater can Publish the root of trust in advance, and blockchain 1 can obtain and deploy the root of trust in advance, so that the blockchain 1 can respond to the response data and the repeater based on the root of trust after obtaining the above-mentioned response data and repeater certification The certificate is verified to ensure that the trusted certificate conversion repeater has verified and passed the verification of the response data provided.
It can be seen that through the use of the above-mentioned cross-chain interaction system, both the trusted anchor and the trusted certification conversion repeater only need to configure the client of the blockchain that has access requirements, instead of configuring all participating cross-chain interactions. The client of the blockchain makes the trusted anchor and the trusted certification conversion repeater very lightweight. At the same time, by configuring the trusted certification conversion technology on the trusted certification conversion repeater, a single-point proof of the reliability of the response data can be realized through the repeater, which is different from the relay chain based on the consensus algorithm in related technologies. Since the conversion process of the repeater proof is more efficient and convenient than the consensus process, the efficiency of cross-chain interaction can be improved while ensuring the reliability of the response data. Moreover, since the trusted certification conversion relayer obtains only one piece of certification information (ie, the relay certification), it is different from the multiple pieces of certification information provided by many verifiers in the relay chain in the related technology (each The verifier provides a piece of proof information), which can greatly simplify the verification process of the blockchain 1 for proof information and help improve the efficiency of verification.
The cross-chain interaction system based on the above structure can be deployed in scale according to actual traffic and capacity requirements, and has extremely strong deployment flexibility. For example, FIG. 2 is a schematic structural diagram of a cross-chain interaction system provided by an exemplary embodiment. As shown in Figure 2, multiple trusted certification conversion repeaters can be deployed in the cross-chain interactive system, such as trusted certification conversion repeaters 1 to 4, etc. On the one hand, the number of trusted certification conversion repeaters can be increased, In order to expand the number of blockchains that can be supported, on the other hand, various types of trusted certification conversion technologies can be configured for each trusted certification conversion repeater, such as TEE (Trusted Execution Environment, trusted execution technology) technology, POA ( Proof of Authority (Proof of Authority) technology, MPC (Secure Multi-Party Computation) technology, Zero-Knowledge Proof technology, etc. This manual does not limit this. Since the performance models and security boundaries implemented by different trusted certification conversion technologies are different, they can meet application requirements in different scenarios.
In one embodiment, TEE technology can be configured in trusted certification conversion repeater 1, POA technology can be configured in trusted certification conversion repeater 2, MPC technology can be configured in trusted certification conversion repeater 3, The trusted certification conversion repeater 4 is equipped with zero-knowledge certification technology, and the blockchain 2 and blockchains 4 to 6 can select specific trusted certification conversion repeaters according to actual needs to be used for the chain provided by themselves. The above certification is transformed into credible certification. For example, blockchain 2 can use trusted certification conversion repeaters 1 to 3, and trusted certification conversion repeaters 1 to 3 need to configure the clients of blockchain 2 respectively; blockchain 4 can select trusted Proof conversion repeater 1, then trusted certificate conversion repeater 1 needs to configure the client of blockchain 4; block chain 5 can choose trusted certificate conversion repeaters 2, 4, then trusted certificate conversion is in progress The client of the blockchain 5 needs to be configured in the relays 2 and 4; the trusted certification conversion relays 2 and 4 can be selected for the blockchain 6, and the trusted certification conversion relays 2 and 4 need to be configured with the blockchain 6 clients.
In one embodiment, blockchain 2, blockchains 4 to 6, etc. can share trusted certification conversion repeaters 1 to 4, which means that the trusted certification conversion repeaters 1 to 4 are of public type. Reducing the number of identical trusted certification conversion repeaters (that is, equipped with the same trusted certification conversion technology) in the cross-chain interactive system helps simplify the system complexity. Of course, this manual does not limit the configuration of the same trusted certification conversion repeater in the cross-chain interactive system. For example, when there are a large number of blockchains that need to be called, the performance of the same trusted certification conversion repeater is limited. , You can configure multiple identical trusted certification conversion repeaters to achieve the shunt of performance requirements. For another example, the same trusted certification conversion repeater can be configured based on data privacy requirements; for example, FIG. 3 is a schematic structural diagram of another cross-chain interactive system provided by an exemplary embodiment, assuming a trusted certification conversion repeater 1 is a public repeater equipped with TEE technology, and although the blockchain 2 hopes to use TEE technology to achieve credible certification conversion, it does not want the response data provided by itself to be recorded in the credible certification conversion repeater 1. In the event of leakage, the blockchain 2 can be equipped with a dedicated private trusted certification conversion repeater, which is equipped with TEE technology, and the private trusted certification conversion repeater only has a zone The client of Blockchain 2 and other blockchains cannot (such as no operation authority) set their own client in the private trusted certificate conversion repeater, so that only Blockchain 2 can use the private trusted certificate in conversion. Repeater.
In an embodiment, similar to the repeater, the trusted anchor may also have a public type and a private type to meet different application requirements. For example, as shown in Figure 3, the blockchain 3 can be connected to a public trusted anchor, and the client of the blockchain 3 can be configured in the public trusted anchor to enable it to monitor the cross-chain on the blockchain 3. Request and assist the blockchain 3 to obtain response data provided by other blockchains. This is similar to the embodiment shown in FIG. 1 and will not be repeated here. Similarly, other blockchains can also be connected to the public trusted anchor, so that the public trusted anchor can configure the clients of these blockchains and assist these blockchains in completing cross-chain interactions. Repeat it again. For another example, blockchain 1 can be configured with a private trusted anchor, and the client of blockchain 1 is configured on the private trusted anchor, and other blockchains cannot (if there is no operation permission) in the private trusted anchor. The trust anchor is configured with its own client, so that the private trusted anchor is only used to monitor cross-chain requests on blockchain 1, and assist blockchain 1 in completing cross-chain interaction.
It can be seen that based on the cross-chain interaction system shown in Figure 3, the blockchain as the caller can choose a private trusted anchor or a public trusted anchor according to actual needs, and the blockchain as the callee can be based on The actual requirement is to select a private trusted certification conversion repeater or a public trusted certification conversion repeater to meet the privacy requirements of the blockchain as the caller or callee.
It should be pointed out that each trusted certification conversion repeater in this manual can be regarded as "a device" logically, so that each trusted certification conversion repeater obtains the information returned by the callee’s blockchain. After the cross-chain data and the on-chain proof, the on-chain proof can be converted into a trusted relay certificate based on the verification result of the cross-chain data and the on-chain proof, and the number of the relay certificate is only one. It is different from the multiple certificates provided by multiple verifiers in the relay chain in the related technology. Of course, every trusted certification conversion repeater can actually run on a single electronic device, such as a physical server, PC, notebook computer, mobile phone, etc. containing an independent host; or, every trusted certification conversion The relay can run on a device cluster composed of multiple electronic devices, such as a virtual server carried by a host cluster; this specification does not limit this.
Fig. 4 is a schematic structural diagram of yet another cross-chain interaction system provided by an exemplary embodiment. As shown in Figure 4, when the blockchain 1 uses a private trusted anchor, the private trusted anchor can be connected to a public type of trusted certification conversion repeater 1, which is not necessarily the same as that shown in Figure 3. The private trusted certification conversion relay shown is connected. In fact, if blockchain 1 as the caller has privacy requirements, and blockchain 2 as the callee does not have privacy requirements, then blockchain 1 can use private trusted anchors, and blockchain 2 can choose The public type of credible proof transforms the repeater 1 to meet the actual needs of each blockchain.
In the embodiments shown in Figures 1 to 4, the trusted anchor in the cross-chain interactive system and the trusted certification conversion repeater are directly connected; while in other embodiments, such as Figure 5 An exemplary embodiment provides a schematic structural diagram of a cross-chain interaction system that provides a bridging function. A bridge can be set up so that the bridge is connected to a trusted anchor and a trusted certification conversion repeater to realize a trusted anchor The bridge function between the setter and the trusted certification conversion repeater.
For example, by setting up a public bridge to connect to public trusted certification conversion repeaters 1 to 4, etc. Wherein, the public bridge can be connected to the public trusted anchor, for example, the public trusted anchor can be directly configured at the public bridge, of course, this specification does not limit this; or, the public bridge can be connected To private trusted anchor 1 or other private trusted anchors. Then, when the blockchain A1 is connected to the public trusted anchor, and the blockchains B1 to B4 are respectively connected to each public trusted certification conversion repeater, the blockchain A1 can be implemented for the blockchains B1 to B4 Cross-chain interaction; when the blockchain A2 is connected to the private trusted anchor 1, and the blockchains B1 to B4 are respectively connected to various public trusted certification conversion repeaters, the blockchain A2 can target the blockchain B1 to B4 realize cross-chain interaction.
For another example, by setting up a private bridge, you can connect to the private trusted anchor 2 and the private trusted certification conversion repeater 1 to 2 respectively. When the blockchain A3 is connected to the private trusted anchor 2, block When the chain B5 is connected to the private trusted certification conversion repeater 1 to 2, the block chain A3 can realize cross-chain interaction for the block chain B5.
Of course, as mentioned above, public bridges, private bridges, and other bridges are not necessary. For example, private trusted anchor 1 can be directly connected to public trusted certification conversion repeater 4 and private trusted anchor 2 It can be directly connected to the private trusted certification conversion repeater 2, and the public trusted anchor can also be directly connected to the designated public or private type trusted certification conversion repeater, thereby achieving cross-chain interaction of related blockchains .
Although the bridges are divided into public bridges and private bridges in the above-mentioned embodiments, they may not be distinguished in practice. For example, they can be connected to public trusted anchors and private trusted anchors through the same bridge. , Public trusted certification conversion repeater, private trusted certification conversion repeater, as long as the corresponding bridging function can be realized. Of course, for blockchains with high data privacy requirements, you can choose to use a dedicated bridge, which is equivalent to the above-mentioned private bridge.
In summary, this manual proposes a new type of cross-chain interaction system that does not require a centralized relay chain, but uses a single-machine form of trusted certification to transform the relay and the blockchain connection, which is not only relatively lighter , And can flexibly deploy trusted certification conversion repeaters according to traffic and capacity requirements, and can also choose to configure specific trusted certification conversion technologies according to actual needs, not limited to methods such as consensus algorithms. At the same time, the blockchain can be configured with public or private trusted anchors, trusted certification conversion repeaters, and bridges according to requirements. The public related nodes can meet the quick configuration under public chains, while private Types of related nodes can prevent private data from being obtained by other blockchains, meet the privacy requirements of some blockchains, and support the application requirements of private chains or consortium chains with access rights.
The systems, devices, modules, or units explained in the above embodiments can be implemented by computer chips or entities, or implemented by products with certain functions. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game. Console, tablet, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
Memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory ( flash RAM). Memory is an example of computer-readable media.
Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM) , Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital multi-function disc (DVD) or other optical storage, magnetic cassette, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media, which can be used for storage and can be accessed by computing devices Information. According to the definition in this article, computer-readable media does not include transient computer-readable media (transitory media), such as modulated data signals and carrier waves.
It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, product or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or include elements inherent to this process, method, commodity, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.
The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the attached patent application. In some cases, the actions or steps described in the scope of the patent application may be performed in a different order from the embodiment and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired result. In some embodiments, multiplexing and parallel processing are also possible or may be advantageous.
The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms "a", "the" and "the" used in one or more embodiments of this specification and the scope of the appended patent application are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.
It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information can also be referred to as second information, and similarly, the second information can also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to certainty".
The above descriptions are only the preferred embodiments of one or more embodiments of this specification, and are not used to limit one or more embodiments of this specification. All within the spirit and principle of one or more embodiments of this specification, Any modification, equivalent replacement, improvement, etc. made should be included in the protection scope of one or more embodiments of this specification.
