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
Chore - Update Bridge to support deposit validation for create_deposit
1. Description
Update the Bridge to support the new deposit validation requirements in the API as outlined in #1116 and implemented in PR #1197. Specifically, the Bridge must retrieve the full Bitcoin transaction as a hex-encoded string using OpenNode or Mempool APIs and include it in the transaction_hex field when calling the create_deposit endpoint.
Note that, once this is implemented, the Emily API will not return the right amount value from the create_deposit response.
2. Why It's Necessary
The updated API now requires a transaction_hex field to validate deposit requests, ensuring that only the depositor can inform the system of their deposits. Without this update to the Bridge, it will not comply with the new API requirements and deposit requests will fail.
3. Execution Checklist
Integrate OpenNode or Mempool API to retrieve the hex-encoded Bitcoin transaction.
Update the Bridge to include the transaction_hex field in requests to the create_deposit endpoint.
Test the implementation to ensure deposit requests are properly validated and accepted by the updated API.
The text was updated successfully, but these errors were encountered:
Chore - Update Bridge to support deposit validation for
create_deposit
1. Description
Update the Bridge to support the new deposit validation requirements in the API as outlined in #1116 and implemented in PR #1197. Specifically, the Bridge must retrieve the full Bitcoin transaction as a hex-encoded string using OpenNode or Mempool APIs and include it in the
transaction_hex
field when calling thecreate_deposit
endpoint.Note that, once this is implemented, the Emily API will not return the right
amount
value from the create_deposit response.2. Why It's Necessary
The updated API now requires a
transaction_hex
field to validate deposit requests, ensuring that only the depositor can inform the system of their deposits. Without this update to the Bridge, it will not comply with the new API requirements and deposit requests will fail.3. Execution Checklist
transaction_hex
field in requests to thecreate_deposit
endpoint.The text was updated successfully, but these errors were encountered: