search

OpenBazaar / OpenBazaar-Server

(Deprecated) OpenBazaar 1.0 Server daemon for communication with OpenBazaar-Client
MIT License
608 stars 173 forks source link

Error prevents releasing funds #433

Open clehner opened 8 years ago

clehner commented 8 years ago

I have a transaction as a buyer where a dispute was closed in my favor. When I click "Accept Dispute Payout" in OpenBazaar-Client, I get an error dialog "Data could not be saved. P2SH inner scriptPubKey returned false". This is the same error I got in #347 but in a different place. Opening the web inspector shows the request made to /api/v1/release_funds returning the error. The server console does not show any stack trace.

The order was funded by two transactions (since the exchange rate appeared to change immediately after I sent the first payment) so maybe this is a similar issue to #347 where some parties did not detect all the payments and so are signing different transactions.

OpenBazaar-Server@9e34976c256df985bb6f2d7cc38c602b96281740 OpenBazaar-Client@84f33a2b4d1ec67f6c0879d5c18602f5f16b8400 Debian testing amd64

cc @cpacia

clehner commented 8 years ago

Good news: I got the payment released by switching the order of the two outpoints, similar to what @cpacia suggested with the earlier issue.

for reference:

sqlite3 OB-Mainnet.db
select outpoint from purchases where id = '...';
# copy and edit the outpoint array
update purchases set outpoint = '...' where id = '...';

The order that worked was not the order of the transactions' timestamps, but the order of their vout property in the outpoint object (ascending).

I'll leave this issue open for now since the problem that caused it seems to still be present.