Match specw/code append/replace not yet supported

[zathras-crypto]

No description provided.

[ghost]

+1 this adds more specificity for implementors

[dexX7]

What happens in such a case? Are those transactions currently invalidated?

[marv-engine]

@zathras-crypto how is append/replace not supported by the code? Other than validity checking, it's an example of what I have referred to as an application-advisory attribute.

[zathras-crypto]

Property Type >2 currently invalidated yes.

@marv, not yet implemented is the same as unsupported. Masterchest for
example invalidates property types >2. There is no current code for
notifying the user at the UI layer of a replace or append. Masterchest is
end of life so won't be updated to support this.

If I recall correctly SP was built on multiple codebases and dragged to
consensus in about 3 and a half weeks, those types of timeframes dictate
prioritization, and if memory serves replace/append was put on the "not
important can wait until a later time" list.

Fairly low hanging fruit to do replace/append in Core (when it is the sole
implementation, not until).

Thanks
Z

On Tue, Jul 8, 2014 at 6:56 AM, Marv Schneider notifications@github.com
wrote:

@zathras-crypto https://github.com/zathras-crypto how is append/replace
not supported by the code? Other than validity checking, it's an example of
what I have referred to as an application-advisory attribute.

—
Reply to this email directly or view it on GitHub
#221 (comment).