Interface: ProcedureOpts

Defined in: src/api/procedures/types.ts:113

Properties

mortality?

optional mortality: MortalityProcedureOpt

Defined in: src/api/procedures/types.ts:133

This option allows for transactions that never expire, aka "immortal". By default, a transaction is only valid for approximately 5 minutes (250 blocks) after its construction. Allows for transaction construction to be decoupled from its submission, such as requiring manual approval for the signing or providing "at least once" guarantees.

More information can be found here. Note the Polymesh chain will never reap Accounts, so the risk of a replay attack is mitigated.

---

multiSigOpts?

optional multiSigOpts: MultiSigProcedureOpt

Defined in: src/api/procedures/types.ts:138

These options will only apply when the signingAccount is a MultiSig signer and the transaction is being wrapped as a proposal

---

nonce?

optional nonce: BigNumber | Promise<BigNumber> | () => BigNumber | Promise<BigNumber>

Defined in: src/api/procedures/types.ts:126

nonce value for signing the transaction

An Account can directly fetch its current nonce by calling account.getCurrentNonce. More information can be found at: https://polkadot.js.org/docs/api/cookbook/tx/#how-do-i-take-the-pending-tx-pool-into-account-in-my-nonce

Note

the passed value can be either the nonce itself or a function that returns the nonce. This allows, for example, passing a closure that increases the returned value every time it's called, or a function that fetches the nonce from the chain or a different source

---

signingAccount?

optional signingAccount: string | Account

Defined in: src/api/procedures/types.ts:117

Account or address of a signing key to replace the current one (for this procedure only)

---

skipChecks?

optional skipChecks: SkipChecksOpt

Defined in: src/api/procedures/types.ts:147

This option allows for skipping checks for the Procedure. By default, all checks are performed.

This can be useful while batching transactions which could have failed due to insufficient roles or permissions individually, but you don't want to fail the entire batch.

Note

even if the checks are skipped from being validated on the SDK, they will still be validated on the chain