Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Submit new isomorphic transactions (rbf_btc_tx + rgbpp_ckb_tx_virtual) to RGB++ CKB Transaction Queue #230

Open
Flouse opened this issue Jun 13, 2024 · 0 comments
Labels
enhancement New feature or request P-Low

Comments

@Flouse
Copy link
Contributor

Flouse commented Jun 13, 2024

Discussion

Let's say BTC TX_1 has an isomophic rgbpp_ckb_tx_virtual. And there is a job of TX_1 in the assets-api's RGB++ CKB transaction Queue, called TX_1's job.

How to automatically add TX_2's job to the RGB++ CKB transaction Queue when TX_1 is replaced by TX_2?

  1. Monitor Bitcoin Mempool, and detect TX_1 Replacement
    Continuously monitor the Bitcoin mempool for any new transactions that spend one of the inputs of TX_1.
    When a new transaction (TX_2) spending inputs from TX_1 is detected, identify if TX_2 is a replacement for TX_1 based on criteria like higher fee rate, same inputs, etc.
  1. Verify TX_2 Validity
    Verify that TX_2 is a valid RGB++ transaction by checking if it contains the right RGB++ commitment.

  2. Add TX_2's Job to Queue
    Add a new job for TX_2 to the RGB++ CKB transaction Queue, including the TX_2_txid and the related rgbpp_ckb_tx_virtual, a.k.a TX_1's rgbpp_ckb_tx_virtual.

Why this feature is required?

Sometimes the RBF BTC transaction is submitted by other BTC RBF service providers, not through rgbpp-sdk. in this case, the TX_2's job may not be processed.

This process ensures that when TX_1 is replaced by TX_2 on the Bitcoin network, the RGB++ CKB transaction Queue is automatically updated with the new job for TX_2, allowing for seamless processing of the BTC RBF workflow.

Priority: Low

Originally posted by @Flouse in #82 (comment)

References

@Flouse Flouse added the enhancement New feature or request label Jun 13, 2024
@Flouse Flouse added the P-Low label Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P-Low
Projects
None yet
Development

No branches or pull requests

1 participant