As we all become increasingly aware of the risk of having our privacy taken away whilst demanding interoperability between systems, a single entity or even blockchain providing the single source of truth is no longer satisfactory.

This is where IBC becomes a critical component on which the future is built on.

How we built it

Since the relayer services and zones can be external or public, it makes sense to design for cases where the packets sent can be plain text or encrypted.

The use cases we designed for are communications between:

  • Private to Public zones where information is public: Use Case 1
  • Private to Public zones where information is authorised by the sender only Use Case 2

With all the cases listed, this project uses the concepts of verifiable credential to showcase IBC usage. We use dencentralised identifiers for entities to ensure no social mapping, behaviour patterns can be derived.

Challenges we ran into

The main design challenge is the on-ramp of cosmos-sdk, IBC concepts and importantly, the understanding of verifiable credential role.

Technically, the understanding of different codec types for data over the wire was quite difficult. Thank you to the community on the Discord channel for helping us out.

Accomplishments that we're proud of

Within the time of the hackathon, we were able to get working PoC working for both use cases, which was beyond what we had planned.

What's next for CertX

We are incredibly excited to explore more in the space of verifiable credentials with IBC, this is because identity might be built on centralised / private eco systems and in some cases, rightly so. However, with IBC, it is possible to share what is needed for all zones, use cases might be for KYC, AML management as well.

Built With

  • cosmos
  • go
  • starport
Share this project: