Stop working when breaking changes are detected

[ripper234]

This issue on the spec suggests a way to embed version numbers into the blockchain.

Version in format X.Y.Z, where X,Y,Z are numbers.

When X is incremented, the client needs to IMMEDIATELY STOP processing anything.
When Y is incremented, the client needs to strongly recommend to the user to stop processing further messages.
When Z is incremented, the client needs to recommend to the the user that they update the client (but it's not mandatory).

mastercoin-tools needs to at least honor changes to the X component. Changes to Y component should probablly trigger a high priority log message.

[dacoinminster]

Note that we have not yet decided to do this. Peter and I are worried that
this method is too centralized. Also note that each transaction already has
a version number, and an address which sends a new/unrecognized version
number should have all its balances invalidated. This is already in the
spec, but we haven't done any enforcement that clients do this or any
testing of it yet.

On Tue, Apr 1, 2014 at 9:33 AM, Ron Gross [email protected] wrote:

This issue on the spec https://github.com/mastercoin-MSC/spec/issues/111suggests a way to embed version numbers into the blockchain.

Version in format X.Y.Z, where X,Y,Z are numbers.

When X is incremented, the client needs to IMMEDIATELY STOP processing
anything.
When Y is incremented, the client needs to strongly recommend to the user
to stop processing further messages.
When Z is incremented, the client needs to recommend to the the user that
they update the client (but it's not mandatory).

mastercoin-tools needs to at least honor changes to the X component.
Changes to Y component should probablly trigger a high priority log message.

Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.