BIP-110 Split (continued)

[MoparMiningLLC]

yet they are all over there screaming how they now have "bitcoin" the hardest money around - no one is using it.

[ObeyKnock]

Now, if only Binance would stop pulling old inputs from their cold wallets that can still be replayed to Blake2b to fulfill withdrawals

Not a big deal and entirely avoidable, issue with Binance old cold wallet inputs still being valid on both chains is just due to lack of strong replay protection (see "tainted coin").

This was fixed in BCH back in Aug 2017 with deployment of SIGHASH_FORKID, this is sighash flag which basically makes tx signatures dependant on the network they are being broadcast on, meaning a tx valid and signed on one chain will be invalid on the other. It has been standard playbook for basically every fork since BCH to use SIGHASH_FORKID for replay protection (eg. BTG did same, just with a different forkid number).

It is surprising that Blake2b is still using opt-in-only protection after almost 3 months. Normal signatures are still fully replayable, so it is still possible because whoever wrote the fork did not include the strong mandatory version which has been best practice for almost a decade. Hard to take such fork seriously as being the "real" one when they make such elementary errors.

[LoyceV]

It is surprising that Blake2b is still using opt-in-only protection after almost 3 months. Normal signatures are still fully replayable, so it is still possible because whoever wrote the fork did not include the strong mandatory version which has been best practice for almost a decade. Hard to take such fork seriously as being the "real" one when they make such elementary errors.

I can only assume they did this on purpose.

[pooya87]

It is surprising that Blake2b is still using opt-in-only protection after almost 3 months. Normal signatures are still fully replayable, so it is still possible because whoever wrote the fork did not include the strong mandatory version which has been best practice for almost a decade.

Imagine the case where someone spends his bitcoins and unknowingly the tx is replayed so the forkcoins are moved and burnt this way. A while later that same person tries to claim his airdrop but he realizes he has none so the shitcoiners have 1 less dump to worry about therefore their shitcoin's price can remain a little bit higher than if that tx was not replayed.... win for the shitcoiners perhaps?

Hard to take such fork seriously as being the "real" one when they make such elementary errors.

It was hard to take them seriously the day they decided to fork off with a minute percentage of the hashrate.

[DaveF]

It is surprising that Blake2b is still using opt-in-only protection after almost 3 months. Normal signatures are still fully replayable, so it is still possible because whoever wrote the fork did not include the strong mandatory version which has been best practice for almost a decade.

Imagine the case where someone spends his bitcoins and unknowingly the tx is replayed so the forkcoins are moved and burnt this way. A while later that same person tries to claim his airdrop but he realizes he has none so the shitcoiners have 1 less dump to worry about therefore their shitcoin's price can remain a little bit higher than if that tx was not replayed.... win for the shitcoiners perhaps?

Hard to take such fork seriously as being the "real" one when they make such elementary errors.

It was hard to take them seriously the day they decided to fork off with a minute percentage of the hashrate.

It was hard to take them seriously ever.
The lack of relay protection was deliberate the same way they are the "one true BTC" and the rest of us forked off so therefore we should have been the ones to enable replay protection. Just more of their craziness.

-Dave

[stompix]

It is surprising that Blake2b is still using opt-in-only protection after almost 3 months. Normal signatures are still fully replayable, so it is still possible because whoever wrote the fork did not include the strong mandatory version which has been best practice for almost a decade. Hard to take such fork seriously as being the "real" one when they make such elementary errors.

I can only assume they did this on purpose.

Yup.
I once thought this was just Luke's ego and they did it so they can claim their chain is still the original Bitcoin, but after a lot of stuff happened and Convoy started mining, Luke and Guida's crusade against Chinese miners, their desire to invalidate coin rewards for toher miners and so on, it seems like it was all about money, so Maxwell was right:

It's so they can deplete exchange balances of BJr coins to punish insubordinate exchanges that didn't adopt BJr out the gate.  They deposit split bitcoins and withdraw, then the exchange sends an unsplit coin.  Wash rinse repeat.  They specifically discussed performing this action on their discord.

[MoparMiningLLC]

it now looks like they are serious about delaying coinbase pymts for nearly a year.

[athanred]

Can't wait to read that putting 5MB spam in a block is unstoppable.

Meanwhile, on BIP-110 chain, there are bigger files than 5 MB, and nobody cares, how they are splitted, if the software can combine it, and display properly to the user: https://bitfiles.io/btcb2/827bc6c90a56819cf9afd12a273d36d6b00345da079b16a82b3570704b427558

[DaveF]

Meanwhile, on BIP-110 chain, there are bigger files than 5 MB, and nobody cares, how they are splitted, if the software can combine it, and display properly to the user: https://bitfiles.io/btcb2/827bc6c90a56819cf9afd12a273d36d6b00345da079b16a82b3570704b427558

Needs more puppets :-)



While attempting to read their discord it looks like they want to punish / censor miners that mine TXs like that.
And the 1 year coinbase maturity.

Makes you wonder what else they are going to change to make their coin the way they want.
And if / when some whale is going to dump it down to a double digit price.

Probably the only things saving it is that so few people know about it, so they are not dumping and the low price and thin volume so it becomes not worth it.

-Dave

[MoparMiningLLC]

I think their intent on stopping all new coinbase pymts for a year is in an attempt to keep new coins out of circulation to make their coin less accessible and to try and drive up price.

the problem with that is when the coins start releasing, someone will dump and drive their price right back down.

[DaveF]

I think their intent on stopping all new coinbase pymts for a year is in an attempt to keep new coins out of circulation to make their coin less accessible and to try and drive up price.

the problem with that is when the coins start releasing, someone will dump and drive their price right back down.

That's a 2027 problem.
Do you really think that this is going to last that long.

It's kind of funny how the narrative keeps changing and they just accept it.

Went from "Core has too much spam and people can't afford to run nodes because a larger drive might cost them a few extra dollars" to "Everyone should get a blake2b miner and mine so the network is diversified but who cares if they do not get paid for a year"

I mean, it's fun and all to come here and laugh at them, but it really makes you wonder how long it's really sustainable for.

-Dave

[pooya87]

Has anyone used the BLuke explorer to broadcast a transaction: https://mempool.guide/tx/push

I am trying to test something there and it is being rejected so I am wondering whether the problem is on my side (where what I created is broken) or is on their side like broadcasting it to bitcoin network instead of luke network.

[LoyceV]

I think their intent on stopping all new coinbase pymts for a year is in an attempt to keep new coins out of circulation to make their coin less accessible and to try and drive up price.

Do you really think that this is going to last that long.

So what they're saying is that mining isn't meant to create new coins to increase circulation. Do they not see the irony in this?

[athanred]

Has anyone used the BLuke explorer to broadcast a transaction

Of course, exactly when they forked, to split my coins:

For broadcasting it, you need just some block explorer with some API:

non-BIP-110:

Code:

curl -X POST -sSLd "020000000001011939e6659c99822b21ed010ad98930824afe6b4b013f594fe1d69dbddf6c9b4b0000000000fdffffff01e08d050000000000160014f331f2a4e71986410d58716cdc4baa2db772ace7024730440220774391e4eba583893ad6d87f48417ab9ec4d137f262d5eaf2bd75626c43550cd02206b24f478c88b7016641d60ca4fad6626e7f55f488eb569bd8080d05e437e379a832102c551349ae6688aad6ac3001931c591002ae4765dbb04aeaf97d5ac2e3b9ed06900000000" "https://mempool.space/api/tx"

BIP-110:

Code:

curl -X POST -sSLd "0200000000010148cf3189bf2c387cda8f8c14c5777b61604f7119e4e2ecd382ba29e2583769f00000000000fdffffff01e08d050000000000160014f331f2a4e71986410d58716cdc4baa2db772ace70247304402202e0d1af4e3ce7b3fd14343a35e15ae3235323604971abfbf02aecfcbf400faaa0220787f833bf3a4f2e7df2398797069e45ba5d35914b63e7fcd54058c7d0909f567832102c551349ae6688aad6ac3001931c591002ae4765dbb04aeaf97d5ac2e3b9ed06900000000" "https://mempool.guide/api/tx"

I am trying to test something there and it is being rejected

If you try to use transaction version 3, then they will probably reject it. And in that case, it is yet another way to split coins: by just using a different transaction version.

[ObeyKnock]

Has anyone used the BLuke explorer to broadcast a transaction: https://mempool.guide/tx/push
I am trying to test something there and it is being rejected so I am wondering whether the problem is on my side (where what I created is broken) or is on their side like broadcasting it to bitcoin network instead of luke network.

I just tested this and https://mempool.guide/api/tx does appear to be working.

If you are being turned down it is likely an issue with the tx. Currently common issues with txs are using version 3 txs and also the sighash (some that bitcoin would allow are not allowed on that chain currently), or maybe you have an input that was already spent or a clashing tx in their mempool.

One way you could test to check it is not their issue would be to get a rawtx of some tx that has already been approved on mempool.guide and send it, and if you get a refusal of “missingorspent” then we know that endpoint is working and there is an issue with your tx.

[DaveF]

Has anyone used the BLuke explorer to broadcast a transaction: https://mempool.guide/tx/push

I am trying to test something there and it is being rejected so I am wondering whether the problem is on my side (where what I created is broken) or is on their side like broadcasting it to bitcoin network instead of luke network.

It does work as other have said. Also, if you have a spare machine or VM you can always download knots and just try sending it that way and see what error it spits out.
Also if you are not sure of mempool.guide there is https://mempool.kilombino.com/tx/push

-Dave

[MoparMiningLLC]

I think their intent on stopping all new coinbase pymts for a year is in an attempt to keep new coins out of circulation to make their coin less accessible and to try and drive up price.

Do you really think that this is going to last that long.

So what they're saying is that mining isn't meant to create new coins to increase circulation. Do they not see the irony in this?

maybe their idea is to limit supply and try to drive up price? so that when the coins start releasing after a year - they can dump their own shitcoin and claim they need to hardfork to another algo...