server is down, or taken down.
The site is back up (it has been back up for a couple of hours now). 
Topic: Bitcoin blockchain fork monitor (Read 3718 times)
server is down, or taken down.
I found this alternative https://cash.coin.dance/blocks for anyone who cares
I found this alternative https://cash.coin.dance/blocks for anyone who cares
Bump.
So when is a fork scheduled?
They are all listed on the site.There is no "schedule" for forks, only the time when the forks can begin deployment and when it expires. Forks are not deployed at a set date.
So when is a fork scheduled?
It seems to be having some loading issues ill check on this a bit later.
Good luck with your project. Seems like a cool idea but why would we want to monitor blockchain forks for?
There will be some forks in the future to roll out new features such as Segwit or a larger block size. These all require forks. The point of the site is to monitor blockchain so that we know when/if a fork is going to happen. 
Good luck with your project. Seems like a cool idea but why would we want to monitor blockchain forks for?
Pretty snazzy... you should offer an "alert me" function so that people can be alerted via email, etc when there's a change. You could charge a small fee for it, like 0.0001 btc, etc.
Hmm.. That's a good idea. I'l see if I can get something like that setup to alert people about updates like fork status changes. 
Pretty snazzy... you should offer an "alert me" function so that people can be alerted via email, etc when there's a change. You could charge a small fee for it, like 0.0001 btc, etc.
Very cool project.
It's damn cool like we have) to develop in the same direction
We look to your project
thank you
We look to your project
thank you
Block height in the coinbase transaction
- wow didn't know about this one. have no idea where this may be useful, perhaps bug forks or spv nodes to make it easy compare block heigts? who knows. thanks
I'm not entirely sure why they did that, but it does make indexing blocks easier and tracking forks.- wow didn't know about this one. have no idea where this may be useful, perhaps bug forks or spv nodes to make it easy compare block heigts? who knows. thanks
what about segwit? lightning stuff is there but lack of info how the use of the nop code, how segwit could be added to header and so on
Segwit doesn't replace any NOPs and it doesn't change the block header. The specs for segwit deployment have not been decided yet.
Block height in the coinbase transaction
- wow didn't know about this one. have no idea where this may be useful, perhaps bug forks or spv nodes to make it easy compare block heigts? who knows. thanks
what about segwit? lightning stuff is there but lack of info how the use of the nop code, how segwit could be added to header and so on
- wow didn't know about this one. have no idea where this may be useful, perhaps bug forks or spv nodes to make it easy compare block heigts? who knows. thanks
what about segwit? lightning stuff is there but lack of info how the use of the nop code, how segwit could be added to header and so on
Site down
I have to take it down for a little bit to change the server since the other one kept crashing.Edit: It's fixed now.
I created a project which monitors the blockchain for all of the intended hard and soft forks. It only supports forks that are assigned a BIP number and have a not insignificant fraction of the Bitcoin Community actively pursuing the fork. The website is http://www.btcforkmonitor.info/.
The current fork listing is as follows. It will be updated as new forks come out.
Pending:
The current forking method is as follows. This will also be updated as new fork mechanisms are used.
If you have any suggestions and improvements that I can make, please post them here or pm me. Feedback is welcomed.
Also, sorry for the crappy web design, I suck at web design.
Source code
The source code is hosted on github at https://github.com/achow101/ForkMonitor. The project is written in Java and uses Google Web Toolkit, ObjectDB, ZeroMQ, and bitcoind.
License
This project is licensed under the GNU Affero General Public License. See the LICENSE file for more details.
Donations
If you would like to support and donate to me, please send me some Bitcoin to 15zMaUYjxyRv9yUuGRuTbk7DZYYG8NSKnJ.
The current fork listing is as follows. It will be updated as new forks come out.
Pending:
- BIP 68, 112, 113 (CSV Fork)
- BIP 109 (Classic fork)
- BIP 34 (Block v2)
- BIP 65 (CLTV)
- BIP 66 (Strict DER sigs)
- BIP 101 (XT)
The current forking method is as follows. This will also be updated as new fork mechanisms are used.
- BIP 9 (versionbits)
- BIP 34 (Double threshold supermajority)
- BIP 109 (Whatever BIP 109 happens to be using which is a mix of BIP 101 and BIP 9)
If you have any suggestions and improvements that I can make, please post them here or pm me. Feedback is welcomed.
Also, sorry for the crappy web design, I suck at web design.
Source code
The source code is hosted on github at https://github.com/achow101/ForkMonitor. The project is written in Java and uses Google Web Toolkit, ObjectDB, ZeroMQ, and bitcoind.
License
This project is licensed under the GNU Affero General Public License. See the LICENSE file for more details.
Donations
If you would like to support and donate to me, please send me some Bitcoin to 15zMaUYjxyRv9yUuGRuTbk7DZYYG8NSKnJ.
Jump to: