实名合约代码路径如下：core/contractsdk/cpp/reserved/identity.cc [https://github.com/xuperchain/xuperchain/blob/master/core/contractsdk/cpp/reserved/identity.cc] 实名合约实名的对象是一个具体的ak。 1 2 3 cd ./contractsdk/cpp cp reserved/identity com/xuperchain/xuperchain/blob/master/core/kv/mstorage/test/test_write.go] 读取测试可参考代码 kv/mstorage/test/test_read.go [https://github.com/xuperchain/xuperchain/blob/master/core/kv/mstorage/test/test_read 为了实现跨链请求，仅有上面的链名跨链寻址协议是不够的，在跨链发起的原 链上还需要部署一个链名解析合约，该合约目前也已开源 链名解析合约 [https://github.com/xuperchain/xuperchain/blob/master/core/contractsdk/cpp/example/naming/src/naming.cc]。 1 2 3 4 5 6 7 8 9 10 11 12 // 注册一个网络，同时包含网络初始meta信息

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 40.4. Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . single broker fails, the ring fails. 33.1.4. Fan out Figure 5. Address Federation - Fan Out One master address (it would required no configuration) is linked to by a tree of downstream federated addresses extended to without needing to re-configure existing brokers. In this case messages published to the master address can be received by any consumer connected to any broker in the tree. 33.1.5. Divert Binding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 40.4. Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . single broker fails, the ring fails. 33.1.4. Fan out Figure 5. Address Federation - Fan Out One master address (it would required no configuration) is linked to by a tree of downstream federated addresses extended to without needing to re-configure existing brokers. In this case messages published to the master address can be received by any consumer connected to any broker in the tree. 33.1.5. Divert Binding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 40.4. Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . single broker fails, the ring fails. 33.1.4. Fan out Figure 5. Address Federation - Fan Out One master address (it would required no configuration) is linked to by a tree of downstream federated addresses extended to without needing to re-configure existing brokers. In this case messages published to the master address can be received by any consumer connected to any broker in the tree. 33.1.5. Divert Binding

ret ... Broker Connections 69 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to the target broker. Message Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies

Broker Connections 82 Mirroring Mirroring will reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies inclusion and/or exclusion filter entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to

name="Se ... Broker Connections 79 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to the target broker. Message Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies

Broker Connections 81 Mirroring Mirroring will reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies inclusion and/or exclusion filter entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to

Broker Connections 82 Mirroring Mirroring will reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies inclusion and/or exclusion filter entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to

name="Se ... Broker Connections 76 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to the target broker. Message Mirror configuration Add a element within the element to configure mirroring to the target broker. The following optional arguments can be utilized: queue-removal : Specifies