You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SEP27 was proposed to create a standalone, forward-compatible method for serving asset information from anchors, on-ramps, and other ecosystem members. It solves problems such as localization of asset information, allowing for more than one transfer protocol, and more forward compatibilty.
The text was updated successfully, but these errors were encountered:
msfeldstein
added
bug
CAP that addresses broken behavior in the current protocol.
and removed
bug
CAP that addresses broken behavior in the current protocol.
labels
Dec 4, 2019
Personally I think this is a good change that takes a lot of the shared infrastructure between different SEPs and puts it all in one place, in a way that can support multiple protocols, including people who need to define assets without actually supporting any transfer protocol.
This issue is stale because it has been open for 30 days with no activity. It will be closed in 5 days unless the stale label is removed, or a comment is posted.
SEP27 was proposed to create a standalone, forward-compatible method for serving asset information from anchors, on-ramps, and other ecosystem members. It solves problems such as localization of asset information, allowing for more than one transfer protocol, and more forward compatibilty.
Please discuss thoughts on this proposal here
https://github.com/stellar/stellar-protocol/pull/474/files
The text was updated successfully, but these errors were encountered: