Updates to Stellar Protocol (CAPs) and Ecosystem (SEPs)

Core Advancement Proposals (CAP) and Stellar Ecosystem Proposals (SEP) are a formal way of documenting proposed standards to improve various aspects of the Stellar Network. These function similar to EIPs and BIPs from the Ethereum and Bitcoin communities respectively. CAPs and SEPs represent the culmination of many discussions that often take place on the Stellar Developer Google Group.

Active Discussions

Before SEPs are adopted, there’s a period of discussion when authors look for feedback. Two new SEPs that are currently in that phase: SEP-0026 and SEP-0027.

SEP-0026: Non-interactive Anchor/Wallet Asset Transfer — this SEP defines the standard way for wallets to interact with anchors, improving user experience by allowing wallets to interact with anchors without needing the leave the wallet application. It is based on and backwards compatible with SEP-0006. Read the full proposal here.

SEP-0027: Asset Information Server — this SEP provides an additional solution for serving asset information from anchors, on-ramps, and other ecosystem members. It suggests that anchors or issuers provide an info_server endpoint to supplement stellar.toml files. Read the full proposal here.

A hot topic on the mailing list over the past few days has been a discussion around Delegated Transaction Signing — you can find that here.

In the last issue, I mentioned a proposal for Multliplexed Accounts, the discussion for this topic is still ongoing.

If these types of conversations interest you, consider joining the Stellar Developer mailing list!

Merged PRs

Over the past two weeks 8 PR’s have been merged on the SEP front:

Only one CAP PR was merged: