-
Notifications
You must be signed in to change notification settings - Fork 363
create a spec for the stellar protocol #187
Copy link
Copy link
Open
Labels
enhancementCAP that adds or changes functionality as opposed to a fix.CAP that adds or changes functionality as opposed to a fix.help wantedOpen especially for those who want to write a CAP/SEP!Open especially for those who want to write a CAP/SEP!needs draftThis an issue that has no corresponding draft, and as such has not entered the CAP/SEP process.This an issue that has no corresponding draft, and as such has not entered the CAP/SEP process.
Description
Metadata
Metadata
Assignees
Labels
enhancementCAP that adds or changes functionality as opposed to a fix.CAP that adds or changes functionality as opposed to a fix.help wantedOpen especially for those who want to write a CAP/SEP!Open especially for those who want to write a CAP/SEP!needs draftThis an issue that has no corresponding draft, and as such has not entered the CAP/SEP process.This an issue that has no corresponding draft, and as such has not entered the CAP/SEP process.
SCP is fairly well documented and the XDR schema files describe unambiguously the data structures used. However, the logic for applying transactions is mostly undocumented.
If someone would attempt to build a stellar-core compatible alternative, that fully implements the stellar protocol, the only complete source of truth at their disposal is the stellar-core codebase.
This might block innovation and diversification in stellar implementations.
For the sake of comparison, the ethereum yellowpaper fully defines the ethereum protocol.