import { Transaction, TransferObject } from './types.js';
import { type LedgerCommonSchemas } from '@canton-network/core-ledger-client-types';
import { PartyId } from '@canton-network/core-types';
import { AbstractLedgerProvider } from '@canton-network/core-provider-ledger';
type JsTransaction = LedgerCommonSchemas['JsTransaction'];
export declare class TransactionParser {
    private readonly ledgerProvider;
    private readonly partyId;
    private readonly transaction;
    private readonly isMasterUser;
    constructor(ledgerProvider: AbstractLedgerProvider, transaction: JsTransaction, partyId: PartyId, isMasterUser: boolean);
    parseTransaction(): Promise<Transaction>;
    parseTransferObjects(): Promise<TransferObject[]>;
    private fetchTransferObjectChoice;
    private parseEvents;
    private parseRawCreate;
    private parseRawArchive;
    private buildRawEvent;
    private parseExercise;
    private parseViaTxKind;
    private buildTransfer;
    private buildMergeSplit;
    private buildFromTransferInstructionExercise;
    private buildBasic;
    private getChildren;
    private getEventsForArchive;
}
/** Detects the ledger API CONTRACT_EVENTS_NOT_FOUND error across the
 *  different error shapes thrown by the various provider/transport stacks:
 *  - JsCantonError from a direct ledger client:
 *    `{ code: 'CONTRACT_EVENTS_NOT_FOUND', cause, ... }`
 *  - JSON-RPC error response (e.g. wallet gateway over HTTP):
 *    `{ error: { code, message, data: JsCantonError } }`
 *  - JSON-RPC error object (e.g. extension window transport):
 *    `{ code, message, data: JsCantonError }`
 *  - As a last resort, a stringified error body containing the code. */
export declare function isContractEventsNotFoundError(err: unknown): boolean;
export {};
//# sourceMappingURL=parser.d.ts.map