Updates to Stellar Protocol (CAPs) and Ecosystem (SEPs)
Core Development Proposals (CAP) and Stellar Ecosystem Proposals (SEP) are a proper approach of documenting proposed requirements to enhance numerous features of the Stellar Community. These perform much like EIPs and BIPs from the Ethereum and Bitcoin communities respectively. CAPs and SEPs characterize the end result of many discussions that usually happen on the Stellar Developer Google Group.
Earlier than SEPs are adopted, there’s a interval of debate when authors search for suggestions. Two new SEPs which are presently in that part: SEP-0026 and SEP-0027.
SEP-0026: Non-interactive Anchor/Pockets Asset Switch — this SEP defines the usual approach for wallets to work together with anchors, bettering consumer expertise by permitting wallets to work together with anchors while not having the go away the pockets utility. It’s primarily based on and backwards appropriate with SEP-0006. Learn the complete proposal right here.
SEP-0027: Asset Info Server — this SEP gives a further resolution for serving asset data from anchors, on-ramps, and different ecosystem members. It means that anchors or issuers present an
info_server endpoint to complement stellar.toml information. Learn the complete proposal right here.
A scorching matter on the mailing checklist over the previous few days has been a dialogue round Delegated Transaction Signing — yow will discover that right here.
Within the final concern, I discussed a proposal for Multliplexed Accounts, the dialogue for this matter is nonetheless ongoing.
If some of these conversations curiosity you, think about becoming a member of the Stellar Developer mailing checklist!
Over the previous two weeks eight PR’s have been merged on the SEP entrance:
Just one CAP PR was merged: