Enum VtxoStandardnessError 

pub enum VtxoStandardnessError {
    Dusty,
    DustSibling {
        item_idx: usize,
        item_count: usize,
        output_idx: usize,
    },
    Script,
    ScriptSibling {
        item_idx: usize,
        item_count: usize,
        output_idx: usize,
    },
}

Reason a Vtxo failed the Vtxo::check_standard check.

A VTXO is standard if and only if every output in its exit chain — its own output plus all sibling outputs of every exit transaction — uses a known script type and carries a value at or above that script’s dust limit. Each variant identifies the first violation encountered.

Sibling-typed variants (VtxoStandardnessError::DustSibling and VtxoStandardnessError::ScriptSibling) locate the offending output by genesis item index plus the index inside that item’s other_outputs list; with item_count they tell you how deep along the chain the problem sits.

Variants

Dusty

The VTXO’s own output value is below the dust limit for its script type, so the final exit transaction cannot be relayed.

DustSibling

A sibling output produced somewhere along the exit chain is below the dust limit. The current VTXO can clear dust on its own and still trip this variant — the exit transaction containing the sub-dust sibling is the part that won’t relay.

Example: a small total dust-isolation can’t rescue

Suppose Alice owns a 600-sat VTXO and pays Bob 200 sat. The arkoor builder produces:

600 sat  ->  200 sat   // Bob (sub-dust — below P2TR_DUST = 330)
             400 sat   // Alice's change (above dust)

Even when the builder is asked to apply dust isolation (see ArkoorBuilder::new_with_checkpoint_isolate_dust), the total is too small to fix. An isolation output has to be at least P2TR_DUST (330 sat) to clear the relay limit. Bob’s 200 sat already lives in the dust pool; to reach 330 the builder would have to split Alice’s change and pull another 130 sat into the pool. That leaves 270 sat as the leftover piece of Alice’s change — still sub-dust. Splitting trades one sub-dust output for two, so the builder falls through and emits the 200/400 outputs as-is.

Fields

item_idx: usize

item_count: usize

output_idx: usize

Script

The VTXO’s own output uses an unrecognised script type, or an OP_RETURN longer than the 83-byte standardness ceiling.

ScriptSibling

A sibling output along the exit chain uses an unrecognised script type (or an over-long OP_RETURN). Same locator semantics as VtxoStandardnessError::DustSibling.

Fields

item_idx: usize

item_count: usize

output_idx: usize

Trait Implementations

impl Clone for VtxoStandardnessError

fn clone(&self) -> VtxoStandardnessError

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for VtxoStandardnessError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for VtxoStandardnessError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for VtxoStandardnessError

impl Error for VtxoStandardnessError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl PartialEq for VtxoStandardnessError

fn eq(&self, other: &VtxoStandardnessError) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for VtxoStandardnessError