feature request: event driven removal of dynamic contracts (data sources)

[saurabhburade]

Summary

HyperIndex supports dynamically registering contracts via the contractRegister handler (e.g. context.add<ContractName>(address)), but there is no supported way to remove / unregister a previously registered dynamic contract (dynamic data source).

For long-running indexers, this makes it difficult to handle:

• contracts that are later disabled, paused, or delisted
• factory-created instances that emit a “removed” or “deactivated” event
• incorrect registrations due to bad emitted addresses or logic bugs
• keeping the indexing scope bounded over time

Expected behavior

• Provide a supported mechanism to explicitly remove / unregister a dynamic contract from within any event/block handler.

Acceptance criteria

• API to explicitly remove a dynamic contract, e.g.: context.remove<ContractName>(address) or equivalent.
• Calling the removal API inside an event/block handler immediately unregisters the contract.
• Existing indexed data is preserved; removal only affects future indexing.

[DZakh]

We have a planned feature to be able to set an endBlock for an address during registration like: context.add<ContractName>(address, {endBlock: xxx})

Will it solve your problem, or do you not know an end block during the contract registration?

[saurabhburade]

No it wont solve the problem.
Consider there is event of PoolRemoved, Delist or any such event should be able to do context.remove<ContractName>

This is optional though
context.add<ContractName>(address, {endBlock: xxx})

[DZakh]

Thanks, I see. We are going to refactor this part of the code next month, I'll see whether the feature can fit during the process.

[saurabhburade]

cool, sg