Commitment class

For preflight checks and transaction processing, Solana nodes choose which bank state to query based on a commitment requirement set by the client. The commitment describes how finalized a block is at that point in time. When querying the ledger state, it's recommended to use lower levels of commitment to report progress and higher levels to ensure the state will not be rolled back.

For processing many dependent transactions in series, it's recommended to use confirmed commitment, which balances speed with rollback safety. For total safety, it's recommended to use finalized commitment. https://solana.com/docs/rpc

Properties

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

value → String

final

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toJson([bool preFlight = false]) → Map<String, dynamic>

toString() → String

A string representation of this object.

override

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Methods

fromName(String value, {Commitment? defaultValue}) → Commitment

Constants

confirmed → const Commitment

the node will query the most recent block that has been voted on by supermajority of the cluster.

finalized → const Commitment

the node will query its most recent block. Note that the block may still be skipped by the cluster.

processed → const Commitment

the node will query the most recent block confirmed by supermajority of the cluster as having reached maximum lockout, meaning the cluster has recognized this block as finalized

values → const List<Commitment>