https://pastebin.com/kdQPkELNif anyone can see why i am getting a 16: mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation)failure...It's a p2sh transaction that was created on bitcoin core v0.16, 2 of 3 multisig, where 2 of the pub keys are uncompressed. I am trying to broadcast the transaction on
bitcoin core v0.17 and v0.18 and i am getting the 16 error
picard276: that most likely means that the signature is simply incorrect (or the wrong message was signed); please ask on bitcoin.stackexchange.com; this channel is not for support or generic bitcoin questions
hi guys, I'm `pierreN` on github. I've been trying to contribute to core since this week. thanks for people helping me 🙂
pnn_m: thanks for the contributions!
yes I'm trying to start small with `good first issue` haha. it's nice to be able to chat directly on IRC so I joined the channel.
wumpus (IRC): sorry for not getting your last comment (on why `atoi64` can overflow). in anycase it's true that `ParseInt32` (since the value can be signed) could be more adapted. I could open a new PR for that if you'd prefer ?
Could somebody with MacOS help me and run this: "grep -r posix_fallocate /usr/include/". I couldn't find a man page for posix_fallocate() for MacOS online which probably means the function is not present, but I find it really hard to believe that. Thanks!
vasild: i'm not really a mac user, but i have one from 2012 running macOS 10.14.6 for testing bitcoin core, i don't have a usr/include dir, but grepping /usr is only finding results in usr/local/
and `man posix_fallocate` returns no manual entry
jonatack: you’ll probably want to look in your SDK dir
no /usr/include :-O
jonatack: but do you have the function in /usr/local/include?
vasild: so far it finds matches in third-party libs