Skip to content

Funding Proposal by Jubilee: Privacy-Native NFT Marketplace & CIP-56 Reference Implementation for Canton#267

Open
Jubilee-Market wants to merge 2 commits into
canton-foundation:mainfrom
Jubilee-Market:main
Open

Funding Proposal by Jubilee: Privacy-Native NFT Marketplace & CIP-56 Reference Implementation for Canton#267
Jubilee-Market wants to merge 2 commits into
canton-foundation:mainfrom
Jubilee-Market:main

Conversation

@Jubilee-Market
Copy link
Copy Markdown

Development Fund Proposal Submission

Proposal file:
/proposals/jubilee.md

Summary

Jubilee is a privacy-native NFT marketplace and an opinionated, NFT-focused CIP-56 reference implementation for the Canton Network, fully validated on Canton testnet and prepared for MainNet deployment. The proposal delivers four open-source public goods to the ecosystem: an NFT-focused CIP-56 DAML reference library (Apache 2.0), an atomic payment distribution pattern (platform fee + creator royalty + seller settlement in a single atomic operation), an on-ledger offer escrow primitive that eliminates the unbacked-offer spam pattern common in EVM marketplaces, and a browser-encrypted self-custody wallet reference implementation. Total scope spans 4 milestones over ~13 weeks, including two independent security audits before live economic activity begins.


Checklist

  • Proposal file added under /proposals/
  • Milestones and funding amounts defined (milestones defined; funding amounts intentionally deferred — see Notes for Reviewers)
  • Acceptance criteria included
  • Alignment with Canton priorities described

Notes for Reviewers

Status: Draft — seeking Tech & Ops Committee champion.

We are submitting as Draft per CIP-0100 to begin the champion-identification process as an external contributor team.

On milestone funding: Specific milestone funding amounts have been intentionally deferred to the champion discussion rather than proposed unilaterally. As an external contributor team, we believe allocations are best calibrated jointly — informed by Canton ecosystem norms, comparable proposals, and our champion's perspective on milestone scope. The "Funding" section of the proposal lists the principal cost drivers per milestone to support that conversation. We are open to refining both scope and amounts collaboratively.

Items the Committee may want to focus on:

  1. CIP-56 alignment. The proposal vendors the official Splice CIP-56 DARs and provides explicit Jubilee → CIP-56 type mappings (NFToken → Holding, JubileeTransferFactory → TransferFactory, JubileeTrade → AllocationRequest, JubileeAllocation → Allocation, JubileeAllocationFactory → AllocationFactory).
  2. Audit sequencing. Two independent security audits are scheduled at the start of MS2 — with capital provisioned from MS1 disbursement — and completed before live economic activity begins. The "Why Sequence Audits Between MS1 and MS2" section explains the rationale.
  3. Production maturity. The team has shipped not just contracts but production-side infrastructure (Cloudflare Pages, Resend Pro DKIM-verified, Cloudflare D1+KV waitlist at 10K+/min capacity). Detail in the "Production infrastructure & operations (live)" subsection of Delivered Work.
  4. Recipient entity. A legal entity will be incorporated prior to MS1 funding disbursement. Specific entity details and KYB materials will be provided to the Foundation through the formal acceptance process.
  5. Open-source license. All public goods will be released under Apache License 2.0, the de-facto standard adopted across Canton Foundation OSS repositories.

Live demonstration: Happy to walk Committee members or potential champions through the testnet implementation on request.

Signed-off-by: Jubilee Markets <kerem@jubilee.markets>
Signed-off-by: Jubilee Markets <kerem@jubilee.markets>
@hythloda hythloda moved this from Incoming to Needs Champion in Dev Fund Incoming May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Needs Champion

Development

Successfully merging this pull request may close these issues.

2 participants