Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State Change Indexer: State Change Processors part 2 #134

Open
gouthamp-stellar opened this issue Feb 19, 2025 · 0 comments
Open

State Change Indexer: State Change Processors part 2 #134

gouthamp-stellar opened this issue Feb 19, 2025 · 0 comments
Assignees

Comments

@gouthamp-stellar
Copy link
Contributor

Implement Processors for 4 state changes:
Each processor will:

Extract relevant information from TokenTransferEvents or Operations.
Check if the associated accounts are relevant using relevantAcctService.
If relevant, update the in-memory maps (stateChangeMap, operationsMap, transactionMap).
Type-Specific Validation:
To ensure that each processor only handles the appropriate inputs, each processor should validate the input type before processing.
For example, a processor handling SetOptions operations should ignore Payment operations.

By defining a global list of processors, every TokenTransferEvent and Operation can be passed through each processor in the list. This would make adding new state change types easier - implement a new implementation of the interface and add it to the global list of processors

design: https://docs.google.com/document/d/10Z2Apl6gJYkJp0BXILWn5_vJL4MmZ0QZ4QrRqbW_EHw/edit?tab=t.0

@gouthamp-stellar gouthamp-stellar changed the title State Change Indexer: Processors part 2 State Change Indexer: State Change Processors part 2 Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants