Timeout every offer

[NCKoeter]

I am getting timeouts when trying to buy BSQ oder XMR, no matter what I offer I try to take.
Seems like I cannot get a connection but am fully connected to the tornetwork and have 10 P2P Peers shwoing

Mai-27 02:29:02.672 [JavaFX Application Thread] INFO b.c.b.w.BtcWalletService: swap addressEntry with address 143RoETT2GgXZnz5iXWqjPhXiXb1stnSt4 and offerId umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111 from context OFFER_FUNDING to available
Mai-27 02:29:02.672 [JavaFX Application Thread] INFO b.c.t.TaskRunner: Run task: SellerAsTakerCreatesDepositTxInputs
Mai-27 02:29:02.674 [JavaFX Application Thread] INFO b.c.t.TaskRunner: Run task: TakerSendPayDepositRequest
Mai-27 02:29:02.677 [JavaFX Application Thread] INFO b.c.t.p.t.t.TakerSendPayDepositRequest: Send PayDepositRequest with offerId umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111 and uid 5fcb6335-f845-4889-8f22-a07fea4cd17c to peer a4hpujcffaldfhnb.onion:9999
Mai-27 02:29:02.698 [JavaFX Application Thread] INFO b.c.t.p.t.t.TakerSendPayDepositRequest: PayDepositRequest arrived at peer: offerId=umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111; uid=5fcb6335-f845-4889-8f22-a07fea4cd17c
Mai-27 02:29:03.881 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
Mai-27 02:29:03.882 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
Mai-27 02:29:08.414 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: request from provider http://5bmpx76qllutpcyp.onion/ 62.018 sec. after last request
Mai-27 02:29:09.859 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: Market price for currency BSQ is not provided by the provider http://ceaanhbvluug4we6.onion/. That is expected for currencies not listed at providers.
Mai-27 02:29:09.861 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=BSQ, price=1.7E-4, timestampSec=0, isExternallyProvidedPrice=false) from provider http://ceaanhbvluug4we6.onion/ after 1.447 sec.
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-5bdftu6jdresp3hg.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=5bdftu6jdresp3hg.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-77ti2cclpxy2ivkm.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=77ti2cclpxy2ivkm.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-gorgretxvlx6xgtk.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=gorgretxvlx6xgtk.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-zwgjca26w56krnip.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=zwgjca26w56krnip.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-dzb75lwxpwzaloim.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=dzb75lwxpwzaloim.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:24.062 [NetworkNode:SendMessage-to-mjr5j24tr6e462op.onion:9999] INFO b.n.p.n.NetworkNode: onFailure at sendMessage: peersNodeAddress=mjr5j24tr6e462op.onion:9999
message=GetPeersRequest
throwable=java.io.IOException: Cannot connect to hidden service
Mai-27 02:29:32.090 [JavaFX Application Thread] WARN b.c.d.m.n.StateNetworkService: requestDaoStateHashesHandler with outbound connection failed.
nodeAddress=s67qglwhkgkyvr74.onion:8000
ErrorMessage=A timeout occurred at sending getStateHashesRequest:GetStateHashesRequest{,
height=577928,
nonce=-1912326537
} NetworkEnvelope{
messageVersion=10
} on peersNodeAddress:s67qglwhkgkyvr74.onion:8000
Mai-27 02:29:32.090 [JavaFX Application Thread] WARN b.c.d.m.n.StateNetworkService: requestDaoStateHashesHandler with outbound connection failed.
nodeAddress=s67qglwhkgkyvr74.onion:8000
ErrorMessage=A timeout occurred at sending getStateHashesRequest:GetStateHashesRequest{,
height=571747,
nonce=346784000
} NetworkEnvelope{
messageVersion=10
} on peersNodeAddress:s67qglwhkgkyvr74.onion:8000
Mai-27 02:29:32.090 [JavaFX Application Thread] WARN b.c.d.m.n.StateNetworkService: requestDaoStateHashesHandler with outbound connection failed.
nodeAddress=s67qglwhkgkyvr74.onion:8000
ErrorMessage=A timeout occurred at sending getStateHashesRequest:GetStateHashesRequest{,
height=571747,
nonce=870309415
} NetworkEnvelope{
messageVersion=10
} on peersNodeAddress:s67qglwhkgkyvr74.onion:8000
Mai-27 02:30:03.864 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
Mai-27 02:30:03.864 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
Mai-27 02:30:11.420 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: request from provider http://5bmpx76qllutpcyp.onion/ 63.006 sec. after last request
Mai-27 02:30:16.748 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: Market price for currency BSQ is not provided by the provider http://ceaanhbvluug4we6.onion/. That is expected for currencies not listed at providers.
Mai-27 02:30:16.751 [JavaFX Application Thread] INFO b.c.p.p.PriceFeedService: Received new MarketPrice(currencyCode=BSQ, price=1.7E-4, timestampSec=0, isExternallyProvidedPrice=false) from provider http://ceaanhbvluug4we6.onion/ after 5.331 sec.
Mai-27 02:30:32.598 [JavaFX Application Thread] ERROR b.c.t.p.TradeProtocol: Timeout reached. TradeID=umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111, state=PREPARATION
Mai-27 02:30:32.652 [JavaFX Application Thread] WARN b.c.t.p.TradeProtocol: cleanupTradableOnFault tradeState=PREPARATION
Mai-27 02:30:32.654 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:30:32.654 [JavaFX Application Thread] INFO b.c.b.w.BtcWalletService: swap addressEntry with address 1NHVePx7cCohaZgKb8L6efragF44roPswE and offerId umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111 from context MULTI_SIG to available
Mai-27 02:30:32.655 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade djohdqdb-5ef9f9c7-9819-418c-89b7-692490ce6fe9-111
Mai-27 02:30:32.655 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 70464716-bf56b30a-87d2-4d83-8b3b-fda051e34002-111
Mai-27 02:30:32.655 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade wiXKP-ff938d72-b167-407e-9f0e-14cf7e547f82-111
Mai-27 02:30:32.655 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:30:32.656 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:30:35.731 [JavaFX Application Thread] INFO b.c.b.w.BtcWalletService: resetAddressEntriesForOpenOffer offerId=umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:30:35.731 [JavaFX Application Thread] INFO b.c.b.w.BtcWalletService: swap addressEntry with address 1AUgbtnhi6vgSccc2DzBT8n8wkrEqvPmef and offerId umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111 from context RESERVED_FOR_TRADE to available

Can anybody help?

[NCKoeter]

I also get this when buying BSQ:

Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade djohdqdb-5ef9f9c7-9819-418c-89b7-692490ce6fe9-111
Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 70464716-bf56b30a-87d2-4d83-8b3b-fda051e34002-111
Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade wiXKP-ff938d72-b167-407e-9f0e-14cf7e547f82-111
Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111
Mai-27 02:44:56.944 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade umkr1ay-2a1ed329-bb3d-4d95-b2a8-5c5403614f5b-111

[a123b]

I am the maker of one of the BSQ offers you tried to accept. When you took the offer, I got a popup that said something like “the offer was blocked because the taker is blacklisted”, here’s the relevant part of the log file:

ERROR b.c.t.Task: An error occurred at task: ApplyFilter
Other trader is banned by his node address.
tradingPeerNodeAddress=<your onion address>

I also found your onion address in the thread about the recent SEPA chargeback scams:

URGENT: Certain banks banned until further notice

Please help us stop the stolen bank account scammer and limit damage to victims of stolen bank accounts! If you have any Fiat trade currently open and the BTC buyer has an account age of less than 14 days, please open a dispute with cmd+o (or ctrl+o). You can see the account age and also the onion address when you roll over the avatar icon or click on it. [54] We blocked all reported onion addresses and bank accounts but it seems he continued with fresh accounts, and we needed to extend the…

So if you are not a scammer, you probably got blacklisted by mistake because your trading behaviour was similar to that of the scammer(s).

Whether or not you actually are a scammer, I find it pretty strange that the peers that got blacklisted for FIAT chargeback risk are also blocked from trading altcoins, as there is no chargeback risk there…

[NCKoeter]

Thanks for that response!

I don’t understand why I am blacklisted though. I only had two transactions with bisq and both were successful. Arbitrator even had one of my transactions blocked for over 2 weeks because it was during that scamming time but in the end it got released anyway, because I am not scamming.

So why would I be blacklisted?
@ManfredKarrer @keo @arbitrator1 @Arbitrator2

[alexej996]

Try deleting outdated tor files in Settings. It might help with the connection issues.

[NCKoeter]

I already resynced full SPV, but if the maker gets the message that I am banned, it seems to be clearly because of that reason doesn’t it?

[alexej996]

If you are blacklisted then yes.
Is your fiat account blacklisted or just your onion address?

[a123b]

It must be his onion address that is blacklisted, the trade he tried to accept from me was an altcoin (BSQ) trade.

[ManfredKarrer]

@a123b

I find it pretty strange that the peers that got blacklisted for FIAT chargeback risk are also blocked from trading altcoins, as there is no chargeback risk there…

Chargeback scam is serious crime. Blocking those from all Bisq activities is the least we can do.

[ManfredKarrer]

@NCKoeter

So why would I be blacklisted?

Please PM me your onion address. Might have been a false positive.

[a123b]

@ManfredKarrer

Chargeback scam is serious crime. Blocking those from all Bisq activities is the least we can do.

Oh, if they are proven criminals it’s perfectly fine to ban them from using Bisq altogether, of course! But looking at the thread I linked, it seems like this was only the case for one (or two) of the blacklisted peers. It was even admitted that some the other peers might be false positives. Banning even altcoin trading based on a suspicion seems a bit harsh…

Also, wouldn’t it be a good idea to tell the suspicious users that they are banned within the app instead of “shadowbanning” them, so that they have a chance to reach out to the arbitrators and prove that whatever they did was legitimate? If I hadn’t checked the forums and told the OP that he was banned, it might have taken a while for the mods/helpers to figure out that this was the reason for the timeouts…

[alexej996]

It would be optimal if we had some kind of a more decentralized and yet quick way to ban peers.

Perhaps a new trading protocol with BSQ bonding would help.

[ManfredKarrer]

It is the first time that we had such a situation and as it was pretty severe we preferred to be rather restrictive and risk false positives rather to let the scammer(s) loopholes…
It can be assumed that a honest user who cannot trade anymore will reach out and then we can resolve it. To handle it more graceful would require more dev efforts and it is better to leave scammers in the dark rather to tell them that they are banned.

[Homard]

@ManfredKarrer

To handle it more graceful would require more dev efforts and it is better to leave scammers in the dark rather to tell them that they are banned.

The problem is that leaving scammers in the dark implies also leaving many other, and honest users in the dark.
… so I’m not so sure about the final balance.
If one thing, I think a hashed banlist of banned IBANs (which will be a short list) could help a lot.

[ManfredKarrer]

@Homard

many other, and honest users in the dark.

There should not be many others.