Les donnees on-chain en production : ce que personne ne vous dit | Akousa

typescript

import { createPublicClient, fallback, http } from "viem";
import { mainnet } from "viem/chains";
 
const client = createPublicClient({
  chain: mainnet,
  transport: fallback(
    [
      http("https://eth-mainnet.g.alchemy.com/v2/YOUR_KEY", {
        retryCount: 3,
        retryDelay: 1500,
        timeout: 15_000,
      }),
      http("https://mainnet.infura.io/v3/YOUR_KEY", {
        retryCount: 3,
        retryDelay: 1500,
        timeout: 15_000,
      }),
      http("https://rpc.ankr.com/eth", {
        retryCount: 2,
        retryDelay: 2000,
        timeout: 20_000,
      }),
    ],
    { rank: true },
  ),
});

typescript

interface IndexedBlock {
  number: bigint;
  hash: `0x${string}`;
  parentHash: `0x${string}`;
}
 
async function detectReorg(
  client: PublicClient,
  lastIndexed: IndexedBlock,
): Promise<{ reorged: boolean; depth: number }> {
  const currentBlock = await client.getBlock({
    blockNumber: lastIndexed.number,
  });
 
  if (currentBlock.hash === lastIndexed.hash) {
    return { reorged: false, depth: 0 };
  }
 
  // Remonter en arriere pour trouver ou la chaine a diverge
  let depth = 1;
  let checkNumber = lastIndexed.number - 1n;
 
  while (checkNumber > 0n && depth < 128) {
    const onChain = await client.getBlock({ blockNumber: checkNumber });
    const inDb = await getIndexedBlock(checkNumber); // votre lookup en base de donnees
 
    if (onChain.hash === inDb?.hash) {
      return { reorged: true, depth };
    }
 
    depth++;
    checkNumber--;
  }
 
  return { reorged: true, depth };
}

typescript

import type { PublicClient, Log, AbiEvent } from "viem";
 
async function fetchLogsInChunks<T extends AbiEvent>(
  client: PublicClient,
  params: {
    address: `0x${string}`;
    event: T;
    fromBlock: bigint;
    toBlock: bigint;
    maxBlockRange?: bigint;
  },
): Promise<Log<bigint, number, false, T, true>[]> {
  const { address, event, fromBlock, toBlock, maxBlockRange = 2000n } = params;
  const allLogs: Log<bigint, number, false, T, true>[] = [];
 
  let currentFrom = fromBlock;
 
  while (currentFrom <= toBlock) {
    const currentTo = currentFrom + maxBlockRange - 1n > toBlock ? toBlock : currentFrom + maxBlockRange - 1n;
 
    try {
      const logs = await client.getLogs({
        address,
        event,
        fromBlock: currentFrom,
        toBlock: currentTo,
      });
 
      allLogs.push(...logs);
      currentFrom = currentTo + 1n;
    } catch (error) {
      // Si la plage est trop large (trop de resultats), la diviser en deux
      if (isRangeTooLargeError(error) && currentTo > currentFrom) {
        const mid = currentFrom + (currentTo - currentFrom) / 2n;
        const firstHalf = await fetchLogsInChunks(client, {
          address,
          event,
          fromBlock: currentFrom,
          toBlock: mid,
          maxBlockRange,
        });
        const secondHalf = await fetchLogsInChunks(client, {
          address,
          event,
          fromBlock: mid + 1n,
          toBlock: currentTo,
          maxBlockRange,
        });
        allLogs.push(...firstHalf, ...secondHalf);
        currentFrom = currentTo + 1n;
      } else {
        throw error;
      }
    }
  }
 
  return allLogs;
}
 
function isRangeTooLargeError(error: unknown): boolean {
  const message = error instanceof Error ? error.message : String(error);
  return (
    message.includes("Log response size exceeded") ||
    message.includes("query returned more than") ||
    message.includes("exceed maximum block range")
  );
}

typescript

// LE BUG : Ca a l'air inoffensif, ca ne l'est pas
function formatTokenAmount(amount: bigint, decimals: number): string {
  return (Number(amount) / Math.pow(10, decimals)).toFixed(4);
}
 
// Pour les petits montants ca fonctionne :
formatTokenAmount(1000000n, 6); // "1.0000" -- correct
 
// Pour les gros montants ca casse silencieusement :
formatTokenAmount(123456789012345678n, 18);
// Retourne "0.1235" -- FAUX, la precision est perdue
// Number(123456789012345678n) === 123456789012345680
// Les deux derniers chiffres ont ete arrondis par IEEE 754

typescript

import { formatUnits, parseUnits } from "viem";
 
// Correct : opere sur BigInt, retourne une chaine
function formatTokenAmount(amount: bigint, decimals: number, displayDecimals: number = 4): string {
  const formatted = formatUnits(amount, decimals);
 
  // formatUnits retourne la chaine en precision complete comme "0.123456789012345678"
  // Tronquer (pas arrondir) a la precision d'affichage desiree
  const [whole, fraction = ""] = formatted.split(".");
  const truncated = fraction.slice(0, displayDecimals).padEnd(displayDecimals, "0");
 
  return `${whole}.${truncated}`;
}
 
// Egalement crucial : utiliser parseUnits pour les saisies utilisateur, jamais parseFloat
function parseTokenInput(input: string, decimals: number): bigint {
  // parseUnits gere correctement la conversion chaine vers BigInt
  return parseUnits(input, decimals);
}

typescript

// Serialiseur de reponse API
function serializeForApi(data: Record<string, unknown>): string {
  return JSON.stringify(data, (_, value) => (typeof value === "bigint" ? value.toString() : value));
}

typescript

import { LRUCache } from "lru-cache";
 
const memoryCache = new LRUCache<string, unknown>({
  max: 10_000,
  ttl: 1000 * 60, // 1 minute par defaut
});
 
type CacheTier = "immutable" | "short" | "volatile";
 
const TTL_MAP: Record<CacheTier, number> = {
  immutable: 1000 * 60 * 60 * 24, // 24 heures en memoire, permanent dans Redis
  short: 1000 * 60 * 5, // 5 minutes
  volatile: 1000 * 15, // 15 secondes
};
 
async function cachedRpcCall<T>(key: string, tier: CacheTier, fetcher: () => Promise<T>): Promise<T> {
  // Verifier la memoire en premier
  const cached = memoryCache.get(key) as T | undefined;
  if (cached !== undefined) return cached;
 
  // Puis Redis (si vous en avez un)
  // const redisCached = await redis.get(key);
  // if (redisCached) { ... }
 
  const result = await fetcher();
  memoryCache.set(key, result, { ttl: TTL_MAP[tier] });
 
  return result;
}
 
// Utilisation :
const receipt = await cachedRpcCall(`receipt:${txHash}`, "immutable", () =>
  client.getTransactionReceipt({ hash: txHash }),
);

typescript

// Pas d'inference de type — args est unknown[], le retour est unknown
const result = await client.readContract({
  address: "0x...",
  abi: JSON.parse(abiString), // parse au runtime = pas d'info de type
  functionName: "balanceOf",
  args: ["0x..."],
});

typescript

// Definir l'ABI avec as const pour une inference de type complete
const erc20Abi = [
  {
    name: "balanceOf",
    type: "function",
    stateMutability: "view",
    inputs: [{ name: "account", type: "address" }],
    outputs: [{ name: "balance", type: "uint256" }],
  },
  {
    name: "transfer",
    type: "function",
    stateMutability: "nonpayable",
    inputs: [
      { name: "to", type: "address" },
      { name: "amount", type: "uint256" },
    ],
    outputs: [{ name: "success", type: "bool" }],
  },
] as const;
 
// Maintenant TypeScript sait :
// - functionName autocomplete vers "balanceOf" | "transfer"
// - args pour balanceOf est [address: `0x${string}`]
// - le type de retour pour balanceOf est bigint
const balance = await client.readContract({
  address: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
  abi: erc20Abi,
  functionName: "balanceOf",
  args: ["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"],
});
// typeof balance = bigint -- entierement type

Les donnees on-chain en production : ce que personne ne vous dit

L'illusion de donnees fiables

Les rate limits RPC vont ruiner votre week-end

Les reorgs : le bug que vous ne verrez pas venir

Le problème d'indexation : choisissez votre galere

Appels RPC directs

The Graph (subgraphs)

Indexeurs personnalises (Ponder, Envio)

getLogs est plus dangereux qu'il n'y parait

BigInt va vous remettre a votre place

Stratégie de cache : quoi, combien de temps, et quand invalider

TypeScript et les ABI de contrats : la bonne méthode

La vérité qui derange

Articles similaires

TypeScript Compiler API: Building Custom Linters, Codemods, and Type Analyzers

JSON to TypeScript Guide: Create Safer API Types From Real Payloads