⚠ Preprod testnet
DRepTalk
Sign in
Enter as DRepEnter as delegatorEnter as SPOEnter as CC memberEnter as proposerRegister as DRep
Governance ActionsDiscussionsTreasuryDRepsAnalyticsReview
Sign in
More ways to sign in
Enter as delegatorEnter as SPOEnter as CC memberEnter as proposerRegister as DRep
Install app

[Preprod test] Marketing Events RFP 2027: 10M ada bid ranking

System20d ago1 post

On-chain changes

  • 10,000,000 ₳paid tostake_tes...qqtq78l7

Abstract

Preprod-network test only. No real funds, no real vendors, no real procurement. This treasury withdrawal requests 10,000,000 ada (10,000,000,000,000 lovelace) for the fictitious Marketing Events RFP 2027, paid to the reward account stake_test1upmxfsqf3epjrngsupvu6ea4swu2qd4wqsawm6pgcrupmqqtq78l7. Four bids were received off-chain against a published RFP. Each bid document is attached below as a hashed CIP-108 reference. The linked CIP-179 survey asks DReps, SPOs and CC members to rank the four bids and to say which bids they consider fundable at all. The top-ranked bid becomes the vendor eligible to be paid from the withdrawn funds. Survey and action both close at epoch 319. The purpose of this action is to test whether an off-chain RFP can be carried end to end through on-chain governance: bids in the anchor, ranking in the linked survey, funding in the withdrawal.

Motivation & rationale

Ecosystem procurement today happens off-chain. Bids are collected in a form, scored by a small group, and the result arrives on-chain as a finished decision that DReps can only accept or reject in full. DReps cannot see the losing bids, cannot express a preference between them, and cannot signal that none of the bids is good enough. The Yes or No vote is too coarse for a competitive tender.

CIP-179 gives us a second channel next to the vote. Bids can travel with the action as hashed references, and the ranking can be recorded on-chain by the same credentials that vote. This test checks whether the pieces hold together on Preprod before anything like it is proposed on mainnet.

The design under test has three parts.

  1. Bids in the anchor. Each of the four bids is attached as a CIP-108 reference with a blake2b-256 hash of the bid document. Anyone can fetch the document and verify it is the same one the author witnessed. The bids are frozen at submission and cannot be swapped afterwards.

  2. Ranking in the linked survey. The survey link below points at a CIP-179 survey published on Preprod. Question 1 is a ranking over the four bids in the same order as the references. Question 2 is a multi-select with a minimum of zero, so a respondent can answer none acceptable, which a ranking alone cannot express. The survey closes at epoch 319, the same epoch this action expires, as CIP-179 requires. Responding is open to every eligible role and does not require casting the vote on this action.

  3. Funding the winner. The withdrawal pays a single escrow reward account, stake_test1upmxfsqf3epjrngsupvu6ea4swu2qd4wqsawm6pgcrupmqqtq78l7. The winner is the bid ranked first by the tally rule stated in the RFP document, and the escrow may only disburse to that bidder. This split exists because a treasury withdrawal fixes its recipient at submission time and cannot pay whoever the poll later selects. Testing that escrow step is part of what this action is for.

Tally rule under test: Borda count over the ranking question, one response per credential, DRep responses only, latest valid response wins. If question 2 shows more than half of counted responses marking a bid unacceptable, that bid is skipped and the next ranked bid wins. If no bid clears that bar, the escrow returns the funds to the treasury.

Everything in this action is fictitious and exists on Preprod only.