Except that after the fork both chains will likely tank in price to the point it would be cheaper to buy BTC+BCC after rather than BTC before
this would have only been true IF BCC had any kind of half decent support from the community. currently it has nearly no support. the only people supporting it is the 1 miner that is behind it, also the pocket behind this, the rest are spamming. and don't confuse this with big blocks versus SegWit debate. this is something very different. this is creating an altcoin without any consensus from bitcoin. |
|
|
|
i don't know which one to choose  obviously the profit that buying bitcoin and sometimes trading it gives me is a big motivation. but i also like the freedom and privacy that using bitcoin can give me. the fact that i can easily go on and buy anything and pay for anything i want (if they accept BTC of course) without needing to register, fill in forms and giving them my identity or credit card,... |
|
|
|
|
like Gollum in Lorn of the Rings. i sit on top of a rock every night and i start caressing my paper wallet and mutter these words: "It came to me, my own, my love, ... my precious"
|
|
|
|
is everyone so excited about the BIP91 activation with 93.1% and the price rising ridiculously fast that they forgot BIP141 (bit 1 version, or you may recall it as original SegWit thingy) is increasing in support? where are the watchers  lets see, here is the list: Antpool
Batpool
BitClub
Bitcoin.com
BitFury
Bixin
BTC.com
BTC.TOP
BTCC
BW pool
F2Pool
GBMiners
Kano CKPool
Slushpool
ViaBTC hope i didn't miss anything. source: https://coin.dance/blocks(i believe this is almost 91% of the total hash power) current percentage: 76.4% so far. also it would be great if someone could give us the time frame of this signaling. is it the same as BIP91 since it is the continuation of that or is it the 1 difficulty period? |
|
|
|
it feels good to see this topic after about a month and look back at all the drama that has happened during this time! and we are finally here, BIP91 locked and loaded  lets just hope we can get this done and over with hopefully with least amount of bloodshed and as fast as possible, so that we can focus on the future and things that matter... |
|
|
|
it goes down, they ask why, it goes up, they ask why again. just buy the damn thing already take a look at the charts and see the swings, they all end up being a temporary bump on the road leading to the final rise. and then look at all the potential bitcoin has. it is still the same good ol' decentralized payment system with very limited supply. |
|
|
|
signalling means changing a variable. this variable is the block version. to support BIP91 which SegWit2x implemented you change that variable to 0x20000010 and to support more than one BIP you add the bits to this number for example to support both SegWit2x (BIP91) and SegWit you change it to 0x20000012 (addition of bit 1 and bit 4 if i am not mistaken) SegWit alone is 0x20000002 for these stuff you don't need to run a specific client, you just edit a single line of code. you may also run btc1 client and change your useragent to something different to mask the fact that you are running that client, maybe to protect against getting DDoSed  No. Changing just one bit is not enough to be safe with the BIP91 fork because part of running BIP91 means orphaning any blocks that aren't signalling segwit once support is over 80% @-ck what client you running? Bitnodes shows only 64 btc1 clients while BIP91 is almost 65% at xbt.eu. Almost no one is running Garzik's client just signaling BIP91 it seems.
I run a custom coin daemon but the extra code for BIP91 comes from here: https://github.com/segsignal/bitcointhanks for the explanation. what i wrote, i did with only activation in mind not all that comes after it locks in. i guess i missed quite a bit  |
|
|
|
if you take time and read the BIP instead of spamming nonsense ...
BIP148 is not in Bitcoin Core. BIP91 is not in Bitcoin Core. SegWit only activate when Blocks have the good version integrated. Bitcoin Core (the 79% of the network) only recognize the BIP9 block version ( 2x....02, not 2x....10 and not 2x....12). what the hell does any of these mean there is no Bitcoin Core, there is only Bitcoin. there is no Good Version, there is only block version. and these versions are used to "vote" exactly like last time for previous soft fork to activate P2SH (or you may know it as multisig). these versions show support for proposals. all these different BIP numbers are all activating the same thing. which is Segregated Witness none of them are different in the end result the only difference is in the route they take to reach that end result. bitcoin core is not the network, Bitcoin is the 100% of the network. what you see as bitcoin core and all the different names are only clients you can make one yourself too and call it Meuh. i am running my own client and call it CustomClient 0.9.0 none of them are different, they are all enforcing the same consensus rules we know as bitcoin. with little modification to other stuff. and this has nothing to do with activating SegWit! because core is compatible with SegWit! |
|
|
|
@-ck what client you running? Bitnodes shows only 64 btc1 clients while BIP91 is almost 65% at xbt.eu. Almost no one is running Garzik's client just signaling BIP91 it seems.
signalling means changing a variable. this variable is the block version. to support BIP91 which SegWit2x implemented you change that variable to 0x20000010 and to support more than one BIP you add the bits to this number for example to support both SegWit2x (BIP91) and SegWit you change it to 0x20000012 (addition of bit 1 and bit 4 if i am not mistaken) SegWit alone is 0x20000002 for these stuff you don't need to run a specific client, you just edit a single line of code. you may also run btc1 client and change your useragent to something different to mask the fact that you are running that client, maybe to protect against getting DDoSed |
|
|
|
I guess this means the chain could fork 3 times, with the BIP148 or SegWit soft fork, then SegWit2x's version of SegWit intentional soft fork, then the SegWit2x hard fork.
NO. i don't think so. because there is no "SegWit2x version of SegWit" there is only 1 SegWit. if SegWit2x locks in SegWit successfully then all the rest of them (BIP141, BIP148) will see SegWit activated. it is the same thing but with different thresholds. and majority of nodes are already running Core clients which has no problem with SegWit. split will only happen if after SegWit2x activated SegWit, some miners go against SegWit and never upgrade. and these "some miners" based on the support will be less than 14%. the other one about hard fork will be the same story. if the hashrate is low and nodes don't go for it then there will be a split. |
|
|
|
|
first let me tell you that fees are not $2.5, in the past 8 years they were only that much for about 3 months.
it is impossible to do what you propose, it opens up ways for easier attacks. block size is limited and it should be limited (to whatever number) and in case fees were capped at some very small number, it makes spam attacking bitcoin super cheap hence easy.
the limited block space will be filled with cheap spam.
with the way fees are now, an attacker needs to spend a lot of money to spam attack because fees keep rising as the attack continues happening. so it has to come to an end eventually.
you proposal may work for an altcoin and it will because the usage of an altcoin is very limited and small, and there is no incentive for spam attacking any of them.
|
|
|
|
|
i don't know what you mean by profitable but about your approve or disapprove part of your question i have to say SegWit2x is 2 parts and you should not confuse these.
part 1 which is starting now is about activating SegWit, the same thing that has been waiting to be activated for a long time.
part 2 which won't start for some months (i am not yet sure about 3 or 6 months) is a hard fork to increase block size to 2 MB. that is new and different.
the first part is compatible with the rest of the network and it is a soft fork so you don't have to upgrade. and if you are running a Node it will recognize the fork.
but the second part is not. and many are against it. which may cause some troubles when its date comes.
|
|
|
|
Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want.
don't compare a UASF real modified & verified Bitcoin Core version only with a BIP0148 identified strategy ... and a dark version launched by a mining sector (with 61% of the mining power of the whole Bitcoin network). Segwit2x is not a BIP. BIP0091 is not a BIP recognize by Bitcoin Core (find BIP91 here ? https://bitcoincore.org/en/bips/ = NO). We have, now, a Ethereum Split possibility : ETH & ETC possibility. A tangible Fork possibility. there will be NO split. stop spreading FUDBIP91 is not activating a weird unknown or new thing. the SegWit that will be activated via BIP91 will be the same SegWit that other BIPs you have in mind will activate. if you take time and read the BIP instead of spamming nonsense here you will understand that this BIP is only changing the variables needed fro activation like lowering the 95% to 80% for instance. |
|
|
|
It is easy enough to see if Bitmain is following through on their promise. They have to switch over to the btc1 client and you can see btc1 nodes at bitnodes signaling either Satoshi:1.14.3 or Satoshi:1.14.4. miners have never ran clients provided to them, they have always been running a self modified code. and that Satoshi:1.14.3 thing is just a string that can you change and tell the network as your user agent. you may very well be running anything. this means they don't switch, they just modify their code (merge the changes in their code). and besides who cares what the F.ing client they run, all that matters is the blocks they mine. |
|
|
|
|
i am sorry you sold your coins because of panic at below $1800. next time don't panic dump bitcoin, either sell before the drop starts or make sure to buy when the dip is at its lowest price.
your FUD won't solve the mistakes you have made.
|
|
|
|
|
i am like 99% sure that it has nothing to do with fees. mempool has been empty and doesn't matter how low a fee you pay, your transaction should have been confirmed in less than an hour or a couple of minutes if you are lucky.
Multibit doesn't give bad fee suggestions anyways.
you either spent an unconfirmed transaction, or it was sent and confirmed but probably LBC never credited your account. (that is my guess unless i can see the tx ID)
|
|
|
|
Stolen work:  either i am confusing a lot of things or this picture is very wrong! so please correct where i am wrong: 1. BIP91 does not combine anything. it is a separate consensus layer BIP for SegWit deployment with less than 95% and also has the version bit part which both BIP148 and SegWit2x implement this. BIP91 also has nothing to do with the hard fork! 2. SegWit2x's hard fork is not for 6 months after the activation of SegWit, not in November. 3. i don't get this sentence: "any of these except SegWit2x and BIP91 could result in a hard fork"! you don't potentially result in a hard fork you either have a hard fork or not. SegWit2x is a soft fork for now and hard fork later. BIP91 is a soft fork BIP148 is a soft fork BIP141 is a soft fork split can also be caused by any of these without majority support! |
|
|
|
|
i am not sure how long will it take but it will surely be before August 1st that we can know with good confidence what the outcome of that date will be. so far the SegWit2x seems to be the proposal to get the SegWit finally activated because of the large mining support it has.
but generally speaking bitcoin will never be safe. there is always people who will use any opportunity to spread FUD for many different reasons like being a government agent or an altcoin shill or a desperate shorter. you can easily notice them if you do a little research about things they say and see past the lies. and that is when bitcoin becomes safe. when everyone starts researching instead of taking what strangers tell them online.
|
|
|
|
2. the node goes through a series of hard coded IP addresses to connect to one of them. these IP addresses are for reliable, always up, nodes (that is why they are hard coded anyways). you connect to one of them.
Official Bitcoin Core ... Solution :  2017-07-08 12:14:22 Loaded 58421 addresses from peers.dat 382ms (i am not an expert but) it seems like this is not a solution this is how the client always worked. this seems to be the list of peers (nodes) that you have connected to so far. your node saves them after successful connection or when it receives the list from another node. the solution is what bones said, you edit that part about Seeds out. bitcoin 101 for newcomers (apparently): 1. you download your bitcoin node client and start it up 2. the node goes through a series of hard coded IP addresses to connect to one of them. these IP addresses are for reliable, always up, nodes (that is why they are hard coded anyways). you connect to one of them. 3. end of story. you are now connected to the bitcoin p2p network and receive the rest of the IP addresses from the nodes that you are connected to via a specific message. 1. when you open your node again. restart or whatever. your node has saved all the IP addresses of nodes that it successfully connected to before. now it has a bigger list. where is this DNS thing you ask, it is only a fallback method in case your node failed to connect to any of the nodes (hard coded IPs which are reliable nodes that are always up and responding) or your list of previously connected nodes. it connects to the next source to find IP addresses of the other nodes to connect to. in other words the "casual user" will probably never even use them! True, but for the extra paranoid, they are not bound to use any of DNS seeds as a failover. They can still download the source code for segwit2x, modify the DNS seeds any way as they see fit, and compile. Easy fix. Oh well, I don't run a full node anyway. I just use either Trezor's web interface or interface with Electrum. A full node is not really needed by me to access my 1.8 BTC. the extra paranoid run their own code, they don't trust a downloaded code from anyone like me "trying" to do it. i didn't even know these seeds existed! i just have the hard coded IPs hard coded in my own thing and connect to one without any trouble so far. |
|
|
|
I think it's starting to sink in with some people that FrankenSegwit may not come out with sound code; and with it's planned Hardfork, come November, it's just kicking the can down the road a little for another major forking threat.
It has horrible code. One of the hardcoded seeds is basically an anti-privacy (chain analysis) company by Garzik.  Easy fix. All one has to do is download the source code, delete the offending seeds and compile yourself. Of course, the casual user probably isn't going to do that. I'm worried about the other code. Since I only have a rudimentary understanding of C++, I'm afraid it's way beyond my capability to do an analysis. bitcoin 101 for newcomers (apparently): 1. you download your bitcoin node client and start it up 2. the node goes through a series of hard coded IP addresses to connect to one of them. these IP addresses are for reliable, always up, nodes (that is why they are hard coded anyways). you connect to one of them. 3. end of story. you are now connected to the bitcoin p2p network and receive the rest of the IP addresses from the nodes that you are connected to via a specific message. 1. when you open your node again. restart or whatever. your node has saved all the IP addresses of nodes that it successfully connected to before. now it has a bigger list. where is this DNS thing you ask, it is only a fallback method in case your node failed to connect to any of the nodes (hard coded IPs which are reliable nodes that are always up and responding) or your list of previously connected nodes. it connects to the next source to find IP addresses of the other nodes to connect to. in other words the "casual user" will probably never even use them! |
|
|
|
|
Show Posts
