Protected
constructorReadonly
broadcastReadonly
broadcastReadonly
registryBroadcasts a signed transaction to the network without monitoring it.
If broadcasting is rejected by the node for some reason (e.g. because of a CheckTx failure), an error is thrown.
If the transaction is broadcasted, a string
containing the hash of the transaction is returned. The caller then
usually needs to check if the transaction was included in a block and was successful.
Returns the hash of the transaction
Like execute
but allows executing multiple messages in one transaction.
Protected
forceProtected
forceThrows an error if no contract was found at the address
getContracts() returns all contract instances for one code and is just looping through all pagination pages.
This is potentially inefficient and advanced apps should consider creating their own query client to handle pagination together with the app's screens.
Protected
getProtected
getMakes a smart query on the contract, returns the parsed JSON document.
Promise is rejected when contract does not exist. Promise is rejected for invalid query format. Promise is rejected for invalid response format.
Optional
explicitSignerData: SignerDataCreates a transaction with the given messages, fee and memo. Then signs and broadcasts the transaction.
The address that will sign transactions using this instance. The signer must be able to sign with this address.
Creates a transaction with the given messages, fee and memo. Then signs and broadcasts the transaction.
This method is useful if you want to send a transaction in broadcast, without waiting for it to be placed inside a block, because for example I would like to receive the hash to later track the transaction with another tool.
The address that will sign transactions using this instance. The signer must be able to sign with this address.
Returns the hash of the transaction
Uploads code and returns a receipt, including the code ID
Optional
instantiatePermission: AccessConfigStatic
connectCreates an instance by connecting to the given Tendermint RPC endpoint.
This uses auto-detection to decide between a Tendermint 0.37 and 0.34 client.
To set the Tendermint client explicitly, use create
.
Static
connectCreates an instance by connecting to the given Tendermint RPC endpoint.
This uses auto-detection to decide between a Tendermint 0.37 and 0.34 client.
To set the Tendermint client explicitly, use createWithSigner
.
Static
createCreates an instance from a manually created Tendermint client.
Use this to use Tendermint37Client
instead of Tendermint34Client
.
Static
createCreates an instance from a manually created Tendermint client.
Use this to use Tendermint37Client
instead of Tendermint34Client
.
Static
offlineCreates a client in offline mode.
This should only be used in niche cases where you know exactly what you're doing, e.g. when building an offline signing application.
When you try to use online functionality with such a signer, an exception will be raised.
Generated using TypeDoc
Broadcasts a signed transaction to the network and monitors its inclusion in a block.
If broadcasting is rejected by the node for some reason (e.g. because of a CheckTx failure), an error is thrown.
If the transaction is not included in a block before the provided timeout, this errors with a
TimeoutError
.If the transaction is included in a block, a
DeliverTxResponse
is returned. The caller then usually needs to check for execution success or failure.