Open droplister opened 1 month ago
I haven't tried this again yet, still kind of unsure if it will work given: https://api.counterparty.io:4000/v2/transactions/40e4889c01964003910ecf2babf7176c63464dfe17454e935b7a4d11068b62b5?verbose=true
{
"result": {
"tx_index": 2761821,
"tx_hash": "40e4889c01964003910ecf2babf7176c63464dfe17454e935b7a4d11068b62b5",
"block_index": 866028,
"block_hash": "0000000000000000000308da68d79bbfb45f22e034135919c1ee5230dba786d8",
"block_time": 1729153325,
"source": "1NVdWvtup9zWijkhJ75rn5Hir8psq2g8tb",
"destination": null,
"btc_amount": 0,
"fee": 3000,
"data": "0400768fa6065c85c3cb2f7a30095c4677597120d2a403",
"supported": true,
"utxos_info": "",
"confirmed": true,
"unpacked_data": {
"message_type": "sweep",
"message_type_id": 4,
"message_data": {
"destination": "1BotpWeW4cWRZ26rLvBCRHTeWtaH5fUYPX",
"flags": 3,
"memo": null
}
},
"btc_amount_normalized": "0.00000000"
}
}
But no assets owned were swept: https://api.counterparty.io:4000/v2/addresses/1NVdWvtup9zWijkhJ75rn5Hir8psq2g8tb/assets/owned
And there's no sweep: https://api.counterparty.io:4000/v2/addresses/1NVdWvtup9zWijkhJ75rn5Hir8psq2g8tb/sweeps
My guess is maybe what happened is I tried to compose sweeps on all of my addresses in order to get the error message to tell me how much XCP it would cost. But once I funded the addresses with XCP, then XCP became +1 balance and now I actually needed more XCP so these are failing for under funding.
This is likely unrelated to the recent changes, I think?
I tried to consolidate the assets I own from 80 address to one address.
I funded each address with BTC to make a tx: https://mempool.space/tx/0634cad0ba483faaea66e23851a145653078fbe834fcd155ad489ea4dbbc1a30
I funded each address with XCP to pay gas (exact amount based on compose error that told me XCP needed): https://mempool.space/tx/455090ed252b1502ece9ea9a87e4ea828f0f18097a0acc1c92c2a5da9c02d9c3 https://explorer.unspendablelabs.com/tx/455090ed252b1502ece9ea9a87e4ea828f0f18097a0acc1c92c2a5da9c02d9c3
And then I created a sweep tx for each address.
It looks like only three of those sweeps were successful:
Here's are some unsuccessful examples...
What's odd about it is that on the transaction endpoint it looks like Counterparty understood it was a sweep. But there is no sweep and it looks like the XCP was not consumed.
16E5DrY5Lhu5d35i55T3PGr6j54sGNaMm6 https://api.counterparty.io:4000/v2/transactions/b198231751c2013aa22123a0c9a273cb72017d7f58c882bd0159a4deb9bb958f?verbose=true
https://api.counterparty.io:4000/v2/addresses/16E5DrY5Lhu5d35i55T3PGr6j54sGNaMm6/sweeps
1C7Fityk7q8j4cF1MRFXnvoqQGvWMrf4og https://api.counterparty.io:4000/v2/transactions/1672737eab0a55b2fc8ae960a77bf417c751757b6dfb663e5f42795d3648f30a?verbose=true
https://api.counterparty.io:4000/v2/addresses/1C7Fityk7q8j4cF1MRFXnvoqQGvWMrf4og/sweeps
Before I reload these addresses with more BTC to try again is there something I did wrong or did I "overload" Counterparty? My other guess is that Counterparty didnt think I had enough XCP balance to pay the gas, but I funded these addresses with exactly how much the compose error said was needed and the subsequent compose attempt worked. And three of the 80 were successful of the batch all made programmatically in the same way.