Open Larision opened 1 year ago
This is truly strange, the id
and orderId
should be the same.
These are just regular trades?
This is truly strange, the
id
andorderId
should be the same.
Can you elaborate on this? Curious why they should be the same. In any case since these are not transactions that need the resolver (they are a sale and a fee related to conversions), how about the following ideas:
f"{id}_{orderId}"
as the unique id for the sale,f"{id}_{orderId}/fee"
as the unique id for the fee (to defensively distinguish it from the sale, if needed).Would this work?
Can you elaborate on this? Curious why they should be the same.
Sorry, I misread the CCXT codebase. They shouldn't be the same actually.
I think this change will disambiguate the ids and it make it safe for all the other exchanges as well.
# Users can use other crypto assets to pay for trades
if fee_asset != out_asset and RP2Decimal(transaction_fee) > ZERO:
out_transaction_list.append(
OutTransaction(
plugin=self.plugin_name(),
unique_id=f"{transaction[_ID]}/fee",
will work with this /fee addition in abstract_ccxt_input_plugin??
@Larision I think @eprbell 's suggestion should fix this issue if you want to implement that.
@macanudo527 @eprbell Srry but not easy to me. Where shoud i fix it?
i suppose is a binance issue, @macanudo527 maybe if same uniqueID and different asset pair, check orderid? as you mencioned in #157 ??