Anyone else getting private messages promoting BU? Looks like Ver updated to the astroturfing premium package.

Miner signaling for blocks larger than 1MB is now at 48%, are you still so sure SegWit is not a trojan horse from a bankers backed private company, trying to squeeze in their own code at any costs?

Yes, fuck off please. Who even takes an astroturfing job like that?

submitted by /u/supermari0
[link] [comments]
Bitcoin

Jihan Wu’s messages after the announcement seem to imply he controls the majority of hashing

http://i.imgur.com/sYzHBxG.png

Source: https://twitter.com/007LongShao/status/842796442250952705 ( http://m.weibo.cn/u/2083258595 )

"All the exchanges who signed are not world class level. They think they're clever, but didn't figure out the most basic logic. The situation is more complex but the result is clear. The big pools will win and the rest can't survive".

"These stupid cunts are going to be caught unprepared for the complex circumstances in which the fork is going to occur."

[EDIT: /u/oakpacific provides this corrected translation of that last sentence: "These stupid cunts create such a complex arrangement (implying that it's created by the exchanges), they will be caught by surprise by the complex situations during a fork."]

Other than that, expletives and edgy teenager talk.

Obviously, we're already used to his childish bluster, but it wouldn't be completely out of the question that there is a coalition of miners with 50%+ of the hashing.

IMO, regardless of SegWit, the PoW change option needs to be considered because the underlying problem of total mining centralisation remains there. At least the plan needs to be in place just in case. Even with the support of the exchanges, the situation could be quite precarious.

submitted by /u/muyuu
[link] [comments]
Bitcoin

print websocket messages in a textfile

I am doing a PhD in economics and I am currently working on bitcoin. I am trying to understand how senders decide how much fee they include in transactions. Since in a couple decades miners will be rewarded mostly with fees, I think this is an important question. It would be great if I could have data on all the unconfirmed transactions. This would enable me to see, for each transaction, how much fee it includes given the available information, that is how many transactions are already in the mempool and how much fee do those include. Of course I can see those transactions on blockchain.info, for instance, but is there a way I could save them on a file?

Thanks to a very clear video on you tube I can receive the transactions on my browser’s console log using blockchain.info’s websocket but how can I print, let’s say a couple hundred thousands of them, in a textfile?

Could anyone help me? Thank you very much!

Recent Questions – Bitcoin Stack Exchange

Understanding signing messages with bitcoinjs-lib

I’m trying to understand what a specific line of code does when signing a message using bitcoinjs-lib. Here’s the code:

var bitcoin = require('bitcoinjs-lib') var bitcoinMessage = require('bitcoinjs-message')  var keyPair = bitcoin.ECPair.makeRandom(); //private key var privateKey = keyPair.toWIF(); // Address var address = keyPair.getAddress();  console.log(privateKey); console.log(address);  privateKey = keyPair.d.toBuffer(32) var message = 'your message' var messagePrefix = bitcoin.networks.bitcoin.messagePrefix  var signature = bitcoinMessage.sign(message, messagePrefix, privateKey, keyPair.compressed) console.log(signature.toString('base64')) 

The line I’m curious about is this one:

privateKey = keyPair.d.toBuffer(32) 

What exactly is this code doing and why is it necessary?

Thanks,

Connor

Recent Questions – Bitcoin Stack Exchange

Different error messages under “Mandatory script verify flag failed.”

Good day,

I’ve been playing with raw transactions and signed transaction and I’ve noticed that the error “Mandatory script verify flag failed” comes in two variations.

  1. script failed on OP_EQUALVERIFY OP
  2. Script evaluated without error but finished with a false/empty top stack element.

Now, it appears that error number one is given whenever I try to send a transaction with the wrong TXID or index number. The second error can appear when I provide the wrong signature.

But aren’t both errors just variant of a failure in executing the OP_EQUALVERIFY? At what step of the evaluation each error is thrown and what can we make out of it?

I’ll highly appreciate any pointer you might have. I really struggle here to differentiate the two.

Recent Questions – Bitcoin Stack Exchange