Documentation / @etherfold/core / openReceivingIndexer

Function: openReceivingIndexer()

openReceivingIndexer<ABI, ProcessResultType, State>(options): Promise<ReceivingIndexer<ABI, ProcessResultType, State>>

Defined in: packages/core/src/receivingContainer.ts:768

Open the container: the registry (and its sweep), then the fold this host was built with, then the receiver wired to both.

The generation is REGISTERED here rather than on the first batch, so a cap REFUSES at start-up -- where an operator reads it, naming what could be deleted -- instead of on somebody's ingest. Nothing is written for a refused generation, and nothing partial survives one: openGenerationRegistry.create decides inside the substrate's own transaction, and the state factories this runtime uses create no storage until the first write.

A SECOND fold is added afterwards, through add, because that is when it exists: a successor is created while the incumbent is running.

Type Parameters

ABI

ABI extends Abi

ProcessResultType

ProcessResultType = unknown

State

State = unknown

Parameters

options

ReceivingIndexerOptions<ABI, ProcessResultType, State>

Returns

Promise<ReceivingIndexer<ABI, ProcessResultType, State>>