Thank you! As a community we need nation like them.
Not happy with Coinbase dragging their feet on SegWit integration? Follow these steps:
Remember, this doesn't just affect customers of Coinbase, it affects the whole network. Not optimizing transactions (with SegWit and batching) inflates the fees for everyone else. This is irresponsible for such a large company in this growing industry.
Please do your "bit" and help make the issue known as best you can.
I will continue to push this until we get some answers from Coinbase. I’ll also be recommending alternative services to new users in the meantime.
Can the checksig operator be used to check if private key A signed value X. Where value X is some arbitrary data like a sports score?
I am using https://github.com/bumi/bip70-example to make signed payment request. I bought COMODO Wildcard certificate. And creating certificates bundle in following order:
addtrustexternalcaroot.crt. And specifying this bundle and private key to the code. But when trying to make a payment wallet(Bread wallet for this example) giving me: “payee identity isn’t cerfied. This operation couldn’t be completed. (OSStatusError -9809).”
This article brought to my attention that SIGHASH flags are 4 bytes long when signed, but only the last byte is actually included in the transaction. Then OP_CHECKSIG adds 3 bytes
0x000000 back on before verifying the signature. The article describes a clever way to introduce a fork using those three truncated bytes — so why are the SIGHASH flags 4 bytes long in the first place? Is that a design flaw or feature?