From e52b254f546b4de7a115a3f3730a7a3966f99b5f Mon Sep 17 00:00:00 2001 From: John Wooten <60260750+JFWooten4@users.noreply.github.com> Date: Sun, 23 Aug 2026 17:24:21 -0400 Subject: [PATCH 01/17] Add 2019 meetings Co-authored-by: Codex Web --- meetings/2019-01-24.mdx | 66 +++++++++++++++++++++++++ meetings/2019-03-07.mdx | 107 ++++++++++++++++++++++++++++++++++++++++ meetings/2019-03-14.mdx | 59 ++++++++++++++++++++++ meetings/2019-03-21.mdx | 33 +++++++++++++ meetings/2019-03-28.mdx | 38 ++++++++++++++ meetings/2019-04-04.mdx | 57 +++++++++++++++++++++ meetings/2019-06-13.mdx | 23 +++++++++ meetings/2019-06-27.mdx | 75 ++++++++++++++++++++++++++++ meetings/2019-07-25.mdx | 28 +++++++++++ meetings/2019-11-04.mdx | 26 ++++++++++ meetings/authors.yml | 8 +++ 11 files changed, 520 insertions(+) create mode 100644 meetings/2019-01-24.mdx create mode 100644 meetings/2019-03-07.mdx create mode 100644 meetings/2019-03-14.mdx create mode 100644 meetings/2019-03-21.mdx create mode 100644 meetings/2019-03-28.mdx create mode 100644 meetings/2019-04-04.mdx create mode 100644 meetings/2019-06-13.mdx create mode 100644 meetings/2019-06-27.mdx create mode 100644 meetings/2019-07-25.mdx create mode 100644 meetings/2019-11-04.mdx diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx new file mode 100644 index 0000000000..35f61ec7e1 --- /dev/null +++ b/meetings/2019-01-24.mdx @@ -0,0 +1,66 @@ +--- +title: "2019-01-24" +description: "This overview highlights anchor services and network fees and resource limits." +authors: goodnow +tags: + - legacy + - CAP-10 + - CAP-13 + - CAP-15 + - CAP-5 + - CAP-7 + - CAP-8 + - SEP-13 + - SEP-6 + - SEP-8 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/x0Wrj2kuQ0U/m/CrId5QkoFwAJ) + +### Agenda + +- [CAP-0005](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-0006](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. +- [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. +- [CAP-0007 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/master/drafts/draft-detacct.md). +- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions update. +- CAP-0013 vs SEP-0013 (CAP-0007 + CAP-0008) - Change Trustlines to Balances. + +### Meeting Notes + +- CAP-0006 progressing with specific messaging for a targeted use case. +- CAP-0005 still lacks replace-by-fee and remains problematic. +- Deterministic accounts & creatorTxID (David): + - Vastly simplified since prior iteration. + - Salt mechanism needed; likely a full hash to prevent protocol rewind attacks. +- Cosigned Assets: + - Related to [SEP-8 (Regulated Assets)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md). + - NFT discussions considered orthogonal; may warrant a separate CAP. + - Catalog of no-op operations discussed: + - Payment to oneself + - Bump op 0 + - SetOptions with no fields + +### Follow-up Actions + +- Johnny: coordinate CAP-0006 community and API updates. +- David: expand deterministic accounts draft and address CAP-0010/CAP-0015 implications. +- Orbit: consolidate NFT discussions and assess need for a separate CAP. +- Jeremy: review SEP-13A comments and address shortcomings in SEP-13. + +### Trustline follow-up + +The adjacent trustline-focused discussion reprised the agenda above and surfaced additional nuance around asset onboarding and NFT considerations. Tom and Orbit asked the group to clarify how cosigned assets should handle no-op operations, and David emphasized that NFT work is orthogonal but still worth cataloging. + +- Tom asked for clarity on SEP-13A’s handling of edge cases, and Orbit volunteered to gather NFT-related requirements. The session reviewed the same high-level trustline-use case summary document in [Google Docs](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit#heading=h.8j5x6v50ft4p). That document lays out the anchor requirements around SEP-6/SEP-13 deposits and transfers so wallets set up user-facing flows that never require extra trustlines/XLM or manual follow-up steps, while also supporting sends to accounts that don’t yet exist. + - Deposits must complete once the anchor receives the external asset, delivering funds to the user’s original account whether or not it has a trustline or even exists yet. + - Users shouldn’t need to add additional XLM to finish a deposit, nor should anchors wait on any extra manual action once the deposit is underway. + - The send requirements emphasize end-to-end usability: sends must arrive without the recipient doing any setup, and the document recommends keeping implementations as simple as possible to encourage adoption. + - The group cataloged known no-ops (payment to self, bump op 0, SetOptions with no fields) and challenged attendees to bring simple, actionable alternatives rather than more complexity. + - A short-term TODO list reiterated that deterministic accounts need a salt/hash to guard against rewind attacks, while CAP-0006 updates and SEP-13A comments should stay in sync with the evolving API design. + +### Trustline follow-up actions + +- Johnny: continue improving the DEX-focused messaging tied to CAP-0006 and sync with Jon on API revisions. +- David: add concrete deterministic-account examples, harden salt handling, and spell out whether those accounts supplant CAP-0010/CAP-0015 work. +- Orbit: collect NFT and Asset-object feedback to determine whether a new CAP is warranted. +- Jeremy: respond to Tom’s SEP-13A comments and close the remaining gaps in the proposal. diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx new file mode 100644 index 0000000000..af1dd835c2 --- /dev/null +++ b/meetings/2019-03-07.mdx @@ -0,0 +1,107 @@ +--- +title: "2019-03-07" +description: "This overview highlights network fees and resource limits." +authors: goodnow +tags: + - legacy + - CAP-10 + - CAP-11 + - CAP-13 + - CAP-14 + - CAP-15 + - CAP-16 + - CAP-17 + - CAP-18 + - CAP-7 + - CAP-8 + - CAP-9 + - SEP-13 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/NJl_loV_RXU/m/SarzWEJPAgAJ) + +### Announcements + +- **[Merging in CAP/SEP Process](https://github.com/stellar/stellar-protocol/pull/247)** + - Another round of edits completed; further feedback requested on the PR. + - Intent to merge immediately, formalizing the previously ad-hoc CAP/SEP process. + - All CAPs will be numbered upon acceptance as drafts; competing proposals will be explicitly rejected. + - Post-merge cleanup planned for stale PRs and issues, with authors notified of next steps. +- **Establishing focus given limited developer resources** + - Fee structure + - Payment channels + - Payment network (**Starlight**) + +### Final Comment Period - Acceptance + +- [CAP-0017](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - Update `LastModifiedLedgerSeq` If and Only If LedgerEntry Is Modified (Jonathan Jove) +- [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - Fine-Grained Control of Authorization (Jonathan Jove) +- Address offer mutability (Jon) +- CAP-0016 to be rejected contingent on CAP-0018 approval + +### Priorities + +1. Replace Min Fee Mechanism +2. Trustline (& other) Usability + - Explicit intent to revive [CAP-0013 Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). +3. Payment Channels + - Focus on core components required for a basic payment channel design. +4. Starlight + - Deferred pending availability of dedicated development resources. + +### Deferred Items + +- [CAP-0007](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - Deterministic Account Creation (Jeremy Rubin) +- [CAP-0008](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - Self-Identified Pre-Auth Transaction (Jeremy Rubin) +- [CAP-0009](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) - Linear / Exterior Immutable Accounts (Jeremy Rubin) +- [CAP-0011](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) - Relative Account Freeze (Jeremy Rubin) +- Draft: Deterministic accounts and creatorTxID (David Mazières) +- [CAP-0014](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - Adversarial Transaction Set Ordering (Jeremy Rubin) + +### Agenda + +- Final Comment proposals - new unresolved concerns (30 min max) +- CAP-0017, CAP-0018 +- Address offer mutability +- Replace Min Fee (60 min max) + +### Replace Min Fee Discussion + +- Diverging views: + - David and Nico prefer a mechanism _before_ raising the min fee. + - Jed favors pushing fee increases forward immediately. +- Current proposals: + - [CAP-0010](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - Fee Bump Account (Jeremy Rubin) + - [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions (OrbitLens) + - Pre-draft: feeSource and feeMultiplier (David Mazières) +- [Reference spreadsheet](https://docs.google.com/spreadsheets/d/1_u0LE61V-jkXUcNBZW5xhXZEmIz5rQSgZEr8VsVl47o/edit) (OrbitLens) compares fee-sponsorship approaches (CAP-10 fee balances, feeSource/feeMultiplier, deterministic accounts, CAP-15 metadata) across tradeoffs like explicit sponsor control, pre-signed tx support, and algorithmic complexity. + - CAP-10 introduces dedicated fee balances so sponsors can preload fees, but it requires new operations and careful management of locked fee funds. + - FeeSource/feeMultiplier and deterministic accounts keep fees on existing transactions but push complexity to signers (pick fee source in advance, ensure simultaneous submissions) with limited control. + - CAP-15 embeds fee bumping in the transaction envelope, letting sponsors declare amounts per envelope, while the spreadsheet emphasizes choosing the right tradeoff between sponsor control and implementation simplicity. +- Outcomes: + - David to draft a new CAP superseding CAP-0015, including Transaction versioning. + - Johnny to follow up with David regarding feeSource draft status. + +### Trustline Usability + +- Discussion on next steps for CAP-0013 Change Trustlines to Balances +- Open questions: + - What changes would improve group consensus? + - Are there unpresented fundamental ideas? + - Who should own the proposal going forward? +- Related discussion: **Sender Pays** (sending assets without trustlines). +- Consensus points: + - CAP-0013 enables adding balances to others and simplifies token distribution. + - SEP-0013 approach explicitly rejected. + - Hard requirements need definition; Tom Q. designated owner. + - Developer-friendliness and Account ID semantics must be addressed. + +### Meeting Notes + +- Inline notes (highlighted in blue in original thread) captured above. + +### Follow-Up Actions + +- **Jon Jove** to update CAPs based on email list feedback. +- **Tom Quisel** to revise and present hard requirements for trustline usability. +- **David** to submit a new proposal for TransactionEnvelope versioning to enable changes like CAP-0015. diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx new file mode 100644 index 0000000000..538a178a8c --- /dev/null +++ b/meetings/2019-03-14.mdx @@ -0,0 +1,59 @@ +--- +title: "2019-03-14" +description: "This overview highlights anchor services and network fees and resource limits." +authors: goodnow +tags: + - legacy + - CAP-13 + - CAP-15 + - CAP-17 + - CAP-18 + - CAP-19 + - SEP-13 + - SEP-16 + - SEP-17 + - SEP-6 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/uxmo4LM5FWY/m/psazVteTBgAJ) + +### Announcements + +- Jon made additional changes to [CAP-0018](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. +- [CAP-0017](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. + +### Agenda + +#### Trustline Usability + +- Restated [requirements document](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit#heading=h.8j5x6v50ft4p) up for discussion. The doc captures the desired SEP-6/SEP-13 deposit and send flows: anchors should auto-complete deposits without additional user actions, deliver funds to the intended account even when it has no trustline or XLM, and allow sends to non-existent accounts by crediting the original account ID. + - Deposits must finish once the anchor receives the external asset, never forcing the user to add trustlines or extra XLM, even when accounts are uncreated. + - Sending should work regardless of the recipient’s trustlines or account state, and funds should arrive at the original Stellar account without extra steps. + - The document stresses usability: anchors/wallets should avoid complex workflows, so any solution must stay simple, fast, and easy to implement. + - [SEP-0017](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) + - [SEP-0016](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts + - It is not possible to satisfy all requirements in the protocol's current form. + +#### Issues with [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) + +- If base reserve increases, malicious actors could add large numbers of trustlines to an account. +- Accounts can be DoS'd via the subentry limit. +- The proposal has very large scope, affecting most operations and assumptions in the protocol. + +#### Alternatives Discussed + +- Use deterministic accounts and merge them if the receiver already has an account. +- Introduce a **SentBalance** ledger entry claimable by the receiver. +- Introduce a **remove trustline** operation that returns assets to the sender. + +#### Fee Mechanisms + +- David proposed [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): + - Enables future-upgradability of `TransactionEnvelope` + - Allows a simpler implementation of [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) + +### Follow-up Actions + +- **David**: Write a short proposal on "embryonic accounts". +- **Jeremy**: Clarify SEP-0016 workflow with deterministic accounts. +- **Jon**: Provide analysis of attack surfaces and issues in [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx new file mode 100644 index 0000000000..e015c4e683 --- /dev/null +++ b/meetings/2019-03-21.mdx @@ -0,0 +1,33 @@ +--- +title: "2019-03-21" +description: "This overview highlights order book trading and network fees and resource limits." +authors: goodnow +tags: + - legacy + - CAP-15 + - CAP-16 + - CAP-18 + - CAP-19 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/KzgQc58510o/m/1qRSxo7GCAAJ) + +### Announcements + +- [CAP-0016](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-0016 will only be revived if CAP-0018 encounters implementation issues. +- [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. +- [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. +- Jed was in Singapore this week; trustline discussions were postponed until his return. + +### Agenda + +#### Fee Follow-ups + +- Topics: [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. +- Decision: Push CAP-0019 to FCP: Acceptance and reframe CAP-0015 in the context of CAP-0019. + +#### Future of the Order Book - Ideation + +- Broad discussion of possible directions for the order book. +- No commitments were made. +- Goal: Produce an exhaustive list of ideas, followed by prioritization and requirements definition in future sessions. diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx new file mode 100644 index 0000000000..ef88d7f78a --- /dev/null +++ b/meetings/2019-03-28.mdx @@ -0,0 +1,38 @@ +--- +title: "2019-03-28" +description: "This overview highlights network fees and resource limits." +authors: goodnow +tags: + - legacy + - CAP-15 + - CAP-19 + - CAP-20 + - CAP-5 + - SEP-19 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/t162rVxLYB4/m/XB4_9st1BgAJ) + +### Announcements + +- [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) (Future-upgradable TransactionEnvelope type) is moving to Accepted. +- "Implementation Review" stage added for CAPs (see https://github.com/stellar/stellar-protocol/pull/279); keep in mind for future CAP process. +- Jed out this week; trustline discussion pushed again. +- [CAP-0020](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. + +### Agenda + +- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (Bump Fee Extension): Modified to utilize [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. + - David: Two transaction IDs (inner and outer) as a result of the change. + - Nico: Original feedback was that this relies on [CAP-0005](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) logic that no longer exists in the CAP-0005 implementation. + - Nico and David to discuss offline; David to submit additional edits and document constraints and issues from the meeting. +- [SEP-0019](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) (Bootstrapping Multisig Transaction Submission): + - Significant discussion with contributions from Paul Selden, Antoine (MrTicot), Orbit, Johan, and others. + - Focus should remain on SEP-0019 and direction for any related SEPs. + - Can pull in Paul and others for the next meeting; it is likely the most active SEP currently. + - SEP-0019 is largely focused on the StellarGuard protocol and currently only describes basic flow properties and API endpoints; substantial work remains. + - Open questions: + - Metadata (storage and off-chain handling) + - Coordinator (no core changes required) + - Possible use of an IPFS home domain + - Orbit to send a document outlining design considerations for multisig transaction coordination. diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx new file mode 100644 index 0000000000..d3c7a6acf4 --- /dev/null +++ b/meetings/2019-04-04.mdx @@ -0,0 +1,57 @@ +--- +title: "2019-04-04" +description: "This overview highlights Horizon API and network fees and resource limits." +authors: goodnow +tags: [legacy, CAP-15, SEP-16] +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/QSR2wf207ow/m/stluewnDCQAJ) + +### Announcements + +- Pushing fee work out to next week given David and Orbit's absence (Tomer is also out). + +### Agenda + +- Discussing next steps for trustlines work. +- David personally doesn't feel good about pushing forward Sponsored Trustlines, despite multiple people who think it's mostly there (Tom, Orbit). +- There was initial discussion of going back to [SEP-0016 (atp3 account transfer)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). +- Goal today is to discuss alternative solutions (as opposed to criticism of existing solutions), given the requirements that are extensively listed [here](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit). + - Deposits have to finish without additional user clicks, even when the recipient’s account is uncreated or lacks a trustline, and nor should the user need to fund extra XLM. + - The send workflow should credit the intended account ID even if no trustline exists, so clients don’t need to coordinate new trustlines for every payment. + - The document’s overall goal is usability: keep issuer/wallet flows simple so developers actually ship the solution instead of avoiding a hard protocol change. + +### Jon proposal + +- Trying to solve the add balance problem, and the merge problem related to trustlines. +- We add a concept called a mergeable trustline. +- Can send them to anyone; only the account owner can merge it into a "classic" trustline. +- "CAP-XXXX (Pending Trustlines)" that doesn't break merge. +- Carries its own reserve, uses union-find to merge accounts. Would give O(log n) performance for merging accounts (not the most efficient version of union-find, but still performant). + +### Summary of mergeable trustline details + +- Mergeable trustlines are associated with accounts via a variant of a union-find data structure (see https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-046j-design-and-analysis-of-algorithms-spring-2012/lecture-notes/MIT6_046JS12_lec16.pdf) that does not include the path-compression optimization. +- Mergeable trustlines are immutable, except that the balance can be transferred in its entirety to the "real" trustline for the corresponding asset on the same account (noted in the meeting that this might be relaxable). +- Each mergeable trustline carries an amount of native asset equal to the base reserve at the time it was created, and this is the entire reserve requirement of the mergeable trustline. +- An account can have an arbitrary number of mergeable trustlines associated with it, even multiple mergeable trustlines for the same asset. +- Sending a mergeable trustline never fails if the receiving account exists. +- Merging accounts never fails due to the presence of mergeable trustlines. +- Open questions included what happens if the sender owns the trustline, or if the sender merges their account, creating issues around locking accounts and outstanding trustlines. +- Revocability should not be done on-ledger; it should be handled via pre-authorized transactions or other multi-phase protocols. If it is on-ledger, it should be irrevocable. + +### Nico's caveats + +- Similar complexities arise as with SEP-0016: clients must track incoming mergeable trustlines, decide whether they matter, query them from Horizon, and take actions. +- This puts significant burden on clients to download and reason about many mergeable trustlines. +- Union-find might help reduce what needs to be downloaded, potentially in tandem with SEP-0016. +- David, Nico, and Jon's proposals all rely on some form of "incoming trustline" at the core layer, which does not appear substantially simpler than ecosystem-level approaches. + +### SEP-0016 thoughts + +- Defining the last step is difficult given current protocol constraints and would require "shrink to fit" and other small core changes. +- SEP-0016 should likely remain a living document that evolves alongside core capabilities. + +### Follow-up actions + +- David to put together a list of constraints and concerns blocking [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx new file mode 100644 index 0000000000..db9995647f --- /dev/null +++ b/meetings/2019-06-13.mdx @@ -0,0 +1,23 @@ +--- +title: "2019-06-13" +description: "This overview highlights network fees and resource limits." +authors: goodnow +tags: [legacy, CAP-15, CAP-21] +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/I1GAjjcfDA0/m/CIzRMI-FBAAJ) + +### Announcements + +- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. + +### Agenda + +- David's Pre-Condition proposal: [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) + - After several iterations with the Channels working group, CAP-0021 was presented for decision. + - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-0021 to FCP: Acceptance. +- Clarifying final aspects of fee bump ([CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: + - https://github.com/stellar/stellar-protocol/pull/323 + - CAP-0015 will move to FCP: Acceptance after a final round of wording changes. +- If time permits, Jon to give an update from the trustlines/balances work. + - Decision made not to discuss this fully until the draft is finalized, particularly around rationale and alternative ideas. diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx new file mode 100644 index 0000000000..f3a7a33574 --- /dev/null +++ b/meetings/2019-06-27.mdx @@ -0,0 +1,75 @@ +--- +title: "2019-06-27" +description: "This overview highlights transaction data." +authors: goodnow +tags: + - legacy + - CAP-15 + - CAP-21 + - CAP-22 + - CAP-23 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/va9Y7lkP4uI/m/K2W_AkvzCQAJ) + +### Announcements + +- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. +- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. + +### Agenda + +- [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - _Two-Part Payments with BalanceEntry_ + - Focused on temporal separation between initiating a payment and receiving a payment. + - Explicitly **does not** replace existing payment operations. + - **David's initial framing:** ~10% additional complexity yields significantly more utility. + +#### CAP-0023 Design Discussion + +- **AuthorizeBalance** + - Should include an optional `AccountID *revocableBy`. + - Small increase in complexity but worth it for added control. +- **Threshold semantics** + - `CreateBalance` should use the _medium_ threshold. + - Authorization should mirror AllowTrust. + - Claiming at a _low_ threshold may be acceptable, since low-threshold keys cannot otherwise act. +- **Operation naming** + - Consider appending `Op` to operation names (XDR style / consistency). +- **NATIVE asset semantics** + - AuthorizeBalance behavior for `NATIVE` assets is unspecified (invalid vs no-op). + - Might be better to factor shared data structures out of both AuthorizeBalance and AllowTrustOp. + - AuthorizeBalance operates by ID and is unaware of the asset of the BalanceEntry; this structure may still be useful for AllowTrust. +- **Why AuthorizeBalance exists** + - Needed to authorize _both_ the account and the payment itself. + - Necessary for deauthorization when assets are sent to bad actors. + - Important for payment channels to ensure all parties are authorized before payout. +- **ACCOUNT_MERGE interaction** + - BalanceEntries resemble hyper-specialized deterministic accounts. + - They do **not** participate in merges and may be abandoned (with their own reserve). + - This behavior should be explicitly documented in the CAP. +- **Global revoke scenarios** + - In cases where assets must be returned for replacement, funds locked in BalanceEntries pose challenges. + - AuthorizeBalance enables trustline authorization prior to account creation. + - Even if authorization is revoked, reclaiming balances should still be possible. +- **Extensibility** + - Consider extending `claimBy` using a union to allow future claim-by-signer functionality. +- **UX considerations** + - Some concern that less-knowledgeable users may struggle with the flow. + - Others believe wallet UX and the existing payment operation mitigate this risk. + +### CAP-0021 / CAP-0022 & Payment Channel Implementation + +- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - _Generalized transaction preconditions_ + - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-0022. + - May be implemented separately (branch or protocol version) for payment channels. + - Preference is to resolve outstanding issues before acceptance. +- [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - _Invalid transactions must have no effects_ + - Open question: adopt CAP-0022 as written, or pursue a stronger invariant (only fully executing transactions succeed). + +### Follow-Up Actions + +- [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) + - Add explicit behavior details regarding `ACCOUNT_MERGE`. + - Evaluate low-threshold usage for `ClaimBalance`. + - Append `Op` to operation names in XDR. + - Extend BalanceEntry claimer via a union to support future signer-based claims or wildcard claimBy. diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx new file mode 100644 index 0000000000..d3d237a3b5 --- /dev/null +++ b/meetings/2019-07-25.mdx @@ -0,0 +1,28 @@ +--- +title: "2019-07-25" +description: "This overview highlights protocol updates, tooling demos, and ecosystem discussions." +authors: goodnow +tags: + - legacy + - CAP-15 + - CAP-21 + - CAP-22 + - CAP-24 + - CAP-25 +--- + +## [Public Discussion](https://groups.google.com/g/stellar-dev/c/a9JH2c3jTEw/m/k5wg4XNnDAAJ) + +### Agenda + +- [CAP-0024](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Path Payment w/Fixed Amount + - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. +- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) + - Implementation question around removal of one-time signers, which currently does not take place. + - Consensus: preserve existing behavior for now and discuss behavior changes separately. + - Jon to follow up with Nico when he returns to better understand existing behavior. +- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-0025](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - Preconditions, Invalid Transaction Effects, Shadow Bucket Removal + - CAP-0025 moves to Final Comment Period (FCP): Acceptance. + - CAP-0021 is dependent on CAP-0022. + - CAP-0022 must address additional feedback from Nico. + - David to own follow-up on CAP-0021/0022 dependency resolution. diff --git a/meetings/2019-11-04.mdx b/meetings/2019-11-04.mdx new file mode 100644 index 0000000000..83c12684a4 --- /dev/null +++ b/meetings/2019-11-04.mdx @@ -0,0 +1,26 @@ +--- +title: "2019-11-04" +description: "This overview highlights validator operations and anchor services." +authors: goodnow +tags: [community] +--- + +import YouTube from "@site/src/components/YouTube"; + + + +Denelle Dixon closed day one of Meridian with a forward-looking address on SDF’s evolving role and Stellar’s long-term direction. Speaking from the perspective of her first six months leading the foundation, she emphasized SDF’s identity as a nonprofit steward and ecosystem convener, translating open-network principles such as transparency, interoperability, and trust-by-design into practical support for builders, institutions, and regulators. + +The talk focused on aligning governance, resources, and community momentum as Stellar moves from early growth into a more decentralized and durable network. Dixon outlined what has worked well so far, where SDF has fallen short, and how a restructured treasury and clearer priorities are meant to support sustainable adoption while reducing the foundation’s centrality over time. + +### Key Topics + +- What SDF is (and is not): a nonprofit with no shareholders or dividends, focused solely on long-term network adoption and ecosystem health. +- Decentralization progress: increasing validator independence and a maturing governance feedback loop from community discussion to protocol change. +- What’s working: scalable technology, a growing global team, stronger community coordination, and expanding ecosystem projects. +- What needs improvement: stellar-wide marketing, policy and regulatory engagement, ongoing transparency, and more effective lumen distribution. +- Treasury reset: announcement of a 50B XLM burn, with remaining resources reorganized to better align with mission and execution capacity. +- New funding buckets: operational runway with a multi-year release plan, ecosystem and infrastructure support, currency and liquidity support, use-case investment, and user distribution through applications. +- Enterprise Fund model: the ability to invest in or acquire companies to accelerate priority use cases, with returns recycled back into the fund. +- Regulatory approach: emphasis on education and consumer protection, positioning the network layer as internet-like infrastructure. +- Q&A highlights: sustaining SDF beyond the initial multi-year plan, improving DEX liquidity, overcoming network-effects challenges, environmental advantages versus mining-based chains, and inclusion as a requirement for mainstream adoption. diff --git a/meetings/authors.yml b/meetings/authors.yml index 9d92d724b3..aa795e3513 100644 --- a/meetings/authors.yml +++ b/meetings/authors.yml @@ -56,3 +56,11 @@ kaankacar: image_url: https://github.com/kaankacar.png socials: github: kaankacar +goodnow: + name: Johnny Goodnow + url: https://github.com/theaeolianmachine + image_url: https://github.com/theaeolianmachine.png + page: true + socials: + linkedin: jgoodnow + github: theaeolianmachine From 7bef48dbe2f997753389c30652a45b82c74b8dbe Mon Sep 17 00:00:00 2001 From: John Wooten Date: Sun, 23 Aug 2026 17:27:02 -0400 Subject: [PATCH 02/17] Run build, prettier --- routes.txt | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/routes.txt b/routes.txt index 9f0304cc0d..44bc2b56df 100644 --- a/routes.txt +++ b/routes.txt @@ -837,6 +837,16 @@ /docs/validators/admin-guide/soroban-settings /docs/validators/tier-1-orgs /meetings +/meetings/2019/01/24 +/meetings/2019/03/07 +/meetings/2019/03/14 +/meetings/2019/03/21 +/meetings/2019/03/28 +/meetings/2019/04/04 +/meetings/2019/06/13 +/meetings/2019/06/27 +/meetings/2019/07/25 +/meetings/2019/11/04 /meetings/2024/01/18 /meetings/2024/01/26 /meetings/2024/02/01 @@ -918,6 +928,7 @@ /meetings/authors/carstenjacobsen/page/2 /meetings/authors/carstenjacobsen/page/3 /meetings/authors/elliotfriend +/meetings/authors/goodnow /meetings/authors/kalepail /meetings/page/2 /meetings/page/3 @@ -925,12 +936,40 @@ /meetings/page/5 /meetings/page/6 /meetings/page/7 +/meetings/page/8 /meetings/tags +/meetings/tags/cap-10 +/meetings/tags/cap-11 +/meetings/tags/cap-13 +/meetings/tags/cap-14 +/meetings/tags/cap-15 +/meetings/tags/cap-16 +/meetings/tags/cap-17 +/meetings/tags/cap-18 +/meetings/tags/cap-19 +/meetings/tags/cap-20 +/meetings/tags/cap-21 +/meetings/tags/cap-22 +/meetings/tags/cap-23 +/meetings/tags/cap-24 +/meetings/tags/cap-25 +/meetings/tags/cap-5 +/meetings/tags/cap-7 +/meetings/tags/cap-8 +/meetings/tags/cap-9 +/meetings/tags/community /meetings/tags/developer /meetings/tags/developer/page/2 /meetings/tags/developer/page/3 /meetings/tags/developer/page/4 /meetings/tags/developer/page/5 /meetings/tags/developer/page/6 +/meetings/tags/legacy /meetings/tags/protocol +/meetings/tags/sep-13 +/meetings/tags/sep-16 +/meetings/tags/sep-17 +/meetings/tags/sep-19 +/meetings/tags/sep-6 +/meetings/tags/sep-8 /search From 2c67682c2c87937e63a9fa9ddc4da2b166c49497 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 09:43:09 -0400 Subject: [PATCH 03/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Normalize=20CAP?= =?UTF-8?q?=20and=20SEP=20references?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use unpadded proposal identifiers in meeting prose while preserving canonical padded filenames in URLs. Co-authored-by: Codex --- meetings/2019-01-24.mdx | 22 +++++++++++----------- meetings/2019-03-07.mdx | 34 +++++++++++++++++----------------- meetings/2019-03-14.mdx | 18 +++++++++--------- meetings/2019-03-21.mdx | 10 +++++----- meetings/2019-03-28.mdx | 14 +++++++------- meetings/2019-04-04.mdx | 12 ++++++------ meetings/2019-06-13.mdx | 12 ++++++------ meetings/2019-06-27.mdx | 20 ++++++++++---------- meetings/2019-07-25.mdx | 14 +++++++------- 9 files changed, 78 insertions(+), 78 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 35f61ec7e1..3bf9b40791 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -19,16 +19,16 @@ tags: ### Agenda -- [CAP-0005](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-0006](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. +- [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. -- [CAP-0007 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/master/drafts/draft-detacct.md). -- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions update. -- CAP-0013 vs SEP-0013 (CAP-0007 + CAP-0008) - Change Trustlines to Balances. +- [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/master/drafts/draft-detacct.md). +- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions update. +- CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. ### Meeting Notes -- CAP-0006 progressing with specific messaging for a targeted use case. -- CAP-0005 still lacks replace-by-fee and remains problematic. +- CAP-6 progressing with specific messaging for a targeted use case. +- CAP-5 still lacks replace-by-fee and remains problematic. - Deterministic accounts & creatorTxID (David): - Vastly simplified since prior iteration. - Salt mechanism needed; likely a full hash to prevent protocol rewind attacks. @@ -42,8 +42,8 @@ tags: ### Follow-up Actions -- Johnny: coordinate CAP-0006 community and API updates. -- David: expand deterministic accounts draft and address CAP-0010/CAP-0015 implications. +- Johnny: coordinate CAP-6 community and API updates. +- David: expand deterministic accounts draft and address CAP-10/CAP-15 implications. - Orbit: consolidate NFT discussions and assess need for a separate CAP. - Jeremy: review SEP-13A comments and address shortcomings in SEP-13. @@ -56,11 +56,11 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced - Users shouldn’t need to add additional XLM to finish a deposit, nor should anchors wait on any extra manual action once the deposit is underway. - The send requirements emphasize end-to-end usability: sends must arrive without the recipient doing any setup, and the document recommends keeping implementations as simple as possible to encourage adoption. - The group cataloged known no-ops (payment to self, bump op 0, SetOptions with no fields) and challenged attendees to bring simple, actionable alternatives rather than more complexity. - - A short-term TODO list reiterated that deterministic accounts need a salt/hash to guard against rewind attacks, while CAP-0006 updates and SEP-13A comments should stay in sync with the evolving API design. + - A short-term TODO list reiterated that deterministic accounts need a salt/hash to guard against rewind attacks, while CAP-6 updates and SEP-13A comments should stay in sync with the evolving API design. ### Trustline follow-up actions -- Johnny: continue improving the DEX-focused messaging tied to CAP-0006 and sync with Jon on API revisions. -- David: add concrete deterministic-account examples, harden salt handling, and spell out whether those accounts supplant CAP-0010/CAP-0015 work. +- Johnny: continue improving the DEX-focused messaging tied to CAP-6 and sync with Jon on API revisions. +- David: add concrete deterministic-account examples, harden salt handling, and spell out whether those accounts supplant CAP-10/CAP-15 work. - Orbit: collect NFT and Asset-object feedback to determine whether a new CAP is warranted. - Jeremy: respond to Tom’s SEP-13A comments and close the remaining gaps in the proposal. diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index af1dd835c2..2b99ef8e8d 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -34,16 +34,16 @@ tags: ### Final Comment Period - Acceptance -- [CAP-0017](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - Update `LastModifiedLedgerSeq` If and Only If LedgerEntry Is Modified (Jonathan Jove) -- [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - Fine-Grained Control of Authorization (Jonathan Jove) +- [CAP-17](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - Update `LastModifiedLedgerSeq` If and Only If LedgerEntry Is Modified (Jonathan Jove) +- [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - Fine-Grained Control of Authorization (Jonathan Jove) - Address offer mutability (Jon) -- CAP-0016 to be rejected contingent on CAP-0018 approval +- CAP-16 to be rejected contingent on CAP-18 approval ### Priorities 1. Replace Min Fee Mechanism 2. Trustline (& other) Usability - - Explicit intent to revive [CAP-0013 Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). + - Explicit intent to revive [CAP-13 Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). 3. Payment Channels - Focus on core components required for a basic payment channel design. 4. Starlight @@ -51,17 +51,17 @@ tags: ### Deferred Items -- [CAP-0007](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - Deterministic Account Creation (Jeremy Rubin) -- [CAP-0008](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - Self-Identified Pre-Auth Transaction (Jeremy Rubin) -- [CAP-0009](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) - Linear / Exterior Immutable Accounts (Jeremy Rubin) -- [CAP-0011](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) - Relative Account Freeze (Jeremy Rubin) +- [CAP-7](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - Deterministic Account Creation (Jeremy Rubin) +- [CAP-8](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - Self-Identified Pre-Auth Transaction (Jeremy Rubin) +- [CAP-9](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) - Linear / Exterior Immutable Accounts (Jeremy Rubin) +- [CAP-11](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) - Relative Account Freeze (Jeremy Rubin) - Draft: Deterministic accounts and creatorTxID (David Mazières) -- [CAP-0014](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - Adversarial Transaction Set Ordering (Jeremy Rubin) +- [CAP-14](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - Adversarial Transaction Set Ordering (Jeremy Rubin) ### Agenda - Final Comment proposals - new unresolved concerns (30 min max) -- CAP-0017, CAP-0018 +- CAP-17, CAP-18 - Address offer mutability - Replace Min Fee (60 min max) @@ -71,28 +71,28 @@ tags: - David and Nico prefer a mechanism _before_ raising the min fee. - Jed favors pushing fee increases forward immediately. - Current proposals: - - [CAP-0010](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - Fee Bump Account (Jeremy Rubin) - - [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions (OrbitLens) + - [CAP-10](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - Fee Bump Account (Jeremy Rubin) + - [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions (OrbitLens) - Pre-draft: feeSource and feeMultiplier (David Mazières) - [Reference spreadsheet](https://docs.google.com/spreadsheets/d/1_u0LE61V-jkXUcNBZW5xhXZEmIz5rQSgZEr8VsVl47o/edit) (OrbitLens) compares fee-sponsorship approaches (CAP-10 fee balances, feeSource/feeMultiplier, deterministic accounts, CAP-15 metadata) across tradeoffs like explicit sponsor control, pre-signed tx support, and algorithmic complexity. - CAP-10 introduces dedicated fee balances so sponsors can preload fees, but it requires new operations and careful management of locked fee funds. - FeeSource/feeMultiplier and deterministic accounts keep fees on existing transactions but push complexity to signers (pick fee source in advance, ensure simultaneous submissions) with limited control. - CAP-15 embeds fee bumping in the transaction envelope, letting sponsors declare amounts per envelope, while the spreadsheet emphasizes choosing the right tradeoff between sponsor control and implementation simplicity. - Outcomes: - - David to draft a new CAP superseding CAP-0015, including Transaction versioning. + - David to draft a new CAP superseding CAP-15, including Transaction versioning. - Johnny to follow up with David regarding feeSource draft status. ### Trustline Usability -- Discussion on next steps for CAP-0013 Change Trustlines to Balances +- Discussion on next steps for CAP-13 Change Trustlines to Balances - Open questions: - What changes would improve group consensus? - Are there unpresented fundamental ideas? - Who should own the proposal going forward? - Related discussion: **Sender Pays** (sending assets without trustlines). - Consensus points: - - CAP-0013 enables adding balances to others and simplifies token distribution. - - SEP-0013 approach explicitly rejected. + - CAP-13 enables adding balances to others and simplifies token distribution. + - SEP-13 approach explicitly rejected. - Hard requirements need definition; Tom Q. designated owner. - Developer-friendliness and Account ID semantics must be addressed. @@ -104,4 +104,4 @@ tags: - **Jon Jove** to update CAPs based on email list feedback. - **Tom Quisel** to revise and present hard requirements for trustline usability. -- **David** to submit a new proposal for TransactionEnvelope versioning to enable changes like CAP-0015. +- **David** to submit a new proposal for TransactionEnvelope versioning to enable changes like CAP-15. diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index 538a178a8c..c9a4b55068 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -19,8 +19,8 @@ tags: ### Announcements -- Jon made additional changes to [CAP-0018](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. -- [CAP-0017](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. +- Jon made additional changes to [CAP-18](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. +- [CAP-17](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. ### Agenda @@ -30,11 +30,11 @@ tags: - Deposits must finish once the anchor receives the external asset, never forcing the user to add trustlines or extra XLM, even when accounts are uncreated. - Sending should work regardless of the recipient’s trustlines or account state, and funds should arrive at the original Stellar account without extra steps. - The document stresses usability: anchors/wallets should avoid complex workflows, so any solution must stay simple, fast, and easy to implement. - - [SEP-0017](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - - [SEP-0016](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts + - [SEP-17](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) + - [SEP-16](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts - It is not possible to satisfy all requirements in the protocol's current form. -#### Issues with [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +#### Issues with [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - If base reserve increases, malicious actors could add large numbers of trustlines to an account. - Accounts can be DoS'd via the subentry limit. @@ -48,12 +48,12 @@ tags: #### Fee Mechanisms -- David proposed [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): +- David proposed [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): - Enables future-upgradability of `TransactionEnvelope` - - Allows a simpler implementation of [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) + - Allows a simpler implementation of [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) ### Follow-up Actions - **David**: Write a short proposal on "embryonic accounts". -- **Jeremy**: Clarify SEP-0016 workflow with deterministic accounts. -- **Jon**: Provide analysis of attack surfaces and issues in [CAP-0013](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). +- **Jeremy**: Clarify SEP-16 workflow with deterministic accounts. +- **Jon**: Provide analysis of attack surfaces and issues in [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index e015c4e683..1dd672cb3d 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -14,17 +14,17 @@ tags: ### Announcements -- [CAP-0016](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-0016 will only be revived if CAP-0018 encounters implementation issues. -- [CAP-0018](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. -- [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. +- [CAP-16](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. +- [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. +- [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. - Jed was in Singapore this week; trustline discussions were postponed until his return. ### Agenda #### Fee Follow-ups -- Topics: [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. -- Decision: Push CAP-0019 to FCP: Acceptance and reframe CAP-0015 in the context of CAP-0019. +- Topics: [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. +- Decision: Push CAP-19 to FCP: Acceptance and reframe CAP-15 in the context of CAP-19. #### Future of the Order Book - Ideation diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index ef88d7f78a..042a36b572 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -15,22 +15,22 @@ tags: ### Announcements -- [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) (Future-upgradable TransactionEnvelope type) is moving to Accepted. +- [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) (Future-upgradable TransactionEnvelope type) is moving to Accepted. - "Implementation Review" stage added for CAPs (see https://github.com/stellar/stellar-protocol/pull/279); keep in mind for future CAP process. - Jed out this week; trustline discussion pushed again. -- [CAP-0020](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. +- [CAP-20](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. ### Agenda -- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (Bump Fee Extension): Modified to utilize [CAP-0019](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. +- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (Bump Fee Extension): Modified to utilize [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. - David: Two transaction IDs (inner and outer) as a result of the change. - - Nico: Original feedback was that this relies on [CAP-0005](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) logic that no longer exists in the CAP-0005 implementation. + - Nico: Original feedback was that this relies on [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) logic that no longer exists in the CAP-5 implementation. - Nico and David to discuss offline; David to submit additional edits and document constraints and issues from the meeting. -- [SEP-0019](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) (Bootstrapping Multisig Transaction Submission): +- [SEP-19](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) (Bootstrapping Multisig Transaction Submission): - Significant discussion with contributions from Paul Selden, Antoine (MrTicot), Orbit, Johan, and others. - - Focus should remain on SEP-0019 and direction for any related SEPs. + - Focus should remain on SEP-19 and direction for any related SEPs. - Can pull in Paul and others for the next meeting; it is likely the most active SEP currently. - - SEP-0019 is largely focused on the StellarGuard protocol and currently only describes basic flow properties and API endpoints; substantial work remains. + - SEP-19 is largely focused on the StellarGuard protocol and currently only describes basic flow properties and API endpoints; substantial work remains. - Open questions: - Metadata (storage and off-chain handling) - Coordinator (no core changes required) diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index d3c7a6acf4..58be86d858 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -15,7 +15,7 @@ tags: [legacy, CAP-15, SEP-16] - Discussing next steps for trustlines work. - David personally doesn't feel good about pushing forward Sponsored Trustlines, despite multiple people who think it's mostly there (Tom, Orbit). -- There was initial discussion of going back to [SEP-0016 (atp3 account transfer)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). +- There was initial discussion of going back to [SEP-16 (atp3 account transfer)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). - Goal today is to discuss alternative solutions (as opposed to criticism of existing solutions), given the requirements that are extensively listed [here](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit). - Deposits have to finish without additional user clicks, even when the recipient’s account is uncreated or lacks a trustline, and nor should the user need to fund extra XLM. - The send workflow should credit the intended account ID even if no trustline exists, so clients don’t need to coordinate new trustlines for every payment. @@ -42,16 +42,16 @@ tags: [legacy, CAP-15, SEP-16] ### Nico's caveats -- Similar complexities arise as with SEP-0016: clients must track incoming mergeable trustlines, decide whether they matter, query them from Horizon, and take actions. +- Similar complexities arise as with SEP-16: clients must track incoming mergeable trustlines, decide whether they matter, query them from Horizon, and take actions. - This puts significant burden on clients to download and reason about many mergeable trustlines. -- Union-find might help reduce what needs to be downloaded, potentially in tandem with SEP-0016. +- Union-find might help reduce what needs to be downloaded, potentially in tandem with SEP-16. - David, Nico, and Jon's proposals all rely on some form of "incoming trustline" at the core layer, which does not appear substantially simpler than ecosystem-level approaches. -### SEP-0016 thoughts +### SEP-16 thoughts - Defining the last step is difficult given current protocol constraints and would require "shrink to fit" and other small core changes. -- SEP-0016 should likely remain a living document that evolves alongside core capabilities. +- SEP-16 should likely remain a living document that evolves alongside core capabilities. ### Follow-up actions -- David to put together a list of constraints and concerns blocking [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. +- David to put together a list of constraints and concerns blocking [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index db9995647f..9281d3f58f 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -9,15 +9,15 @@ tags: [legacy, CAP-15, CAP-21] ### Announcements -- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. +- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. ### Agenda -- David's Pre-Condition proposal: [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - - After several iterations with the Channels working group, CAP-0021 was presented for decision. - - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-0021 to FCP: Acceptance. -- Clarifying final aspects of fee bump ([CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: +- David's Pre-Condition proposal: [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) + - After several iterations with the Channels working group, CAP-21 was presented for decision. + - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-21 to FCP: Acceptance. +- Clarifying final aspects of fee bump ([CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: - https://github.com/stellar/stellar-protocol/pull/323 - - CAP-0015 will move to FCP: Acceptance after a final round of wording changes. + - CAP-15 will move to FCP: Acceptance after a final round of wording changes. - If time permits, Jon to give an update from the trustlines/balances work. - Decision made not to discuss this fully until the draft is finalized, particularly around rationale and alternative ideas. diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index f3a7a33574..8492364422 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -14,17 +14,17 @@ tags: ### Announcements -- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. -- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. +- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. +- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. ### Agenda -- [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - _Two-Part Payments with BalanceEntry_ +- [CAP-23](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - _Two-Part Payments with BalanceEntry_ - Focused on temporal separation between initiating a payment and receiving a payment. - Explicitly **does not** replace existing payment operations. - **David's initial framing:** ~10% additional complexity yields significantly more utility. -#### CAP-0023 Design Discussion +#### CAP-23 Design Discussion - **AuthorizeBalance** - Should include an optional `AccountID *revocableBy`. @@ -57,18 +57,18 @@ tags: - Some concern that less-knowledgeable users may struggle with the flow. - Others believe wallet UX and the existing payment operation mitigate this risk. -### CAP-0021 / CAP-0022 & Payment Channel Implementation +### CAP-21 / CAP-22 & Payment Channel Implementation -- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - _Generalized transaction preconditions_ - - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-0022. +- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - _Generalized transaction preconditions_ + - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-22. - May be implemented separately (branch or protocol version) for payment channels. - Preference is to resolve outstanding issues before acceptance. -- [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - _Invalid transactions must have no effects_ - - Open question: adopt CAP-0022 as written, or pursue a stronger invariant (only fully executing transactions succeed). +- [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - _Invalid transactions must have no effects_ + - Open question: adopt CAP-22 as written, or pursue a stronger invariant (only fully executing transactions succeed). ### Follow-Up Actions -- [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) +- [CAP-23](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) - Add explicit behavior details regarding `ACCOUNT_MERGE`. - Evaluate low-threshold usage for `ClaimBalance`. - Append `Op` to operation names in XDR. diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index d3d237a3b5..2d01f0053a 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -15,14 +15,14 @@ tags: ### Agenda -- [CAP-0024](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Path Payment w/Fixed Amount +- [CAP-24](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Path Payment w/Fixed Amount - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. -- [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Implementation question around removal of one-time signers, which currently does not take place. - Consensus: preserve existing behavior for now and discuss behavior changes separately. - Jon to follow up with Nico when he returns to better understand existing behavior. -- [CAP-0021](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-0022](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-0025](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - Preconditions, Invalid Transaction Effects, Shadow Bucket Removal - - CAP-0025 moves to Final Comment Period (FCP): Acceptance. - - CAP-0021 is dependent on CAP-0022. - - CAP-0022 must address additional feedback from Nico. - - David to own follow-up on CAP-0021/0022 dependency resolution. +- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-25](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - Preconditions, Invalid Transaction Effects, Shadow Bucket Removal + - CAP-25 moves to Final Comment Period (FCP): Acceptance. + - CAP-21 is dependent on CAP-22. + - CAP-22 must address additional feedback from Nico. + - David to own follow-up on CAP-21/0022 dependency resolution. From 196545f7f68d095abfb120a9b2b30c412760a574 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 09:46:06 -0400 Subject: [PATCH 04/17] =?UTF-8?q?=F0=9F=A4=9D=20Address=202019=20meeting?= =?UTF-8?q?=20review=20feedback?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add CAP-6 discovery metadata, use the canonical CAP-15 title, and record the generated tag route. Co-authored-by: Codex --- meetings/2019-01-24.mdx | 3 ++- routes.txt | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 3bf9b40791..82d2375db9 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -8,6 +8,7 @@ tags: - CAP-13 - CAP-15 - CAP-5 + - CAP-6 - CAP-7 - CAP-8 - SEP-13 @@ -22,7 +23,7 @@ tags: - [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. - [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/master/drafts/draft-detacct.md). -- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions update. +- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Fee-Bump Transactions update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. ### Meeting Notes diff --git a/routes.txt b/routes.txt index 44bc2b56df..21eec3e0c8 100644 --- a/routes.txt +++ b/routes.txt @@ -954,6 +954,7 @@ /meetings/tags/cap-24 /meetings/tags/cap-25 /meetings/tags/cap-5 +/meetings/tags/cap-6 /meetings/tags/cap-7 /meetings/tags/cap-8 /meetings/tags/cap-9 From 41d27fb3c84ea3434415186a656de1545a39c5fe Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 09:59:46 -0400 Subject: [PATCH 05/17] =?UTF-8?q?=F0=9F=A4=9D=20Correct=20historical=20pro?= =?UTF-8?q?posal=20references?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pin the CAP-7 draft to its final historical revision and use the canonical SEP-16 title. Co-authored-by: Codex --- meetings/2019-01-24.mdx | 2 +- meetings/2019-04-04.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 82d2375db9..cbe788e73f 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -22,7 +22,7 @@ tags: - [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. -- [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/master/drafts/draft-detacct.md). +- [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md). - [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Fee-Bump Transactions update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index 58be86d858..ad2bbf6dcf 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -15,7 +15,7 @@ tags: [legacy, CAP-15, SEP-16] - Discussing next steps for trustlines work. - David personally doesn't feel good about pushing forward Sponsored Trustlines, despite multiple people who think it's mostly there (Tom, Orbit). -- There was initial discussion of going back to [SEP-16 (atp3 account transfer)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). +- There was initial discussion of going back to [SEP-16: Account Transfer Permissionless Payment Protocol (atp3)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). - Goal today is to discuss alternative solutions (as opposed to criticism of existing solutions), given the requirements that are extensively listed [here](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit). - Deposits have to finish without additional user clicks, even when the recipient’s account is uncreated or lacks a trustline, and nor should the user need to fund extra XLM. - The send workflow should credit the intended account ID even if no trustline exists, so clients don’t need to coordinate new trustlines for every payment. From f734604bcdc0363e2a932c0fe7d5bd0cc1645f38 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 10:04:50 -0400 Subject: [PATCH 06/17] =?UTF-8?q?=F0=9F=A4=9D=20Capitalize=20Stellar=20in?= =?UTF-8?q?=20meeting=20notes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Correct the proper-name capitalization in the Meridian meeting summary. Co-authored-by: Codex --- meetings/2019-11-04.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meetings/2019-11-04.mdx b/meetings/2019-11-04.mdx index 83c12684a4..1dbe84e4bd 100644 --- a/meetings/2019-11-04.mdx +++ b/meetings/2019-11-04.mdx @@ -18,7 +18,7 @@ The talk focused on aligning governance, resources, and community momentum as St - What SDF is (and is not): a nonprofit with no shareholders or dividends, focused solely on long-term network adoption and ecosystem health. - Decentralization progress: increasing validator independence and a maturing governance feedback loop from community discussion to protocol change. - What’s working: scalable technology, a growing global team, stronger community coordination, and expanding ecosystem projects. -- What needs improvement: stellar-wide marketing, policy and regulatory engagement, ongoing transparency, and more effective lumen distribution. +- What needs improvement: Stellar-wide marketing, policy and regulatory engagement, ongoing transparency, and more effective lumen distribution. - Treasury reset: announcement of a 50B XLM burn, with remaining resources reorganized to better align with mission and execution capacity. - New funding buckets: operational runway with a multi-year release plan, ecosystem and infrastructure support, currency and liquidity support, use-case investment, and user distribution through applications. - Enterprise Fund model: the ability to invest in or acquire companies to accelerate priority use cases, with returns recycled back into the fund. From 4a2bd293f89771310f61abe1c3d3744642b0776a Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 10:18:49 -0400 Subject: [PATCH 07/17] =?UTF-8?q?=F0=9F=96=8B=EF=B8=8F=20Improve=202019=20?= =?UTF-8?q?meeting=20descriptions?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 2 +- meetings/2019-03-07.mdx | 2 +- meetings/2019-03-14.mdx | 2 +- meetings/2019-03-21.mdx | 2 +- meetings/2019-03-28.mdx | 2 +- meetings/2019-04-04.mdx | 2 +- meetings/2019-06-13.mdx | 2 +- meetings/2019-06-27.mdx | 2 +- meetings/2019-07-25.mdx | 2 +- meetings/2019-11-04.mdx | 8 ++++---- 10 files changed, 13 insertions(+), 13 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index cbe788e73f..8b76f8299f 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -1,6 +1,6 @@ --- title: "2019-01-24" -description: "This overview highlights anchor services and network fees and resource limits." +description: "This protocol discussion covered CAP-5 and CAP-6, deterministic account creation, fee-bump transactions, and trustline usability proposals for simpler deposits and payments." authors: goodnow tags: - legacy diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 2b99ef8e8d..95cb2ec9f2 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-07" -description: "This overview highlights network fees and resource limits." +description: "This protocol discussion reviewed CAP-17 and CAP-18, prioritized trustline and payment-channel work, and compared fee-sponsorship proposals including CAP-10 and CAP-15." authors: goodnow tags: - legacy diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index c9a4b55068..e030935685 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-14" -description: "This overview highlights anchor services and network fees and resource limits." +description: "This protocol discussion covered CAP-17 and CAP-18 decisions, SEP-16 and SEP-17 payment flows, CAP-13 trustline balances, and CAP-19 transaction-envelope versioning." authors: goodnow tags: - legacy diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index 1dd672cb3d..ff6ca1afe7 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-21" -description: "This overview highlights order book trading and network fees and resource limits." +description: "This protocol discussion advanced authorization and transaction-envelope proposals, revisited fee-bump design, and explored possible directions for Stellar’s order book." authors: goodnow tags: - legacy diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index 042a36b572..daec81cc2f 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-28" -description: "This overview highlights network fees and resource limits." +description: "This protocol discussion reviewed CAP-19 and CAP-20 implementation progress, refined CAP-15 fee-bump transactions, and considered SEP-19 multisig transaction submission." authors: goodnow tags: - legacy diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index ad2bbf6dcf..b54fc468a8 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -1,6 +1,6 @@ --- title: "2019-04-04" -description: "This overview highlights Horizon API and network fees and resource limits." +description: "This protocol discussion evaluated alternatives to sponsored trustlines, including SEP-16 and mergeable trustlines, with attention to client complexity, privacy, and payment usability." authors: goodnow tags: [legacy, CAP-15, SEP-16] --- diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 9281d3f58f..9a81b08cc4 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -1,6 +1,6 @@ --- title: "2019-06-13" -description: "This overview highlights network fees and resource limits." +description: "This protocol discussion advanced CAP-21 generalized transaction preconditions and CAP-15 fee-bump transactions toward acceptance, focusing on payment channels and implementation details." authors: goodnow tags: [legacy, CAP-15, CAP-21] --- diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index 8492364422..396c75e49a 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -1,6 +1,6 @@ --- title: "2019-06-27" -description: "This overview highlights transaction data." +description: "This protocol discussion examined CAP-23 two-part payments and claimable balances alongside CAP-21 transaction preconditions and CAP-22 invalid-transaction semantics." authors: goodnow tags: - legacy diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index 2d01f0053a..bfc07735fe 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -1,6 +1,6 @@ --- title: "2019-07-25" -description: "This overview highlights protocol updates, tooling demos, and ecosystem discussions." +description: "This protocol discussion reviewed CAP-24 path-payment symmetry, CAP-15 signer behavior, and decisions involving transaction preconditions, invalid transactions, and bucket shadowing." authors: goodnow tags: - legacy diff --git a/meetings/2019-11-04.mdx b/meetings/2019-11-04.mdx index 1dbe84e4bd..bf904225e8 100644 --- a/meetings/2019-11-04.mdx +++ b/meetings/2019-11-04.mdx @@ -1,6 +1,6 @@ --- title: "2019-11-04" -description: "This overview highlights validator operations and anchor services." +description: "Denelle Dixon’s Meridian address examined SDF’s nonprofit stewardship, decentralization progress, and treasury restructuring, followed by a Q&A with Jed McCaleb." authors: goodnow tags: [community] --- @@ -11,7 +11,7 @@ import YouTube from "@site/src/components/YouTube"; Denelle Dixon closed day one of Meridian with a forward-looking address on SDF’s evolving role and Stellar’s long-term direction. Speaking from the perspective of her first six months leading the foundation, she emphasized SDF’s identity as a nonprofit steward and ecosystem convener, translating open-network principles such as transparency, interoperability, and trust-by-design into practical support for builders, institutions, and regulators. -The talk focused on aligning governance, resources, and community momentum as Stellar moves from early growth into a more decentralized and durable network. Dixon outlined what has worked well so far, where SDF has fallen short, and how a restructured treasury and clearer priorities are meant to support sustainable adoption while reducing the foundation’s centrality over time. +The talk focused on aligning governance, resources, and community momentum as Stellar moves from early growth into a more decentralized and durable network. Denelle outlined what has worked well so far, where SDF has fallen short, and how a restructured treasury and clearer priorities are meant to support sustainable adoption while reducing the foundation’s centrality over time. Jed McCaleb joined Denelle for the closing audience Q&A. ### Key Topics @@ -19,8 +19,8 @@ The talk focused on aligning governance, resources, and community momentum as St - Decentralization progress: increasing validator independence and a maturing governance feedback loop from community discussion to protocol change. - What’s working: scalable technology, a growing global team, stronger community coordination, and expanding ecosystem projects. - What needs improvement: Stellar-wide marketing, policy and regulatory engagement, ongoing transparency, and more effective lumen distribution. -- Treasury reset: announcement of a 50B XLM burn, with remaining resources reorganized to better align with mission and execution capacity. +- Treasury reset: announcement of a 55.5 billion lumen burn, with remaining resources reorganized to better align with mission and execution capacity. - New funding buckets: operational runway with a multi-year release plan, ecosystem and infrastructure support, currency and liquidity support, use-case investment, and user distribution through applications. - Enterprise Fund model: the ability to invest in or acquire companies to accelerate priority use cases, with returns recycled back into the fund. - Regulatory approach: emphasis on education and consumer protection, positioning the network layer as internet-like infrastructure. -- Q&A highlights: sustaining SDF beyond the initial multi-year plan, improving DEX liquidity, overcoming network-effects challenges, environmental advantages versus mining-based chains, and inclusion as a requirement for mainstream adoption. +- Closing Q&A with Jed McCaleb: sustaining SDF beyond the initial multi-year plan, improving DEX liquidity, overcoming network-effects challenges, environmental advantages versus mining-based chains, and inclusion as a requirement for mainstream adoption. From 27b7c90fed6dd2af4e79bb896e329f8981abce89 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 12:17:02 -0400 Subject: [PATCH 08/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Unquote=20meeting?= =?UTF-8?q?=20descriptions?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 2 +- meetings/2019-03-07.mdx | 2 +- meetings/2019-03-14.mdx | 2 +- meetings/2019-03-21.mdx | 2 +- meetings/2019-03-28.mdx | 2 +- meetings/2019-04-04.mdx | 2 +- meetings/2019-06-13.mdx | 2 +- meetings/2019-06-27.mdx | 2 +- meetings/2019-07-25.mdx | 2 +- meetings/2019-11-04.mdx | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 8b76f8299f..326538523f 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -1,6 +1,6 @@ --- title: "2019-01-24" -description: "This protocol discussion covered CAP-5 and CAP-6, deterministic account creation, fee-bump transactions, and trustline usability proposals for simpler deposits and payments." +description: This protocol discussion covered CAP-5 and CAP-6, deterministic account creation, fee-bump transactions, and trustline usability proposals for simpler deposits and payments. authors: goodnow tags: - legacy diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 95cb2ec9f2..122f949372 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-07" -description: "This protocol discussion reviewed CAP-17 and CAP-18, prioritized trustline and payment-channel work, and compared fee-sponsorship proposals including CAP-10 and CAP-15." +description: This protocol discussion reviewed CAP-17 and CAP-18, prioritized trustline and payment-channel work, and compared fee-sponsorship proposals including CAP-10 and CAP-15. authors: goodnow tags: - legacy diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index e030935685..dfa20184c4 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-14" -description: "This protocol discussion covered CAP-17 and CAP-18 decisions, SEP-16 and SEP-17 payment flows, CAP-13 trustline balances, and CAP-19 transaction-envelope versioning." +description: This protocol discussion covered CAP-17 and CAP-18 decisions, SEP-16 and SEP-17 payment flows, CAP-13 trustline balances, and CAP-19 transaction-envelope versioning. authors: goodnow tags: - legacy diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index ff6ca1afe7..4a7b1790e6 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-21" -description: "This protocol discussion advanced authorization and transaction-envelope proposals, revisited fee-bump design, and explored possible directions for Stellar’s order book." +description: This protocol discussion advanced authorization and transaction-envelope proposals, revisited fee-bump design, and explored possible directions for Stellar’s order book. authors: goodnow tags: - legacy diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index daec81cc2f..928dd897a3 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -1,6 +1,6 @@ --- title: "2019-03-28" -description: "This protocol discussion reviewed CAP-19 and CAP-20 implementation progress, refined CAP-15 fee-bump transactions, and considered SEP-19 multisig transaction submission." +description: This protocol discussion reviewed CAP-19 and CAP-20 implementation progress, refined CAP-15 fee-bump transactions, and considered SEP-19 multisig transaction submission. authors: goodnow tags: - legacy diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index b54fc468a8..c7a88c8e7a 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -1,6 +1,6 @@ --- title: "2019-04-04" -description: "This protocol discussion evaluated alternatives to sponsored trustlines, including SEP-16 and mergeable trustlines, with attention to client complexity, privacy, and payment usability." +description: This protocol discussion evaluated alternatives to sponsored trustlines, including SEP-16 and mergeable trustlines, with attention to client complexity, privacy, and payment usability. authors: goodnow tags: [legacy, CAP-15, SEP-16] --- diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 9a81b08cc4..579e77139f 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -1,6 +1,6 @@ --- title: "2019-06-13" -description: "This protocol discussion advanced CAP-21 generalized transaction preconditions and CAP-15 fee-bump transactions toward acceptance, focusing on payment channels and implementation details." +description: This protocol discussion advanced CAP-21 generalized transaction preconditions and CAP-15 fee-bump transactions toward acceptance, focusing on payment channels and implementation details. authors: goodnow tags: [legacy, CAP-15, CAP-21] --- diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index 396c75e49a..ebe8702bb5 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -1,6 +1,6 @@ --- title: "2019-06-27" -description: "This protocol discussion examined CAP-23 two-part payments and claimable balances alongside CAP-21 transaction preconditions and CAP-22 invalid-transaction semantics." +description: This protocol discussion examined CAP-23 two-part payments and claimable balances alongside CAP-21 transaction preconditions and CAP-22 invalid-transaction semantics. authors: goodnow tags: - legacy diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index bfc07735fe..e9f039a4d0 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -1,6 +1,6 @@ --- title: "2019-07-25" -description: "This protocol discussion reviewed CAP-24 path-payment symmetry, CAP-15 signer behavior, and decisions involving transaction preconditions, invalid transactions, and bucket shadowing." +description: This protocol discussion reviewed CAP-24 path-payment symmetry, CAP-15 signer behavior, and decisions involving transaction preconditions, invalid transactions, and bucket shadowing. authors: goodnow tags: - legacy diff --git a/meetings/2019-11-04.mdx b/meetings/2019-11-04.mdx index bf904225e8..93df2587df 100644 --- a/meetings/2019-11-04.mdx +++ b/meetings/2019-11-04.mdx @@ -1,6 +1,6 @@ --- title: "2019-11-04" -description: "Denelle Dixon’s Meridian address examined SDF’s nonprofit stewardship, decentralization progress, and treasury restructuring, followed by a Q&A with Jed McCaleb." +description: Denelle Dixon’s Meridian address examined SDF’s nonprofit stewardship, decentralization progress, and treasury restructuring, followed by a Q&A with Jed McCaleb. authors: goodnow tags: [community] --- From 4492b8970e503f56363026319179d55a159b8e36 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 12:33:38 -0400 Subject: [PATCH 09/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Standardize=20pro?= =?UTF-8?q?posal=20separators?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-03-07.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 122f949372..6d2d9d1053 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -43,7 +43,7 @@ tags: 1. Replace Min Fee Mechanism 2. Trustline (& other) Usability - - Explicit intent to revive [CAP-13 Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). + - Explicit intent to revive [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). 3. Payment Channels - Focus on core components required for a basic payment channel design. 4. Starlight From 014727d8c7d7c503124f544342b8d0bc41188951 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 13:24:41 -0400 Subject: [PATCH 10/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Correct=20histori?= =?UTF-8?q?cal=20proposal=20labels?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-07-25.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index e9f039a4d0..4974c7b70e 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -17,7 +17,7 @@ tags: - [CAP-24](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Path Payment w/Fixed Amount - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. -- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Implementation question around removal of one-time signers, which currently does not take place. - Consensus: preserve existing behavior for now and discuss behavior changes separately. - Jon to follow up with Nico when he returns to better understand existing behavior. From d2e575c13bf344584e8b78dd5909c22f4cb5c231 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 14:41:09 -0400 Subject: [PATCH 11/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Correct=20histori?= =?UTF-8?q?cal=20proposal=20titles?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 2 +- meetings/2019-03-07.mdx | 8 ++++---- meetings/2019-07-25.mdx | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 326538523f..a8df92b5e0 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -23,7 +23,7 @@ tags: - [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. - [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md). -- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Fee-Bump Transactions update. +- [CAP-15: Bump Fee Transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. ### Meeting Notes diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 6d2d9d1053..3752af09cc 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -34,7 +34,7 @@ tags: ### Final Comment Period - Acceptance -- [CAP-17](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - Update `LastModifiedLedgerSeq` If and Only If LedgerEntry Is Modified (Jonathan Jove) +- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) (Jonathan Jove) - [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - Fine-Grained Control of Authorization (Jonathan Jove) - Address offer mutability (Jon) - CAP-16 to be rejected contingent on CAP-18 approval @@ -52,8 +52,8 @@ tags: ### Deferred Items - [CAP-7](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - Deterministic Account Creation (Jeremy Rubin) -- [CAP-8](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - Self-Identified Pre-Auth Transaction (Jeremy Rubin) -- [CAP-9](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) - Linear / Exterior Immutable Accounts (Jeremy Rubin) +- [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) (Jeremy Rubin) +- [CAP-9: Linear/Exterior Immutable Accounts](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) (Jeremy Rubin) - [CAP-11](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) - Relative Account Freeze (Jeremy Rubin) - Draft: Deterministic accounts and creatorTxID (David Mazières) - [CAP-14](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - Adversarial Transaction Set Ordering (Jeremy Rubin) @@ -72,7 +72,7 @@ tags: - Jed favors pushing fee increases forward immediately. - Current proposals: - [CAP-10](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - Fee Bump Account (Jeremy Rubin) - - [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Bump Fee Transactions (OrbitLens) + - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (OrbitLens) - Pre-draft: feeSource and feeMultiplier (David Mazières) - [Reference spreadsheet](https://docs.google.com/spreadsheets/d/1_u0LE61V-jkXUcNBZW5xhXZEmIz5rQSgZEr8VsVl47o/edit) (OrbitLens) compares fee-sponsorship approaches (CAP-10 fee balances, feeSource/feeMultiplier, deterministic accounts, CAP-15 metadata) across tradeoffs like explicit sponsor control, pre-signed tx support, and algorithmic complexity. - CAP-10 introduces dedicated fee balances so sponsors can preload fees, but it requires new operations and careful management of locked fee funds. diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index 4974c7b70e..292958597f 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -15,7 +15,7 @@ tags: ### Agenda -- [CAP-24](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Path Payment w/Fixed Amount +- [CAP-24: Make PathPayment Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - Implementation question around removal of one-time signers, which currently does not take place. From 8d6ffa34ef0aa1018db43b1fbdda958ae6c21e55 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 15:00:43 -0400 Subject: [PATCH 12/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Expand=20historic?= =?UTF-8?q?al=20proposal=20link=20labels?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 2 +- meetings/2019-03-07.mdx | 10 +++++----- meetings/2019-03-14.mdx | 14 +++++++------- meetings/2019-03-21.mdx | 8 ++++---- meetings/2019-03-28.mdx | 8 ++++---- meetings/2019-04-04.mdx | 2 +- meetings/2019-06-13.mdx | 6 +++--- meetings/2019-06-27.mdx | 12 ++++++------ meetings/2019-07-25.mdx | 2 +- 9 files changed, 32 insertions(+), 32 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index a8df92b5e0..2fa0d6e669 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -20,7 +20,7 @@ tags: ### Agenda -- [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. +- [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. - [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md). - [CAP-15: Bump Fee Transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) update. diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 3752af09cc..0c1cc9f637 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -35,7 +35,7 @@ tags: ### Final Comment Period - Acceptance - [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) (Jonathan Jove) -- [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - Fine-Grained Control of Authorization (Jonathan Jove) +- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (Jonathan Jove) - Address offer mutability (Jon) - CAP-16 to be rejected contingent on CAP-18 approval @@ -51,12 +51,12 @@ tags: ### Deferred Items -- [CAP-7](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - Deterministic Account Creation (Jeremy Rubin) +- [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) (Jeremy Rubin) - [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) (Jeremy Rubin) - [CAP-9: Linear/Exterior Immutable Accounts](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) (Jeremy Rubin) -- [CAP-11](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) - Relative Account Freeze (Jeremy Rubin) +- [CAP-11: Relative Account Freeze](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) (Jeremy Rubin) - Draft: Deterministic accounts and creatorTxID (David Mazières) -- [CAP-14](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - Adversarial Transaction Set Ordering (Jeremy Rubin) +- [CAP-14: Adversarial Transaction Set Ordering](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) (Jeremy Rubin) ### Agenda @@ -71,7 +71,7 @@ tags: - David and Nico prefer a mechanism _before_ raising the min fee. - Jed favors pushing fee increases forward immediately. - Current proposals: - - [CAP-10](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - Fee Bump Account (Jeremy Rubin) + - [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) (Jeremy Rubin) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (OrbitLens) - Pre-draft: feeSource and feeMultiplier (David Mazières) - [Reference spreadsheet](https://docs.google.com/spreadsheets/d/1_u0LE61V-jkXUcNBZW5xhXZEmIz5rQSgZEr8VsVl47o/edit) (OrbitLens) compares fee-sponsorship approaches (CAP-10 fee balances, feeSource/feeMultiplier, deterministic accounts, CAP-15 metadata) across tradeoffs like explicit sponsor control, pre-signed tx support, and algorithmic complexity. diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index dfa20184c4..7726fc86a2 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -20,7 +20,7 @@ tags: ### Announcements - Jon made additional changes to [CAP-18](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. -- [CAP-17](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. +- [CAP-17: Update LastModifiedLedgerSeq If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. ### Agenda @@ -30,11 +30,11 @@ tags: - Deposits must finish once the anchor receives the external asset, never forcing the user to add trustlines or extra XLM, even when accounts are uncreated. - Sending should work regardless of the recipient’s trustlines or account state, and funds should arrive at the original Stellar account without extra steps. - The document stresses usability: anchors/wallets should avoid complex workflows, so any solution must stay simple, fast, and easy to implement. - - [SEP-17](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - - [SEP-16](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts + - [SEP-17: Issuer account funding protocol](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) + - [SEP-16: Account Transfer Permissionless Payment Protocol (@p2p)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts - It is not possible to satisfy all requirements in the protocol's current form. -#### Issues with [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +#### Issues with [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - If base reserve increases, malicious actors could add large numbers of trustlines to an account. - Accounts can be DoS'd via the subentry limit. @@ -48,12 +48,12 @@ tags: #### Fee Mechanisms -- David proposed [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): +- David proposed [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): - Enables future-upgradability of `TransactionEnvelope` - - Allows a simpler implementation of [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) + - Allows a simpler implementation of [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) ### Follow-up Actions - **David**: Write a short proposal on "embryonic accounts". - **Jeremy**: Clarify SEP-16 workflow with deterministic accounts. -- **Jon**: Provide analysis of attack surfaces and issues in [CAP-13](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). +- **Jon**: Provide analysis of attack surfaces and issues in [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index 4a7b1790e6..573606dff4 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -14,16 +14,16 @@ tags: ### Announcements -- [CAP-16](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. -- [CAP-18](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. -- [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. +- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. +- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. +- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. - Jed was in Singapore this week; trustline discussions were postponed until his return. ### Agenda #### Fee Follow-ups -- Topics: [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. +- Topics: [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. - Decision: Push CAP-19 to FCP: Acceptance and reframe CAP-15 in the context of CAP-19. #### Future of the Order Book - Ideation diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index 928dd897a3..4847726eea 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -15,18 +15,18 @@ tags: ### Announcements -- [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) (Future-upgradable TransactionEnvelope type) is moving to Accepted. +- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) is moving to Accepted. - "Implementation Review" stage added for CAPs (see https://github.com/stellar/stellar-protocol/pull/279); keep in mind for future CAP process. - Jed out this week; trustline discussion pushed again. -- [CAP-20](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. +- [CAP-20: Bucket Initial Entries](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. ### Agenda -- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (Bump Fee Extension): Modified to utilize [CAP-19](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md): Modified to utilize [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. - David: Two transaction IDs (inner and outer) as a result of the change. - Nico: Original feedback was that this relies on [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) logic that no longer exists in the CAP-5 implementation. - Nico and David to discuss offline; David to submit additional edits and document constraints and issues from the meeting. -- [SEP-19](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) (Bootstrapping Multisig Transaction Submission): +- [SEP-19: Bootstrapping Multisig Transaction Submission](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md): - Significant discussion with contributions from Paul Selden, Antoine (MrTicot), Orbit, Johan, and others. - Focus should remain on SEP-19 and direction for any related SEPs. - Can pull in Paul and others for the next meeting; it is likely the most active SEP currently. diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index c7a88c8e7a..e93e65fbbf 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -54,4 +54,4 @@ tags: [legacy, CAP-15, SEP-16] ### Follow-up actions -- David to put together a list of constraints and concerns blocking [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. +- David to put together a list of constraints and concerns blocking [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 579e77139f..3fc34e31ec 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -9,14 +9,14 @@ tags: [legacy, CAP-15, CAP-21] ### Announcements -- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. ### Agenda -- David's Pre-Condition proposal: [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- David's Pre-Condition proposal: [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - After several iterations with the Channels working group, CAP-21 was presented for decision. - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-21 to FCP: Acceptance. -- Clarifying final aspects of fee bump ([CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: +- Clarifying final aspects of fee bump ([CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: - https://github.com/stellar/stellar-protocol/pull/323 - CAP-15 will move to FCP: Acceptance after a final round of wording changes. - If time permits, Jon to give an update from the trustlines/balances work. diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index ebe8702bb5..beb809c3a5 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -14,12 +14,12 @@ tags: ### Announcements -- [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. -- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. +- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. ### Agenda -- [CAP-23](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - _Two-Part Payments with BalanceEntry_ +- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - Focused on temporal separation between initiating a payment and receiving a payment. - Explicitly **does not** replace existing payment operations. - **David's initial framing:** ~10% additional complexity yields significantly more utility. @@ -59,16 +59,16 @@ tags: ### CAP-21 / CAP-22 & Payment Channel Implementation -- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - _Generalized transaction preconditions_ +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-22. - May be implemented separately (branch or protocol version) for payment channels. - Preference is to resolve outstanding issues before acceptance. -- [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - _Invalid transactions must have no effects_ +- [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - Open question: adopt CAP-22 as written, or pursue a stronger invariant (only fully executing transactions succeed). ### Follow-Up Actions -- [CAP-23](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) +- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) - Add explicit behavior details regarding `ACCOUNT_MERGE`. - Evaluate low-threshold usage for `ClaimBalance`. - Append `Op` to operation names in XDR. diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index 292958597f..baf4c5d0a0 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -21,7 +21,7 @@ tags: - Implementation question around removal of one-time signers, which currently does not take place. - Consensus: preserve existing behavior for now and discuss behavior changes separately. - Jon to follow up with Nico when he returns to better understand existing behavior. -- [CAP-21](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-22](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-25](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - Preconditions, Invalid Transaction Effects, Shadow Bucket Removal +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-25: Remove Bucket Shadowing](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - CAP-25 moves to Final Comment Period (FCP): Acceptance. - CAP-21 is dependent on CAP-22. - CAP-22 must address additional feedback from Nico. From 8fa7ff4b6873808919dccb8c0960bb9cc26a5442 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 15:04:16 -0400 Subject: [PATCH 13/17] =?UTF-8?q?=F0=9F=93=9D=20Consolidate=20historical?= =?UTF-8?q?=20proposal=20resources?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 21 +++++++++++++++++---- meetings/2019-03-07.mdx | 35 +++++++++++++++++++++++++---------- meetings/2019-03-14.mdx | 26 +++++++++++++++++++------- meetings/2019-03-21.mdx | 15 +++++++++++---- meetings/2019-03-28.mdx | 18 +++++++++++++----- meetings/2019-04-04.mdx | 9 +++++++-- meetings/2019-06-13.mdx | 11 ++++++++--- meetings/2019-06-27.mdx | 19 +++++++++++++------ meetings/2019-07-25.mdx | 14 +++++++++++--- 9 files changed, 124 insertions(+), 44 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index 2fa0d6e669..d2522a7a9c 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -20,10 +20,10 @@ tags: ### Agenda -- [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) & [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - moving to approval. +- CAP-5 & CAP-6 - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. -- [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md). -- [CAP-15: Bump Fee Transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) update. +- CAP-7 revised proposal. +- CAP-15 update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. ### Meeting Notes @@ -34,7 +34,7 @@ tags: - Vastly simplified since prior iteration. - Salt mechanism needed; likely a full hash to prevent protocol rewind attacks. - Cosigned Assets: - - Related to [SEP-8 (Regulated Assets)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md). + - Related to SEP-8. - NFT discussions considered orthogonal; may warrant a separate CAP. - Catalog of no-op operations discussed: - Payment to oneself @@ -65,3 +65,16 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced - David: add concrete deterministic-account examples, harden salt handling, and spell out whether those accounts supplant CAP-10/CAP-15 work. - Orbit: collect NFT and Asset-object feedback to determine whether a new CAP is warranted. - Jeremy: respond to Tom’s SEP-13A comments and close the remaining gaps in the proposal. + +### Resources + +- [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) +- [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) +- [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md) +- [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) +- [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) +- [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +- [CAP-15: Bump Fee Transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [SEP-6: Anchor/Client interoperability](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) +- [SEP-8: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) +- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 0c1cc9f637..60afa3ee5d 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -34,8 +34,8 @@ tags: ### Final Comment Period - Acceptance -- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) (Jonathan Jove) -- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (Jonathan Jove) +- CAP-17 (Jonathan Jove) +- CAP-18 (Jonathan Jove) - Address offer mutability (Jon) - CAP-16 to be rejected contingent on CAP-18 approval @@ -43,7 +43,7 @@ tags: 1. Replace Min Fee Mechanism 2. Trustline (& other) Usability - - Explicit intent to revive [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) (Dan Robinson). + - Explicit intent to revive CAP-13 (Dan Robinson). 3. Payment Channels - Focus on core components required for a basic payment channel design. 4. Starlight @@ -51,12 +51,12 @@ tags: ### Deferred Items -- [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) (Jeremy Rubin) -- [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) (Jeremy Rubin) -- [CAP-9: Linear/Exterior Immutable Accounts](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) (Jeremy Rubin) -- [CAP-11: Relative Account Freeze](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) (Jeremy Rubin) +- CAP-7 (Jeremy Rubin) +- CAP-8 (Jeremy Rubin) +- CAP-9 (Jeremy Rubin) +- CAP-11 (Jeremy Rubin) - Draft: Deterministic accounts and creatorTxID (David Mazières) -- [CAP-14: Adversarial Transaction Set Ordering](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) (Jeremy Rubin) +- CAP-14 (Jeremy Rubin) ### Agenda @@ -71,8 +71,8 @@ tags: - David and Nico prefer a mechanism _before_ raising the min fee. - Jed favors pushing fee increases forward immediately. - Current proposals: - - [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) (Jeremy Rubin) - - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) (OrbitLens) + - CAP-10 (Jeremy Rubin) + - CAP-15 (OrbitLens) - Pre-draft: feeSource and feeMultiplier (David Mazières) - [Reference spreadsheet](https://docs.google.com/spreadsheets/d/1_u0LE61V-jkXUcNBZW5xhXZEmIz5rQSgZEr8VsVl47o/edit) (OrbitLens) compares fee-sponsorship approaches (CAP-10 fee balances, feeSource/feeMultiplier, deterministic accounts, CAP-15 metadata) across tradeoffs like explicit sponsor control, pre-signed tx support, and algorithmic complexity. - CAP-10 introduces dedicated fee balances so sponsors can preload fees, but it requires new operations and careful management of locked fee funds. @@ -105,3 +105,18 @@ tags: - **Jon Jove** to update CAPs based on email list feedback. - **Tom Quisel** to revise and present hard requirements for trustline usability. - **David** to submit a new proposal for TransactionEnvelope versioning to enable changes like CAP-15. + +### Resources + +- [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) +- [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) +- [CAP-9: Linear/Exterior Immutable Accounts](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0009.md) +- [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) +- [CAP-11: Relative Account Freeze](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0011.md) +- [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +- [CAP-14: Adversarial Transaction Set Ordering](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) +- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) +- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) +- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index 7726fc86a2..4a657a79de 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -20,7 +20,7 @@ tags: ### Announcements - Jon made additional changes to [CAP-18](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. -- [CAP-17: Update LastModifiedLedgerSeq If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) moved to **Approved**. +- CAP-17 moved to **Approved**. ### Agenda @@ -30,11 +30,11 @@ tags: - Deposits must finish once the anchor receives the external asset, never forcing the user to add trustlines or extra XLM, even when accounts are uncreated. - Sending should work regardless of the recipient’s trustlines or account state, and funds should arrive at the original Stellar account without extra steps. - The document stresses usability: anchors/wallets should avoid complex workflows, so any solution must stay simple, fast, and easy to implement. - - [SEP-17: Issuer account funding protocol](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md): Deposit & transfer of assets using [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - - [SEP-16: Account Transfer Permissionless Payment Protocol (@p2p)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md): Deposit & transfer of assets using deterministic accounts + - SEP-17: Deposit & transfer of assets using CAP-13 + - SEP-16: Deposit & transfer of assets using deterministic accounts - It is not possible to satisfy all requirements in the protocol's current form. -#### Issues with [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +#### Issues with CAP-13 - If base reserve increases, malicious actors could add large numbers of trustlines to an account. - Accounts can be DoS'd via the subentry limit. @@ -48,12 +48,24 @@ tags: #### Fee Mechanisms -- David proposed [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md): +- David proposed CAP-19: - Enables future-upgradability of `TransactionEnvelope` - - Allows a simpler implementation of [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) + - Allows a simpler implementation of CAP-15 ### Follow-up Actions - **David**: Write a short proposal on "embryonic accounts". - **Jeremy**: Clarify SEP-16 workflow with deterministic accounts. -- **Jon**: Provide analysis of attack surfaces and issues in [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md). +- **Jon**: Provide analysis of attack surfaces and issues in CAP-13. + +### Resources + +- [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-17: Update LastModifiedLedgerSeq If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) +- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) +- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [SEP-6: Anchor/Client interoperability](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) +- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [SEP-16: Account Transfer Permissionless Payment Protocol (@p2p)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md) +- [SEP-17: Issuer account funding protocol (CAP-13 Based)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md) diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index 573606dff4..cf6e90710a 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -14,16 +14,16 @@ tags: ### Announcements -- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) rejected in favor of [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. -- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) moved to Accepted. -- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) moved to FCP: Acceptance. +- CAP-16 rejected in favor of CAP-18 (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. +- CAP-18 moved to Accepted. +- CAP-19 moved to FCP: Acceptance. - Jed was in Singapore this week; trustline discussions were postponed until his return. ### Agenda #### Fee Follow-ups -- Topics: [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md), [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), and other fee-related suggestions. +- Topics: CAP-19, CAP-15, and other fee-related suggestions. - Decision: Push CAP-19 to FCP: Acceptance and reframe CAP-15 in the context of CAP-19. #### Future of the Order Book - Ideation @@ -31,3 +31,10 @@ tags: - Broad discussion of possible directions for the order book. - No commitments were made. - Goal: Produce an exhaustive list of ideas, followed by prioritization and requirements definition in future sessions. + +### Resources + +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) +- [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) +- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index 4847726eea..dc58a24d09 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -15,18 +15,18 @@ tags: ### Announcements -- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) is moving to Accepted. +- CAP-19 is moving to Accepted. - "Implementation Review" stage added for CAPs (see https://github.com/stellar/stellar-protocol/pull/279); keep in mind for future CAP process. - Jed out this week; trustline discussion pushed again. -- [CAP-20: Bucket Initial Entries](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) implementation is mostly there. +- CAP-20 implementation is mostly there. ### Agenda -- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md): Modified to utilize [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md). Goal is to bring it to a vote, or enumerate what is needed to make it pass. +- CAP-15: Modified to utilize CAP-19. Goal is to bring it to a vote, or enumerate what is needed to make it pass. - David: Two transaction IDs (inner and outer) as a result of the change. - - Nico: Original feedback was that this relies on [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) logic that no longer exists in the CAP-5 implementation. + - Nico: Original feedback was that this relies on CAP-5 logic that no longer exists in the CAP-5 implementation. - Nico and David to discuss offline; David to submit additional edits and document constraints and issues from the meeting. -- [SEP-19: Bootstrapping Multisig Transaction Submission](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md): +- SEP-19: - Significant discussion with contributions from Paul Selden, Antoine (MrTicot), Orbit, Johan, and others. - Focus should remain on SEP-19 and direction for any related SEPs. - Can pull in Paul and others for the next meeting; it is likely the most active SEP currently. @@ -36,3 +36,11 @@ tags: - Coordinator (no core changes required) - Possible use of an IPFS home domain - Orbit to send a document outlining design considerations for multisig transaction coordination. + +### Resources + +- [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [CAP-20: Bucket Initial Entries](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) +- [SEP-19: Bootstrapping Multisig Transaction Submission](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index e93e65fbbf..ce23d4b99d 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -15,7 +15,7 @@ tags: [legacy, CAP-15, SEP-16] - Discussing next steps for trustlines work. - David personally doesn't feel good about pushing forward Sponsored Trustlines, despite multiple people who think it's mostly there (Tom, Orbit). -- There was initial discussion of going back to [SEP-16: Account Transfer Permissionless Payment Protocol (atp3)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md). +- There was initial discussion of going back to SEP-16. - Goal today is to discuss alternative solutions (as opposed to criticism of existing solutions), given the requirements that are extensively listed [here](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit). - Deposits have to finish without additional user clicks, even when the recipient’s account is uncreated or lacks a trustline, and nor should the user need to fund extra XLM. - The send workflow should credit the intended account ID even if no trustline exists, so clients don’t need to coordinate new trustlines for every payment. @@ -54,4 +54,9 @@ tags: [legacy, CAP-15, SEP-16] ### Follow-up actions -- David to put together a list of constraints and concerns blocking [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) from moving forward with Nico. +- David to put together a list of constraints and concerns blocking CAP-15 from moving forward with Nico. + +### Resources + +- [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [SEP-16: Account Transfer Permissionless Payment Protocol (atp3)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md) diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 3fc34e31ec..1b41ede862 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -9,15 +9,20 @@ tags: [legacy, CAP-15, CAP-21] ### Announcements -- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) and [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) moved to FCP: Acceptance. +- CAP-21 and CAP-15 moved to FCP: Acceptance. ### Agenda -- David's Pre-Condition proposal: [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- David's Pre-Condition proposal: CAP-21 - After several iterations with the Channels working group, CAP-21 was presented for decision. - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-21 to FCP: Acceptance. -- Clarifying final aspects of fee bump ([CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md)), including questions raised in Nico's latest pull request: +- Clarifying final aspects of fee bump (CAP-15), including questions raised in Nico's latest pull request: - https://github.com/stellar/stellar-protocol/pull/323 - CAP-15 will move to FCP: Acceptance after a final round of wording changes. - If time permits, Jon to give an update from the trustlines/balances work. - Decision made not to discuss this fully until the draft is finalized, particularly around rationale and alternative ideas. + +### Resources + +- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index beb809c3a5..34b1c6198a 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -14,12 +14,12 @@ tags: ### Announcements -- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) move to _Accepted_ today (after this meeting), barring no new concerns. -- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) moves back to _Draft_ in order to resolve [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) prior to acceptance. +- CAP-15 and CAP-21 move to _Accepted_ today (after this meeting), barring no new concerns. +- CAP-21 moves back to _Draft_ in order to resolve CAP-22 prior to acceptance. ### Agenda -- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) +- CAP-23 - Focused on temporal separation between initiating a payment and receiving a payment. - Explicitly **does not** replace existing payment operations. - **David's initial framing:** ~10% additional complexity yields significantly more utility. @@ -59,17 +59,24 @@ tags: ### CAP-21 / CAP-22 & Payment Channel Implementation -- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- CAP-21 - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-22. - May be implemented separately (branch or protocol version) for payment channels. - Preference is to resolve outstanding issues before acceptance. -- [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) +- CAP-22 - Open question: adopt CAP-22 as written, or pursue a stronger invariant (only fully executing transactions succeed). ### Follow-Up Actions -- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) (Jon) +- CAP-23 (Jon) - Add explicit behavior details regarding `ACCOUNT_MERGE`. - Evaluate low-threshold usage for `ClaimBalance`. - Append `Op` to operation names in XDR. - Extend BalanceEntry claimer via a union to support future signer-based claims or wildcard claimBy. + +### Resources + +- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) +- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index baf4c5d0a0..a1a747c16f 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -15,14 +15,22 @@ tags: ### Agenda -- [CAP-24: Make PathPayment Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) +- CAP-24 - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. -- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- CAP-15 - Implementation question around removal of one-time signers, which currently does not take place. - Consensus: preserve existing behavior for now and discuss behavior changes separately. - Jon to follow up with Nico when he returns to better understand existing behavior. -- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md), [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md), [CAP-25: Remove Bucket Shadowing](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) +- CAP-21, CAP-22, CAP-25 - CAP-25 moves to Final Comment Period (FCP): Acceptance. - CAP-21 is dependent on CAP-22. - CAP-22 must address additional feedback from Nico. - David to own follow-up on CAP-21/0022 dependency resolution. + +### Resources + +- [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) +- [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) +- [CAP-24: Make PathPayment Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) +- [CAP-25: Remove Bucket Shadowing](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) From 60eebc31ec0f883de2c0537e34c0a34b93522658 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 15:09:31 -0400 Subject: [PATCH 14/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Promote=20histori?= =?UTF-8?q?cal=20meeting=20headings?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 15 +++++++-------- meetings/2019-03-07.mdx | 23 +++++++++++------------ meetings/2019-03-14.mdx | 19 +++++++++---------- meetings/2019-03-21.mdx | 13 ++++++------- meetings/2019-03-28.mdx | 9 ++++----- meetings/2019-04-04.mdx | 19 +++++++++---------- meetings/2019-06-13.mdx | 9 ++++----- meetings/2019-06-27.mdx | 15 +++++++-------- meetings/2019-07-25.mdx | 7 +++---- 9 files changed, 60 insertions(+), 69 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index d2522a7a9c..ccca203c6c 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -16,9 +16,7 @@ tags: - SEP-8 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/x0Wrj2kuQ0U/m/CrId5QkoFwAJ) - -### Agenda +## Agenda - CAP-5 & CAP-6 - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. @@ -26,7 +24,7 @@ tags: - CAP-15 update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. -### Meeting Notes +## Meeting Notes - CAP-6 progressing with specific messaging for a targeted use case. - CAP-5 still lacks replace-by-fee and remains problematic. @@ -41,14 +39,14 @@ tags: - Bump op 0 - SetOptions with no fields -### Follow-up Actions +## Follow-up Actions - Johnny: coordinate CAP-6 community and API updates. - David: expand deterministic accounts draft and address CAP-10/CAP-15 implications. - Orbit: consolidate NFT discussions and assess need for a separate CAP. - Jeremy: review SEP-13A comments and address shortcomings in SEP-13. -### Trustline follow-up +## Trustline follow-up The adjacent trustline-focused discussion reprised the agenda above and surfaced additional nuance around asset onboarding and NFT considerations. Tom and Orbit asked the group to clarify how cosigned assets should handle no-op operations, and David emphasized that NFT work is orthogonal but still worth cataloging. @@ -59,14 +57,14 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced - The group cataloged known no-ops (payment to self, bump op 0, SetOptions with no fields) and challenged attendees to bring simple, actionable alternatives rather than more complexity. - A short-term TODO list reiterated that deterministic accounts need a salt/hash to guard against rewind attacks, while CAP-6 updates and SEP-13A comments should stay in sync with the evolving API design. -### Trustline follow-up actions +## Trustline follow-up actions - Johnny: continue improving the DEX-focused messaging tied to CAP-6 and sync with Jon on API revisions. - David: add concrete deterministic-account examples, harden salt handling, and spell out whether those accounts supplant CAP-10/CAP-15 work. - Orbit: collect NFT and Asset-object feedback to determine whether a new CAP is warranted. - Jeremy: respond to Tom’s SEP-13A comments and close the remaining gaps in the proposal. -### Resources +## Resources - [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) - [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) @@ -78,3 +76,4 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced - [SEP-6: Anchor/Client interoperability](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) - [SEP-8: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) - [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/x0Wrj2kuQ0U/m/CrId5QkoFwAJ) diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 60afa3ee5d..9fc65420bf 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -18,9 +18,7 @@ tags: - SEP-13 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/NJl_loV_RXU/m/SarzWEJPAgAJ) - -### Announcements +## Announcements - **[Merging in CAP/SEP Process](https://github.com/stellar/stellar-protocol/pull/247)** - Another round of edits completed; further feedback requested on the PR. @@ -32,14 +30,14 @@ tags: - Payment channels - Payment network (**Starlight**) -### Final Comment Period - Acceptance +## Final Comment Period - Acceptance - CAP-17 (Jonathan Jove) - CAP-18 (Jonathan Jove) - Address offer mutability (Jon) - CAP-16 to be rejected contingent on CAP-18 approval -### Priorities +## Priorities 1. Replace Min Fee Mechanism 2. Trustline (& other) Usability @@ -49,7 +47,7 @@ tags: 4. Starlight - Deferred pending availability of dedicated development resources. -### Deferred Items +## Deferred Items - CAP-7 (Jeremy Rubin) - CAP-8 (Jeremy Rubin) @@ -58,14 +56,14 @@ tags: - Draft: Deterministic accounts and creatorTxID (David Mazières) - CAP-14 (Jeremy Rubin) -### Agenda +## Agenda - Final Comment proposals - new unresolved concerns (30 min max) - CAP-17, CAP-18 - Address offer mutability - Replace Min Fee (60 min max) -### Replace Min Fee Discussion +## Replace Min Fee Discussion - Diverging views: - David and Nico prefer a mechanism _before_ raising the min fee. @@ -82,7 +80,7 @@ tags: - David to draft a new CAP superseding CAP-15, including Transaction versioning. - Johnny to follow up with David regarding feeSource draft status. -### Trustline Usability +## Trustline Usability - Discussion on next steps for CAP-13 Change Trustlines to Balances - Open questions: @@ -96,17 +94,17 @@ tags: - Hard requirements need definition; Tom Q. designated owner. - Developer-friendliness and Account ID semantics must be addressed. -### Meeting Notes +## Meeting Notes - Inline notes (highlighted in blue in original thread) captured above. -### Follow-Up Actions +## Follow-Up Actions - **Jon Jove** to update CAPs based on email list feedback. - **Tom Quisel** to revise and present hard requirements for trustline usability. - **David** to submit a new proposal for TransactionEnvelope versioning to enable changes like CAP-15. -### Resources +## Resources - [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0007.md) - [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) @@ -120,3 +118,4 @@ tags: - [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/NJl_loV_RXU/m/SarzWEJPAgAJ) diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index 4a657a79de..b36de75870 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -15,16 +15,14 @@ tags: - SEP-6 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/uxmo4LM5FWY/m/psazVteTBgAJ) - -### Announcements +## Announcements - Jon made additional changes to [CAP-18](https://github.com/stellar/stellar-protocol/pull/263); with no further comments, it will move out of FCP next week. - CAP-17 moved to **Approved**. -### Agenda +## Agenda -#### Trustline Usability +### Trustline Usability - Restated [requirements document](https://docs.google.com/document/d/1_3KcBTbF7Diu_wu-ArvajYhEcPoDp9SgK5-dNruOK3c/edit#heading=h.8j5x6v50ft4p) up for discussion. The doc captures the desired SEP-6/SEP-13 deposit and send flows: anchors should auto-complete deposits without additional user actions, deliver funds to the intended account even when it has no trustline or XLM, and allow sends to non-existent accounts by crediting the original account ID. - Deposits must finish once the anchor receives the external asset, never forcing the user to add trustlines or extra XLM, even when accounts are uncreated. @@ -34,31 +32,31 @@ tags: - SEP-16: Deposit & transfer of assets using deterministic accounts - It is not possible to satisfy all requirements in the protocol's current form. -#### Issues with CAP-13 +### Issues with CAP-13 - If base reserve increases, malicious actors could add large numbers of trustlines to an account. - Accounts can be DoS'd via the subentry limit. - The proposal has very large scope, affecting most operations and assumptions in the protocol. -#### Alternatives Discussed +### Alternatives Discussed - Use deterministic accounts and merge them if the receiver already has an account. - Introduce a **SentBalance** ledger entry claimable by the receiver. - Introduce a **remove trustline** operation that returns assets to the sender. -#### Fee Mechanisms +### Fee Mechanisms - David proposed CAP-19: - Enables future-upgradability of `TransactionEnvelope` - Allows a simpler implementation of CAP-15 -### Follow-up Actions +## Follow-up Actions - **David**: Write a short proposal on "embryonic accounts". - **Jeremy**: Clarify SEP-16 workflow with deterministic accounts. - **Jon**: Provide analysis of attack surfaces and issues in CAP-13. -### Resources +## Resources - [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) @@ -69,3 +67,4 @@ tags: - [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) - [SEP-16: Account Transfer Permissionless Payment Protocol (@p2p)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md) - [SEP-17: Issuer account funding protocol (CAP-13 Based)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/uxmo4LM5FWY/m/psazVteTBgAJ) diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index cf6e90710a..659a73f63d 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -10,31 +10,30 @@ tags: - CAP-19 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/KzgQc58510o/m/1qRSxo7GCAAJ) - -### Announcements +## Announcements - CAP-16 rejected in favor of CAP-18 (now Accepted). CAP-16 will only be revived if CAP-18 encounters implementation issues. - CAP-18 moved to Accepted. - CAP-19 moved to FCP: Acceptance. - Jed was in Singapore this week; trustline discussions were postponed until his return. -### Agenda +## Agenda -#### Fee Follow-ups +### Fee Follow-ups - Topics: CAP-19, CAP-15, and other fee-related suggestions. - Decision: Push CAP-19 to FCP: Acceptance and reframe CAP-15 in the context of CAP-19. -#### Future of the Order Book - Ideation +### Future of the Order Book - Ideation - Broad discussion of possible directions for the order book. - No commitments were made. - Goal: Produce an exhaustive list of ideas, followed by prioritization and requirements definition in future sessions. -### Resources +## Resources - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) - [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) - [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/KzgQc58510o/m/1qRSxo7GCAAJ) diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index dc58a24d09..dfb6b0d725 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -11,16 +11,14 @@ tags: - SEP-19 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/t162rVxLYB4/m/XB4_9st1BgAJ) - -### Announcements +## Announcements - CAP-19 is moving to Accepted. - "Implementation Review" stage added for CAPs (see https://github.com/stellar/stellar-protocol/pull/279); keep in mind for future CAP process. - Jed out this week; trustline discussion pushed again. - CAP-20 implementation is mostly there. -### Agenda +## Agenda - CAP-15: Modified to utilize CAP-19. Goal is to bring it to a vote, or enumerate what is needed to make it pass. - David: Two transaction IDs (inner and outer) as a result of the change. @@ -37,10 +35,11 @@ tags: - Possible use of an IPFS home domain - Orbit to send a document outlining design considerations for multisig transaction coordination. -### Resources +## Resources - [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) - [CAP-20: Bucket Initial Entries](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) - [SEP-19: Bootstrapping Multisig Transaction Submission](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/t162rVxLYB4/m/XB4_9st1BgAJ) diff --git a/meetings/2019-04-04.mdx b/meetings/2019-04-04.mdx index ce23d4b99d..e1063701f0 100644 --- a/meetings/2019-04-04.mdx +++ b/meetings/2019-04-04.mdx @@ -5,13 +5,11 @@ authors: goodnow tags: [legacy, CAP-15, SEP-16] --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/QSR2wf207ow/m/stluewnDCQAJ) - -### Announcements +## Announcements - Pushing fee work out to next week given David and Orbit's absence (Tomer is also out). -### Agenda +## Agenda - Discussing next steps for trustlines work. - David personally doesn't feel good about pushing forward Sponsored Trustlines, despite multiple people who think it's mostly there (Tom, Orbit). @@ -21,7 +19,7 @@ tags: [legacy, CAP-15, SEP-16] - The send workflow should credit the intended account ID even if no trustline exists, so clients don’t need to coordinate new trustlines for every payment. - The document’s overall goal is usability: keep issuer/wallet flows simple so developers actually ship the solution instead of avoiding a hard protocol change. -### Jon proposal +## Jon proposal - Trying to solve the add balance problem, and the merge problem related to trustlines. - We add a concept called a mergeable trustline. @@ -29,7 +27,7 @@ tags: [legacy, CAP-15, SEP-16] - "CAP-XXXX (Pending Trustlines)" that doesn't break merge. - Carries its own reserve, uses union-find to merge accounts. Would give O(log n) performance for merging accounts (not the most efficient version of union-find, but still performant). -### Summary of mergeable trustline details +## Summary of mergeable trustline details - Mergeable trustlines are associated with accounts via a variant of a union-find data structure (see https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-046j-design-and-analysis-of-algorithms-spring-2012/lecture-notes/MIT6_046JS12_lec16.pdf) that does not include the path-compression optimization. - Mergeable trustlines are immutable, except that the balance can be transferred in its entirety to the "real" trustline for the corresponding asset on the same account (noted in the meeting that this might be relaxable). @@ -40,23 +38,24 @@ tags: [legacy, CAP-15, SEP-16] - Open questions included what happens if the sender owns the trustline, or if the sender merges their account, creating issues around locking accounts and outstanding trustlines. - Revocability should not be done on-ledger; it should be handled via pre-authorized transactions or other multi-phase protocols. If it is on-ledger, it should be irrevocable. -### Nico's caveats +## Nico's caveats - Similar complexities arise as with SEP-16: clients must track incoming mergeable trustlines, decide whether they matter, query them from Horizon, and take actions. - This puts significant burden on clients to download and reason about many mergeable trustlines. - Union-find might help reduce what needs to be downloaded, potentially in tandem with SEP-16. - David, Nico, and Jon's proposals all rely on some form of "incoming trustline" at the core layer, which does not appear substantially simpler than ecosystem-level approaches. -### SEP-16 thoughts +## SEP-16 thoughts - Defining the last step is difficult given current protocol constraints and would require "shrink to fit" and other small core changes. - SEP-16 should likely remain a living document that evolves alongside core capabilities. -### Follow-up actions +## Follow-up actions - David to put together a list of constraints and concerns blocking CAP-15 from moving forward with Nico. -### Resources +## Resources - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [SEP-16: Account Transfer Permissionless Payment Protocol (atp3)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/QSR2wf207ow/m/stluewnDCQAJ) diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 1b41ede862..9404979dc2 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -5,13 +5,11 @@ authors: goodnow tags: [legacy, CAP-15, CAP-21] --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/I1GAjjcfDA0/m/CIzRMI-FBAAJ) - -### Announcements +## Announcements - CAP-21 and CAP-15 moved to FCP: Acceptance. -### Agenda +## Agenda - David's Pre-Condition proposal: CAP-21 - After several iterations with the Channels working group, CAP-21 was presented for decision. @@ -22,7 +20,8 @@ tags: [legacy, CAP-15, CAP-21] - If time permits, Jon to give an update from the trustlines/balances work. - Decision made not to discuss this fully until the draft is finalized, particularly around rationale and alternative ideas. -### Resources +## Resources - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/I1GAjjcfDA0/m/CIzRMI-FBAAJ) diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index 34b1c6198a..9ed9a1b8fb 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -10,21 +10,19 @@ tags: - CAP-23 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/va9Y7lkP4uI/m/K2W_AkvzCQAJ) - -### Announcements +## Announcements - CAP-15 and CAP-21 move to _Accepted_ today (after this meeting), barring no new concerns. - CAP-21 moves back to _Draft_ in order to resolve CAP-22 prior to acceptance. -### Agenda +## Agenda - CAP-23 - Focused on temporal separation between initiating a payment and receiving a payment. - Explicitly **does not** replace existing payment operations. - **David's initial framing:** ~10% additional complexity yields significantly more utility. -#### CAP-23 Design Discussion +### CAP-23 Design Discussion - **AuthorizeBalance** - Should include an optional `AccountID *revocableBy`. @@ -57,7 +55,7 @@ tags: - Some concern that less-knowledgeable users may struggle with the flow. - Others believe wallet UX and the existing payment operation mitigate this risk. -### CAP-21 / CAP-22 & Payment Channel Implementation +## CAP-21 / CAP-22 & Payment Channel Implementation - CAP-21 - Moved out of Final Comment Period back to Draft due to concerns raised by CAP-22. @@ -66,7 +64,7 @@ tags: - CAP-22 - Open question: adopt CAP-22 as written, or pursue a stronger invariant (only fully executing transactions succeed). -### Follow-Up Actions +## Follow-Up Actions - CAP-23 (Jon) - Add explicit behavior details regarding `ACCOUNT_MERGE`. @@ -74,9 +72,10 @@ tags: - Append `Op` to operation names in XDR. - Extend BalanceEntry claimer via a union to support future signer-based claims or wildcard claimBy. -### Resources +## Resources - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/va9Y7lkP4uI/m/K2W_AkvzCQAJ) diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index a1a747c16f..9a79e1c934 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -11,9 +11,7 @@ tags: - CAP-25 --- -## [Public Discussion](https://groups.google.com/g/stellar-dev/c/a9JH2c3jTEw/m/k5wg4XNnDAAJ) - -### Agenda +## Agenda - CAP-24 - Jon to follow up with Morley to get perspective on how this feels from a wallet implementation's perspective, particularly between the two operations. @@ -27,10 +25,11 @@ tags: - CAP-22 must address additional feedback from Nico. - David to own follow-up on CAP-21/0022 dependency resolution. -### Resources +## Resources - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) - [CAP-24: Make PathPayment Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - [CAP-25: Remove Bucket Shadowing](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) +- [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/a9JH2c3jTEw/m/k5wg4XNnDAAJ) From b885da37c19eb093e43f303ffb788e7fd6b75eca Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 15:09:49 -0400 Subject: [PATCH 15/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Refine=20historic?= =?UTF-8?q?al=20meeting=20references?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 3 +-- meetings/2019-06-13.mdx | 2 +- meetings/2019-11-04.mdx | 2 +- 3 files changed, 3 insertions(+), 4 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index ccca203c6c..e45c2784f1 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -20,7 +20,7 @@ tags: - CAP-5 & CAP-6 - moving to approval. - [Cosigned Assets Draft](https://github.com/stellar/stellar-protocol/issues/146) - in draft since September; current approach considered viable. -- CAP-7 revised proposal. +- [CAP-7 Revised Proposal](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md). - CAP-15 update. - CAP-13 vs SEP-13 (CAP-7 + CAP-8) - Change Trustlines to Balances. @@ -68,7 +68,6 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced - [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) - [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) -- [CAP-7: Deterministic Account Creation](https://github.com/stellar/stellar-protocol/blob/8f7ea7628cfb0c3e26723963b784752c9e0ea8e5/drafts/draft-detacct.md) - [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) diff --git a/meetings/2019-06-13.mdx b/meetings/2019-06-13.mdx index 9404979dc2..e5e94f4618 100644 --- a/meetings/2019-06-13.mdx +++ b/meetings/2019-06-13.mdx @@ -15,7 +15,7 @@ tags: [legacy, CAP-15, CAP-21] - After several iterations with the Channels working group, CAP-21 was presented for decision. - Following discussion on its importance for payment channels and its fit within the current framework, the group agreed to move CAP-21 to FCP: Acceptance. - Clarifying final aspects of fee bump (CAP-15), including questions raised in Nico's latest pull request: - - https://github.com/stellar/stellar-protocol/pull/323 + - [Add some clarifications to CAP-0015 regarding handling of duplicate bumpFee transactions PR](https://github.com/stellar/stellar-protocol/pull/323) - CAP-15 will move to FCP: Acceptance after a final round of wording changes. - If time permits, Jon to give an update from the trustlines/balances work. - Decision made not to discuss this fully until the draft is finalized, particularly around rationale and alternative ideas. diff --git a/meetings/2019-11-04.mdx b/meetings/2019-11-04.mdx index 93df2587df..4fe06092e5 100644 --- a/meetings/2019-11-04.mdx +++ b/meetings/2019-11-04.mdx @@ -9,7 +9,7 @@ import YouTube from "@site/src/components/YouTube"; -Denelle Dixon closed day one of Meridian with a forward-looking address on SDF’s evolving role and Stellar’s long-term direction. Speaking from the perspective of her first six months leading the foundation, she emphasized SDF’s identity as a nonprofit steward and ecosystem convener, translating open-network principles such as transparency, interoperability, and trust-by-design into practical support for builders, institutions, and regulators. +Denelle Dixon closed day one of the inaugural Meridian with a forward-looking address on SDF’s evolving role and Stellar’s long-term direction. Speaking from the perspective of her first six months leading the foundation, she emphasized SDF’s identity as a nonprofit steward and ecosystem convener, translating open-network principles such as transparency, interoperability, and trust-by-design into practical support for builders, institutions, and regulators. The talk focused on aligning governance, resources, and community momentum as Stellar moves from early growth into a more decentralized and durable network. Denelle outlined what has worked well so far, where SDF has fallen short, and how a restructured treasury and clearer priorities are meant to support sustainable adoption while reducing the foundation’s centrality over time. Jed McCaleb joined Denelle for the closing audience Q&A. From 1f5c9d4aa5033f9ee39aa8cd5b82421dc13c4cc7 Mon Sep 17 00:00:00 2001 From: John Wooten Date: Mon, 24 Aug 2026 15:11:59 -0400 Subject: [PATCH 16/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Format=20protocol?= =?UTF-8?q?=20identifiers=20in=20proposal=20titles?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 4 ++-- meetings/2019-03-07.mdx | 6 +++--- meetings/2019-03-14.mdx | 6 +++--- meetings/2019-03-21.mdx | 4 ++-- meetings/2019-03-28.mdx | 2 +- meetings/2019-06-27.mdx | 2 +- meetings/2019-07-25.mdx | 2 +- 7 files changed, 13 insertions(+), 13 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index e45c2784f1..ac72a347c8 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -67,12 +67,12 @@ The adjacent trustline-focused discussion reprised the agenda above and surfaced ## Resources - [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) -- [CAP-6: Add ManageBuyOffer Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) +- [CAP-6: Add `ManageBuyOffer` Operation](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0006.md) - [CAP-8: Self Identified Pre-Auth Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0008.md) - [CAP-10: Fee Bump Account](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0010.md) - [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - [CAP-15: Bump Fee Transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [SEP-6: Anchor/Client interoperability](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) - [SEP-8: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) -- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [SEP-13: `DEPOSIT_SERVER` proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/x0Wrj2kuQ0U/m/CrId5QkoFwAJ) diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 9fc65420bf..6222fdcc24 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -114,8 +114,8 @@ tags: - [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - [CAP-14: Adversarial Transaction Set Ordering](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0014.md) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) -- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) -- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) +- [CAP-16 — Cosigned assets: `NopOp` and `COAUTHORIZED_FLAG`](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) +- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If `LedgerEntry` is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) -- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [SEP-13: `DEPOSIT_SERVER` proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/NJl_loV_RXU/m/SarzWEJPAgAJ) diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index b36de75870..dfe3960ca0 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -60,11 +60,11 @@ tags: - [CAP-13: Change Trustlines to Balances](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0013.md) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) -- [CAP-17: Update LastModifiedLedgerSeq If and Only If LedgerEntry is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) +- [CAP-17: Update `LastModifiedLedgerSeq` If and Only If `LedgerEntry` is Modified](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0017.md) - [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) -- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [CAP-19: Future-upgradable `TransactionEnvelope` type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) - [SEP-6: Anchor/Client interoperability](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) -- [SEP-13: DEPOSIT_SERVER proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) +- [SEP-13: `DEPOSIT_SERVER` proposal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0013.md) - [SEP-16: Account Transfer Permissionless Payment Protocol (@p2p)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0016.md) - [SEP-17: Issuer account funding protocol (CAP-13 Based)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0017.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/uxmo4LM5FWY/m/psazVteTBgAJ) diff --git a/meetings/2019-03-21.mdx b/meetings/2019-03-21.mdx index 659a73f63d..7e07e8b32d 100644 --- a/meetings/2019-03-21.mdx +++ b/meetings/2019-03-21.mdx @@ -33,7 +33,7 @@ tags: ## Resources - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) -- [CAP-16 — Cosigned assets: NopOp and COAUTHORIZED_FLAG](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) +- [CAP-16 — Cosigned assets: `NopOp` and `COAUTHORIZED_FLAG`](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0016.md) - [CAP-18: Fine-Grained Control of Authorization](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0018.md) -- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [CAP-19: Future-upgradable `TransactionEnvelope` type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/KzgQc58510o/m/1qRSxo7GCAAJ) diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index dfb6b0d725..e0c3b4a463 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -39,7 +39,7 @@ tags: - [CAP-5: Throttling and transaction pricing improvements](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md) - [CAP-15: Bump Fee Extension](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) -- [CAP-19: Future-upgradable TransactionEnvelope type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) +- [CAP-19: Future-upgradable `TransactionEnvelope` type](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0019.md) - [CAP-20: Bucket Initial Entries](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0020.md) - [SEP-19: Bootstrapping Multisig Transaction Submission](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0019.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/t162rVxLYB4/m/XB4_9st1BgAJ) diff --git a/meetings/2019-06-27.mdx b/meetings/2019-06-27.mdx index 9ed9a1b8fb..9d2316b1b5 100644 --- a/meetings/2019-06-27.mdx +++ b/meetings/2019-06-27.mdx @@ -77,5 +77,5 @@ tags: - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) -- [CAP-23: Two-Part Payments with BalanceEntry](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) +- [CAP-23: Two-Part Payments with `BalanceEntry`](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/va9Y7lkP4uI/m/K2W_AkvzCQAJ) diff --git a/meetings/2019-07-25.mdx b/meetings/2019-07-25.mdx index 9a79e1c934..eb2549b7a5 100644 --- a/meetings/2019-07-25.mdx +++ b/meetings/2019-07-25.mdx @@ -30,6 +30,6 @@ tags: - [CAP-15: Fee Bump Transaction](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) - [CAP-21: Generalized transaction preconditions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0021.md) - [CAP-22: Invalid transactions must have no effects](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0022.md) -- [CAP-24: Make PathPayment Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) +- [CAP-24: Make `PathPayment` Symmetrical](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0024.md) - [CAP-25: Remove Bucket Shadowing](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0025.md) - [Original mailing-list discussion](https://groups.google.com/g/stellar-dev/c/a9JH2c3jTEw/m/k5wg4XNnDAAJ) From a92613fdebd812155b15a63509d9b02ec706b9fd Mon Sep 17 00:00:00 2001 From: John Wooten Date: Tue, 25 Aug 2026 06:33:26 -0400 Subject: [PATCH 17/17] =?UTF-8?q?=F0=9F=96=8A=EF=B8=8F=20Order=20meeting?= =?UTF-8?q?=20tags=20numerically?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meetings/2019-01-24.mdx | 8 ++++---- meetings/2019-03-07.mdx | 6 +++--- meetings/2019-03-14.mdx | 2 +- meetings/2019-03-28.mdx | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/meetings/2019-01-24.mdx b/meetings/2019-01-24.mdx index ac72a347c8..96c249f6ce 100644 --- a/meetings/2019-01-24.mdx +++ b/meetings/2019-01-24.mdx @@ -4,16 +4,16 @@ description: This protocol discussion covered CAP-5 and CAP-6, deterministic acc authors: goodnow tags: - legacy - - CAP-10 - - CAP-13 - - CAP-15 - CAP-5 - CAP-6 - CAP-7 - CAP-8 - - SEP-13 + - CAP-10 + - CAP-13 + - CAP-15 - SEP-6 - SEP-8 + - SEP-13 --- ## Agenda diff --git a/meetings/2019-03-07.mdx b/meetings/2019-03-07.mdx index 6222fdcc24..8b5914295a 100644 --- a/meetings/2019-03-07.mdx +++ b/meetings/2019-03-07.mdx @@ -4,6 +4,9 @@ description: This protocol discussion reviewed CAP-17 and CAP-18, prioritized tr authors: goodnow tags: - legacy + - CAP-7 + - CAP-8 + - CAP-9 - CAP-10 - CAP-11 - CAP-13 @@ -12,9 +15,6 @@ tags: - CAP-16 - CAP-17 - CAP-18 - - CAP-7 - - CAP-8 - - CAP-9 - SEP-13 --- diff --git a/meetings/2019-03-14.mdx b/meetings/2019-03-14.mdx index dfe3960ca0..1601555877 100644 --- a/meetings/2019-03-14.mdx +++ b/meetings/2019-03-14.mdx @@ -9,10 +9,10 @@ tags: - CAP-17 - CAP-18 - CAP-19 + - SEP-6 - SEP-13 - SEP-16 - SEP-17 - - SEP-6 --- ## Announcements diff --git a/meetings/2019-03-28.mdx b/meetings/2019-03-28.mdx index e0c3b4a463..14538314ed 100644 --- a/meetings/2019-03-28.mdx +++ b/meetings/2019-03-28.mdx @@ -4,10 +4,10 @@ description: This protocol discussion reviewed CAP-19 and CAP-20 implementation authors: goodnow tags: - legacy + - CAP-5 - CAP-15 - CAP-19 - CAP-20 - - CAP-5 - SEP-19 ---