内容简介：读书笔记基于cosmos最新的ibc开发分支:本文参与登链社区写作激励计划 ，好文好收益，欢迎正在阅读的你也加入。
读书笔记基于cosmos最新的ibc开发分支: cwgoes/ibc-demo-fixes , 主要是针对ibc相关的代码解读和ibc的实现机制.
该repository作为本人读书笔记, 记录知识的获取, 以blog的形式记录下来. 该文库我会不断更新, 如果喜欢的话麻烦点一下 star
.
ps. 测试环境:
Linux Yieazy 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu18.04 go version: 1.13.5 cpu: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz memory: 16GB
读书笔记基于cosmos最新的ibc开发分支: cwgoes/ibc-demo-fixes , 主要是针对ibc相关的代码解读和ibc的实现机制. ibc-demo中给出了ibc环境的完整部署与ibc交易的调试步骤以及所有的源代码, 但是却为给出证明ibc的有效性以及相关的数学证明, 因此本文将分析ibc的实现机制以及cosmos声称ibc具备跨链操作的原子特性进行分析. 完整的ibc-demo环境, 链接在这里 抛开gaia的初始环境, 直接到文档的IBC Command Sequence, 我们看到:
操作一: Client Creation
client creation中不仅传入chain id还传入一个非常重要的共识状态文档(consensus_state.json), 根据官方给出的命令:
gaiacli --home ibc1/n0/gaiacli q ibc client node-state
我们可以同样生成一个, 结果:
{
"type": "ibc/client/tendermint/ConsensusState",
"value": {
"chain_id": "ibc0",
"height": "71497",
"root": {
"type": "ibc/commitment/merkle/Root",
"value": {
"hash": "2gi0YPMec1GHn4WNR0urWPpf2kABOTKBT5OaFfATtFQ="
}
},
"next_validator_set": {
"validators": [
{
"address": "F6009D93FEC4CACDD273225E78DDAF07B582FC35",
"pub_key": {
"type": "tendermint/PubKeyEd25519",
"value": "6yUYsrbCi1CY7NBSy8Zxx2CKA+Tc1YsUX+w57OFGM58="
},
"voting_power": "100",
"proposer_priority": "0"
}
],
"proposer": {
"address": "F6009D93FEC4CACDD273225E78DDAF07B582FC35",
"pub_key": {
"type": "tendermint/PubKeyEd25519",
"value": "6yUYsrbCi1CY7NBSy8Zxx2CKA+Tc1YsUX+w57OFGM58="
},
"voting_power": "100",
"proposer_priority": "0"
}
}
}
}
源码中的结构定义:
// ConsensusState defines a Tendermint consensus state
type ConsensusState struct {
ChainID string `json:"chain_id" yaml:"chain_id"`
Height uint64 `json:"height" yaml:"height"` // NOTE: defined as 'sequence' in the spec
Root commitment.RootI `json:"root" yaml:"root"`
NextValidatorSet *tmtypes.ValidatorSet `json:"next_validator_set" yaml:"next_validator_set"` // contains the PublicKey
}
这个json是其中一条链的共识信息, 其中包含了块高信息, 接下来的验证人集信息以及一个root信息, 从root的type可以看出, root中的hash与当前块高merkle树相关( 为当前块的AppHash ). client创建的命令:
# client for chain ibc1 on chain ibc0 echo -e "12345678\n" | gaiacli --home ibc0/n0/gaiacli \ tx ibc client create ibconeclient \ $(gaiacli --home ibc1/n0/gaiacli q ibc client node-state) \ --from n0 -y -o text # client for chain ibc0 on chain ibc1 echo -e "12345678\n" | gaiacli --home ibc1/n0/gaiacli \ tx ibc client create ibczeroclient \ $(gaiacli --home ibc0/n0/gaiacli q ibc client node-state) \ --from n1 -y -o text
该命令的执行结果, 会将consensus state保存的信息将以key为clients/{chain-id}/consensusState的存入数据库中, 其中的root信息又会再次以key为clients/{chain-id}/roots/{height}存入数据库中. 创建的client的结构:
// State is a type that represents the state of a client.
// Any actor holding the Stage can access on and modify that client information.
type State struct {
// Client ID
id string `json:"id" yaml:"id"`
// Boolean that states if the client is frozen when a misbehaviour proof is
// submitted in the event of an equivocation.
Frozen bool `json:"frozen" yaml:"frozen"`
}
ps. 该结构与具体节点和地址无关, 显然client的创建是以链本身为单位, 而链的识别仅仅以chain-id, 对client的操作仅有冻结选项. 完成了几项数据库的写入之后, key为clients/{chain-id}/consensusState和key为clients/{chain-id}/roots/{height}是写入操作中最重要的两项, 其他具体写入项请参看HandleMsgCreateClient函数, 在此不赘述. 之后会发出client创建成功的events:
ctx.EventManager().EmitEvents(sdk.Events{
sdk.NewEvent(
EventTypeCreateClient,
sdk.NewAttribute(AttributeKeyClientID, msg.ClientID),
),
sdk.NewEvent(
sdk.EventTypeMessage,
sdk.NewAttribute(sdk.AttributeKeyModule, AttributeValueCategory),
sdk.NewAttribute(sdk.AttributeKeySender, msg.Signer.String()),
),
})
操作二: Connection Creation
In order to send transactions using IBC there are two different handshakes that must be performed. First there is a connection created between the two chains. Once the connection is created, an application specific channel handshake is performed which allows the transfer of application specific data. Examples of applications are token transfer, cross-chain validation, cross-chain accounts, and in this tutorial ibc-mock.
为了使用IBC发送交易那么必须执行两种不同握手. 首先, 两个链之间建立了连接, 将执行特定于应用程序的通道握手, 从而可以传输特定于应用程序的数据. 应用程序示例包括令牌转移, 跨链验证, 跨链帐户以及本教程中的ibc-mock.
connection在源码中以 ConnectionEnd
结构体表示, 其在源码中的定义:
// ConnectionEnd defines a stateful object on a chain connected to another separate
// one.
// NOTE: there must only be 2 defined ConnectionEnds to stablish a connection
// between two chains.
type ConnectionEnd struct {
State State `json:"state" yaml:"state"`
ClientID string `json:"client_id" yaml:"client_id"`
// Counterparty chain associated with this connection.
Counterparty Counterparty `json:"counterparty" yaml:"counterparty"`
// Version is utilised to determine encodings or protocols for channels or
// packets utilising this connection.
Versions []string `json:"versions" yaml:"versions"`
}
创建connection的命令:
gaiacli \ --home ibc0/n0/gaiacli \ tx ibc connection handshake \ connectionzero ibconeclient $(gaiacli --home ibc1/n0/gaiacli q ibc client path) \ connectionone ibczeroclient $(gaiacli --home ibc0/n0/gaiacli q ibc client path) \ --chain-id2 ibc1 \ --from1 n0 --from2 n1 \ --node1 tcp://localhost:26657 \ --node2 tcp://localhost:26557
其中产生path chain的命令:
gaiacli --home ibc1/n0/gaiacli q ibc client path
得到的结果:
{
"type": "ibc/commitment/merkle/Prefix",
"value": {
"key_prefix": "aWJj"
}
}
connection create的流程:
- connection_open_init操作: 1. 在ibc0链上记录ConnectionEnd状态为init, 并且以connections/connectionzero和clients/ibconeclient/connections为key存储该ConnectionEnd.
- update_client操作: 1. 会做对client是否frozen的检查, 以及块高检查, client是否tendermint client检查(是否为同构链), 以及检查ibc0最新consensus state, 2. 最后更新ibc1上的client: ibczeroclient的consensus state中的root, height以及nextvalidatorset字段(除了chain-id, 都更新到最新状态), 其状态为ibc0的最新consensus state状态, 奇怪的是打印却是ibconeclient更新 . 3. 数据库更新client state和root状态.
- connection_open_try: 1. 会做版本检查 2. 验证conection state 3. 验证consensus state(被注释) 4. 创建一个状态为tryopen的连接 5. 连接的connectionEnd写数据库
步骤2的验证过程, 会将ibc0链上的proof传送过ibc1链, 包含两条proof信息其中一条为ibc0链的connectionzero的 ConnectionEnd 状态信息, 另一条为ibc0当前块高-1的AppHash的multistore信息, 完整 信息示例如下
{
"proof":{
"StoreInfos":[
{
"Name":"staking",
"Core":{
"CommitID":{
"Version":38,
"Hash":"OyAHcb9W4SvGpTv/fX6VEqWicaOM+9qTXwquGsiwT2o="
}
}
},
{
"Name":"acc",
"Core":{
"CommitID":{
"Version":38,
"Hash":"xHw/kuGR12u6nN+27zsiZ2T6DJ+lZDdPoBj8ZiM1QvU="
}
}
},
{
"Name":"ibc",
"Core":{
"CommitID":{
"Version":38,
"Hash":"wFqTYG72fimvvKU/t7/EF6JSfelTJxslDEbw8vZdHtU="
}
}
},
{
"Name":"params",
"Core":{
"CommitID":{
"Version":38,
"Hash":"3PrT6GfafJIT6djcrepbPNe1pxBCwErffxJdEuW3gBU="
}
}
},
{
"Name":"slashing",
"Core":{
"CommitID":{
"Version":38,
"Hash":"h7c4wbsuEsYYgjhJhCztAGBPREKDWc2M88JZaXOnQao="
}
}
},
{
"Name":"main",
"Core":{
"CommitID":{
"Version":38,
"Hash":"Llfvk2BxBfQuVDx2CcfTIaMDoD6Y6I0m+E3VKdOR0WA="
}
}
},
{
"Name":"supply",
"Core":{
"CommitID":{
"Version":38,
"Hash":"DyyskpRi7Miac9UxgSDUlFwjlmKYawF/myIKoLZK60A="
}
}
},
{
"Name":"distribution",
"Core":{
"CommitID":{
"Version":38,
"Hash":"/awR8FmcgY8vcy4MKPmZ9o95rNBBtFEx95KOH2yvtsw="
}
}
},
{
"Name":"mint",
"Core":{
"CommitID":{
"Version":38,
"Hash":"5zTw4N/uFMgbxIZB7wRoAZ78zbMrwQNaE62Mv+0uPmg="
}
}
},
{
"Name":"gov",
"Core":{
"CommitID":{
"Version":38,
"Hash":"YM0TfBli7KxhY4nWgDSDPykhUJwtKFql9RU5l86WinQ="
}
}
}
]
}
}
该信息会与另一条链的connection state状态一起放入 VerifyMembership
作校验, 该校验函数会放在ics003的读书笔记中讲解.
还有一条与共识相关的ConsensusState Proof信息, 其中也包含两条proof信息, 第一条正是ibc1链在ibc0链上的子状态信息, 信息结构为 ConsensusState 上文提供了源码的定义, 另一条与前一个proof一样是AppHash的multistore信息.
- ibc0链上client updateclient
- connection_open_ack: 1. 会做版本检查 2. 验证链上已有的连接状态是否为init 3. 验证conection state 4. 验证consensus state(被注释) 5. 创建一个状态为open的连接 6. 连接的connectionEnd写数据库
- ibc1链上client updateclient
- connection_open_confirm: 1. 会做版本检查 2. 验证链上已有的连接状态是否为tryopen 3. 验证conection state 4. 创建一个状态为open的连接 5. 连接的connectionEnd写数据库
Connection建立后, ibc0链与ibc1链上均具备状态为open的connection, 可通过该命令查看通道状态:
gaiacli --home ibc0/n0/gaiacli q ibc connection end connectionzero --indent --trust-node
得到结果:
{
"type": "ibc/connection/ConnectionEnd",
"value": {
"state": "OPEN",
"client_id": "ibconeclient",
"counterparty": {
"client_id": "ibczeroclient",
"connection_id": "connectionone",
"prefix": {
"type": "ibc/commitment/merkle/Prefix",
"value": {
"key_prefix": "aWJj"
}
}
},
"versions": [
"1.0.0"
]
}
}
操作三: Create Channel
A channel serves as a conduit for packets passing between a module on one chain and a module on another, ensuring that packets are executed only once, delivered in the order in which they were sent (if necessary), and delivered only to the corresponding module owning the other end of the channel on the destination chain.
通道服务可以当做一个渠道使得消息可以从一条链上的模块传递给另一条链的模块, 确保这个包有且仅穿第一次, 并且准确按照发送的顺序进行传递(如有必要), 并且传递仅发生在分别拥有同一通道对应两端的链间对应模块之间.
创建通道时需要指定通道是否为有序通道以及端口ID, 通道的源码结构:
type Channel struct {
State State `json:"state" yaml:"state"`
Ordering Order `json:"ordering" yaml:"ordering"`
Counterparty Counterparty `json:"counterparty" yaml:"counterparty"`
ConnectionHops []string `json:"connection_hops" yaml:"connection_hops"`
Version string `json:"version" yaml:"version "`
}
// Counterparty defines the counterparty chain's channel and port identifiers
type Counterparty struct {
PortID string `json:"port_id" yaml:"port_id"`
ChannelID string `json:"channel_id" yaml:"channel_id"`
}
创建channel的命令:
gaiacli tx ibc channel handshake [client-id] [port-id] [chan-id] [conn-id] [cp-client-id] [cp-port-id] [cp-chain-id] [cp-conn-id] gaiacli \ --home ibc0/n0/gaiacli \ tx ibc channel handshake \ ibconeclient bank chanshixianzhongnelzero connectionzero \ ibczeroclient bank channelone connectionone \ --node1 tcp://localhost:26657 \ --node2 tcp://localhost:26557 \ --chain-id2 ibc1 \ --from1 n0 --from2 n1
bank: 即为portID.
[cp-*]: counterparty, 指代参与跨链的另一条链.
Create Channel的流程, 与create connection类似, 有4种操作 channel_open_init
, channel_open_try
, channel_open_ack
, channel_open_confirm
:
-
channel_open_init操作(ibc0):
- 检查链上connection状态不为none
- 构建一个状态为init的channel
- 设置该ibc0上channel的发送与接收的sequence为1, 通过写数据库的形式
-
channel_open_try操作(ibc1):
- 检查链上connection状态是否为open
- 构建一个状态为opentry的channel
- 根据MsgChannelOpenTry.ProofInit验证channel信息与apphash是否正确
- 设置该ibc1上channel的发送与接收的sequence为1, 通过写数据库的形式
-
channel_open_ack操作(ibc0):
- 检查链上channel状态是否为init
- 检查链上connection状态是否为open
- 根据MsgChannelOpenAck.ProofTry验证channel信息与apphash是否正确
- 修改channel状态为open
-
channel_open_confirm操作(ibc1)
- 检查链上channel状态是否为opentry
- 检查链上connection状态是否为open
- 根据MsgChannelOpenConfirm.ProofAck验证channel信息与apphash是否正确
- 修改channel状态为open
4种操作之间必然也存在这update_client操作, 该操作与创建connection过程中update_client操作完全一样.
操作四: Packet
包的结构:
// Packet defines a type that carries data across different chains through IBC
type Packet struct {
Sequence uint64 `json:"sequence"` // number corresponds to the order of sends and receives, where a Packet with an earlier sequence number must be sent and received before a Packet with a later sequence number.
Timeout uint64 `json:"timeout"` // indicates a consensus height on the destination chain after which the Packet will no longer be processed, and will instead count as having timed-out.
SourcePort string `json:"source_port"` // identifies the port on the sending chain.
SourceChannel string `json:"source_channel"` // identifies the channel end on the sending chain.
DestinationPort string `json:"destination_port"` // identifies the port on the receiving chain.
DestinationChannel string `json:"destination_channel"` // identifies the channel end on the receiving chain.
Data []byte `json:"data"` // opaque value which can be defined by the application logic of the associated modules.
}
-
Sequence: 序号, 与包在通道上的发送, 接收序列有关, 通道中的包依据序号大小, 有序发送与接收 -
Timeout: 超时, 表示目标链上的区块高度, 当超过该高度以后该包将不会被处理, 并会将其视为已超时 -
SourcePort: 源端口, 发送链上的端口 -
SourceChannel: 源通道, 发送链上的通道 -
DestinationPort: 目标端口, 目标链链上的端口 -
DestinationChannel: 目标通道, 目标链上的通道 -
Data: 数据, 数据与应用逻辑关联的模块相关
包发送
To send a packet using the bank
application protocol, you need to know the channel
you plan to send on, as well as the port
on the channel. You also need to provide an address
and amount
. Use the following command to send the packet:
包发送用到了 bank
应用协议, 你需要知道你计划使用哪个通道来发送包, 以及该通道上端口. 你需要提供地址与金额.
gaiacli \ --home ibc0/n0/gaiacli \ tx ibc transfer transfer \ bank channelzero \ $(gaiacli --home ibc0/n0/gaiacli keys show n1 -a) 1stake \ --from n0 \ --source
该命令即会组装一个上文的 Packet
结构, 该结构中的 Data
字段:
{
"amount":[
{
"denom":"bank/channelone/stake",
"amount":"1"
}
],
"sender":"cosmos15dzt38uzufx0fhga3f373yveccla8he8mh6gmt",
"receiver":"cosmos1xax60gm9pfq3d5fcasymw0lx7cu3l3ee8q3esy",
"source":true
}
denom
说明了交易的token是跨链token. 值得一提的是, 源码实现中在发送端如果跨链token的发送链为原始链, token在发生跨链时会将token发送到escrowAddress 第三方保管地址, 如果跨链token的发送链不是原始链, 那么token在发生跨链时token将会被销毁.
包接收
包发送后需要对目标链提交一笔含在发送链上发送包的接收交易, 才能完成接收链跨链token的接收.
gaiacli \ tx ibc transfer recv-packet \ bank channelzero ibczeroclient \ --home ibc1/n0/gaiacli \ --packet-sequence 1 \ --timeout $TIMEOUT \ --from n1 \ --node2 tcp://localhost:26657 \ --chain-id2 ibc0 \ --source
值得一说的是, 源码实现中会需要一个账户, 并且该账户需要具备铸币与销币的权限, 也就是说目标链接收token过程, 实际上是接收包的交易校验通过以后, 由该特殊账户铸币产生相应的跨链币后转账到对应账户中, 之后需要发送出去的时候, 作销币操作.
before ibc
查询账户余额:
{
"type":"cosmos-sdk/Account",
"value":{
"address":"cosmos1vgu8e3vchsnztlepzutpxwsf8p7c27awdx9xmj",
"coins":[
{
"denom":"n0token",
"amount":"1000000000"
},
{
"denom":"stake",
"amount":"400000000"
}
],
"public_key":{
"type":"tendermint/PubKeySecp256k1",
"value":"Ah9M7XPQIrjniXpghE3+bWeLG/0Phck58aqS/gQQjmxY"
},
"account_number":"3",
"sequence":"10"
}
}
after ibc
再次查询账户查询余额:
{
"type":"cosmos-sdk/Account",
"value":{
"address":"cosmos1vgu8e3vchsnztlepzutpxwsf8p7c27awdx9xmj",
"coins":[
{
"denom":"bank/channelone/stake",
"amount":"1"
},
{
"denom":"n0token",
"amount":"1000000000"
},
{
"denom":"stake",
"amount":"400000000"
}
],
"public_key":{
"type":"tendermint/PubKeySecp256k1",
"value":"Ah9M7XPQIrjniXpghE3+bWeLG/0Phck58aqS/gQQjmxY"
},
"account_number":"3",
"sequence":"12"
}
}
增加了该项**"denom":"bank/channelone/stake"**, 并且数量为1, 与实际发送一致, 说明至此跨链操作完成.
该repository作为本人读书笔记, 记录知识的获取, 以blog的形式记录下来. 该文库我会不断更新, 如果喜欢的话麻烦点一下 star
.
ps. 测试环境:
Linux Yieazy 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu18.04 go version: 1.13.5 cpu: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz memory: 16GB
读书笔记基于cosmos最新的ibc开发分支: cwgoes/ibc-demo-fixes , 主要是针对ibc相关的代码解读和ibc的实现机制. ibc-demo中给出了ibc环境的完整部署与ibc交易的调试步骤以及所有的源代码, 但是却为给出证明ibc的有效性以及相关的数学证明, 因此本文将分析ibc的实现机制以及cosmos声称ibc具备跨链操作的原子特性进行分析. 完整的ibc-demo环境, 链接在这里 抛开gaia的初始环境, 直接到文档的IBC Command Sequence, 我们看到:
操作一: Client Creation
client creation中不仅传入chain id还传入一个非常重要的共识状态文档(consensus_state.json), 根据官方给出的命令:
gaiacli --home ibc1/n0/gaiacli q ibc client node-state
我们可以同样生成一个, 结果:
{
"type": "ibc/client/tendermint/ConsensusState",
"value": {
"chain_id": "ibc0",
"height": "71497",
"root": {
"type": "ibc/commitment/merkle/Root",
"value": {
"hash": "2gi0YPMec1GHn4WNR0urWPpf2kABOTKBT5OaFfATtFQ="
}
},
"next_validator_set": {
"validators": [
{
"address": "F6009D93FEC4CACDD273225E78DDAF07B582FC35",
"pub_key": {
"type": "tendermint/PubKeyEd25519",
"value": "6yUYsrbCi1CY7NBSy8Zxx2CKA+Tc1YsUX+w57OFGM58="
},
"voting_power": "100",
"proposer_priority": "0"
}
],
"proposer": {
"address": "F6009D93FEC4CACDD273225E78DDAF07B582FC35",
"pub_key": {
"type": "tendermint/PubKeyEd25519",
"value": "6yUYsrbCi1CY7NBSy8Zxx2CKA+Tc1YsUX+w57OFGM58="
},
"voting_power": "100",
"proposer_priority": "0"
}
}
}
}
源码中的结构定义:
// ConsensusState defines a Tendermint consensus state
type ConsensusState struct {
ChainID string `json:"chain_id" yaml:"chain_id"`
Height uint64 `json:"height" yaml:"height"` // NOTE: defined as 'sequence' in the spec
Root commitment.RootI `json:"root" yaml:"root"`
NextValidatorSet *tmtypes.ValidatorSet `json:"next_validator_set" yaml:"next_validator_set"` // contains the PublicKey
}
这个json是其中一条链的共识信息, 其中包含了块高信息, 接下来的验证人集信息以及一个root信息, 从root的type可以看出, root中的hash与当前块高merkle树相关( 为当前块的AppHash ). client创建的命令:
# client for chain ibc1 on chain ibc0 echo -e "12345678\n" | gaiacli --home ibc0/n0/gaiacli \ tx ibc client create ibconeclient \ $(gaiacli --home ibc1/n0/gaiacli q ibc client node-state) \ --from n0 -y -o text # client for chain ibc0 on chain ibc1 echo -e "12345678\n" | gaiacli --home ibc1/n0/gaiacli \ tx ibc client create ibczeroclient \ $(gaiacli --home ibc0/n0/gaiacli q ibc client node-state) \ --from n1 -y -o text
该命令的执行结果, 会将consensus state保存的信息将以key为clients/{chain-id}/consensusState的存入数据库中, 其中的root信息又会再次以key为clients/{chain-id}/roots/{height}存入数据库中. 创建的client的结构:
// State is a type that represents the state of a client.
// Any actor holding the Stage can access on and modify that client information.
type State struct {
// Client ID
id string `json:"id" yaml:"id"`
// Boolean that states if the client is frozen when a misbehaviour proof is
// submitted in the event of an equivocation.
Frozen bool `json:"frozen" yaml:"frozen"`
}
ps. 该结构与具体节点和地址无关, 显然client的创建是以链本身为单位, 而链的识别仅仅以chain-id, 对client的操作仅有冻结选项. 完成了几项数据库的写入之后, key为clients/{chain-id}/consensusState和key为clients/{chain-id}/roots/{height}是写入操作中最重要的两项, 其他具体写入项请参看HandleMsgCreateClient函数, 在此不赘述. 之后会发出client创建成功的events:
ctx.EventManager().EmitEvents(sdk.Events{
sdk.NewEvent(
EventTypeCreateClient,
sdk.NewAttribute(AttributeKeyClientID, msg.ClientID),
),
sdk.NewEvent(
sdk.EventTypeMessage,
sdk.NewAttribute(sdk.AttributeKeyModule, AttributeValueCategory),
sdk.NewAttribute(sdk.AttributeKeySender, msg.Signer.String()),
),
})
操作二: Connection Creation
In order to send transactions using IBC there are two different handshakes that must be performed. First there is a connection created between the two chains. Once the connection is created, an application specific channel handshake is performed which allows the transfer of application specific data. Examples of applications are token transfer, cross-chain validation, cross-chain accounts, and in this tutorial ibc-mock.
为了使用IBC发送交易那么必须执行两种不同握手. 首先, 两个链之间建立了连接, 将执行特定于应用程序的通道握手, 从而可以传输特定于应用程序的数据. 应用程序示例包括令牌转移, 跨链验证, 跨链帐户以及本教程中的ibc-mock.
connection在源码中以 ConnectionEnd
结构体表示, 其在源码中的定义:
// ConnectionEnd defines a stateful object on a chain connected to another separate
// one.
// NOTE: there must only be 2 defined ConnectionEnds to stablish a connection
// between two chains.
type ConnectionEnd struct {
State State `json:"state" yaml:"state"`
ClientID string `json:"client_id" yaml:"client_id"`
// Counterparty chain associated with this connection.
Counterparty Counterparty `json:"counterparty" yaml:"counterparty"`
// Version is utilised to determine encodings or protocols for channels or
// packets utilising this connection.
Versions []string `json:"versions" yaml:"versions"`
}
创建connection的命令:
gaiacli \ --home ibc0/n0/gaiacli \ tx ibc connection handshake \ connectionzero ibconeclient $(gaiacli --home ibc1/n0/gaiacli q ibc client path) \ connectionone ibczeroclient $(gaiacli --home ibc0/n0/gaiacli q ibc client path) \ --chain-id2 ibc1 \ --from1 n0 --from2 n1 \ --node1 tcp://localhost:26657 \ --node2 tcp://localhost:26557
其中产生path chain的命令:
gaiacli --home ibc1/n0/gaiacli q ibc client path
得到的结果:
{
"type": "ibc/commitment/merkle/Prefix",
"value": {
"key_prefix": "aWJj"
}
}
connection create的流程:
- connection_open_init操作: 1. 在ibc0链上记录ConnectionEnd状态为init, 并且以connections/connectionzero和clients/ibconeclient/connections为key存储该ConnectionEnd.
- update_client操作: 1. 会做对client是否frozen的检查, 以及块高检查, client是否tendermint client检查(是否为同构链), 以及检查ibc0最新consensus state, 2. 最后更新ibc1上的client: ibczeroclient的consensus state中的root, height以及nextvalidatorset字段(除了chain-id, 都更新到最新状态), 其状态为ibc0的最新consensus state状态, 奇怪的是打印却是ibconeclient更新 . 3. 数据库更新client state和root状态.
- connection_open_try: 1. 会做版本检查 2. 验证conection state 3. 验证consensus state(被注释) 4. 创建一个状态为tryopen的连接 5. 连接的connectionEnd写数据库
步骤2的验证过程, 会将ibc0链上的proof传送过ibc1链, 包含两条proof信息其中一条为ibc0链的connectionzero的 ConnectionEnd 状态信息, 另一条为ibc0当前块高-1的AppHash的multistore信息, 完整 信息示例如下
{
"proof":{
"StoreInfos":[
{
"Name":"staking",
"Core":{
"CommitID":{
"Version":38,
"Hash":"OyAHcb9W4SvGpTv/fX6VEqWicaOM+9qTXwquGsiwT2o="
}
}
},
{
"Name":"acc",
"Core":{
"CommitID":{
"Version":38,
"Hash":"xHw/kuGR12u6nN+27zsiZ2T6DJ+lZDdPoBj8ZiM1QvU="
}
}
},
{
"Name":"ibc",
"Core":{
"CommitID":{
"Version":38,
"Hash":"wFqTYG72fimvvKU/t7/EF6JSfelTJxslDEbw8vZdHtU="
}
}
},
{
"Name":"params",
"Core":{
"CommitID":{
"Version":38,
"Hash":"3PrT6GfafJIT6djcrepbPNe1pxBCwErffxJdEuW3gBU="
}
}
},
{
"Name":"slashing",
"Core":{
"CommitID":{
"Version":38,
"Hash":"h7c4wbsuEsYYgjhJhCztAGBPREKDWc2M88JZaXOnQao="
}
}
},
{
"Name":"main",
"Core":{
"CommitID":{
"Version":38,
"Hash":"Llfvk2BxBfQuVDx2CcfTIaMDoD6Y6I0m+E3VKdOR0WA="
}
}
},
{
"Name":"supply",
"Core":{
"CommitID":{
"Version":38,
"Hash":"DyyskpRi7Miac9UxgSDUlFwjlmKYawF/myIKoLZK60A="
}
}
},
{
"Name":"distribution",
"Core":{
"CommitID":{
"Version":38,
"Hash":"/awR8FmcgY8vcy4MKPmZ9o95rNBBtFEx95KOH2yvtsw="
}
}
},
{
"Name":"mint",
"Core":{
"CommitID":{
"Version":38,
"Hash":"5zTw4N/uFMgbxIZB7wRoAZ78zbMrwQNaE62Mv+0uPmg="
}
}
},
{
"Name":"gov",
"Core":{
"CommitID":{
"Version":38,
"Hash":"YM0TfBli7KxhY4nWgDSDPykhUJwtKFql9RU5l86WinQ="
}
}
}
]
}
}
该信息会与另一条链的connection state状态一起放入 VerifyMembership
作校验, 该校验函数会放在ics003的读书笔记中讲解.
还有一条与共识相关的ConsensusState Proof信息, 其中也包含两条proof信息, 第一条正是ibc1链在ibc0链上的子状态信息, 信息结构为 ConsensusState 上文提供了源码的定义, 另一条与前一个proof一样是AppHash的multistore信息.
- ibc0链上client updateclient
- connection_open_ack: 1. 会做版本检查 2. 验证链上已有的连接状态是否为init 3. 验证conection state 4. 验证consensus state(被注释) 5. 创建一个状态为open的连接 6. 连接的connectionEnd写数据库
- ibc1链上client updateclient
- connection_open_confirm: 1. 会做版本检查 2. 验证链上已有的连接状态是否为tryopen 3. 验证conection state 4. 创建一个状态为open的连接 5. 连接的connectionEnd写数据库
Connection建立后, ibc0链与ibc1链上均具备状态为open的connection, 可通过该命令查看通道状态:
gaiacli --home ibc0/n0/gaiacli q ibc connection end connectionzero --indent --trust-node
得到结果:
{
"type": "ibc/connection/ConnectionEnd",
"value": {
"state": "OPEN",
"client_id": "ibconeclient",
"counterparty": {
"client_id": "ibczeroclient",
"connection_id": "connectionone",
"prefix": {
"type": "ibc/commitment/merkle/Prefix",
"value": {
"key_prefix": "aWJj"
}
}
},
"versions": [
"1.0.0"
]
}
}
操作三: Create Channel
A channel serves as a conduit for packets passing between a module on one chain and a module on another, ensuring that packets are executed only once, delivered in the order in which they were sent (if necessary), and delivered only to the corresponding module owning the other end of the channel on the destination chain.
通道服务可以当做一个渠道使得消息可以从一条链上的模块传递给另一条链的模块, 确保这个包有且仅穿第一次, 并且准确按照发送的顺序进行传递(如有必要), 并且传递仅发生在分别拥有同一通道对应两端的链间对应模块之间.
创建通道时需要指定通道是否为有序通道以及端口ID, 通道的源码结构:
type Channel struct {
State State `json:"state" yaml:"state"`
Ordering Order `json:"ordering" yaml:"ordering"`
Counterparty Counterparty `json:"counterparty" yaml:"counterparty"`
ConnectionHops []string `json:"connection_hops" yaml:"connection_hops"`
Version string `json:"version" yaml:"version "`
}
// Counterparty defines the counterparty chain's channel and port identifiers
type Counterparty struct {
PortID string `json:"port_id" yaml:"port_id"`
ChannelID string `json:"channel_id" yaml:"channel_id"`
}
创建channel的命令:
gaiacli tx ibc channel handshake [client-id] [port-id] [chan-id] [conn-id] [cp-client-id] [cp-port-id] [cp-chain-id] [cp-conn-id] gaiacli \ --home ibc0/n0/gaiacli \ tx ibc channel handshake \ ibconeclient bank chanshixianzhongnelzero connectionzero \ ibczeroclient bank channelone connectionone \ --node1 tcp://localhost:26657 \ --node2 tcp://localhost:26557 \ --chain-id2 ibc1 \ --from1 n0 --from2 n1
bank: 即为portID.
[cp-*]: counterparty, 指代参与跨链的另一条链.
Create Channel的流程, 与create connection类似, 有4种操作 channel_open_init
, channel_open_try
, channel_open_ack
, channel_open_confirm
:
-
channel_open_init操作(ibc0):
- 检查链上connection状态不为none
- 构建一个状态为init的channel
- 设置该ibc0上channel的发送与接收的sequence为1, 通过写数据库的形式
-
channel_open_try操作(ibc1):
- 检查链上connection状态是否为open
- 构建一个状态为opentry的channel
- 根据MsgChannelOpenTry.ProofInit验证channel信息与apphash是否正确
- 设置该ibc1上channel的发送与接收的sequence为1, 通过写数据库的形式
-
channel_open_ack操作(ibc0):
- 检查链上channel状态是否为init
- 检查链上connection状态是否为open
- 根据MsgChannelOpenAck.ProofTry验证channel信息与apphash是否正确
- 修改channel状态为open
-
channel_open_confirm操作(ibc1)
- 检查链上channel状态是否为opentry
- 检查链上connection状态是否为open
- 根据MsgChannelOpenConfirm.ProofAck验证channel信息与apphash是否正确
- 修改channel状态为open
4种操作之间必然也存在这update_client操作, 该操作与创建connection过程中update_client操作完全一样.
操作四: Packet
包的结构:
// Packet defines a type that carries data across different chains through IBC
type Packet struct {
Sequence uint64 `json:"sequence"` // number corresponds to the order of sends and receives, where a Packet with an earlier sequence number must be sent and received before a Packet with a later sequence number.
Timeout uint64 `json:"timeout"` // indicates a consensus height on the destination chain after which the Packet will no longer be processed, and will instead count as having timed-out.
SourcePort string `json:"source_port"` // identifies the port on the sending chain.
SourceChannel string `json:"source_channel"` // identifies the channel end on the sending chain.
DestinationPort string `json:"destination_port"` // identifies the port on the receiving chain.
DestinationChannel string `json:"destination_channel"` // identifies the channel end on the receiving chain.
Data []byte `json:"data"` // opaque value which can be defined by the application logic of the associated modules.
}
-
Sequence: 序号, 与包在通道上的发送, 接收序列有关, 通道中的包依据序号大小, 有序发送与接收 -
Timeout: 超时, 表示目标链上的区块高度, 当超过该高度以后该包将不会被处理, 并会将其视为已超时 -
SourcePort: 源端口, 发送链上的端口 -
SourceChannel: 源通道, 发送链上的通道 -
DestinationPort: 目标端口, 目标链链上的端口 -
DestinationChannel: 目标通道, 目标链上的通道 -
Data: 数据, 数据与应用逻辑关联的模块相关
包发送
To send a packet using the bank
application protocol, you need to know the channel
you plan to send on, as well as the port
on the channel. You also need to provide an address
and amount
. Use the following command to send the packet:
包发送用到了 bank
应用协议, 你需要知道你计划使用哪个通道来发送包, 以及该通道上端口. 你需要提供地址与金额.
gaiacli \ --home ibc0/n0/gaiacli \ tx ibc transfer transfer \ bank channelzero \ $(gaiacli --home ibc0/n0/gaiacli keys show n1 -a) 1stake \ --from n0 \ --source
该命令即会组装一个上文的 Packet
结构, 该结构中的 Data
字段:
{
"amount":[
{
"denom":"bank/channelone/stake",
"amount":"1"
}
],
"sender":"cosmos15dzt38uzufx0fhga3f373yveccla8he8mh6gmt",
"receiver":"cosmos1xax60gm9pfq3d5fcasymw0lx7cu3l3ee8q3esy",
"source":true
}
denom
说明了交易的token是跨链token. 值得一提的是, 源码实现中在发送端如果跨链token的发送链为原始链, token在发生跨链时会将token发送到escrowAddress 第三方保管地址, 如果跨链token的发送链不是原始链, 那么token在发生跨链时token将会被销毁.
包接收
包发送后需要对目标链提交一笔含在发送链上发送包的接收交易, 才能完成接收链跨链token的接收.
gaiacli \ tx ibc transfer recv-packet \ bank channelzero ibczeroclient \ --home ibc1/n0/gaiacli \ --packet-sequence 1 \ --timeout $TIMEOUT \ --from n1 \ --node2 tcp://localhost:26657 \ --chain-id2 ibc0 \ --source
值得一说的是, 源码实现中会需要一个账户, 并且该账户需要具备铸币与销币的权限, 也就是说目标链接收token过程, 实际上是接收包的交易校验通过以后, 由该特殊账户铸币产生相应的跨链币后转账到对应账户中, 之后需要发送出去的时候, 作销币操作.
before ibc
查询账户余额:
{
"type":"cosmos-sdk/Account",
"value":{
"address":"cosmos1vgu8e3vchsnztlepzutpxwsf8p7c27awdx9xmj",
"coins":[
{
"denom":"n0token",
"amount":"1000000000"
},
{
"denom":"stake",
"amount":"400000000"
}
],
"public_key":{
"type":"tendermint/PubKeySecp256k1",
"value":"Ah9M7XPQIrjniXpghE3+bWeLG/0Phck58aqS/gQQjmxY"
},
"account_number":"3",
"sequence":"10"
}
}
after ibc
再次查询账户查询余额:
{
"type":"cosmos-sdk/Account",
"value":{
"address":"cosmos1vgu8e3vchsnztlepzutpxwsf8p7c27awdx9xmj",
"coins":[
{
"denom":"bank/channelone/stake",
"amount":"1"
},
{
"denom":"n0token",
"amount":"1000000000"
},
{
"denom":"stake",
"amount":"400000000"
}
],
"public_key":{
"type":"tendermint/PubKeySecp256k1",
"value":"Ah9M7XPQIrjniXpghE3+bWeLG/0Phck58aqS/gQQjmxY"
},
"account_number":"3",
"sequence":"12"
}
}
增加了该项 "denom":"bank/channelone/stake" , 并且数量为1, 与实际发送一致, 说明至此跨链操作完成.
本文参与登链社区写作激励计划 ，好文好收益，欢迎正在阅读的你也加入。
- 发表于 21分钟前
- 阅读 ( 8 )
- 学分 ( 0 )
- 分类：Cosmos
以上就是本文的全部内容，希望对大家的学习有所帮助，也希望大家多多支持 码农网
猜你喜欢:
- 以太坊源码分析(36)ethdb源码分析
- [源码分析] kubelet源码分析（一）之 NewKubeletCommand
- libmodbus源码分析（3）从机（服务端）功能源码分析
- [源码分析] nfs-client-provisioner源码分析
- [源码分析] kubelet源码分析（三）之 Pod的创建
- Spring事务源码分析专题（一）JdbcTemplate使用及源码分析
本站部分资源来源于网络，本站转载出于传递更多信息之目的，版权归原作者或者来源机构所有，如转载稿涉及版权问题，请联系我们。
iPhone开发实战
2009-10 / 69.00元
《iPhone开发实战》全面探讨了iPhone平台的两种编程方式——Web开发和SDK编程。全书结合示例对这两种编程方式的基本流程、基本原理和基本原则给出了详细而通俗的讲解。在Web开发方面，分别介绍了三个iPhone Web库，即WebKit、iUI和Canvas，并讨论了Web开发环境Dashcode，最后阐述Web应用程序的调试。在SDK开发方面，详细描述其各种组件和功能，包括Xcode、I......一起来看看 《iPhone开发实战》 这本书的介绍吧!
