Direct interaction with ledger code
This is an advanced guide for those who want to develop applications that directly interact with the ledger code.
There are two custom modules on cheqd ledger related to identity functionality:
Types and utilities are available for re-use for each module as well. The
utilsinclude functions for working with these custom modules, validation logic, etc.
After compiling a message (in your custom application), you can make a gRPC call to the ledger with your message.
In general, the process building applications that work with cheqd in other languages follows very similar logic as described above for Golang apps.
The high-level steps are:
- 2.Prepare and sign the message correctly: This relies partly on understanding general Cosmos SDK message format and transaction signing, as well as any cheqd-specific bits. A real-world example of this is the
@cheqd/sdkNPM package that consumes
- 3.Send the message to ledger using gRPC/RPC: Once a message/transaction is correctly compiled and signed, standard transport libraries can be used to target the gRPC/RPC endpoints for a