Re: Knots/BIP110 designed to fork off?

[PepeLapiu]

So DaveF created a very misleading thread and he's deleting all my replies to it.
Here is his original thread:
https://bitcointalk.org/index.php?topic=5583540.0

And here is my answer:

(retard link removed)
But since he sums it up so well I figured it was worth a mention here. Because sooner or later the mod of r/bitcoinismoney will probably remove the post since they are pro 110 and remove a lot of anti 110 stuff.

I don't do Reddit so I'll have to take your word for it. One thing for sure, the post is still there while most pro-BIP110 posts on this forum do get removed, moved, locked, or you get yourself kicked out.

Maybe Reddit is pro-BIP110 but this forum in 100% pro-spam and pro-bitcoin-as-dickbutt.jpegs. And the censorship here is far worst than most anywhere else.

BIP-110 nodes aggressively attempt to connect to 8 outbound BIP-110 nodes using normal Core rules, and only connect to 0-2 non-BIP-110 nodes as an optional "sidecar".

Knots has been doing this since the very beginning, long before the spam war started. Furthermore, if you dislike preferential peering, I suggest you look into Peter Toad's LibreRelay. It's a node client derived from core designed to maximize spam on bitcoin. With no filtering, and preferential peering. It's designed for miners who want to include more spam for cheaper.

The net result is that BIP-110 nodes barely participate in the wider network, from the beginning they formed their own network that is sparsely connected to Core nodes.

It's my belief that core is an attack vector and pure spanware. The network doesn't want spam, the network want bitcoin as money. I think core 30 node operators should be tarred, feathered, and ran out of town.

There's only one reason to do this: if you assume you're going to be the minority in a partition.

That is completely absurd. You believe that Luke designed Knots to fork off with the minority hash at least a full decade before core 30?

If you sincerely believe preferential peering's only reason to be is to hard fork the chain, you should ask Peter Toad why his software also does preferential peering. You think Peter Toad wants to hard fork the miners away from the network?

The BIP-110 networking code gives away the author's true beliefs: BIP-110 would fail to attain a majority in hash or nodes, and would fork off.

Coretards told us we would fail when we had 3% of the nodes with Knots. Now we have 25% of the nodes with Knots, and 9-10% with BIP110.

More bitcoiners switched to Knots/BIP110 than upgraded to spamware core 30.

1) Some people (well at least 1 person) has been crossing the line with personal attacks.

Calling you a coretard is not a personal attack if it's true. And added that rule later on.
Can't exactly recall, but I don't think my post was too insulting.

2) If you say no that is not going to happen or anything code related. You need to post the code or at least point out in the code why what you said was true.

Fuck! Now only C++ coders are allowed to post on your bullshit thread?

So I can say YES knots / 110 will reject blocks starting in early August because of this code:
in https://github.com/bitcoinknots/bitcoin/blob/29.x-knots

Nobody is running that garbage. It's not even main net ready with no plans to bring it on main net.

You know what's strange here? For the last 6 months coretards have been trying to tell us that BIP110 will either fail or we will end up hard forking. Those are the only two options you can come up with: fail or hard fork.

We kept insisting we have no desire to give away bitcoin to spammers and start our own shit/altcoin. Spammers don't get to show up 4 years ago, and kick out bitcoiners. You'll get kicked out, not bitcoiners.

And now you claim it's a secret conspiracy? That we secretly want to hard fork out? WTF are you sniffin'?

[ertil]

Re: Knots/BIP110 designed to fork off?

Of course it is. After block 961632, Knots will switch to a different chain, if the majority of miners won't support it.

I suggest you look into Peter Toad's LibreRelay.

It is not a part of Bitcoin Core. It is an alternative client, based on it.

You believe that Luke designed Knots to fork off with the minority hash at least a full decade before core 30?

Why a full decade before? Just since BIP-110, it is programmed to fork after block 961632, if it will be in a minority.

You think Peter Toad wants to fork the miners away from the network?

No, because his client does not reject blocks, after a given point in time, like Knots do.

Now only C++ coders are allowed to post on your bullshit thread?

If you cannot point at the code, and explain it, then you probably don't understand, how it works. Which means, that your posts are based on "beliefs", instead of facts.

For the last 6 months coretards have been trying to tell us that BIP110 will either fail or we will end up hard forking.

Because this is what the code is doing here and now. And even links from sites like https://bip110.org/ agree on that:

If BIP 110 lacks economic support, its nodes stall. They sit at the last valid block, waiting for a signaling block that doesn’t come. The main chain continues as if nothing happened. No split, no disruption, no damage. BIP 110 just quietly fails.

If you think it is false, then you should justify it with something stronger, than "I don't believe it".

Those are the only two options you can come up with: fail or hard fork.

The first option, "failing", is directly explained in pro-BIP-110 articles. The second option is logical, if you want a chain, that is moving forward, while the majority of miners is not supporting it. If you have 1% miners, mining BIP-110 chain, then you produce around one block per day. Unless you change the code, which means hard-forking, or making other adjustments, to make it working in a minority.

And now you claim it's a secret conspiracy?

It's not a secret: it is literally in Bitcoin Knots source code, and people pointed at relevant fragments at least a few times.

That we secretly want to hard fork out?

Forking is not a "secret". It is clearly visible, how many miners are signalling for BIP-110. There are even sites, that can simulate scenarios, based on the hashrate support for a given side.

And then, hard-forking is just a logical next step. Unless you want to claim, that BIP-110 miners will keep producing one block per day, and will patiently wait for the difficulty to drop. And they will mine at a loss, while being unable to sell BIP-110 coins for the same price as BTC, just to keep the BIP-110 chain running. Because this is what they would need, if they would be in a minority.

[PepeLapiu]

(Coretard slop removed)

Of course there is no question that BIP110 will fork, it's in the name: RDTS or reduced data temporary soft fork. (emphasis on the S in RDTS)

The claim is that the code was secretly designed to hard fork. And the claim is that preferencial peeering is part of this secret design for a hard fork.

This is false. BIP110 is based on Knots 29. And Knots has always done preferential peering for reasons that have nothing to do with some eventual hard fork.

DaveF claims that a hard fork is the only possible reason for preferential peering. If so, is DaveF and his ilk making the claim that LibreRelay also is planning to hard fork the spam miners from the rest of the network?

[bitmover]

Fork? A new bitcoin cash?

We all have seen thia before.

They can fork and i will selling my forked coins instantly 

[DaveF]

1) Some people (well at least 1 person) has been crossing the line with personal attacks.

Calling you a coretard is not a personal attack if it's true. And added that rule later on.
Can't exactly recall, but I don't think my post was too insulting.

Actually it was CoreRulezKnotsAreFulez who IMO crossed a line a couple of times in a couple of other places.
Just didn't want it in that thread.

Now only C++ coders are allowed to post on your bullshit thread?

If you cannot point at the code, and explain it, then you probably don't understand, how it works. Which means, that your posts are based on "beliefs", instead of facts.

Yup, I don't see why some people have had such a hard time with that. There are plenty of posts to discuss opinion and views about what why how is going to happen in the beginning of August. Having 1 place to bounce around a tech discussion about it did not seem like the worst idea.

DaveF claims that a hard fork is the only possible reason for preferential peering. If so, is DaveF and his ilk making the claim that LibreRelay also is planning to hard fork the spam miners from the rest of the network?

LR does not have the code to reject blocks is does not like, so it will always follow the chain with the most work.
Although I cannot speak to the true thoughts of the people who wrote the code, since it is more permissive allowing more transactions in their mempools they probably wanted to talk to nodes that have them.

110 has less transactions in it's mempool since it limits what it accepts. If it talks to .30 nodes or LR nodes they still get all the TXs in the mempool and then they can ignore the ones they don't want.

-Dave

[PrivacyG]

The claim is that the code was secretly designed to hard fork. And the claim is that preferencial peeering is part of this secret design for a hard fork.

This is false.

I have been looking around BIP-110 articles, proposal and all the other pages I could find for more than half an hour and no where can I find any one single place where preferential peering is mentioned.  Which considering it is an important aspect, it does look like a 'hidden' design.  As in.  How many people will actually open the Code and look through it to find this line of code,

Code:

  // BIP-110: Allow up to 2 non-BIP110 outbound peers.

And it is obviously preferential peering to forcefully integrate the BIP-110 nodes as a majority.  Why would it not be mentioned, this is a cunning strategy to protect your own herd.

Now I do not know why you keep hoping this does not end up being a Hard Fork.  The BIP-110 supporters do not seem to even want to consider backing up a little bit.  You are intruders in a community who does NOT want Censorship and you never even tried to put an effort and at the very least pretend to be friends.  You came out straight away with insults, personal attacks et cetera trying to promote how restricting financial transactions and subjectively splitting them in 'Financial and Non Financial transactions' is better for everyone.  It is not, it will never be.

You can turn words upside down, you can forcefully mostly integrate only your own community in the network, you can lie and mislead, at the end of the day the facts remain the same.

Your network will continue to be stubborn and stupid and this will be a Hard Fork as your network will NOT reach majority either and then you can finally cry your tears in a bucket.

[(BTC)]

Fork? A new bitcoin cash?

We all have seen thia before.

They can fork and i will selling my forked coins instantly  

No, no. Not instantly. Hold them for a few months/until the next BTC cycle peak then sell them. Kind of like when BCH forked, you could have immediately sold them for like $200-400 in July/August '17, but price went up to like $2000-2700 in November/December '17. If you're going to profit off Knotzis, profit the most you can right?  

[mindrust]

If there is one thing I learned from the earlier fork-off event, it is this:

“A pint of blood costs more than a gallon of satoshi.”

Fork-off, do your thing but these infightings are costing us munney.

The bottom line is, I hope knots’ bottom line gets impacted pretty brutally on the markets. I also must add:

“Historically, historical changes have come out of fork-offs.”

[bitmover]

Fork? A new bitcoin cash?

We all have seen thia before.

They can fork and i will selling my forked coins instantly  

No, no. Not instantly. Hold them for a few months/until the next BTC cycle peak then sell them. Kind of like when BCH forked, you could have immediately sold them for like $200-400 in July/August '17, but price went up to like $2000-2700 in November/December '17. If you're going to profit off Knotzis, profit the most you can right?  

I will convert them to BTC instead of selling for dollars.

Bhc ratio was 1/10 when it forked. They were able to push it to almost 0.5 btc for a brief time, but lost value quickly after that

[PepeLapiu]

So replying to DaveF here so he can't delete my posts for retarded reasons.

Not sure what point you are making here.

My point is that LibreRelay does preferential peering. Do you take that to mean LibreRelay is trying to hard fork Bitcoin?

My point is that Knots was doing preferential peering ever since Knots was created over 12 years ago. Do you take that to mean that Knots was trying to hark fork 12 years ago when Segwit and B-cash didn't even exist yet?

The point is that there is code out there for core nodes to run so they can ban Knots nodes from their peers. Not just preferencial peering, but an outright black list.

But it's only when BIP110 does prrferencial peering that you suddenly declare that the only reason to do this is to hard fork?

Is it even remotely possible that there could be other reasons to do preferential peering? Or are you going to stick to that stupid secret hard fork BIP110 conspiracy theory?

In knots the code says use knots for the most part and kind of connect to core / other nodes.

Yes, that's what preferencial peering is. Similar to what LibreRelay is doing. Do you think Peter Toad and LibreRelay are trying to hard fork the spam miners away from the rest of us? Or could there be other reasons to do preferential peering?

[,quote]
What you linked to is some code that is not in core or any other distribution that I am aware of that people have to manually download and put into a config file.
[/quote]

Even if I knew how, I ain't fucking telling you how to install and run it. And besides, it no longer works anyways.

Many people have been doing that or something similar for months to improve their node performance since not having all the TXs causes your node to have to do more when it gets a block that it does not have all the TXs for. So making sure you don't connect to nodes that are not sending the full mempool helps you.

So you claim that there are valid non-hard fork reasons for an outright ban of a specific client. But no valid  reasons other than hard fork, for preferential peering. And only when BIP110 is concerned but not when LibreRelay.

What you are saying is that LibreRelay has legit reasons to do preferential peering.
Core nodes have legit reasons to outright ban Knots nodes.
And Knots had legit reasons to do preferential peering, but those legit reasons suddenly became nefarious last year?

Your conspiracy theories are retarded. You should focus on Big Foot and space lizzards.

Futhermore, here's something interesting:

Many people have been doing that or something similar for months to improve their node performance since not having all the TXs causes your node to have to do more when it gets a block that it does not have all the TXs for. So making sure you don't connect to nodes that are not sending the full mempool helps you.

Knots filters out spam. Knots doesn't filter out legit monetary transactions. So if you get around Knots filters and block Knots from connecting with you, you are basically facilitating spam.

If you oppose Knots, you fight for spam. And you will be tarred, fetgered, and ran out of town. Sooner or later.

Furthermore, Knots uses a 2nd mempool. Something coretards are too retarded to know about.

When my node filters out a jpeg, it goes into the 2nd mempool. It doesn't get relayed to others, but it doesn't get deleted either. So that I don't have to download and verify the same transaction twice if it gets into a block.

Core is stoopit. Core deletes what they already downloaded and filtered out, so that can download it again later on if it gets in a block.

And to solve core's horrible inneficient and wasteful design, some people decide to block Knots from connecting with their nodes?

How fucking stupid is that?

But I tell you what. Don't ask core to get a 2nd mempool like Knots does. Just ask them to make software that doesn't delete your keys and steals your coin. Okay?

[PrivacyG]

Knots filters out spam. Knots doesn't filter out legit monetary transactions. So if you get around Knots filters and block Knots from connecting with you, you are basically facilitating spam.

I should be able to spend between my two Addresses back and forth until all my Bitcoin is spent on Fees.  That may take a couple hundred or maybe even thousand Transactions at the lowest Fee rate and I should be able to do that even if your empty drooling brains end up thinking that should be flagged as spam and restricted or prevented too later on.

Anyway.  Did you get your bucket ready for the tears yet?

[DaveF]

...
When my node filters out a jpeg, it goes into the 2nd mempool. It doesn't get relayed to others, but it doesn't get deleted either. So that I don't have to download and verify the same transaction twice if it gets into a block.
.....

Which means I and others have no reason to connect to your node.
If your node does not send the full mempool that it has, all it is trying to do is make my node have to work a bit harder and get more TXs from other nodes to validate a block.

-Dave

[PepeLapiu]

...
When my node filters out a jpeg, it goes into the 2nd mempool. It doesn't get relayed to others, but it doesn't get deleted either. So that I don't have to download and verify the same transaction twice if it gets into a block.
.....

Which means I and others have no reason to connect to your node.
If your node does not send the full mempool that it has, all it is trying to do is make my node have to work a bit harder and get more TXs from other nodes to validate a block.

Your nodevworks harder because it's poorly designed. Your node has to download some transactions once, verify them, dump them, download them again, and verify them again. Which is a horrible, wasteful, and inneficient design.

But most importantly, which txs exactly are you having to download and verify twice? They are all spam. So your node effectively needs to ban other nodes in order to be more effective at relaying and facilitating spam.

Furthermore, your excuse to ban Knots nodes makes absolutely no sense. Even if 90% of the nodes you are connected to are Knots nodes, the other 10% you are connected to will relay all the spam you want to receive and relay to others. You don't need to ban all Knots nodes from your list of peers in order to receive and relay all the spam you want to relay.

You are a shitcoiner, you are making excuses as to how relaying spam is beneficial to your node, and how banning those who filter spam is technically a good idea for claims of efficiency.