Author

Topic: What is BIP148? (Read 4286 times)

jr. member
Activity: 42
Merit: 2
December 13, 2017, 05:42:38 AM
#17
Hey folks!
Could you please tell me what does it mean? #bip148 #bip149 are practically everywhere now

BIP148 is a UASF (User Activated Soft Fork) which has been programmed to cause the existing SegWit MASF (Miner Activated Soft Fork) deployment to cause activation in all existing SegWit capable node software (which currently is 80% of the network nodes), so miners must also check blocks prior to their own and ensure that they also signal for SegWit, and only build on those blocks.

to read more:

https://bitcoinmagazine.com/articles/bitcoin-beginners-guide-surviving-bip-148-uasf/

http://www.uasf.co/
sr. member
Activity: 314
Merit: 251
July 12, 2017, 01:59:20 PM
#16
Is core planning on integrating Segwit2x?
No.

If no, what exactly is core planning in regards to a BIP148 chain split or a Segwit2x hard fork, if anything?
Nothing. Many of the Core developers believe that both BIP 148 and Segwit2x will fail. In the event of a chain split, there will be an alert posted on bitcoin.org (there's going to be one anyways because of the possibility of a chain split) with instructions on how to make your node follow the chain you want it to follow. It's very easy to do by using the invalidateblock RPC command.

Thank you.

I am running Luke's BIP148 and mining at Slushpool/UASF since it was available because it seemed that nothing would break the deadlock and the BIP141 activation threshold was ridiculously set to 95%.  I realize I'm in the minority on this, but I hope there's enough of guys like me willing to do something to get Segwit activated one way or another.

Large miners claim they will be running 2x and activating SegWit by July 25, which will moot the point of BIP148.  This is 100% fine by me.

I will return to running the original core after Segwit is guaranteed locked in.  Hopefully the forking hash to 2x will be minimal and we won't end up with CoreCoin and BitmainCoin.



staff
Activity: 3458
Merit: 6793
Just writing some code
July 12, 2017, 11:31:51 AM
#15
Is core planning on integrating Segwit2x?
No.

If no, what exactly is core planning in regards to a BIP148 chain split or a Segwit2x hard fork, if anything?
Nothing. Many of the Core developers believe that both BIP 148 and Segwit2x will fail. In the event of a chain split, there will be an alert posted on bitcoin.org (there's going to be one anyways because of the possibility of a chain split) with instructions on how to make your node follow the chain you want it to follow. It's very easy to do by using the invalidateblock RPC command.
sr. member
Activity: 314
Merit: 251
July 12, 2017, 11:24:27 AM
#14
Is core planning on integrating BIP148 or BIP149?
No

Is core planning on integrating Segwit2x?

If no, what exactly is core planning in regards to a BIP148 chain split or a Segwit2x hard fork, if anything?

sr. member
Activity: 700
Merit: 300
July 12, 2017, 12:23:41 AM
#13
Thanks to everybody up there for reply to this question. I was unaware about the fact too. It seems this is major change in the bitcoin that going to take place. Can anyone explain the after effects of this one? Any related articles please share the reading material if anyone has. Thanks :-)


full member
Activity: 126
Merit: 100
July 11, 2017, 11:18:04 AM
#12
can you advise what hardware wallets would be good to secure your btc on for this BIP148?
For hardware wallet, Trezor is good. If you don't have a large amount of bitcoin, you can go for mobile or desktop wallet too. But make sure have a backup. You can go for BICOIN CORE or BITCOIN KNOTS and can hold your private keys. This would help you in securing your bitcoin in case of possible chain split. Remember to be on the safe side, avoid any transactions on and shortly after August 1st. (How “shortly after” depends on what happens.).

Yes, You can use Trezor.
the service of Trezor is excellent,
it's trusted too. At first you may fetched a little problem bur if you understand proper uses then you find interest.
staff
Activity: 3458
Merit: 6793
Just writing some code
July 09, 2017, 01:09:19 PM
#11
Is core planning on integrating BIP148 or BIP149?
No
sr. member
Activity: 314
Merit: 251
July 09, 2017, 08:19:04 AM
#10
Is core planning on integrating BIP148 or BIP149?

I hate running anything non-core but I really want segwit.
legendary
Activity: 1372
Merit: 1252
July 08, 2017, 10:50:44 AM
#9
I recommend that you watch this video, which is better to understand than reading I think:


https://www.youtube.com/watch?v=QjZk7N7RXfA

If you are just going to hold, then put it in a paper wallet, trezor or any other place where you control the private keys, but do not transact or receive anything until the situation is resolved.

If you want to transact and receive, then run a full bitcoin core node, and another BIP148 core node, annoying yes, but that's the only way to know what you are doing.
newbie
Activity: 12
Merit: 0
July 08, 2017, 10:38:24 AM
#8
I use Trezor, its excellent.
sr. member
Activity: 644
Merit: 250
July 06, 2017, 07:56:35 PM
#7
can you advise what hardware wallets would be good to secure your btc on for this BIP148?
For hardware wallet, Trezor is good. If you don't have a large amount of bitcoin, you can go for mobile or desktop wallet too. But make sure have a backup. You can go for BICOIN CORE or BITCOIN KNOTS and can hold your private keys. This would help you in securing your bitcoin in case of possible chain split. Remember to be on the safe side, avoid any transactions on and shortly after August 1st. (How “shortly after” depends on what happens.).
full member
Activity: 299
Merit: 100
July 06, 2017, 05:33:21 PM
#6
You can use Trezor
newbie
Activity: 24
Merit: 0
June 02, 2017, 10:55:27 AM
#5
can you advise what hardware wallets would be good to secure your btc on for this BIP148?
newbie
Activity: 26
Merit: 0
May 19, 2017, 01:54:38 PM
#4
BIP148 is a UASF that is designed to cause the existing SegWit MASF deployment to cause activation in all existing SegWit capable node software (which currently is 80% of the network nodes). From August 1st, 2017, miners are required to signal readiness for SegWit by creating blocks with the version bit 1.
You can read about it more detailed here: http://www.uasf.co
Both BIPs are proposals for a User Activate Soft Fork.

BIP 148 specifies that Starting on August 1st, all blocks must signal for segwit. This is enforced by having a majority of users and miners running BIP 148 nodes so that that rule is enforced. This will mean that segwit will activate by miner signalling per the current BIP 9 deployment.

BIP 149 is a renewal of the current segwit deployment system except it uses the BIP 8 deployment system instead of the BIP 9 system. This BIP specifies that segwit will activate on July 4th 2018 if it is not already activated by miner signalling beforehand.

Thanks a lot!
staff
Activity: 3458
Merit: 6793
Just writing some code
May 19, 2017, 01:39:18 PM
#3
Both BIPs are proposals for a User Activate Soft Fork.

BIP 148 specifies that Starting on August 1st, all blocks must signal for segwit. This is enforced by having a majority of users and miners running BIP 148 nodes so that that rule is enforced. This will mean that segwit will activate by miner signalling per the current BIP 9 deployment.

BIP 149 is a renewal of the current segwit deployment system except it uses the BIP 8 deployment system instead of the BIP 9 system. This BIP specifies that segwit will activate on July 4th 2018 if it is not already activated by miner signalling beforehand.
member
Activity: 65
Merit: 11
May 19, 2017, 01:37:11 PM
#2
BIP148 is a UASF that is designed to cause the existing SegWit MASF deployment to cause activation in all existing SegWit capable node software (which currently is 80% of the network nodes). From August 1st, 2017, miners are required to signal readiness for SegWit by creating blocks with the version bit 1.
You can read about it more detailed here: http://www.uasf.co
newbie
Activity: 26
Merit: 0
May 19, 2017, 01:28:55 PM
#1
Hey folks!
Could you please tell me what does it mean? #bip148 #bip149 are practically everywhere now
Jump to: