Stellar Dev Digest: Issue #49

Anchor basics webinar, Stellarport’s new look, and user-friendly key management on Stellar.

Hey everyone! Welcome to another issue of the Stellar Dev Digest, a weekly recap of all things related to the development of the Stellar Network.

What is Stellar? Stellar is a platform that connects banks, payment systems, and people. Integrate to move money quickly, reliably, and at almost no cost.

News & Posts of the Week

• ⚠️ There is currently an email scam going around encouraging users to participate in staking on Stellar. Do not interact with this email. There is no such thing as staking on Stellar. It is an attempt to steal your private key and your funds. Protect your account. Read our security guide.
• 🛠️ Tyler is hosting a developer-focused workshop on tomorrow, June 30 at 2PM EDT to explain SEP24, and to show how easy it is for a wallet to implement interactive deposits and withdrawals using anchor services. — Sign up for it here.
• Director of Partnerships at SDF, Boris Reznikov, released a blog post recapping the Anchor Basics webinar SDF hosted a couple of weeks ago. If watching webinars isn’t your thing, this is the resource for you. — Read it here.
• Last week, Principal Software Engineer at SDF, Leigh McCulloch, gave an Engineering Talk on SEP-30. Key management in crypto wallets is not typically user-friendly, and that creates a major barrier to widespread adoption. SEP-30 defines an approach that enables an individual to regain access to a Stellar account after the individual has lost their private key. — Listen to it here.
• Tyler and I hopped on the mic last week to discuss the latest news in the Stellar ecosystem including the Vibrant beta launch, this round of the Stellar Community Fund, and more. — Listen to it here.
• CEO of Tangem, Sergio Mello, shows off the new Tangem and Lobstr Vault collaboration by sending $30,000 using a Tangem and Lobstr Vault multi-signature scheme. — Watch the demo here.
• You can now send money instantly to Nigeria from South Africa using the Stellar-based Uhuru WhatsApp Wallet. You can learn more about Uhuru and how they’re building on Stellar here.

Application of the Week

This week I’m featuring Stellarport — your portal to all assets on the Stellar network!

Stellarport is a platform that combines an easy-to-use noncustodial wallet, Stellar decentralized exchange trading, and an asset discovery engine. Remember: there are thousands (7,876 to be exact) of assets on the Stellar network, and interfaces like Stellarport make finding, sending, and trading those assets significantly easier.

Stellarport has been around for a while, but has recently received quite a face-lift in preparation for Protocol 13. Some of the new changes include:

• a revamping of the UI/UX
• a new assets search engine
• the ability to trade Stellar-based non-fungible tokens

While the new changes aren’t completely finished, you can begin messing around on the new interface and read about the pending updates here.

Releases and Updates

The Go SDK’s txnbuild v3.2.0 has a new release. The previous version allowed txnbuild to create transaction envelopes which are accepted by both Protocol 12 and Protocol 13. In this release, txnbuild will only create transactions that are accepted by Protocol 13.

The Python SDK version 2.6.1 has been released and includes breaking changes. Previously, the SDK defaulted to building transactions compatible with Protocol 12, now these transactions are built to be compatible with Protocol 13.

SEP-0033: Identicons for Stellar Accounts has been merged as a Draft! If you have any questions or concerns regarding this new SEP you can find the mailing list conversation here. Lobstr also has a blog post explaining the identicons and their implementation here.

⚒ ️Subscribe here to get Stellar maintenance reminders and incident reports sent straight to your inbox.

Active Discussions

💬 This week two CAPS made it in to the Final Comment Period: CAP-0023 and CAP-0033!

Quick refresher: when a CAP makes it in to a Final Comment Period, everyone has one week to make any final comments or critiques, and based on those discussions, the CAP is either accepted, rejected, or moved back to the draft phase. Find more about the CAP process here. Now on to the CAPs:

CAP-0023: Two-Part Payments with ClaimableBalanceEntry makes it easier to send a payment to an account that is not necessarily prepared to receive the payment. The two key objectives:

• to make it easy for protocols (like an implementation of payment channels) to pay out to participants, and
• to make it possible for issuers to issue assets non-interactively.

I discussed CAP-0023 at length in Issue #33 which you can read here. You can also find the latest CAP-0023 discussion here.

CAP-0033: Sponsored Reserve seeks to solve the following problem: an entity should be able to provide the reserve for accounts controlled by other parties without giving those parties control of the reserve. CAP-0033 is a direct compliment to CAP-0015: Fee-bump Transactions, which allows one account to pay another account’s transaction fee.

I discussed CAP-0033 at length in Issue #44 and you can find the latest discussion around CAP-0033 here.

👉 If you have any questions or concerns about these CAPS, make sure to hop in to the discussion!

Not Yet Signed Up?

Want to get the Stellar Dev Digest and other developer updates directly to your inbox? Sign up for the developer newsletter today!

Did I Miss Something?

If you found that something from this issue is missing or inaccurate reach out to me (kolten) on Keybase and I’ll make sure to fix it 👍