Create egress packets and listening for incoming packets

[ebuchman]

Jae:

We're missing is a way for other plugins to initiate an egress packet.
We should just start with a test transaction called IBCTestTx which can be signed by anyone (at first). So any user can submit an IBCTestTx to save an egress Packet of any sort.

We're also missing a way for other plugins to handle incoming packets. How can another plugin, like the TokenTransferPlugin register to "listen" for incoming "coin" packets?

[faddat]

Jargon check:

egress packet - packet that is destined for another chain, where it will _______

ingress packet - packet from another chain to the local chain, which will ________

Hope it's helpful

[ethanfrey]

I think we can do a lot on the client side (in light-client lib)

What is an egress packet other than a proof that a given tx was commited to the chain (tx, proof, header, commit sigs, maybe validator set). This can go to the hub (and we can figure out if syncing validator changes is independent of the egress packet).

What is an ingress packet but the same thing, signed by the hub for a local chain?

I was working on exporting all this info for txs (not just abci state), but found the current api limiting (I must export all txs for one block).

I think a bunch of us need to sit down together and hash out all the important flows and proofs we will need for cosmos, so we can build them as one unified whole.

[faddat]

I would love that.

Oh, also all this talk of abstraction is delightful. I had not seen this until 30 seconds ago-- get a lot of github "traffic" I guess you could say

Anyway-- yes, let's.

[ethanfrey]

I think this is done by 0.6.0 with the relay and all.