The Bundle subclass to use.
The agent which will sign and/or broadcast the bundle.
Optional
callbackNested bundles are flattened, this counts the depth.
Next message id.
Messages in this bundle, unencrypted.
Static
bundleThe address from which transactions are signed and sent.
Disallowed in bundle - do it beforehand or afterwards.
Private
conformedFormat the messages for API v1 like secretjs and encrypt them.
The default denomination in which the agent operates.
Get a client instance for talking to a specific smart contract as this executor.
Optional
address: stringOptional
codeHash: stringRest
...args: unknown[]Get an uploader instance which performs code uploads and optionally caches them.
Optional
options: Partial<U>Disallowed in bundle - do it beforehand or afterwards.
The friendly name of the agent.
Disallowed in bundle - do it beforehand or afterwards.
Complete the asynchronous initialization of this Agent.
Nested bundles are flattened, i.e. trying to create a bundle from inside a bundle returns the same bundle.
Optional
cb: BundleCallback<B>Private
composePrivate
encryptPrivate
encryptAdd an init message to the bundle.
await agent.instantiate(template.define({ label, initMsg })
the unmodified input.
Add multiple init messages to the bundle.
await agent.bundle().wrap(async bundle=>{
await bundle.instantiateMany(template.instances({
One: { label, initMsg },
Two: { label, initMsg },
}))
await agent.instantiateMany({
One: template1.instance({ label, initMsg }),
Two: template2.instance({ label, initMsg }),
})
})
the unmodified inputs.
Queries are disallowed in the middle of a bundle because even though the bundle API is structured as multiple function calls, the bundle is ultimately submitted as a single transaction and it doesn't make sense to query state in the middle of that.
Format the messages for API v1beta1 like secretcli and generate a multisig-ready
unsigned transaction bundle; don't execute it, but save it in
state/$CHAIN_ID/transactions
and output a signing command for it to the console.
Optional
name: stringBroadcast a bundle to the chain.
Uploads are disallowed in the middle of a bundle because it's easy to go over the max request size, and difficult to know what that is in advance.
Optional
meta: Partial<Uploadable>Uploads are disallowed in the middle of a bundle because it's easy to go over the max request size, and difficult to know what that is in advance.
Generated using TypeDoc
Base class for transaction-bundling Agent for both Secret Network implementations.