Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Update top-level README: post meeting 75 #606

Merged
merged 5 commits into from
Oct 26, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions CIP-0102/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,9 @@ CIP: 102
Title: Royalty Datum Metadata
Authors:
- Sam Delaney <sdelaney@ikigaitech.org>
Implementors: []
Implementors:
- Grabbit <https://grabbit.market/>
- Nebula <https://github.com/spacebudz/nebula/>
Discussions:
- https://github.com/ikigai-github/CIPs/pull/1
- https://github.com/cardano-foundation/CIPs/pull/551
Expand Down Expand Up @@ -80,6 +82,7 @@ royalty_info = #6.121([royalty_recipients, version, extra])
```

#### Example of onchain variable fee calculation:

```cddl
; Given a royalty fee of 1.6% (0.016)

Expand Down Expand Up @@ -150,11 +153,11 @@ In addition to providing a way to create guaranteed royalties, this has several
- Minimal Storage Requirement - An optional boolean has about the smallest memory impact possible. This is especially important because it's attached to the - Reference NFT and will be set for each individual NFT.
- Intra-Collection Utility - This already allows for minting a collection with some NFTs with royalties and some without. A future version of this standard will likely make use of this field to allow for multiple versions of royalties for even more granular control.


### Backward Compatibility
To keep metadata compatibility with changes coming in the future, we introduce a `version` field in the datum.


To keep metadata compatibility with changes coming in the future, we introduce a `version` field in the datum.
## Extending & Modifying this CIP
See the [CIP-0068 Extension Boilerplate](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0068/extension_boilerplate.md)
## Path to Active

### Acceptance Criteria
Expand Down
2 changes: 1 addition & 1 deletion CPS-0007/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
CPS: 7
Title: Voltaire: Cardano Governance
Title: Voltaire era Governance
Status: Open
Category: Ledger
Authors:
Expand Down
7 changes: 3 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,7 @@ CIP Editors meetings are public, recorded, and [published on Youtube](https://ww
| 0094 | [SPO On-chain Polls](./CIP-0094) | Active |
| 0095 | [Web-Wallet Bridge - Governance](./CIP-0095) | Proposed |
| 0101 | [Integration of keccak256 into Plutus](./CIP-0101) | Proposed |
| 0102 | [Royalty Datum Metadata](./CIP-0102) | Proposed |
| 0381 | [Plutus Support for Pairings Over BLS12-381](./CIP-0381) | Proposed |
| 1694 | [A proposal for entering the Voltaire phase](./CIP-1694) | Proposed |
| 1852 | [HD (Hierarchy for Deterministic) Wallets for Cardano](./CIP-1852/) | Active |
Expand All @@ -99,7 +100,7 @@ CIP Editors meetings are public, recorded, and [published on Youtube](https://ww
| 1855 | [Forging policy keys for HD Wallets](./CIP-1855/) | Active |
| 9999 | [Cardano Problem Statements](./CIP-9999/) | Active |

<p align="right"><i>Last updated on 2023-09-19</i></p>
<p align="right"><i>Last updated on 2023-10-17</i></p>

> 💡 For more details about CIP statuses, refer to [CIP-0001](./CIP-0001).

Expand All @@ -126,14 +127,12 @@ Below are listed tentative CIPs still under discussion with the community. They
| 0092? | [First-class errors in Plutus](https://github.com/cardano-foundation/CIPs/pull/469) |
| 0096? | [On-chain dApp Certification Metadata](https://github.com/cardano-foundation/CIPs/pull/499) |
| 0097? | [Representing the Script Context as a SOP term](https://github.com/cardano-foundation/CIPs/pull/507) |
| 0098? | [Distributed Artifact Token Metadata](https://github.com/cardano-foundation/CIPs/pull/530) |
| 0099? | [Proof of Onboarding](https://github.com/cardano-foundation/CIPs/pull/546) |
| 0100? | [Governance Metadata](https://github.com/cardano-foundation/CIPs/pull/556) |
| 0102? | [Royalty Datum Metadata](https://github.com/cardano-foundation/CIPs/pull/551) |
| 0103? | [Web-Wallet Bridge - Bulk transaction signing](https://github.com/cardano-foundation/CIPs/pull/587) |
| 0104? | [Web-Wallet Bridge - Account public key](https://github.com/cardano-foundation/CIPs/pull/588) |

<p align="right"><i>Last updated on 2023-10-03</i></p>
<p align="right"><i>Last updated on 2023-10-18</i></p>

## Cardano Problem Statements (CPS)

Expand Down