Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doublespend.py looking for outpoint, which is not on the JSON output #8

Open
0KaL opened this issue Jan 14, 2017 · 1 comment
Open

Comments

@0KaL
Copy link

0KaL commented Jan 14, 2017

I'm trying to play with "Replace by fee" but the exploit code seems to be looking for an "outpoint" entry that does not exist on the RPC output, as showed on the picture below:

https://pbs.twimg.com/media/C2BeuQQXcAAum78.jpg:large

Is there some setting or some way to gather that outpoint in the script code?

Thanks in advance!

@jesobreira
Copy link

This is weird. Note that the outpoint does not come from the RPC itself. Rather, it's added to the return by the Python lib, by this code:

unspent['outpoint'] = COutPoint(lx(unspent['txid']), unspent['vout'])

Anyway, I see that your bitcoin-cli listunspent output lists only 1 transaction, so I guess it's some problem about the list itself. Would you please me by sending a second transaction and testing it again?

Oh, and the amount you're trying is too low... It might bring problems as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants