Spending a tx with a low claim bid fails - edge case (rejected as dust) #186

New issue

Closed

opened 2018-08-05 22:40:05 +02:00 by tzarebczan · 3 comments

tzarebczan commented

2018-08-05 22:40:05 +02:00

(Migrated from github.com)

See example edge case here: https://github.com/lbryio/lbry/issues/768#issuecomment-367110131

brynet-cli claim_abandon --claim_id=182c6ef1e2c5d22c06eebe9f87baa63e37ed441f
ERROR: Abandon of 182c6ef1e2c5d22c06eebe9f87baa63e37ed441f/None:None failed: error: the transaction was rejected by network rules.

64: dust
[0100000001101a35dbc7c60426bdd20b1863d6eeec23db81ae446e9ba8386c06284f639279000000006b483045022100b8217b0664b2326609dbfb2081568fd21aacc702ece69bcd3727008df36c45530220509ac35b972ad25d854ed297483f23a8d1440362735d38a880e747c923927d87012103be327adddbf705c863115dfaad45f3dceab48bccf58406b74a33595695867d0affffffff0100000000000000001976a9141e6f4ffc9a0864297617fc879a04cfe579aea2a688ac00000000]

See example edge case here: https://github.com/lbryio/lbry/issues/768#issuecomment-367110131 brynet-cli claim_abandon --claim_id=182c6ef1e2c5d22c06eebe9f87baa63e37ed441f ERROR: Abandon of 182c6ef1e2c5d22c06eebe9f87baa63e37ed441f/None:None failed: error: the transaction was rejected by network rules. 64: dust [0100000001101a35dbc7c60426bdd20b1863d6eeec23db81ae446e9ba8386c06284f639279000000006b483045022100b8217b0664b2326609dbfb2081568fd21aacc702ece69bcd3727008df36c45530220509ac35b972ad25d854ed297483f23a8d1440362735d38a880e747c923927d87012103be327adddbf705c863115dfaad45f3dceab48bccf58406b74a33595695867d0affffffff0100000000000000001976a9141e6f4ffc9a0864297617fc879a04cfe579aea2a688ac00000000] Related: https://github.com/lbryio/lbrycrd/issues/97 https://github.com/lbryio/lbrycrd/issues/98

BrannonKing commented

2018-08-09 21:33:34 +02:00

(Migrated from github.com)

@bvbfan , can you see if your fixes for #97 return a different error code in this situation?

bvbfan commented

2018-08-10 18:01:42 +02:00

(Migrated from github.com)

It returns REJECT_NONSTANDARD (64), patch makes it REJECT_DUST (65)

lbrynaut commented

2019-03-20 18:27:39 +01:00

(Migrated from github.com)

The transaction created has no value being spent, which is correctly identified as below the threshold for dust. A solution is to create a transaction that sends a non-zero value.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#186

No description provided.