Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create 2024-08-29.mdx #953

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Create 2024-08-29.mdx #953

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions meeting-notes/2024-08-29.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: '2024-08-29'
authors: naman
tags: [protocol]
---

<iframe src="https://drive.google.com/file/d/1RBFt9diUPAgoeurw4xluyA9Qq1JNG2w8/preview" width="640" height="360" allow="autoplay" ></iframe>

Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1278045556211716171)

CAP Core team deliberated on the proposed CAPs:

1. Addition of a constructor to Soroban's flavor of Rust. [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md)
1. Team's concern was about potential break in compatibility, which Dima had addressed. There were no further concerns.
3. Addition of BLS12-381 curve and required field arithmetics - [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md)
1. Team's concern was about providing functions to check invalid input. It's too computationally expensive to do the check at the contract layer so the it may need to be implemented as a host function. Jay is seeking ecosystem input around use cases that require strict input validation.
2. There were no further concerns.
5. Increase performance by upgrading Soroban's VM. [CAP Discussion](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md)
1. Team's comments were about accuracy of the measurement method but the demonstrated benefits of wall clock time were thought to be promising.
2. There was a suggestion to expose performance improvements to contract developers thus creating the incentive to optimize contracts to leverage the improvements.
3. There were no further concerns.
Loading