Update documentation

Author: Ferossgp

apps/docs/src/content/components/effect-abi-store-interface.md

@@ -1,8 +1,23 @@
 ```ts
 export interface AbiStore {
+  /**
+   * Set of resolver strategies grouped by chain id and a `default` bucket.
+   */
   readonly strategies: Record<ChainOrDefault, readonly ContractAbiResolverStrategy[]>
-  readonly set: (key: AbiParams, value: ContractAbiResult) => Effect.Effect<void, never>
+  /**
+   * Persist a resolved ABI or a terminal state for a lookup key.
+   */
+  readonly set: (key: AbiParams, value: CacheContractABIParam) => Effect.Effect<void, never>
+  /**
+   * Fetch all cached ABIs for the lookup key. Implementations may return multiple entries.
+   */
   readonly get: (arg: AbiParams) => Effect.Effect<ContractAbiResult, never>
+  /** Optional batched variant of `get` for performance. */
   readonly getMany?: (arg: Array<AbiParams>) => Effect.Effect<Array<ContractAbiResult>, never>
+  /** Optional helper for marking an existing cached ABI as invalid or changing its status. */
+  readonly updateStatus?: (
+    id: string | number,
+    status: 'success' | 'invalid' | 'not-found',
+  ) => Effect.Effect<void, never>
 }
 ```

apps/docs/src/content/components/vanilla-abi-store-interface.md

@@ -2,6 +2,6 @@
 export interface VanillaAbiStore {
   strategies?: readonly ContractAbiResolverStrategy[]
   get: (key: AbiParams) => Promise<ContractAbiResult>
-  set: (key: AbiParams, val: ContractAbiResult) => Promise<void>
+  set: (key: AbiParams, val: ContractABI) => Promise<void>
 }
 ```

apps/docs/src/content/docs/reference/data-loaders.mdx

@@ -10,10 +10,11 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'
 Data Loaders are mechanisms for retrieving the necessary ABI and Contract Metadata for transaction decoding. They are responsible for:
 
 - Resolving ABIs and Contract Metadata using specified strategies and third-party APIs
-- Automatically batching requests when processing logs and traces in parallel
-- Caching request results in the [Data Store](/reference/data-store)
+- Automatically batching requests and deduplicating identical lookups during parallel log/trace processing
+- Caching results and negative lookups in the [Data Store](/reference/data-store)
+- Applying rate limits, circuit breaking, and adaptive concurrency via a shared request pool
 
-Loop Decoder implements optimizations to minimize API requests to third-party services. For example, when a contract’s ABI is resolved via Etherscan, it is cached in the store. If the ABI is requested again, the store provides the cached version, avoiding redundant API calls.
+Loop Decoder implements optimizations to minimize API requests to third-party services. For example, when a contract’s ABI is resolved via Etherscan, it is cached in the store. If the ABI is requested again, the store provides the cached version, avoiding redundant API calls. When a source returns no result, a `not-found` entry can be stored to skip repeated attempts temporarily.
 
 ## ABI Strategies
 

apps/docs/src/content/docs/reference/data-store.mdx

@@ -67,7 +67,7 @@ The full interface of ABI store is:
 
 <EffectABI />
 
-ABI Store Interface requires 2 methods: `set` and `get` to store and retrieve the ABI of a contract. Optionally, you can provide a batch get method `getMany` for further optimization. Because our API supports ABI fragments, the get method will receive both the contract address and the fragment signature.
+ABI Store Interface requires `set` and `get` to store and retrieve ABIs. Optionally, you can provide a batch get method `getMany` and an `updateStatus` helper used by the decoder to mark ABIs invalid after failed decode attempts. Because our API supports ABI fragments, the get method will receive both the contract address and the fragment signature.
 
 ```typescript
 interface AbiParams {

apps/docs/src/content/docs/welcome/overview.md

@@ -26,7 +26,7 @@ The Transaction Decoder package transforms raw transactions, including calldata,
 
 See the Decoded Transaction section in our [playground](https://loop-decoder-web.vercel.app/) for transaction examples.
 
-The minimal configuration for the Transaction Decoder requires an RPC URL, ABIs, and contract metadata stores, which can be in-memory (see the [Data Store](/reference/data-store/) section). We also provide data loaders for popular APIs like Etherscan (see the full list in the [ABI Strategies](/reference/data-loaders/) section). These loaders request contract metadata and cache it in your specified store. The decoder supports RPCs with both Debug (Geth tracers) and Trace (OpenEthereum/Parity and Erigon tracers) APIs.
+The minimal configuration for the Transaction Decoder requires an RPC URL, ABIs, and contract metadata stores, which can be in-memory (see the [Data Store](/reference/data-store/) section). We also provide data loaders for popular APIs like Etherscan (see the full list in the [ABI Strategies](/reference/data-loaders/) section). These loaders fetch ABIs/metadata, cache results and negative lookups in your store, and avoid querying sources previously marked invalid for a key. The decoder supports RPCs with both Debug (Geth tracers) and Trace (OpenEthereum/Parity and Erigon tracers) APIs.
 
 ### Transaction Interpreter