Feature Request: Toggle Participant Tracking in Contract Arguments and Footprint #258
Description
What problem does your feature solve?
When identifying participants in contract operations, we decided to not index+ingest participants that were presented in:
- arguments (from invoke contract and constructors)
- Footprints (restore or extendTTL)
This decision was made to reduce noise, as tracking these fields can often surface irrelevant or spam-like data. However, in some use cases — such as when a user receives an NFT — it’s useful to track participants from these fields.
What would you like to see?
Allow hosts to enable or disable participant tracking in contract arguments and footprints via an environment variable. This flexibility would let each host choose what’s best for their context, since there’s no universally correct behavior.
📓 Implementation Note
To reintroduce this tracking, one could revert the following commits from PR #238: