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.

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

Updated meeting notes #370

Merged
merged 5 commits into from
Mar 19, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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-02-29.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: '2024-02-29'
authors: naman
tags: [protocol]
---

<iframe
src="https://drive.google.com/file/d/10Yx14FsyoPctqSVCs8LQU_cfMN0bilQK/view"
width="640"
height="360"
allow="autoplay"
></iframe>

[Discord agenda thread](https://discord.com/channels/897514728459468821/1212118102565855243)

1. Tommaso (@tdep) proposed a core change to allow for extending instance and code TTL with separate values on the host environment to allow for more cost-efficient designs
a. Proposal and discussion are captured in github discussions [stellar-core#1447](https://github.com/stellar/stellar-protocol/discussions/1447)
2. Tommaso receieved feedback on the proposal as well as implementation. Since it didn't require a metering change, core devs thought it to be a quick change.
3. The ecosystem voted in favor of the proposal by upvoting the post on Github Discussions. 13 votes were [recorded](https://github.com/stellar/stellar-protocol/discussions/).
4. As next steps, a CAP will be authored to capture the proposal and put forth for approval from CAP Core Team.

25 changes: 25 additions & 0 deletions meeting-notes/2024-03-14.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: '2024-03-14'
authors: naman
tags: [protocol]
---

<iframe
src="https://drive.google.com/file/d/1Wh-MGz7foRLvGVU2J9w-ZBFt-BO3JVEb/view"
width="640"
height="360"
allow="autoplay"
></iframe>

[Discord agenda thread](https://discord.com/channels/897514728459468821/1217193723612368926)

1. CAP Core Team deliberated over the latest proposals put forth by the Stellar ecosystem to advance stellar-core.
2. Nicholas and David from the CAP Core Team listened to the following proposals and discussed the proposals with the authors.
a. CAP Core team will deliver their vote over email.
3. Proposals discussed:
a. [CAP-51](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): add support for secp256r1 verification; by @leigh
b. [CAP-53](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): create separate functions for extending the time-to-live for contract instance and contract code; by @tdep
c. [CAP-54](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md): lower total costs by refining the Soroban cost model used for VM instantiation into multiple separate and more-accurate costs; by @graydon
d. [CAP-55](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md): lower total costs by linking fewer host functions during VM instantiation in Soroban; by @graydon
e. [CAP-56](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md): lower total costs by caching parsed Wasm modules within a Soroban transaction; by @graydon

2 changes: 1 addition & 1 deletion meeting-notes/authors.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,6 @@ kalepail:
image_url: https://github.com/kalepail.png
naman:
name: Naman Kumar
title: Senior Product Manager
title: Product Manager
url: https://github.com/namankumar
image_url: https://github.com/namankumar.png
Loading