[AMA] I am a proponent of the BIP-110 (a.k.a RDTS) - ask me anything

[DaveF]

i said "i don't see any announcement", not "there's no announcement".

Yesterday, OCEAN mining pool announced and rolled out the new Stratum endpoint: bip110 . mine . ocean . xyz (port 3110).

Except it's not a new endpoint. The mine . ocean . xyz resolves to the same IPs that are hosted @ amazon and google and I think I saw a digital ocean IP in there too.

Just a quick snip of one nslookup

Code:

C:\Users\Dave>nslookup mine.ocean.xyz 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    mine.ocean.xyz
Address:  35.196.61.137


C:\Users\Dave>nslookup bip110.mine.ocean.xyz 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    bip110.mine.ocean.xyz
Address:  35.196.61.137


C:\Users\Dave>nslookup 35.196.61.137 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    137.61.196.35.bc.googleusercontent.com
Address:  35.196.61.137

So they added a DNS entry and a port mapping.
Big whoop, not like they were mining non 110 blocks anyway.

But it does look like they are going to break 1% signaling for this period with all the hash they rented.

-Dave

[Greg Tonoski]

Yesterday, OCEAN mining pool announced and rolled out the new Stratum endpoint: bip110 . mine . ocean . xyz (port 3110).

Except it's not a new endpoint.

Liar. There is the endpoint that is new.

Another news: Abundant Mines announced they would start signalling for BIP-110 in a week or two.

[DaveF]

Yesterday, OCEAN mining pool announced and rolled out the new Stratum endpoint: bip110 . mine . ocean . xyz (port 3110).

Except it's not a new endpoint.

Liar. There is the endpoint that is new.

Another news: Abundant Mines announced they would start signalling for BIP-110 in a week or two.

The DNS name is new.

The servers (endpoint) that it is pointing to are the same google / amazon / digital ocean IPs that they have been using.

Just a new DNS name and new port connecting to the same back end.

-Dave

[ABCbits]

i said "i don't see any announcement", not "there's no announcement".

Yesterday, OCEAN mining pool announced and rolled out the new Stratum endpoint: bip110.mine.ocean.xyz (port 3110).

What is your point? i already mention a link that shows most mined block that signal BIP 110 block from ocean. That means i already know some miners use that mining pool to mine block that signal BIP 110.

Edit: mining pool and miner are 2 different things.

But it does look like they are going to break 1% signaling for this period with all the hash they rented.

In addition, ocean mining pool decide default behavior of their current endpoint.

The existing endpoint (mine.ocean.xyz:3334) will switch to signaling BIP110 in 1 week (July 15th).

[Greg Tonoski]

Foundry USA considers signaling for the BIP-110, reportedly.

[stompix]

Foundry USA considers signaling for the BIP-110, reportedly.

Reportedly by .....whom? 
Foundry will be signaling with their blocks, what does the last block mined by Foundry say?

But it does look like they are going to break 1% signaling for this period with all the hash they rented.

The whole thing got annoying; they obviously rented hashrate from different farms and labelled them individually, seems like they are conserving money for now:
https://mempool.space/mining/pool/ocean
How do you go down from 7 blocks a day to 2 blocks in 48 hours? 

[DaveF]

Foundry USA considers signaling for the BIP-110, reportedly.

No foundry is asking its miners to vote.

The whole thing got annoying; they obviously rented hashrate from different farms and labelled them individually, seems like they are conserving money for now:
https://mempool.space/mining/pool/ocean
How do you go down from 7 blocks a day to 2 blocks in 48 hours?  

Either conserving or ran out. Doing some back of the napkin math with MRR and NiceHash costs vs expected results at perfect luck they are loosing between 3% and 4% per block mined. Obviously luck has a tremendous impact on that. Good run of luck you can be way up or with a bad run way down.


And someone found another nice bug in knots code:
https://blockslop.dev/

Is that block valid on 110? Is that block invalid 110? Guess it does not matter. Keep it anyway.

-Dave

[ABCbits]

Foundry USA considers signaling for the BIP-110, reportedly.

No wonder you don't mention the source, because Foundry USA actually do different thing. The one who may consider (voting "yes") are their their miner.

Foundry Digital, the world’s leading Bitcoin mining pool operator, has said it will allow mining clients how the pool should signal on the BIP-110.

The Rochester, New York-based firm said Friday in an email to miners that they will be able to vote by using their hashrate — literally computing power — to vote either for or against the proposal.

Personally i don't expect any change, considering such miner who actually want to signal BIP 110 would already take action some time ago.

And someone found another nice bug in knots code:
https://blockslop.dev/

Is that block valid on 110? Is that block invalid 110? Guess it does not matter. Keep it anyway.

-Dave

The finding isn't surprising, when there's no public network test specifically for BIP 110 and there aren't that many developer who maintain/contribute on Knots.

[DaveF]

Foundry USA considers signaling for the BIP-110, reportedly.

No wonder you don't mention the source, because Foundry USA actually do different thing. The one who may consider (voting "yes") are their their miner.

Foundry Digital, the world’s leading Bitcoin mining pool operator, has said it will allow mining clients how the pool should signal on the BIP-110.

The Rochester, New York-based firm said Friday in an email to miners that they will be able to vote by using their hashrate — literally computing power — to vote either for or against the proposal.

Wonder what the spin from 110 supporters is going to be when everyone votes no to 110?

The finding isn't surprising, when there's no public network test specifically for BIP 110 and there aren't that many developer who maintain/contribute on Knots.

Is there really more then one developer for knots?

And, does anyone even care that much. You have a bunch of people supporting it, but for the most part they are going for the social media influencer style of things. Postings on X, rambling YouTube videos, a subreddit dedicated to them, the people posting here, etc.

But no real discussions on tech locations as far as I can tell. No testnet.

20 days and a bunch of hours from now we get to see it all fall apart anyway.

-Dave

[stompix]

Wonder what the spin from 110 supporters is going to be when everyone votes no to 110?

No need to wonder, they are already in full force preparing for the NO.
Their claim is that Foundry is unfair and it will count hashrate that hasn't voted as NO!
From what I saw on x on all the news about this, they didn't just buy hashrate, they also bought shilling accounts for it.

Anyhow, if I were a miner on Foundry or Via or whatever, if I wanted to show my support for this I would have switched pools a while ago, well actually, I wouldn't have even mined on a pool that allows "spam" on the network, right?

20 days and a bunch of hours from now we get to see it all fall apart anyway.

This is going to feel like waiting for ages for nothing, but god I want it done and over!

[Greg Tonoski]

BIP-110 adoption is climbing as the activation is approaching fast. Update you node software if it isn't the fully validating one Bitcoin Knots v29.3.knots20260508 (https://github.com/bitcoinknots/bitcoin/releases).

In order to catch-up with the upcoming security update of the Bitcoin protocol - Bitcoin Improvement Proposal 110 (BIP-110), I advise maintenance update of Bitcoin nodes software to Bitcoin Knots v29.3.knots20260508 which fully validates transactions and blocks. The activation is anticipated to occur around the 8th/9th of August 2026 (block height 961632).

Additionally, I strongly recommend updating configuration options in the bitcoin.conf file with:

Code:

consensusrules=rdts
datacarrier=0

[DaveF]

BIP-110 adoption is climbing as the activation is approaching fast.

HAHAHAHAHAHAHA

Looks like it's going actually go over 1% that is real adoption you got there.

-Dave

[Greg Tonoski]

In 2 weeks the BIP-110 improvement will come into effect. There isn't any chain-split imminent. All review comments were processed and the whole review process completed. There isn't any major issue open. Activation is on track. BIP-110 is the best soft-fork in the Bitcoin history.

[DaveF]

So at this last period 1.3% of the blocks signaled for 110.
Yeah, all the newer knots clients are going to drop off the chain with the most work in about 14 days.

Wonder if people are going to keep mining it.

-Dave

[stompix]

There isn't any chain-split imminent.

Finally, you got something right.

Foundry USA considers signaling for the BIP-110, reportedly.

Foundry just mined the first block out of this new era, what are they saying?

So at this last period 1.3% of the blocks signaled for 110.
Yeah, all the newer knots clients are going to drop off the chain with the most work in about 14 days.

I just realized they needed 55% for their "soft-lock", so the whole drama will be over in less than seven days when 1000 of this epoch's blocks would have been mined with only like what ..at max 10-20 blocks signaling their support?

[athanred]

so the whole drama will be over

It would be, if their client would mark the BIP as "failed". But because of "mandatory signalling", BIP-110 clients will enforce new rules, even with 0% hashrate, which will stuck them on their own chain.

Finally, you got something right.

Well, if BIP-110 chain will produce at least one block, while the heaviest chain will be somewhere else, then it could be called a "split". Because their client won't follow the heaviest non-signalling chain. Also, it would be funny to see non-BIP-110 Knots clients following a different chain, than BIP-110 Knots clients.

at max 10-20 blocks signaling their support?

They will mine something like one or two blocks per day. After a few non-signalling blocks, it will be exponentially harder and harder for them, to catch the heaviest chain.

Foundry just mined the first block out of this new era, what are they saying?

At the time of this writing, they didn't signal for BIP-110 yet with any block. You can check it here: https://wickedsmartbitcoin.com/bip110_signaling

There is a tab, which can show you signalling pools, blocks, and so on.

[DaveF]

I just realized they needed 55% for their "soft-lock", so the whole drama will be over in less than seven days when 1000 of this epoch's blocks would have been mined with only like what ..at max 10-20 blocks signaling their support?

There are 2 parts to this. 1 is BIP-110 the other is the knots client.
We tend to lump them together but they really are 2 separate things.

The newer knots clients, which is the only one that natively supports BIP-110 are hard coded to start rejecting blocks that do not signal support for BIP-110 at the end of the period we are in. No matter what happens to BIP-110

So 110 according to the BIP will not activate, but the people running knots will stop accepting blocks in about 2 weeks.

The people who just made changes to a regular clients conf file will keep accepting all blocks.
The fact that they do not relay / accept some TXs from the mempool does not matter much since they are such a small % of the nodes out there.

-Dave

[stompix]

There are 2 parts to this. 1 is BIP-110 the other is the knots client.
We tend to lump them together but they really are 2 separate things.

Because if one fails, the other has no chance of doing anything.
Yes, Knots clients will reject blocks, good for them, they will only accept Ocean's blocks, which are 1-2 blocks a day depeding if it's sunny outside or not, while the other chain will get most work and most nodes connected to!

So 110 according to the BIP will not activate, but the people running knots will stop accepting blocks in about 2 weeks.

Yup, so 20% of the nodes will reject the only actual working chain, also, it's going to be closer to 0.2% in terms of individuals who own nodes, as we all know those numbers are overly inflated with clones. You can have 20% of the nodes if the top exchanges /liquidty pools/mixer/payment gateways all run core or else, it doesn't really matter!

This is why I'm saying that we will be over this in 7 days
- if miners move to 110 then well...what is done is done...fuck my life
- if miners don't move to 110 and the situation stays as it is now, there will be no 110 chain, sorry, but someone building a block a day 100 days late, it's not a chain, it's a hemorrhoid growing.

Also, never actually bothered to look into it but did they plan on doing anything about the difficulty adjustment if they lose the majority of the hash rate?
Because if they "split" right now, it will take them 2 years to reach the next adjustment.

Well, if BIP-110 chain will produce at least one block, while the heaviest chain will be somewhere else, then it could be called a "split". Because their client won't follow the heaviest non-signalling chain. Also, it would be funny to see non-BIP-110 Knots clients following a different chain, than BIP-110 Knots clients.

As I said, this is not going to be a split, BCH was a split, they are actually 1500 blocks ahead of BTC right now, let me be optimistic and say that they will not get more 100 added to it before they quit and abandon it, as I said, this will be more like something than you get on your skin after bathing where you shouldn't have rather than a true split.

At the time of this writing, they didn't signal for BIP-110 yet with any block.

Let me guess without checking
- Ocean is the only pool signaling
- They have 2% of the blocks as they've rented power again after that pause
- As if fees weren't already a problem on a damn 3cents per th/s income, they are also losing half of those on their half-empty blocks , right?

[athanred]

BIP-110: All other known use cases are not affected.
Meanwhile: https://mempool.kilombino.com/tx/f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16

[stompix]

BIP-110: All other known use cases are not affected.
Meanwhile: https://mempool.kilombino.com/tx/f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16

Yeah, it was known that it would block sending to P2PK, but to be completely unbiased here it doesn't mark transactions from, so spending would still work.
They wouldn't have dared to touch that, it would have been way too much even for them
Anyhow, I see way too few "invalid" transactions in the last blocks, fees are up by a thrid, consolidations are up. Are people actually caring about this?