You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when looking at the BTC/RAREPEPE BTCpay pair on Freewallet a strange issue is showing up
when viewing the orders for BTC/RAREPEPE in FW the UI is showing:
where the seller of the rarepepe apparently shows they are selling "0.99999998" RAREPEPE, which can't happen because the card is not divisible
when viewing it from the opposite pairing RAREPEPE/BTC:
The RAREPEPE is now not fractionalized and is shown as a whole token.
Furthermore, when browsing xchain and FW, finding the tx info for both of the orders shown in the pair is not very user friendly, and without knowing the address for the buy order put in to BUY the rarepepe with btc, I cannot find the tx for the order....
as for the strange 'fractional, but not showing as fractional on the opposite pair' tx it is here:
when looking at the BTC/RAREPEPE BTCpay pair on Freewallet a strange issue is showing up
when viewing the orders for BTC/RAREPEPE in FW the UI is showing:
where the seller of the rarepepe apparently shows they are selling "0.99999998" RAREPEPE, which can't happen because the card is not divisible
when viewing it from the opposite pairing RAREPEPE/BTC:
The RAREPEPE is now not fractionalized and is shown as a whole token.
Furthermore, when browsing xchain and FW, finding the tx info for both of the orders shown in the pair is not very user friendly, and without knowing the address for the buy order put in to BUY the rarepepe with btc, I cannot find the tx for the order....
as for the strange 'fractional, but not showing as fractional on the opposite pair' tx it is here:
https://xchain.io/tx/2712881
and it could only be found by clicking the lowest listing for it on https://pepe.wtf/asset/RAREPEPE
I wasn't able to find the tx for the other order which is shown here on the RAREPEPE/BTC pair:
The text was updated successfully, but these errors were encountered: