Bitcoin Forum
June 16, 2024, 07:47:31 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: 4 byte size limit for time in block header on: November 11, 2022, 12:25:24 PM
My only thought is to have it reset to 0, but how would you even go about doing that without doing a hardfork?

Hardfork will be needed since node only accept block with 2 hours offset.

I really feel like this is a discussion we should having now rather than latter.

I disagree, year 2106 is 84 years eight from now and most of us won't live until then (unless live expectancy significant improved). There are more pressing concern such as full-RBF, quantum-resistant cryptography and block size.

yep... just found that 2 hour offset feature...

Also, you make a good point. Perhaps in the future there will have to be a mandatory hard fork that makes the hashing algo more difficult, updates the time to 64 bits over 32 bits, along with other things that may come up.

Question is, is a hard fork ethical? From a philosophical view, is it still Bitcoin at that point?



I disagree, year 2106 is 84 years eight from now and most of us won't live until then (unless live expectancy significant improved). There are more pressing concern such as full-RBF, quantum-resistant cryptography and block size.

I plan to live forever or die trying ;-)

But seriously, since it is going to cause so many issues on so many things it's a known and solvable problem.
Put it in a hardfork with some other things that will have to happen and set it be enforced so far in the future that nobody will even think about it. If it's released in 2075 with a 15 year wait to be enforced then you still have another 16 years for people to stop running old clients. And if you are running, what would be 30+ year old software at that point you get to upgrade.

-Dave

Yeah that's a good idea!

Having a waiting period of X amount of years would prove the code to be genuine and battle tested. I would suggest having the code updated in perhaps 2057 with mandatory upgrade by 2107 so that 50 years prior (2009-2057) Bitcoin was tested and we trust it, so in theory, if this fork also holds up for 50 years it could also be considered as a worthy.

In addition, I believe virtually everyone will be on the updated version after 50 years and that their computer's OS won't even be able to install the original Bitcoin Core v0.1. After thinking everything through, this really is the smallest problem Bitcoin really needs to overcome.

Mod note: Consecutive posts merged
2  Bitcoin / Development & Technical Discussion / Re: 4 byte size limit for time in block header on: November 11, 2022, 12:01:42 PM
This has been discussed many times here as recently as a couple of weeks ago:

https://bitcointalk.org/index.php?topic=5418910

It's a known problem, with several discussions in various places on how to fix it. Since it is 84 years off it's not a major concern. The general 2038 bug is probably going be more of an issue since in 80+ years almost nobody is going to be running an OS / software from this era, but there are still things being written today that will be running in 16 years.

-Dave


2038 bug? For signed integers yes; but not unsigned because it is only whole numbers, not negatives ones.

That bug wouldn't effect Bitcoin right?
3  Bitcoin / Development & Technical Discussion / 4 byte size limit for time in block header on: November 11, 2022, 11:33:26 AM
Sunday, February 7, 2106 6:28:14 AM is 4294967294 in UNIX. 4294967294 is the highest int that can fit within the 4 byte limit of timestamp portion of the blockheader.

If there is no room for the timestamp, and the timestamp has to be 5 bytes, how will bitcoin continue to create blocks?

My only thought is to have it reset to 0, but how would you even go about doing that without doing a hardfork? I really feel like this is a discussion we should having now rather than latter.
4  Bitcoin / Mining / Re: Solo mine / sovereign individual on: October 31, 2022, 04:27:09 PM
I just wanted to give an update since I kinda just went AFK.

So the shitcoin event happened and I have almost sold off all my hardware. It feels amazing not supporting that unregulated security. I feel guilty, dirty for mining those coins and selling them to people but idk what to say... I guess in todays space, everyone goes through their shitcoin phase; glad to be out of mine.

I am going to buy an antminer S9 and start working on this...
here is my goal and why I am doing this:

There should be an open source mining software on Github anyone can fork to be fully sovereign and mine to their own node. I do not have the skills to build that, but I will eventually as long as every week I make one step in that direction and don't give up.

Yeah, it would suck if I had an orphan block I guess. But doesn't every miner, even pools, have the same luck? Why would a large pool fork after I find a valid nonce rather than build on this chain? It seems illogical that this would happen. UNLESS, I found a block at the literal same time as another pool and the pools are in their own consensus to help each other by beating my block out by building on the chain the pool contributed to. Nonetheless, this is still a risk for the pools in this little make shift alliance. What happens when two of them find a block at the same time? At the end of the day, blocks are blocks, nonce is a nonce, consensus is consensus; it's all luck no matter how we slice it.

I plan to fork my own BTC to test my get block code to test and see how it performs. Yeah, it isn't the same as being on the network, but at least this lets me see if I can even run a "get block" command.

I fully, in my heart and soul feel like you should be able to click a button in Bitcoin Core that says "start mining", and begin mining with your own full node. YES, it is largely impractical. YES, it won't matter to one single user. But I consider it like going to vote. Will my vote make a difference, probably not; but I still spend my time and resources to vote because I care about democracy (or what little of it we have left in North America).

If everyone used their computers and little piss ant miners to mine, it would largely help Bitcoin as a network and give the community a sense of pride knowing they are doing their part.
5  Bitcoin / Mining / Solo mine / sovereign individual on: June 09, 2022, 09:50:59 AM
I feel like I have to say this to start. I知 not trying to buy a lottery ticket and try my luck. I知 3 years into my Bitcoin journey and after mining shitcoins with my GPU farm, I知 ready for my next step.

I don稚 want to pool mine Bitcoin. I want to be a sovereign individual, buy my s9s, mine with my own node, my own software, my own VPS. I知 not expecting some YouTube video or easy answer. I know I still have a long way to go. I知 learning python now and I know some C++ .

I don稚 care about electricity costs, ROI, blah blah blah. This is my life, and it makes me happy to learn; happiness and fulfillment has no ROI prerequisite to me.

Can anyone give me some good advice on what questions I should be asking? Or where I should start? Thank you
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!