cheqd-sdk (forked from Evernym VDR Tools).build_create_did_request(id, verkey, alias)indy_crypto_sign(did, verkey)build_tx(pool_alias, pub_key, builded_request, account_number, account_sequence, max_gas, max_coin_amount, denom, timeout_height, memo)cheqd_keys_sign(wallet_handle, key_alias, tx).broadcast_tx_commit(pool_alias, signed).id (string): Target DID as Base58-encoded string with 16 or 32 byte long unique identifier.verkey (string): All Verification Method key(s) linked to this DID and its DID controller(s). At least one Verification Method key must be defined.CreateDidRequest must be signed by the controller DID(s) and their associated key(s) defined. It is invoked as follows:key string. This key is how the DID is uniquely referenced when it is stored in the ledger state.id (string): Target DID as Base58-encoded string with 16 or 32 byte long unique identifier.verkey (string): All Verification Method key(s) linked to this DID and its DID controller(s).versionId (string): Transaction hash of the last applicable DIDDoc version.controller field must already be stored on ledger, from a previous CreateDidRequest.controller field, or if controller does not exist, by at least one key from authentication.key string. This key is how the DID is uniquely referenced when it is stored in the ledger state.id associated with the DID that needs to be fetched.path: Path for the Tendermint RPC endpoint from which the response was returned.data: Query with an key that corresponds to a specific DID state, encoded to bytes.height: Block height from which the state is to be fetched. This can be set to none for auto-calculation that fetches from latest ledger state, while providing a previously block height can be used to query the DID state at a previous block height / equivalent time.prove: Boolean value (true or false) that defines whether the state proof should be fetched along with the response.