Fund parameters
Fund13 Operating parameters are the actual operating parameters that make up the Catalyst voting protocol put in place to enable the community to decide which proposal will receive funding under the Project Catalyst program. Please note that given the dynamic nature of Project Catalyst, the following dates and parameters may change as the actual Fund progresses. If this is the case, community announcements will be distributed for clarifications.
# | PARAMETER | VALUE | DESCRIPTION |
| General Parameters | ||
A1 | Direct Voting privacy state | Yes | Are votes private? |
A2 | Fund name | Fund13 |
|
A3 | Funds under control | 50,000,000 ada |
|
A4 | Challenges title and budget | Cardano Open: Developers - ₳8,000,000 Cardano Open: Ecosystem - ₳5,000,000 Cardano Use Cases: Concept - ₳5,000,000 Cardano Use Cases: Product - ₳8,500,000 Cardano Partners: Enterprise R&D - ₳15,000,000 Cardano Partners: Growth & Acceleration - ₳5,000,000 |
|
A5 | Minimum budget request per proposal | Cardano Open: ₳15,000 Cardano Uses Cases: ₳15,000 Cardano Partners: ₳500,000 | Minimum amount for each proposal. |
A6 | Maximum budget request per proposal
| Cardano Open:
Cardano Uses Cases:
Cardano Partners:
Growth & Acceleration: ₳2,000,000 | Maximum amount for each proposal. |
A7 | Proposals submission fee | Free | Proposers can submit up to 6 proposals for discussion on Ideascale. Catalyst Team will remove ‘placeholder’ proposals at the point where the submission deadline elapses. Placeholder proposals include proposals where any of the form fields are left unanswered or obviously incomplete by the deadline. |
A8 | Compensations and funds distribution target date | Feb 10, 2025 | Target date, subject to change
When community compensations and F13 funding for initial milestone 1 tranche is paid following verification of test transaction. |
A9 | Maximum proposals per Proposer or co-proposer that can be put on the ballot | 6 | If more than 6 applications are submitted by the same entity either as lead or co proposer, only the first 6 submissions received will be accepted for the voting process. |
A10 | Community Reviewer registration | Through Ideascale | Anyone can register as a Community Reviewer.
Community Reviewers will be delineated between LV0, LV1, LV2 reviewers based on their contributions during the Community Review stage. |
A11 | Proposals registration on the blockchain | Nov 25, 2024 | Target date, subject to change
When proposals are loaded into the vote plan and registered into Block0. |
A12 | Voting power threshold | Minimum 25,000,000 lovelace (25 ada)
| 25 ada is the minimum stake threshold to become a voter, based on the efficiency benchmarks of the voting protocol. |
A13 | Registration snapshot date | Nov 20, 2024 09:45 PM UTC (epoch boundary 522 into 523) | Target date, subject to change
Snapshot takes place around the epoch boundary.
Advised to hold the balance for one epoch beyond the snapshot time and date. |
A14 | Voting period start time | Nov 28, 2024, 12:00 PM UTC | Target date, subject to change
UTC date and time when voters can start voting on proposals |
A15 | Voting period end time | Dec 12, 2024, 11:00AM UTC | Target date, subject to change |
A16 | Start of tallying | Dec 12, 2024 | Target date, subject to change |
A17 | End of tallying | Dec 15, 2024
| Target date, subject to change
UTC date when the decrypted tally is made publicly available. |
A18 | Tallying optimization | 1 ADA = 1 voting token (i.e. the stake amount in lovelace is divided by 1,000,000) | How voting power is being proportionally reduced in order to optimize tallying performance |
| Compensation Parameters | ||
B1 | Proposal Funding logic (winner selection rule) | Proposals are ranked by the Yes votes and funded one by one until the category budget is exhausted. Any leftover funds logic will follow guidelines outlined in the Fund Rules document. | `Proposals are ranked by Yes votes and funded in order. If the amount requested by a proposal is larger than the remaining challenge amount, it is skipped. |
B2 | Proposal acceptance threshold | 1% of total voting power
| At least 1% of the total registered stake must vote YES on a proposal.
E.g., there is 1 billion ADA as a total registered stake. To be accepted (become an ‘approved proposal’ as well as be eligible for funding), a proposal must be voted by at least 0.01 * (1 * 10^9) = 10 millions of ADA. |
B3 | Voting options | Yes/Abstain | There is only Yes and Abstain across all categories |
B4 | Voter compensations formula | Voter compensations will be given for active participants only in proportion to the voting power voters have. | |
B5 | 2.50% ₳1,250,000 | Voter Compensations
Compensation is for active participation in the Voting (cast at least 1 vote)
In order to benefit from voter rewards, voters must select either ‘Yes’ or ‘Abstain’ in the voter interface. By choosing to not select the ‘Abstain’ option, this will not cast an ‘Abstain’ vote and therefore not generate a unit of voter compensation. | |
B6 | 2.50% ₳1,250,000 | Community Review Compensations
LV0 (20% of share - ₳250,000):
LV1 (80% of share - ₳1,000,000):
| |
B7 | 0.40% ₳200,000 | Community Moderator Compensations
Share of compensations based on number of flags raised by scripts for LV2 moderator review | |
B8 | 1.60% ₳800,000
| Project Accountability Management Compensations
Compensating Community Reviewer help to verify :
Funded projects will submit to Catalyst a Statement of Milestones PoA and SoM are verified by at least 2 community reviewers and compensated ada for their work. | |
| Back-End Parameters | ||
C1 | Direct Voting privacy state | Yes | Are votes private? |
C2 | Funds under control | 50,000,000 ada | Fund will control 50M ada |
C3 | Voting power threshold | 25,000,000 lovelace. (25 ada) | 25 ada is the minimum stake threshold to become a voter, based on the efficiency benchmarks of the voting protocol. |
C4 | current_fund_name | Fund13 |
|
C5 | current_insight_sharing_start | Sep 26, 2024 | Target date, subject to change |
C6 | current_proposal_submission_start | Sep 26, 2024 | Target date, subject to change |
C7 | current_refine_proposals_start | Sep 26, 2024 | Target date, subject to change |
C8 | current_finalize_proposals_start | Oct 11, 2024 | Target date, subject to change |
C9 | current_proposal_assessment | Oct 24, 2024 | Target date, subject to change |
C10 | current_assessment_qa_start | Nov 14, 2024 | Target date, subject to change |
C11 | current_snapshot_start | Nov 20, 2024 | Target date, subject to change |
C12 | current_voting_start | Nov 28, 2024 | Target date, subject to change |
C13 | current_voting_end | Dec 12, 2024 | Target date, subject to change |
C14 | current_tallying_end | Dec 15, 2024 | Target date, subject to change |
Last updated