* cip-0108 add maxlength field to schema * enforce required properties of witness * ensure references are unique * add clarification on reference types * add description to reference label
* working commit - starting on V2 * add research report * add report in pdf form * [WIP] Rethink structure for clarity * [WIP] Intracollection Royalties Standard * update royalty token construction example * add clarity on versioning * CIP-88 extension * CIP-88 references * update implementation details * drop research report from standard * master cddl comment conformity * drop table of contents * changes per review * Drop output selection optionality
* Initial draft * Add note about banning non-builtin applications in function arguments * Clarify current higher-order builtins * Modify GenerateArray case to reflect possible future changes to arrays and Data encoding * Link to PR discussion * Assign number to CPS * Formatting
* Post-quantum signature CPS * Add another example * Proper link to discussion * Fix typo in date * Fix missing link * Rename CPS.md to README.md * Expand a bit more that this is a more specific part of a bigger problem, and why * Emphasize how difficult rolling your own would be * Backreference to earlier work, describe some candidates * Assign CPS a number * Fix title, fix broken link
Signed-off-by: Chris Gianelloni <[email protected]>
* TFHE CPS * More use cases * Add link to discussion * Rename CPS.md to README.md * Break up the open problem section a bit * Modify approaches now that we know Rust binding is feasible * Fix typo Co-authored-by: Yura <[email protected]> * Assign CPS a number, correct broken link * Formatting * Fix title * Update CPS-0026/README.md Co-authored-by: Robert Phair <[email protected]> --------- Co-authored-by: Yura <[email protected]> Co-authored-by: Robert Phair <[email protected]>
Reduce dependencies on MemoryStore
* CIP-0068 | Support multi-asset metadata a la CIP-0025 (#1112) Add version 4 metadata support with 721-ERC-style mappings to NFT (222), FT (333) and RFT (444) standards, ensuring consistency across all asset classes. Changes: - Add metadata_field union type supporting both direct and 721-map formats - Add __RESERVE_KEYWORD_721_V4__ marker for 721-style detection - Update retrieval steps to handle both metadata formats - Support version 4 in FT standard - Support version 3/4 in RFT standard - Add 721-style JSON example for NFT standard - Update pattern descriptions with asset_name terminology - Fix URI support to include [* bounded_bytes] for RFT * CIP-0068 | Address review feedback on v4 metadata format Fix terminology and CDDL syntax issues identified in review: - Remove "721-ERC-style" terminology; clarify reference to CIP-0025's nested map structure vs individual metadata fields - Fix CDDL syntax: use proper bounded_bytes for "721", policy_id, and asset_name keys (matching CIP-0025 version 2 conventions) - Remove __RESERVE_KEYWORD_721_V4__ marker; presence of "721" key is sufficient for format detection - Update retrieval steps to detect format by checking for "721" key - Clarify "backwards-compatible" in changelog: version 4 adds nested map format as additional option, compatible with v1-3 direct format - Rename "721-style" example label to "nested map format" - Propagate all fixes consistently across 222, 333, and 444 standards * CIP-0068 | Add rationale for version 4 nested map format Add comprehensive rationale explaining the motivation for introducing the CIP-0025-compatible nested map format in version 4: - Addresses minUTxO cost barriers for large NFT collections - Enables metadata consolidation to reduce ADA locking (10-20% savings) - Improves migration path from CIP-0025 to CIP-0068 - Preserves backward compatibility through strict optionality This rationale explains the economic and practical benefits that led to the version 4 design decision.
Start to re-organize test hierarchy: ImpSpec
fix(gateway): upgrade protobufjs past audit advisories