Make FirstEvent configurable to better support public chain with multi-party
#331
Labels
good first issue
Good for newcomers
Comments
Chengxuan
changed the title
FirstEvent configurableFirstEvent configurable to better support public chain with multi-party
EnriqueL8
added
bug
MKVEERENDRA
added a commit
to MKVEERENDRA/firefly-cli1
that referenced
this issue
Nov 17, 2024
MKVEERENDRA
added a commit
to MKVEERENDRA/firefly-cli1
that referenced
this issue
Nov 18, 2024
…Fly config Signed-off-by: MKVEERENDRA <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the discussion here: https://discord.com/channels/905194001349627914/1306104244486668369/1306929797296816200, Firefly-cli currently hard code the starting block of the Firefly batch pin contract event to
0to ensure no events could be missed. But this is impractical when using multi-party mode with a public chain:firefly-cli/internal/stacks/stack_manager.go
Line 988 in 14e7721
Workaround
The currently workaround is to update the firefly_core yaml generated manually to start indexing the events from a desired block number. (hint:
newestcan be used if you don't care about missing events which breaks integrity of indexed data)An enhancement would be making the FirstEvent configurable
The text was updated successfully, but these errors were encountered: