Vana SDK - v2.2.2
    Preparing search index...

    Interface TransactionResult<C, F>

    Represents a submitted blockchain transaction as a self-describing POJO.

    Transaction results MUST include contract and function for proper event parsing. This strongly-typed design enables automatic event extraction without heuristics. Use vana.waitForTransactionEvents() to retrieve typed events from the receipt.

    Architecture: POJOs (Plain Old JavaScript Objects) ensure serialization safety and framework independence. Contract and function fields enable deterministic event parsing.

    const result: TransactionResult = {
      hash: '0x123...',
      from: '0x456...',
      contract: 'DataRegistry',
      fn: 'addFile',
      chainId: 14800
    };

    // Wait for events
    const events = await vana.waitForTransactionEvents(result);
    interface TransactionResult<
        C extends Contract = Contract,
        F extends Fn<C> = Fn<C>,
    > {
        hash: `0x${string}`;
        from: `0x${string}`;
        contract: C;
        fn: F;
        chainId?: number;
        value?: bigint;
        nonce?: number;
        to?: `0x${string}`;
    }

    Type Parameters

    • C extends Contract = Contract
    • F extends Fn<C> = Fn<C>
    Index

    Properties

    hash from contract fn chainId? value? nonce? to?

    Properties

    hash: `0x${string}`

    Transaction hash for tracking and confirmation

    from: `0x${string}`

    Sender's wallet address

    contract: C

    Contract that was called (required for event parsing)

    fn: F

    Function that was called (required for event parsing)

    chainId?: number

    Network chain ID where transaction was submitted

    value?: bigint

    Transaction value in wei (for payable functions)

    nonce?: number

    Transaction sequence number for the sender

    to?: `0x${string}`

    Contract address (if different from standard deployment)

    Settings

    Member Visibility

    On This Page

    Properties