-
Notifications
You must be signed in to change notification settings - Fork 18
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
When using :testnet network the app crashes after trying to store block 542 #2
Comments
It's due to unfinished script engine. I haven't touched the project in a while so I don't remember how far it was syncing on testnet (it's full of edge cases, which is nice). I plan to get back to it soon to try to implement segwit, so I'll make sure to keep info about sync progress in the README. If you are not using libsecp256k1, then definitely try with it. Although if all tests are passing then it's "just" another script bug that needs to be fixed. Script compatibility is crucial and very hard. I'm too busy to currently dive into this issue right away, sorry. If you feel like poking around then I'm happy to answer any questions. If not I'll update the ticket when I get back to the project. |
Okay - the issue was in the Interperter.ex file here: https://github.com/comboy/bitcoin-elixir/blob/develop/lib/bitcoin/script/interpreter.ex#L169
|
Wow, great job! Sorry about the late answer. I'll definitely dive back a bit into the project this week. Yeah, I couldn't decide between Keyword and Map. I settled on Map eventually because function matching works with it unlike Keyword. Check this setting: https://github.com/comboy/bitcoin-elixir/blob/develop/config/dev.exs#L7 When you run test node in dev env, and this is set to If you feel like diving into script I mostly used bitcoin wiki, there is now newer developer guide but I still trust wiki more. Awesome that you've spent time on finding that. |
I have the following issue when trying to start the node using
:testnet
networkWas trying to debug this but I'm afraid my bitcoin foo is still to low to tackle this issue. Any help would be much appreciated.
The app is configured to use postgres as a Storage
The text was updated successfully, but these errors were encountered: