-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition period to disable BIPs? #8
Comments
I'm not sure what you're talking about. Bitcoin Improvement Proposals is merely a standardised way of documenting cross-implementation improvements to Bitcoin. It's not software... there's nothing to disable. |
Here is the testnet issue btc1#65 I don't know much of the details, but from what I've gathered someone with mining power came to testnet and caused problems since he had so much mining power he accidentally activated one of the BIPs. So I was wondering if there is anything apart of changing PoW that needs to be though about in case someone with bad intentions pointed a lot of mining power into the fork. |
That was just due to incompetence (we even warned them about it, and suggested a better solution...). The closest thing that would affect us would be if we ended up changing the PoW algorithm and didn't have any mining software that could actually mine it. But BFGMiner is modularised so it's easy to add algorithms - mostly copy/paste from the hardfork code, really. |
Hi,
regarding the recent events on testnet, is there a plan to temporarily disable BIPs in case an attacker points mining power into the network in an effort to cause havoc?
Is this scenario being analysed / What needs to be addressed?
The text was updated successfully, but these errors were encountered: