Enum DydxError 

pub enum DydxError {
    Http(DydxHttpError),
    WebSocket(DydxWsError),
    Grpc(Box<Status>),
    Signing(String),
    Encoding(EncodeError),
    Decoding(DecodeError),
    Json {
        message: String,
        raw: Option<String>,
    },
    Config(String),
    InvalidData(String),
    InvalidOrderSide(String),
    UnsupportedOrderType(String),
    NotImplemented(String),
    Order(String),
    Parse(String),
    Wallet(String),
    Nautilus(Error),
}

The main error type for all dYdX adapter operations.

Variants

Http(DydxHttpError)

HTTP client errors.

WebSocket(DydxWsError)

WebSocket connection errors.

Grpc(Box<Status>)

gRPC errors from Cosmos SDK node.

Signing(String)

Transaction signing errors.

Encoding(EncodeError)

Protocol buffer encoding errors.

Decoding(DecodeError)

Protocol buffer decoding errors.

Json

JSON serialization/deserialization errors.

Fields

message: String

raw: Option<String>

The raw JSON that failed to parse, if available.

Config(String)

Configuration errors.

InvalidData(String)

Invalid data errors.

InvalidOrderSide(String)

Invalid order side error.

UnsupportedOrderType(String)

Unsupported order type error.

NotImplemented(String)

Feature not yet implemented.

Order(String)

Order construction and submission errors.

Parse(String)

Parsing errors (e.g., string to number conversions).

Wallet(String)

Wallet and account derivation errors.

Nautilus(Error)

Nautilus core errors.

Implementations

impl DydxError

pub fn is_sequence_mismatch(&self) -> bool

Returns true if this error is a sequence mismatch (code=32 or code=104 with sequence hint).

Sequence mismatch occurs when:

• Multiple transactions race for the same sequence number
• A transaction was submitted but not yet included in a block
• The local sequence counter is out of sync with chain state

On dYdX v4, sequence mismatches can manifest as either:

• code=32: Standard Cosmos SDK “account sequence mismatch”
• code=104: dYdX authenticator “signature verification failed; please verify sequence”

These errors are typically recoverable by resyncing the sequence from chain and rebuilding the transaction.

pub fn is_tx_in_mempool(&self) -> bool

Returns true if this error indicates the transaction is already in the mempool (code=19).

This is benign for short-term orders – the transaction was already accepted by the mempool on a previous submission and will be processed. Callers can safely treat this as success.

pub fn is_cancel_already_in_memclob(&self) -> bool

Returns true if this error indicates a duplicate cancel already in the memclob (code=9).

dYdX rejects cancel messages when an existing cancel for the same order has a greater-than-or-equal GoodTilBlock. The original cancel will be processed.

pub fn is_order_does_not_exist(&self) -> bool

Returns true if this error indicates the order to cancel does not exist (code=3006).

The order was already filled, expired, or previously cancelled.

pub fn is_benign_cancel_error(&self) -> bool

Returns true if this error is benign for short-term cancel operations.

Benign cancel errors occur during overlapping cancel waves (common in grid MM):

• code=19: Transaction already in mempool cache (duplicate tx bytes)
• code=9: Cancel already exists in memclob with >= GoodTilBlock
• code=3006: Order to cancel does not exist (already filled/expired/cancelled)

pub fn is_transient(&self) -> bool

Returns true if this error is likely transient and worth retrying.

Transient errors include:

• Sequence mismatch (recoverable by resync)
• Network timeouts
• Temporary node unavailability

pub fn is_definitive_broadcast_rejection(&self) -> bool

Returns true if this error is a definitive CheckTx rejection of the broadcast transaction.

broadcast_tx uses sync mode, so a code=N failure is the node’s verdict: the transaction never entered the mempool and no message in it executed. Benign codes (tx already in mempool, duplicate cancel, order already gone) mean the command was already handled, and transient errors (sequence mismatch, timeouts) are never a final verdict; both return false, as do transport failures that leave the outcome unknown.

Trait Implementations

impl Debug for DydxError

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

Formats the value using the given formatter.

impl Display for DydxError

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

Formats the value using the given formatter.

impl Error for DydxError

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 From<Box<Status>> for DydxError

fn from(source: Box<Status>) -> Self

Converts to this type from the input type.

impl From<DecodeError> for DydxError

fn from(source: DecodeError) -> Self

Converts to this type from the input type.

impl From<DydxHttpError> for DydxError

fn from(source: DydxHttpError) -> Self

Converts to this type from the input type.

impl From<DydxWsError> for DydxError

fn from(source: DydxWsError) -> Self

Converts to this type from the input type.

impl From<EncodeError> for DydxError

fn from(source: EncodeError) -> Self

Converts to this type from the input type.

impl From<Error> for DydxError

fn from(source: Error) -> Self

Converts to this type from the input type.