feat(intent factory): extend types with if substatus values and deposit#514
Open
feat(intent factory): extend types with if substatus values and deposit#514
Conversation
Signed-off-by: georgi <georgi@li.finance>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://linear.app/lifi-linear/issue/CORE-203/extend-lifitypes-with-if-substatus-values-and-deposit-address-status
Summary
INTENT_-prefixed SubstatusPending values for Intent Factory execution stages.depositAddressfield toGetStatusRequestfor SCA-based status polling before a deposit tx is confirmed on-chainContext
The Intent Factory integration in
lifi-backendmaps 11 IF FSM states to LiFi statuses. Currently, 5 distinct pending states collapse into the genericWAIT_DESTINATION_TRANSACTIONsubstatus, making it impossible for the widget to distinguish between "waiting for funds", "executing", and "retrying after failure". The new typed values let the widget show granular execution progress.The depositAddress field enables a new status query path where the widget polls by SCA deposit address + fromChain instead of txHash, which is needed before the user's deposit transaction lands on-chain.