/**
 * Block explorer URL patterns for different chains
 * This mapping allows for easy configuration and extension of transaction link formats
 */
export interface BlockExplorerPattern {
    /** Domain pattern to match against block explorer URLs */
    domain: string;
    /** Function to generate the transaction URL */
    generateUrl: (baseUrl: string, transactionHash: string) => string;
    /** Description of the pattern for documentation */
    description: string;
}
/**
 * Predefined patterns for known block explorers
 * Add new patterns here as needed for different chains
 */
export declare const BLOCK_EXPLORER_PATTERNS: BlockExplorerPattern[];
/**
 * Default pattern for standard block explorers
 * Used when no specific pattern matches
 */
export declare const DEFAULT_PATTERN: BlockExplorerPattern;
/**
 * Block explorer domains known to support the /op/{userOpHash} route
 * for ERC-4337 UserOperation lookups.
 *
 * Only Blockscout-based explorers are known to support this route.
 * Etherscan-family explorers (etherscan.io, polygonscan.com, etc.)
 * return 404 for /op/ paths. JiffyScan uses /userOpHash/ instead.
 *
 * Customers can extend this list via the transaction-confirmation view override.
 */
export declare const USER_OP_SUPPORTED_EXPLORER_DOMAINS: string[];
/**
 * Check whether a block explorer URL supports the /op/{hash} route.
 * Matches against the built-in list and any additional domains provided
 * by the customer via the transaction-confirmation view override.
 */
export declare const supportsUserOpPath: (blockExplorerUrl: string, additionalDomains?: string[]) => boolean;
/**
 * Find the appropriate pattern for a given block explorer URL
 */
export declare const findBlockExplorerPattern: (blockExplorerUrl: string) => BlockExplorerPattern;