indexer agent & cli - max lifetime options #343
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Currently, agent uses maximum allocations provided by the network, which is 28 epoches on the mainnet. Some indexers might want the agent to renew the allocations more frequently
Updates
allocationLifetimeallocationLifetime, globalallocationLifetime, and then network max epoch. Agent allows you to set lifetimes higher than network maximum so be careful with itFuture considerations
closeAndAllocatedoesn't account for rewards as the transaction are instant