rich1.0npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2njumphttps://nostr.ae📅 Original date posted:2015-06-19 📝 Original message:On Fri, Jun 19, 2015 at 08:20:52AM -0700, Adrian Macneil wrote: > > > > Unless you're sybil attacking the network and miners, consuming valuable > > resources and creating systemic risks of failure like we saw with > > Chainalysis, I don't see how you're getting "very small" double-spend > > probabilities. > > > > So connecting to many nodes just because we can and it's not technically > prevented is bad for the network and creating systemic risks of failure, Well it is actually; that's why myself, Wladimir van der Laan, and Gregory Maxwell all specifically¹ called Chainalysis's actions a sybil attack. The Bitcoin P2P network is resilliant to failure when the chance of any one node going down is uncorrelated with others. For instance if you accidentally introduced a bug in your nodes that failed to relay transactions/blocks properly, you'd simultaneously be disrupting a large portion of the network all at once. How many nodes is Coinbase connecting too? What software are they running? What subnets are they using? In particular, are they all on one subnet or multiple? > but relaying harmful double spend transactions just because you can and > it's not technically prevented, is good for everyone? You realise that Hearn/Andresen/Harding's double-spend-relaying patch, included in Bitcoin XT, relays double-spend transactions right? Do you consider that harmful? > > You know, you're creating an interesting bit of game theory here: if I'm > > a miner who doesn't already have a mining contract, why not implement > > full-RBF to force Coinbase to offer me one? One reason might be because > > other miners with such a contract - a majority - are going to be asked > > by Coinbase to reorg you out of the blockchain, but then we have a > > situation where a single entity has control of the blockchain. > > > > If someone did enter into contracts with miners to mine certain > transactions, and had a guarantee that the miners would not build on > previous blocks which included double spends, then they would only need > contracts with 51% of the network anyway. So it wouldn't really matter if > you were a small time miner and wanted to run full-RBF. But of course, you'd never 51% the network right? After all it's not possible to guarantee that your miner won't mine double-spends, as there is no single consensus definition of which transaction came first, nor can there be. Or do you see things differently? If I'm a small miner should I be worried my blocks might be rejected by the majority with hashing power contracts because I'm unable to predict which transactions Coinbase believes should go in the blockchain? > > For the good of Bitcoin, and your own company, you'd do well to firmly > > state that under no condition will Coinbase ever enter into mining > > contracts. > > > > I don't personally see what good this does for bitcoin. Now you are > suggesting that we should prevent a 51% attack by using policy and > promises, rather than a technical solution. How is this any better than us > relying on existing double spend rules which are based on policy and > promises? Well, I think I've shown how dangerous mining contracts can be to the overall health of the Bitcoin ecosystem; I'm simply asking you to promise not to make use of this dangerous option regardless of what happens. Like I said, if for whatever reason the first-seen mempool behavior proves to be insufficient at preventing double-spends from your perspective, you did suggest you might use mining contracts to ensure txs you want mined get mined, over others. 1) "Chainalysis CEO Denies 'Sybil Attack' on Bitcoin's Network", March 14th 2015, Grace Caffyn, Coindesk, http://www.coindesk.com/chainalysis-ceo-denies-launching-sybil-attack-on-bitcoin-network/ -- 'peter'[:-1]@petertodd.org 00000000000000000e806870e7e9cf4d507af6b78fc709e6839a8d34b52ea334 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 650 bytes Desc: Digital signature URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/7559ea0b/attachment.sig>