Skip to main content

6 posts tagged with "developer"

View All Tags

· One min read
Naman Kumar

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 1 (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.

· One min read
Tyler van der Hoeven

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. (https://developers.stellar.org/docs/learn/smart-contract-internals/fees-and-metering#transaction-fee)
  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.

· 2 min read
Tyler van der Hoeven

Discord agenda thread

  1. Plan and schedule for these meetings
    1. Protocol meetings every other Thursday at 4pm ET
    2. Developer meetings every other Friday at 1pm ET
    3. Will continue to adjust as needed
  2. Fee bump bug - announcement | discussion thread
    1. Fee sponsorship bug: unused fee is refunded to the inner tx source rather than the sponsor source.
    2. Fix in new release. Up to the ecosystem and validators to upgrade. The fix will likely be rolled out before Phase 2.
    3. Up to validators to determine if they’d like to push the v20 upgrade date to wait for the fix; or upgrade with current release.
  3. TxMeta Deprecation in Horizon - announcement
  4. Ideas around testing against ledger snapshots - request
    1. Define the needs a bit more clearly
    2. Definitely something here we should be addressing to make testing against specific ledger state easier
  5. How do you get a list of smart contracts? - thread
    1. Observe create contract ops as ledgers close
    2. Use an indexing service
  6. What is the status of contracts caching support? - question
    1. response