@jonny1000 : Thanks for sharing that perspective and what I view as a pretty useful taxonomy.I think the above illustrates what many mean by a "safe" or "dangerous" hardfork. "Safe" does not necessarily mean two chains cannot survive.
I'm also of the opinion that it involves risk which could be mitigated by a cleaner fork (of type 3)The characteristic that people lose funds makes this method dangerous
I don't see this as a problem but an advantage - it is tolerant toward the old chain.However the new chain can never wipe out the old chain.
I agree, it may be good the new chain cannot wipe out the old chain. What I am trying to emphasize is the asymmetric nature of this, the old chain can wipe out the new one. That is the problem.I don't see this as a problem but an advantage - it is tolerant toward the old chain.
This has already happened. Everyone already wants larger blocks. The question is just how to do it in a safe way."This is how I visualized such a [BU]hard fork playing out. First the miners will begin signalling. Once there is enough hash power signalling 2mb, we would begin to see a number of large bitcoin companies (coinbase, bitpay, wallets, dark markets etc...) begin to promote that they are willing to accept bigger blocks.
Implement this in code. What is the disadvantage of implementing that in code?After a miner then becomes sufficiently satisfied that the opportunity of mining a bigger block is > the risk of the network rejecting it
Why not get rid of the asymmetric advantage to the original side, like Ethereum did? I appreciate you do not see the risk. However, what is the downside of removing the risk?This isn't Etheruem
Short question to the BU guys:
There was the call to translate the website to different languages (which is a good idea imho, a lot of people still read Bitcoin stuff in their native language), is there a coordination which languages are already done/being worked on?
Another idea: Imho it would be wise to have the tutorials/manuals about how to set up a node and use the json RPC on the website as well. As of today you can only get the info at bitcoin.org afaik. And I have seen a lot of new users to Bitcoin, who want to "help the ecosystem" to just run Bitcoin core because that's still the "current client" for them. Imho it is good to take away the advantages of bitcoin core in the "information warfare" from them. Make it easier for people to get into Bitcoin without getting in touch with core.
I read your Pull Request@github. Congratulations, good translation!I could do a German translation if nobody else is crazy for doing that.
Help me out here...
My understanding of LN is not especially solid so I may be making a mistake here...
So to open a LN channel, I time-lock some number of Bitcoins. Then the LN nodes between me and the endpoint generate bitcoin transactions which incrementally increase the amount I am to pay the endpoint but this transaction is not published to the Bitcoin network. Both I and the endpoint receive this transaction (the endpoint uses this to meter services or whatever it is providing to me. Either of us can close the channel at any time by publishing this transaction to the Bitcoin network.
Is there any reason this whole thing couldn't be coordinated directly from my wallet software and a connection directly to the endpoint's accounting system? Why do I need these funky middlemen doing stuff in between?
Again, sure I'm missing something but I have a cold...
1MB supporter
Thanks for reviewing it!I read your Pull Request@github. Congratulations, good translation!
Hehe, yeah I wasn't so sure about it, "betreiben" was the first word coming to mind but I thought it didn't sound great than. But now I think you're right, I'll fix it.Just two things: You translated "main
tain" (a satoshi client) to develop (entwickeln in German). BU is already in use, only the beta-version of 12.1 is in development. I would prefer to translate maintain with "
betreiben" or a similar literally translation.
Yes, I think you can guess that I found the short text about how Unlimited works the hardest part to translate. I'm not sure about leaving it out completely though. Maybe you are right and it is good enough to write, that a failsafe mode exists on the front page instead of "explaining" it. On the other hand, users actually "have to" adjust the block depth..The translation of the BU´s "failsafe mode" is as ununderstandable as in the english original, with the exclusion of the term "failsafe mode". This maybe gets potential user even more confused.
I wasn´t crazy for doing a German translation, because i can´t explain the BU Client including the "failsafe mode" in one paragraph.
Maybe we should exclude the explanation of the failsafe mode from the text? Instead we could just write that a failsafe mode exists for the case of a chain spit. It justs discourage interested users to mention, that the user have to adjust a "block depth" to potentially follow another fork of the chain.