Class A Rule Simplification #36
Conversation
Class A is only intended to provide backwards compatibility & is not used in any of the respective wallet implementations or for any features other than basic simple send. Thus the effort being expended on Class A does not correlate with its utility to the project and this pull is intended to put Class A to bed so we can move onto other more useful work.
…dress & that the two same valued outputs are in addition to the Exodus output.
|
Overall +1; I replied in the forums since your explanation is there as well. |
Tachikoma raised a valid point noting that users have control over outputs but not seqnums, thus the human controlled aspect (outputs) should take precedence in conflicts. Accepted & modified to accomodate.
|
Let's merge this, it's been 6 days since this was created. |
|
I think it should be good this way; I wish one of the other devs would have +1 or -1 this but I think we can always amend it later. |
|
Yes - would be good to get this merged as I think we're all now already Thanks On Mon, Jan 20, 2014 at 11:23 PM, Maran notifications@github.com wrote:
|
Class A is only intended to provide backwards compatibility & is not used in any of the respective wallet implementations or for any features other than basic simple send. Thus the effort being expended on Class A does not correlate with its utility to the project and this pull is intended to put Class A to bed so we can move onto other more useful work.
As discussed with Tachikoma. Further details please see https://bitcointalk.org/index.php?topic=292628.msg4499342#msg4499342