Manfred_Karrer[m it seems that guy did just make trades for spam sake -.- will have my funds locked for a week
chek2fire has quit
riclas: i am sorry but we cannot do much atm. he will lose his sec. deposit of 0.03 btc in such a case. as said that will be delegated to the maker in future. so if u want better security against such, u will set a high deposit. fo course the hgiher the deposit the higher the burden, so people need to find the right balnace themself
riclas: if it was sepa and day 6 has passed u can open a dispute. he will prob not be able to pay in the last day a sepa often taeks 2-3 days.
i will add also something the the buyer need to pay before hte half of the period
or maybe even earlier. the long period is just bc banks sleep over long weekends, but he can start payment fast anyway.
riclas: feel free to make a suggestion at the forum how u would handle that. i will try to get that into the next version. there is differnece if buyer is maker or taker. if taker he shoudl be able to start payment directly after block confirm. if buyer is maker we need to give more time as he might not be at the computer then it got taken. it should be not too complicate as well. so i would suggest the buyer has
1 day and seller can open dispute of buyer does not signal payment in that period. of course he can lie but then its normal dispute case...
yeah i'm just alerting to this case
he did 3 trades with me
losing 0.09 lol
i think leaving 3 days for payment + 4 to receive is fine. because maybe you need to go to the bank and have a weekend ahead
i'm not sure about what maker setting the deposit solves... even in cases of hacking, it's not that risky. so you would be just making it harder for regular users to make trades, maybe.
btw we should have spanish and portuguese + portuguese brasil done soon. i've done a push on some forums and got some translators on
DiCE1904 joined the channel
riclas has quit
NOTICE: [13bitsquare] 15ManfredKarrer pushed 2 new commits to 06BSQ: 02https://git.io/vSW6E
riclas: Manfred_Karrer: @ bitcoin.de you have 1 hour to make the payment. 1 day should be more than enough for SEPA maybe 3 for cash deposit (weekend, holidays)
Thinking about it, I realized that if you put up an offer to buy you might be not at the machine running Bitsquare. You should have at least a day to start a payment. Maybe there should be different time frames for offerers and takers.
aielima joined the channel
riclas joined the channel
pro joined the channel
yes, i think i make it 1 day for both (maker/taker). otherwise it gets too complicate for users
aielima has quit
that sounds good enough
i was only worried if the buyer needs to go to the bank to make the transfer
but then a dispute will explain that
same for any delay over 3 days
sepa is usually 1/2 days, not 2/3
i'll write up a post in the forum in the afternoon
depends on countr austria take 2-3 days
i receive from austrians all the time in 1 day
btw the guy that created the trades with me is online
he has 2 sell offers open
can i open dispute on one asking if he intends to pay?
NOTICE: [13bitsquare] 15riclas opened pull request #793: full spanish translation from transifex (06DAO...06patch-3) 02https://git.io/vSWxL
maybe it is just my bank... austrian banks have usually free accounts, so they keep your money longer to make their profit...
riclas: how long is the trade open?
NOTICE: [13bitsquare] 15ManfredKarrer closed pull request #793: full spanish translation from transifex (06DAO...06patch-3) 02https://git.io/vSWxL
NOTICE: [13bitsquare] 15ManfredKarrer pushed 2 new commits to 06DAO: 02https://git.io/vSWp5
NOTICE: 13bitsquare/06DAO 14cef00d2 15riclas: full spanish translation from transifex
lets wait 1 day longer. it is stated sowmehere that he need to pay until the half (4 days) is
as said we will improve that btu we cannot break current rules.
ok i guess i wait until monday and we talk again
yes, u can open at day 4. that is ok
this sucks though, i could have made much more profit than the 0.09 of the security, and he gets the opportunity to buy now that the price has risen for a huge discount, or to accept the dispute if the price had dropped.
NOTICE: [13bitsquare] 15ManfredKarrer pushed 1 new commit to 06DAO: 02https://git.io/vSWhH
NOTICE: [13bitsquare] 15ManfredKarrer pushed 1 new commit to 06DAO: 02https://git.io/vSlId
NOTICE: 13bitsquare/06DAO 14e96e408 15Manfred Karrer: Fix incorrect handling of logical and/or. Rename rpc optionkeys. Use lombok in BSQ tx value objcts. Use map with txId, index tuple instead of nested map for utxo. Rename BSQ Tx classes. Fix BSQ parsing algo. Add and improve tests.
NOTICE: [13bitsquare] 15ManfredKarrer pushed 1 new commit to 06DAO: 02https://git.io/vSltY
NOTICE: 13bitsquare/06DAO 14db966ca 15Manfred Karrer: Add missing dependency to pom. Map callbacks to userthread
NOTICE: [13bitsquare] 15ManfredKarrer 04deleted 06BSQ at 143f48aaf: 02https://git.io/vSltO