64 posts tagged with "developer"

1. Tdep discussed Zephyr, an execution env built on top of the indexer Mercury. He also walked through examples demonstrating how Zephyr can simplify dapp development.

1. Piyal demonstrated that Freighter's swap functionality is now served by Soroswap. It was previously served by Stellar Dex.
2. Freighter has made integration instructions available here.
3. Esteban shared that Palta Labs has created a DEX aggregator and made it available to all via the Router SDK.
4. The Router SDK finds the optimal path for the swap in terms of swap cost across all dexes on Soroban.

Note: the first part of the call was lost. The video posted above captures the second half of the call where various ecosystem developers shared their use cases and needs for a smart wallet on Stellar.

1. Tyler put forward a proposal for a smart wallet as a public good. Given that the native auth can be overloaded by using __check_auth, Stellar implementation of a smart wallet is fairly straightforward. The capability to customize the auth is already built into the core protocol.
2. See the proposal here and implementation here
3. The proposal only uses WebAuthN-based signers i.e. passkeys. It does not use ed25519, which, perhaps it should given that ~100% of the accounts on Stellar use the scheme. It also introduces the notion of temporary and admin signers to illustrate the notion that the account can be managed by multiple signers, each with a different access policy.
4. The biggest unlock with custom auth is the ability to execute custom logic. We heard from various ecosystem members about how might they us it. 4a. A dev is building a perpetual protocol and thought smart wallets could be used to automatically manage defi positions, which would be a significant improvement over status quo where the user has to constantly track assets to determine when to execute a trade. 4b. Folks are excited about foregoing the seed phrase for passkeys, which is especially meaningful when onboarding net new users to the blockchain. 4c. Authorizing a cross-chain message from a different chain, especially programmatic authorization, requires an implementation of custom accounts. 4d. Some apps have noted that users prefer not to have a wallet but simply experience the value of the app, especially games. For this, the app may assign a temporary account to the user and control access via check_auth. 4c. Microtransactions without needing user sign is super interesting for apps as well.
5. This has been a very insightful meeting and we learnt about how the Stellar ecosystem plans to leverage smart wallet. Let's continue the conversation in discord!

1. SDF Data team gave a crash course in analysis of Stellar data, and covered how to access Hubble, tips for efficient querying, and how to get started with data exploration.
2. Slides are publicly available and legible async.
3. Tips for data anlaysis are also covered in docs
4. Share your queries and post questions in #hubble in Stellar discord, which is a dedicated channel for data-related topics.

1. Chad and Willem from Aha Labs discuss the updates to the new and improved stellar-cli
2. Some highlights include the change from the name 'soroban' to 'stellar' when using the CLI tool and the addition of new commands.
3. They cover some cool functions like local network setup, account creation, and transaction signing. with the following commands:
   • stellar network container [start|logs]
   • stellar keys [generate|fund|ls]
   • stellar contract init to get a whole new Soroban project
   • and so much more!
4. They also discuss expected future updates including support for more Stellar operations and integration with Stellar Lab V2!

1. Kirckz discusses Meru, a Financial services app for Freelancers and remote workers in Latin America.
2. He shares his experience integrating Meru with Blend, a liquidity protocol primitive for Stellar.
3. Kirckz shares the challenges faced during the integration and how they were overcome.
4. He shares the sdks and libraries his team used to facilitate the integration.

Follow Meru on X (formerly Twitter) to stay updated: https://x.com/getmeru

1. Tyler created Super Peach, a web3 application that uses passkeys to sign transactions. He demonstrated how passkeys can be used in authorization flows and how they can be used to sign transactions.
   • Code: https://github.com/kalepail/superpeach
   • Demo: https://superpeach.xyz
2. Introduced passkey-kit. A TypeScript SDK for creating and managing Smart Wallets via passkeys (includes the actual Smart Wallet interface)
   • Code: https://github.com/kalepail/passkey-kit
   • Demo: https://passkey-kit-demo.pages.dev
3. Introduced Launchtube, a service for submitting transactions onchain by covering both the transaction fee AND the sequence number. Wild!
   • Code: https://github.com/kalepail/launchtube (ask in the #passkeys channel on Discord for a testnet token)
4. He shared his vision for pushing the passkey implementation through to becoming a standard for the ecosystem.

Join the #passkeys channel on the Discord to continue the discussion

1. Tyler built a voting application using passkeys to sign the transaction, which is an implementation of the secp256r1 verification function.
2. He showed a cross-platform implementation (web and mobile) and demonstrated that passkeys are the perfect interface between web3 contracts and web2 authentication mechanisms that most end users are accostomed to.
3. Ecosystem members discussed the use of smart wallets that would use passkeys as a signer. Challenges were identified around fees requires for smart wallets, the need for a common implementation for a smart wallet, as well as how might it interface with existing password managers.
4. The voting application can be tried out at passkey.sorobanbyexample.org
5. Code for the demo is here github.com/kalepail/soroban-passkey

Discord Agenda thread

1. Fifo presented Stellar Plus, which is a Javascript library to simplify the Stellar and Soroban development.
2. Ecosystem members found the design for Stellar Plus composable and encompassing of all Stellar related functionality including management of assets, accounts, wasm-related operations, as well as RPC utils.
3. The links to Fifo's presentation and Stellar Plus are:
   • Miro Board showing Stellar Plus architecture
   • Stellar Plus Repositore
   • Examples Repository
   • Docs

Discord agenda thread

1. Justin from ortege.ai demo'd Ortege, a data analytics platform for Stellar and Soroban.
2. Ortege lets anyone in the Stellar ecosystem create dashboards to track any and all desired metrics. Ortege's queries, widgets, and dashboards are shareable making it the perfect platform to surface
3. Justin will be releasing an AI soon and enable querying and insights via natural language.
4. All are invited to create a free account and track the success metrics for their dashboard.

Today's recording has two parts. The first 12 minutes are audio-only. The next 45 minutes have video as well. Please note the slides were shared in discord chat over screensharing, due to technical difficulties.

Part 1 (audio-only):

Part 2 (video):

Discord Agenda thread

1. Piyal surfaced the proposal for a Wallet Standard and requested feedback.
2. Cubist, an ecosystem project, discussed CubeSigner, a low-latency API for generating keys and signing transactions inside secure hardware.
3. Stellar-based example of CubeSigner is available in the Cubist Labs Github repository
4. Cubist devs can be contacted via the Stellar discord or the web form.

Discord agenda thread

1. There's a discussion on a TX meta change increasing visibility and analytics within the Stellar network. (https://github.com/stellar/stellar-xdr/pull/175)
2. Read-only invocations for contracts is explained, focusing on ensuring certain functions remain read-only without side effects. (https://github.com/stellar/stellar-protocol/discussions/1454) (https://github.com/stellar/stellar-protocol/discussions/1456) (https://github.com/stellar/stellar-protocol/discussions/1464)
3. Enabling contract discovery is introduced to enhance the visibility and authenticity of smart contracts within the Stellar ecosystem.
4. The implementation of a standardized contract meta data schema is proposed to link contracts to source code and enhance contract discoverability.(https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.contractmeta.html)
5. Issues related to inclusion fees in the Stellar network, highlighting the importance of monitoring fees closely and understanding the implications of surge pricing
6. Plans are discussed for designing a new RPC endpoint to provide developers with better visibility and information on setting inclusion fees, aiming to improve transparency and decision-making regarding fee trade-offs.