Add support for Bitstamp crypto transactions #1863
Comments
yabirgb
added
Exchange Addition Request
LefterisJP
added a commit
to LefterisJP/rotkehlchen
that referenced
this issue
Dec 12, 2023
Fix rotki#1863 Achieve that by querying an extra endpoint for bitstamp deposit/withdrawals. The crypto_transactions. Unfortunately we need to query both user_transactions and crypto_transactions for the full picture. The first tells us the fees and the second tells us the address and tx_id. After querying them, correlating them by matching them via timestamp, type, asset is also done.
LefterisJP
added a commit
to LefterisJP/rotkehlchen
that referenced
this issue
Dec 13, 2023
Fix rotki#1863 Achieve that by querying an extra endpoint for bitstamp deposit/withdrawals. The crypto_transactions. Unfortunately we need to query both user_transactions and crypto_transactions for the full picture. The first tells us the fees and the second tells us the address and tx_id. After querying them, correlating them by matching them via timestamp, type, asset is also done.
LefterisJP
added a commit
that referenced
this issue
Dec 13, 2023
Fix #1863 Achieve that by querying an extra endpoint for bitstamp deposit/withdrawals. The crypto_transactions. Unfortunately we need to query both user_transactions and crypto_transactions for the full picture. The first tells us the fees and the second tells us the address and tx_id. After querying them, correlating them by matching them via timestamp, type, asset is also done.
|
Should be fixed by #7096 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per Bitstamp API v2 documentation, the JSON returned by the user transactions endpoint does not include any chain-related data (e.g. txid, address). This data is obtained by requesting the crypto transactions endpoint.
Be aware the crypto transactions endpoint is not paginated like the user transactions one (e.g. it has no
since_id).Related #1856 and more specifically: #1856 (comment)
The text was updated successfully, but these errors were encountered: