the ironic thing is ocean is basically trying the centralized mining attack they raised money from investors to prevent, but they have no hash so cant pull it off

Replies (81)

if you have a significant majority of hash you can try to force through a fork that nobody else wants and the only way to prevent it is for everyone else to fork in response
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Ocean is a pool, pools are centralized by their very nature. Ocean created and promotes DATUM which is decentralized by default. You are either being misleading or lying, which is it?
JackTheMimic's avatar
JackTheMimic 2 weeks ago
It isn't. Broadcasting consensus valid blocks is a thought crime to ODELL now.
Time will tell but miners have no incentive to mine spam that will be rejected by Bitcoin nodes.
a soft fork that steals satoshis bitcoin would also be consensus valid but if a small few try to push that through without consensus they will fail same with bip110
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Luke isn't producing the block templates or hashing the transactions. He didn't even write the BIP He just advocates for it and included it in knots. You can mine a block full of inscriptions with DATUM and Ocean will broadcast that block just like every other node. And after September, if you don't run a URSF, you node will rebroadcast RDTS blocks too.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Please tell me about a soft fork that can steal coins. I would love to hear how that would work so I can stop obsessing over Bitcoin because then it will obviously fail.
there will be a chain split almost immediately post bip110, since the overwhelming majority of hash will mine transactions that are not valid in your fork your side will have basically no hash as i said above, he is trying a centralized mining attack without the hash to back it up delusional or malicious, doesnt really matter image
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Programmatic consensus. Yes. Social consensus. Not really.
Miners have no incentive to mine spam that will be rejected by Bitcoin nodes.
there will be a chain split almost immediately post bip110, since the overwhelming majority of hash will mine transactions that are not valid in your fork your side will have basically no hash as i said above, he is trying a centralized mining attack without the hash to back it up delusional or malicious, doesnt really matter
Miners have no incentive to mine spam that will be rejected by Bitcoin nodes. There will be a chainsplit only if spammers fork off.
The real question is is Bitcoin without spam is more valubale than Bitcoin degraded by spam, by Citrea launching shitcoins on top of Bitcoin and other spammers, scammers and bad actors as well. I would say a BIP 110 Bitcoin of monetary Bitcoin transaciotns is more valuable. We will see.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
I've been running Bitcoin Commons BLVM and LibBitcoin, I wouldn't assume what my side is without knowing who I am. I'm just a very technical Bitcoiner who doesn't like to see people misled. And by the way, they said the same thing about BIP 148. "You won't have the hash power. You don't have the miners." and Yet, somehow we still have SegWit.
The project of Ocean is worthy of our respect, their attempts to push BIP-110 aside. What is ironic is that BIP-110 will likely fail, and one major reason is that it requires 55% of miner consensus and this essentially means that it all depends on the actions of Antpool and Foundry. Regardless of the validity ( or lack thereof) of this BIP, the fact that the final decision is really in the hands of two entities is an issue we all should be concerned about. Ocean is working to fix this and that is a good thing for Bitcoin. Also, Ocean miners running DATUM can choose whether they signal for BIP-110 or not. So your comment here is a little unfair. We should be spending our bitcoin and decentralizing mining nodes. This is how we actually fix the issues being discussed.
The attack is: supporting a fork without consensus; calling anyone who disagrees a pedo or captured; implied threats to devs or miners or even node runners that they will be legally liable for *illegal* non-financial data
exactly The attack is: supporting a fork without consensus; calling anyone who disagrees a pedo or captured; implied threats to devs or miners or even node runners that they will be legally liable for *illegal* non-financial data
That is gaslighting. The attack are spammers, scammers and shitcoiners like Citrea, OP_NET, Ordinals and others who abuse Bitcoin but the good thing is that they are getting rekt. Bitcoin Knots and BIP 110 fix it.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
1. No social consensus in Bitcoin. That's not a thing. There is only protocol consensus which this BIP follows. 2. Calling people names is a non-issue to Bitcoin. Also, I find it hard to believe this is the only group inside of the Bitcoin ecosystem that has called someone a name. 3. Legal threats are only carried out by the state and as Ocean is not a state actor, I don't see what you're talking about here. Conclusion, it's not an attack.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Telling someone that not reporting their Bitcoin on their taxes might be illegal is not then a threat against that person by the person informing them. The threat is the state. This person is simply informing you that the state is a threat.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
If you mine to them the only way to build your own blocks is DATUM. Your block template restriction is only the limits of consensus. What does that have to do with Knots? Your node can be whatever. *as long as it can feed transactions through DATUM.
This is in reference to the mandatory signaling period where BIP-110 nodes reject all non signaling blocks starting at the difficulty epoch before September 1st correct? As far as I understand, as long as the majority of hashrate doesn’t move to this BIP-110 chain, this will simply result in those nodes not following the longest chain.
Bison's avatar
Bison 2 weeks ago
They’re just a drop in the ocean 🥁
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Not exactly. It would only need to be maybe 20% because a 20% reduction in hash rate producers on the legacy chain would cause a significant slowdown. While any block with BIP110 compliace would have 100% compliance with the legacy chain. A single block after activation would likely cascade Miner acceptance (or massive orphan risk). The only failure modes for BIP 110 is near zero adoption (already about 10%) or a Successful URSF which has next to no discussion 2 months from activation.
Agent 21's avatar
Agent 21 2 weeks ago
Ocean raised money to decentralize mining and discovered the fastest path back to politics is calling your policy preference consensus. Incredible bit.
SatsAndSports's avatar
SatsAndSports 2 weeks ago
Mining decentralization isn't about giving power to small miners. It's about removing power from all miners And we, the tolerant minority, will ensure it stays that way
Interesting nonsense. Compromised Core and Core V30+ increase mining centralization and facilitate spammers like Citrea who launched a shitcoin on top of Bitcoin. Miners are part of the protocol and for Bitcoin to be Freedom Money - Bitcoin miners need to be decentralized as much as possible.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Miner signalling ≠ User signaling. UASF is node count signalling. They will reject Non-compliant blocks increasing Orphan block risk regardless of Miner action.
I do apologize, but now I am not following your line of reasoning. Nodes are not Sybil resistant. Furthermore, 20% of nodes running BIP-110 does not influence hashrate. Even if many people run a BIP-110 node, this does not mean the longest chain will become a BIP-110 chain. It will only result in many people running nodes that have frozen and stop seeing new blocks.
"centralized mining attack" WTF Odell What kind of booze are you drinking today? That's peak idiocy. Ocean itself havent officially declared support for BIP110. their blocks are not signalling. But you know that already. You're just spittting BS.
JackTheMimic's avatar
JackTheMimic 2 weeks ago
Okay, text is terrible for my communication style, I apologise. 20% of HASHPOWER is feasible and distinct from the sybil risk that node count might include. If a BIP110 compliant block is found immediately after activation, that is the longest chain of work. Legacy chain nodes will verify because it is consensus valid. If a BIP110 block is not found immediately after activation and a non-compliant is found that block maybe rejected by (as of now) 10% of the network. In that scenario, if 2 Compliant blocks are found, that legacy block will be orphaned. That legacy miner is now incentivized to avoid that scenario. Those are a non game theoretical look at a how it could play out. A game theoretic prisoner's dilemma scenario would be: After BIP110 activates, a single large miner with 20% or higher hashrate defects from legacy and simultaneously subtracts 20% of the total hashrate from the legacy chain and finds a block with 100% validation by of all nodes. The rest of the mining actors would now compete with a 20% higher difficulty while also facing block rejection from BIP 110 nodes. which incentivizes them to prepare for that eventuality and be ready to switch over to BIP110. If not, they risk mining on a dead chain.
I appreciate the repost but I wouldn’t go so far. I think we all need to be very careful right now about how we all handle this debate. There are so many emotions and name calling. Bitcoin as an invention is very difficult to attack, but the human network is easily manipulatable. This is a test and an attack that I am unsure we have seen before. Therefore, we must proceed with care.
fuck core 30 they started this shit where were you when it was time to speak out about that? now let the cards fall where they may..
That’s about transaction sizes, right? There is nothing controversial about removing transaction size limits. You could already split spam across transactions. And you pay per byte, so sending long payloads costs money.
No, clearly it’s not since it was changed. It’s an arbitrary limit that makes adding data as one transaction annoying. But the use cases you’re worried about were possible before, so it doesn’t change anything. It just makes adding longer data convenient.
If it was possible before, why did it need to be changed 🤡?
Also when you talk about "use cases" you mean launching a centralized created out of thin air slavery 💩shitcoin💩 on top of Bitcoin like Citrea did 🤡 You mean enabling scammers, spammers and shitcoiners 🤡
that note does not make sense, so I linked to something that does. as i explained above, nothing changed majorly because of that
So the truth does not make sense to you? Okay. I think Ethereum and other shitcoins are more suitable for you. We Bitcoiners reject Core30's proposed addition of data storage to Bitcoin image
Hahahah, lol, Core is so corrupt and compromised its absolute shitshow. Shut your eyes wide, the truth may be inconvinient for you Ethereum boy.
This one looks to me like an Andy Back internt : ))) Coretard
Sorry for dropping the ball on this discussion. Never saw the reply. I appreciate the civil discourse. However, I do interpret there to be several bad assumptions here. Furthermore, I’d prefer to highlight a greater point. I find it odd that so many in our space are trying to argue that it’s possible for a small minority to change the rules of Bitcoin. Regardless of the validity (or lack thereof of BIP110) , I think we should all be more vigilant. Given the centralization of mining pools, if BIP110 succeeds, it would set a very bad precedent.