All 5 CAPs have been moved to Accepted state

48 views
Skip to first unread message

Naman Kumar

unread,
Mar 25, 2024, 5:16:16 PMMar 25
to Stellar Developers
Hello everyone, 

The following CAPs have been accepted on the merits of the idea, and because no new concerns were raised during the Final Comment Period. The CAPs are ready for implementation. 

It is still possible that a CAP may be rejected due to issues that arise during the initial implementation. Otherwise all of the CAPs will be moved to "Implemented" once they are included in the protocol. 
  1. CAP-51: add support for secp256r1 verification.
  2. CAP-53: create separate functions for extending the time-to-live for contract instance and contract code.
  3. CAP-54: lower total costs by refining the Soroban cost model used for VM instantiation into multiple separate and more-accurate costs.
  4. CAP-55: lower total costs by linking fewer host functions during VM instantiation in Soroban.
  5. CAP-56: lower total costs by caching parsed Wasm modules within a Soroban transaction.
Best,
Naman

Naman Kumar

unread,
May 9, 2024, 1:29:25 PMMay 9
to Stellar Developers
All five CAPs have been moved to the Implemented state and are expected to go live with Protocol 21. Once the CAPs are live on mainnet, they will be moved to the Final state.

CAP-51: add support for secp256r1 verification, enabling passkeys.

CAP-53: create separate functions for extending the time-to-live for contract instance and contract code.
CAP-54: lower total costs by refining the Soroban cost model used for VM instantiation into multiple separate and more-accurate costs.
CAP-55: lower total costs by linking fewer host functions during VM instantiation in Soroban.
CAP-56: lower total costs by caching parsed Wasm modules within a Soroban transaction.

Best,
Naman

Reply all
Reply to author
Forward
0 new messages