You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we do not support the withdrawals finalization - I need to investigate why the wrong redemption key is built based on the parameters from the submitRedemptionProof call.
We must figure out what's wrong and fully support it in the Acre subgraph.
Once solved, we need to remove the Threshold subgraph reference in SDK.
The text was updated successfully, but these errors were encountered:
This PR adds support for indexing the withdrawals in Acre. Here we
subscribe to the `RedemptionRequested` event from the tBTC Bridge
contract. Because we are listening to events from tBTC bridge not from
`BitcoinRedeemer` we must make sure the withdrawal comes from the Acre
network (the Acre subgraph should index only Acre withdrawals). Also,
t's possible to create 2 redemptions with the same redemption key in
tBTC v2 network (once the previous ones are finalized- meaning only one
pending redemption with the same key can exist). In that case we must
add a suffix to the `Withdraw` id - we count redemptions with the same
redemption key in `RedemptionKeyCounter` entity.
Currently, we do not support the withdrawals finalization - I need to
investigate why the wrong redemption key is built based on the
parameters from the `submitRedemptionProof` call.
This will be handled in #562Closes: #276Closes: #268
As mentioned in #513:
We must figure out what's wrong and fully support it in the Acre subgraph.
Once solved, we need to remove the Threshold subgraph reference in SDK.
The text was updated successfully, but these errors were encountered: