WIP: SPV Generic Reference

[sirdeggen]

This pull request:

Proposes a new standard by creating a new markdown file in the appropriate directory and requests discussion and assignment of a BRC number

Summary

A more generic definition of SPV which doesn't refer to any specific implementation - as a clear reference definition.

The current BRC-9 is too implementation specific, while this should cover all known implementations, and more succinctly defines what would constitute SPV from a higher level.

[sirdeggen]

@ty-everett please consider renaming BRC-9 something more specific to Babbage stack, I've tried to outline a non specific version here for the sake of explaining to other developers who are not familiar with your stack or SPV generally.

Let's discuss here before merging anything.

[ty-everett]

As discussed in RFC-3, I don't really think titles need to be unique, as these are just notes from different people. The notes can be on the same topic, such as SPV. As we get more of these documents, de-conflicting titles would be a significant undertaking. Reference should be made to the document number rather than the title.

If you disagree with this reasoning then I'm happy to change it, but I don't think all documents will necessarily have differentiated titles going forward. Otherwise, this document looks good from first glance, and I do like the idea of a self-contained explanation.

[sirdeggen]

Your argument is valid, agreed. Adding to the summary page and then merging as is.

[sirdeggen]

Updating to 67