Skip to content
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

[spec] Add specification for May 2020 Upgrade #444

Merged
merged 5 commits into from Mar 3, 2020

Conversation

@Mengerian
Copy link
Contributor

Mengerian commented Feb 15, 2020

No description provided.

@Mengerian Mengerian force-pushed the Mengerian:spec-2020-may branch from 9cd6bda to 54f50b5 Feb 15, 2020
@Mengerian Mengerian changed the title [spec] Add specification for Nov 2020 Upgrade [spec] Add specification for May 2020 Upgrade Feb 15, 2020
@Mengerian Mengerian force-pushed the Mengerian:spec-2020-may branch from 54f50b5 to 98d79b6 Feb 15, 2020
@Mengerian Mengerian force-pushed the Mengerian:spec-2020-may branch from 98d79b6 to cc21f83 Mar 3, 2020
spec/2020-05-15-upgrade.md Outdated Show resolved Hide resolved
spec/2020-05-15-upgrade.md Outdated Show resolved Hide resolved
spec/2020-05-15-upgrade.md Outdated Show resolved Hide resolved
@Mengerian Mengerian merged commit 279e1fa into bitcoincashorg:master Mar 3, 2020
@Mengerian Mengerian deleted the Mengerian:spec-2020-may branch Mar 3, 2020
@ftrader

This comment has been minimized.

Copy link
Contributor

ftrader commented Mar 4, 2020

I consider the merge of this PR , sneaking in the addition of IP enforcement cc21f83 which is not even well specified, and the merging of the PR by the same person who originated it, as something that should have never happened.

I will raise an issue and a pull request to fully revert the inclusion of the IFP component for May's upgrade - it does NOT have community consensus in any way.

As a personal note, I think this is disgraceful behavior by the stewards of this repository.


## Infrastructure Funding Plan

The purpose of the Infrastructure Funding Plan (IFP) is to provide funding to development projects working on common Bitcoin Cash infrastructure. If activated, it enforces that 5% of the block reward is spent to one of a set of specified addresses. The IFP has the following features:

This comment has been minimized.

Copy link
@BigBlockIfTrue

BigBlockIfTrue Mar 4, 2020

Contributor

There is no agreement to include the IFP in the official Bitcoin Cash specification and we are already way past the feature-freeze deadline. NACK

@ShadowOfHarbringer

This comment has been minimized.

Copy link

ShadowOfHarbringer commented Mar 4, 2020

Two issues:

  1. It is way past code freeze deadline

  2. It is unacceptable for any single developer to re-define what "Bitcoin Cash" is without any kind of agreement among neither miners, community, developers or popular service providers.

This behavior is contemptible.

NACK.

@molecular

This comment has been minimized.

Copy link

molecular commented Mar 4, 2020

NACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

7 participants
You can’t perform that action at this time.