What happened in CIPs last week?

[migamake]

Post-quantum CIP:

CIP-???? | Post Quantum signatures and native wallets

1. It has been split into Cardano Problem statement and Cardano Improvement Proposal.
2. It has been requested that we also deal with wallets beside Plutus APIs.

[RyanW]

What happened in CIPs last week?

• CPS-??? | Reading metadata in Plutus contracts [New Proposal]:
  • This CPS argues that the inability for Plutus scripts to read transaction metadata is an issue.
• CPS-??? | PostQuantum resistance and migration [New CPS]:
  • This CPS outlines the need for Quantum resistant cryptography in Cardano.
  • This was spawned from feedback on CIP-??? | PostQuantum signatures and native wallets.
  • This and accompanying CIP have had a lot of good engagment.

Continued Recommendations:

• CIP-1694? | A proposal for entering the Voltaire phase
  • This proposes a revision of Cardano’s on-chain governance system to support the new requirements for Voltaire.
  • This is a very important CIP has had tonnes of recent engagement from the community and it to see further refinement in the coming weeks.
• CIP-85? | Sums-of-products in Plutus Core:
  • This CIP proposes to add native support for datatypes to Plutus Core, and to use that support to implement more efficient interchange of the script context between the ledger and scripts.
  • Lots of new engagement and discussion.

Next Meeting:

• CIP Editors Meeting #62 (tomorrow!):
  • March 14th 9:30am UTC.
  • Postponed from 02.28
  • Held on Discord - here.
  • Agenda.

[RyanW]

What happened in CIPs last week?

• CIP-??? | Supercharged Native Scripts [New Proposal]:
  • This CIP proposes replacing the current native scripts used for minting Cardano Native Tokens with simple smart contracts.
• CPS-??? | Voltaire era Governance [New Problem]:
  • This CPS tried to frame a set of motivations, goals, constraints, and open questions for the very broad topic of Cardano governance.
  • This is to accompany CIP-1694 to allow for discussion of the problem of governance rather than the technical solution.

CIP Editors Meeting #62 – my notes:

• CIP-0084? | Ledger evolution (meta):
  • Looking good to merge – due to the nature of the proposal it does not need much engagement past the Ledger team.
  • With post meeting clarification on RSS CIPs application to the Ledger category, this is in Last Check for the next meeting.
• CIP-0030 | Upgrade to latest format & propose version / extension scheme:
  • With small amendments to remove positional arguments, this can be merged as it has a lot of positive discussion.
• CIP-0090? | Extendable dApp-Wallet Web Bridge:
  • Author (me) present to discuss.
  • Overall needs more discussion from wallet providers.
  • Number can be assigned.
• CIP-0091? | Don’t force Built-In functions:
  • Lots of good discussion with author engaging very well.
  • Assign a number and look to merge in the next meeting.
• CIP-0092? | First-class errors in Plutus:
  • Author present and provided great explanation.
  • Benchmarks/analysis on how much more efficient this is would be nice.
• CIP-0089? | Beacon Tokens & Distributed Dapps:
  • Seems to be some off-github discussions around this proposal - would be good to link them.
  • Can assign a number.
  • Somewhat informal, might benefit from a CPS.
• CIP-0088?: Native Asset Policy Registration/Information Certificates:
  • Can assign a number.
  • Author has had some good engagement.
  • More comments and discussion around related CIPs and CPSs should be added.
• CPS-??? | Reading metadata in Plutus contracts:
  • More detail is needed.
  • This is more of a feature request than a problem statement. Furthermore this is a feature which had purposely not included by the Plutus team.
  • So this is rejected for now.
• CIP-0030 | Add chain id to differentiate between testnets:
  • Has good support.
  • This should fit as an extension to CIP-30 as discussed in #466, although it is unclear if the author wants to pursue.
• CIP-0077? | Verified Stake Pool Identity:
  • Could benefit from more discussion by SPOs.
  • Good and timely proposal.

Next Meeting:

• CIP Editors Meeting #63:
  • March 28th 5pm UTC.
  • Held on Discord - here.
  • Agenda TBC.

[RyanW]

What happened in CIPs last week? (week starting 20thMarch)

• CIP-??? | Extend token metadata for translations [New Proposal]:
  • This proposal defines an addition to CIP-25 | Media NFT Metadata Standard to support more languages than English.
• CIP-0030 | Better describe API extension compatibility [New Discussions]:
  • This update to CIP-30 attempts to add additional clarity and guardrails to the API extension mechanism recently introduced in #446.

Continued Recommendations:

• CPS-??? | Voltaire era Governance:
  • This CPS tried to frame a set of motivations, goals, constraints, and open questions for the very broad topic of Cardano governance.
  • This is to accompany CIP-1694 to allow for discussion of the problem of governance rather than the technical solution.
• CIP-0045? | Decentralized WebRTC dApp-Wallet Communication:
  • This proposal describes a decentralized communication method between dApps and wallets based on WebTorrent trackers and WebRTC.
  • This has seen some decent engagement and is an interesting idea.

Next Meeting:

• CIP Editors Meeting #63:
  • Postponed to April 4th 5:30 GMT
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week? (week starting March 27th):

• CPS-??? | Governance Security [New Problem]:
  • This problem statement describes security issues to be considered by protocol governance CIPs.

Continued Recommendations:

• CIP-0057? | Plutus Smart-Contract Blueprints:
  • This proposal specifies a language for documenting Plutus contracts in a machine-readable manner.
• CIP-0038? | Arbitrary Script as Native Script spending conditions:
  • This CIP introduces a way to use native scripts as a starting point for more complex interactions which helps unlock use cases such as simple proxy contracts.
• CPS-02? | Pointer Address Removal:
  • This problem statement proposes the removal of pointer type addresses.

Next Meeting:

• CIP Editors Meeting #63 (tomorrow):
  • April 4th 5:30 GMT
  • Postponed from March 28th
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week? (week starting 3rd April) – lots!

• CIP-??? | Cardano FUDS (Financial Updates & Disclosure Specification) [New Proposal]:
  • This proposal outlines a framework for what projects building in Cardano should disclose about their financials.
• CIP-??? | SPO On-chain Polls [New Proposal]:
  • This proposal from the Cardano foundation suggests an mechanism for polling SPOs on-chain.
• CPS-??? | Plutus Script Usability [New Problem]:
  • This problem statement aims to pull together a number of Plutus usability issues which have motivated a few CIPS.
• CIP-??? | On-chain dApp Certification Metadata [New Proposal]:
  • This proposal offers a mechanism for linking certification metadata to on-chain entities.
• Draft CIP-??? | Automated Stake Pool Node Version Reporting [New Draft Problem]:
  • This draft proposal outlines a mechanism to automatically report the node version of stake pools in the Cardano network.
• CIP-0001 | Add extended taxonomy [Update]:
  • This update proposes additional taxonomy to CIPs, including a new grouping through “types”.
• CIP-0068 | Add SFT Semi-fungible token support [Update]:
  • This update proposes extending CIP-68 to include support for SFTs such as fractional NFTs.
• CIP-0060 | Update to v2 [Update]:
  • This update to CIP-60 provides a version 2 of the specification.

Next Meeting:

• CIP Editors Meeting #64:
  • April 18th 8:30am UTC.
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week? (week starting 10th April)

Continued Recommendations:

• CIP-0072? | DApp Registration & Discovery
  • This proposal outlines a mechanism for linking off-chain metadata to on-chain entities.
  • This has seen some recent updates and discussions!
• CIP-0092? | First class errors
  • This proposal suggests making error a first-class value within Plutus.
• CIP-0089? | Beacon Tokens & Distributed Dapps
  • This proposal introduces a standard to create distributed L1 Dapps where users maintain full delegation control of their assets and also maintain full custody of their assets at all times.
  • This is an interesting design.

Next Meeting:

• CIP Editors Meeting #64:
  • April 18th 8:30am UTC (tomorrow!).
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week? (week starting the 17th April)

• CIP-??? | On-chain Transaction Chaining [New Proposal]:
  • This proposal outlines alterations needed to ledger to allow on-chain transaction chaining.
• CIP-??? | Representing the Script Context as a SOP term [New Proposal]:
  • This proposal suggests using sums-of-products (SOPs) in Plutus Core (proposed in CIP-85?) to represent script contexts. This aims to speed up the processing time of script contexts.

CIP Editors Meeting #64 - my notes:

• CIP-??? | Supercharged Native Scripts:
  • Further discussion is needed, through Github.
  • Unsure if this is the optimal solution, there seems to be more desirable alternatives.
• CPS-??? | Voltaire era Governance:
  • Framed well, can assign a number.
  • Discussion around assigning the number of 1694 - CIP-21694 authors confirm this approach.
• CIP-??? | On-chain dApp Certification Metadata:
  • Good proposal and author present to discuss.
  • A few open questions from the proposal - these are on Github.
  • Discussion around an additional proposal for certification levels.
  • Can add a number.
• CIP-0072? | DApp Registration & Discovery:
  • Author present to engage with discussion.
  • Need a CDDL specification, need clarification on versioning, need more details to be added to implementation plan.
• CIP-0067 | add ADA Handles Virtual SubHandle:
  • Good engagement with questions on the proposal.
  • This would benefit from engagement.
• CIP-0060 | Update to v2:
  • Looks good.
  • Should ping author to respond to recent comments.
• CIP-0048? | NFT metadata references and payloads:
  • Needs CDDL schema.
  • Needs to abide by the latest CIP-01 structure.
  • Needs more engagement from the author to respond to comments.
• CIP-0030 | Better describe API extension compatibility:
  • Author present for discussion.
  • Potential alterations discussed.

Next Meeting:

• CIP Editors Meeting #65:
  • May 2nd 5:00pm UTC.
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week?

• CIP-??? | Cardano dApp-Wallet Web Bridge Governance Extension [New Proposal]:
  • This proposal extends CIP-30 | Cardano dApp-Wallet Web Bridge to provide support for CIP-1694 focussed web-based stacks.
  • I am the author
• CIP-??? | Proposal creation metadata [New Proposal]:
  • This proposal outlines a metadata standard for (governance) proposal mint transactions to include that can be read by off-chain applications in a consistent way.
  • This come from Agora.

Continued Recommendations:

• CIP-0045? | Decentralized WebRTC dApp-Wallet Communication:
  • This proposal describes a decentralized communication method between dApps and wallets based on WebTorrent trackers and WebRTC.
• CIP-??? | Authenticated Web3 HTTP requests
  • This proposal provides a standard approach for implementing wallet signature authentication in dApps via HTTP requests.
  • This has had some recent engagement

Next Meeting:

• CIP Editors Meeting #65:
  • May 2nd 4:00pm UTC (tomorrow!).
  • Held on Discord - here.
  • Agenda TBC

[RyanW]

What happened in CIPs last week?

• CIP-??? | Proposal creation metadata [New Proposal]:
  • This proposal presents a generic transaction metadata standard that can be used for generic governance proposals.

CIP Editors Meeting #65 (agenda w/ notes) – my notes:

• CIP-??? | Proposal creation metadata:
  • Needs a CDDL specification.
  • Needs a path-to-active.
  • There is a larger question: if this is meant to be a generic standard or application (agora) specific?
• CIP-??? | Cardano dApp-Wallet Web Bridge Governance Extension:
  • Author (me ) present to discuss.
  • Derivation path could be lifted and moved into CIP-1852.
  • The “role of the wallet” vs “role of dApp libraries” needs more clarification.
  • Can assign a number.
  • CIP-??? | Representing the Script Context as a SOP term:
  • Well written, this was split out of CIP-85.
• CIP-0048? | NFT metadata references and payloads:
  • Seems to be abandoned, and now CIP-88 could be used as a replacement to this.
  • Ready to close.
• CIP-0067 | add ADA Handles Virtual SubHandle:
  • Waiting on CIP-67 author to add their input.
  • Could have the author of this addition to propose a process for updating CIP-67 as such.
• CIP-0085 | Sums-of-products in Plutus Core:
  • Looks good can be merged (now merged).
  • Discussions have reached a conclusion.
  • Further discussion can happen on CIP-???? | Representing the Script Context as a SOP term by michaelpj · Pull Request #507 · cardano-foundation/CIPs · GitHub.
• CIP-0068 | Add SFT Semi-fungible token support:
  • Author of this addition present to discuss.
  • Generally well accepted update.
  • Rename to something like “Rich (metadata) Fungible Token” will make it clearer.
  • Relevant EIP.
• CIP-0086? | NFT Metadata Update Oracles:
  • Community concerns seem to be addressed by the author.
  • Generally good positive consensus.
  • Can move to merge (now merged).

Next Meeting:

• CIP Editors Meeting #66:
  • May 16th 9:30am UTC.
  • Held on Discord - here.
  • Agenda TBC.

[RyanW]

What happened in CIPs last week? (week starting 8th May)

• No new CIPs…

Continued Recommendations:

• CIP-0070? | Add rejected CIP for spending policies:
  • This proposal stands to explain why allowing native tokens on Cardano to have a
    spending policy in addition to their minting policy is an idea that should be rejected.
• CPS-01 | Metadata Discoverability and Trust:
  • This problem statement aims to illustrate the problem of the discovery and trust for off-chain metadata.
  • This is a common problem area for Blockchain systems.
• CIP-0045? | Decentralized WebRTC dApp-Wallet Communication:
  • This proposal describes a decentralized communication method between dApps and wallets based on WebTorrent trackers and WebRTC.
  • This has seen some decent engagement and is an interesting idea.

Next Meeting:

• CIP Editors Meeting #66:
  • May 16th 9:30am UTC (tomorrow!).
  • Held on Discord - here.
  • Agenda TBC.

[RyanW]

What happened in CIPs last week?

• No new CIPs…

Continued Recommendations:

• CIP-??? | Authenticated Web3 HTTP requests
  • This proposal outlines a structure for data payloads that are signed by wallets, which can be used by
    web applications to authenticate user requests.
  • This is a well written proposal.
• CIP-0095? | Cardano dApp-Wallet Web Bridge Governance Extension
• This proposal extends CIP-30 | Cardano dApp-Wallet Web Bridge to provide support for CIP-1694 focussed web-based stacks.
• (I am biased because I am the author )
• CIP-??? | On-chain dApp Certification Metadata
  • This proposal offers a mechanism for linking smart contract certification metadata to on-chain entities.
  • This is an interesting proposal.

Next Meeting:

• CIP Editors Meeting #67:
  • May 30th 4:30pm UTC.
  • Held on Discord - here.
  • Agenda TBC.