DraculaDAO
Badges (10)
We believe in taking an ultra long-term approach to important decisions. We will not vote for what we believe are short sighted decisions and will generally not support proposals for treasury funds being used for venture capital or short-term marketing efforts, unless there is a compelling benefit to the ecosystem and there is low risk. Burning ADA tokens is a non-starter.
Qualifications
General experience in crypto since 2012 and specifically Cardano since 2018. Experience working with Bitcoin, Ethereum, most of the EVM L2's, Near, Solana and of course Cardano.
Payment address: addr1q8h8...5srh77p0
On-chain data as of 4d ago.
Forum activity (0)
No forum posts yet.
Voting stats
- Yes74 (65%)
- No38 (33%)
- Abstain2 (2%)
Voting history (114)
YesBlockfrost's transformation to not-for-profitRationaleActive10d ago
Vote: YES
This proposal (governance action 5439b6141625436ccf600f910bb0b3301b6288933a2cdf7939758848ae8b9997#0) requests a one-time treasury grant of ₳9,832,979 (~$1.57M USD at the ~$0.16/ADA reference rate) to transition Blockfrost — today a private company's product — into a free, community-governed public good under an independent not-for-profit. The plan commits to a free, open public API across mainnet, preview, and preprod with no paid tier, a minimum 99% monthly uptime, a legal transfer of source code, trademarks, and domains into community stewardship, and an on-chain-elected community board, phased across Q3 2026 (architecture and public dashboard), Q4 2026 (board elected), and Q1 2027 (traffic migrated, IP legally transferred). Any unspent funds are returned to the Cardano Treasury.
Dracula DAO votes YES. Blockfrost is not optional tooling — it is load-bearing infrastructure that a large share of Cardano wallets, dApps, and builders query every day. Its current status as a single private company's product is itself a systemic risk: the ecosystem's most widely used API is a single point of failure controlled by one commercial entity, and that entity has already returned to the treasury and to Catalyst for funding more than once. Converting that dependency into a neutral, openly governed public good — with the source, trademarks, and domains irreversibly transferred into community stewardship and a community-elected board directing it — durably removes that single point of failure. This is foundational, long-term infrastructure of exactly the kind the DREP exists to support, and a free, no-paid-tier API directly lowers the cost of building on Cardano for every team that follows.
The value accrues to ADA holders, not to a private balance sheet. Rather than the ecosystem paying rent in perpetuity to a company it does not control, this transition puts a critical piece of Cardano's infrastructure into the hands of the people who depend on it and gives them governance over how it is run and funded. The commitment to a public usage dashboard, quarterly technical and budget reporting, a minimum 99% uptime SLA, and the return of unspent funds to the treasury reflects a level of transparency and accountability that a lump-sum request would not carry. The ₳9.8M is a one-time cost to acquire and open-source an asset the ecosystem will own outright — a fundamentally different proposition from an operating subsidy for a private venture.
Dracula DAO registers its standard concerns and does not let them override the vote. The funding is structured as a one-time transition grant to the incumbent team without competitive bidding, and while deliverables are staged by quarter, staged reporting is weaker than per-milestone smart-contract release with independent sign-off of the kind that secured the IO Hydra withdrawal; we would have preferred escrowed, completion-gated disbursement. The free-forever, no-revenue model also leaves the long-term operating cost of the service unresolved, and the withdrawal is made at a depressed ADA price. These are real, and Dracula DAO expects the incoming community board to treat a sustainable funding path — an endowment, usage-based revenue, or a defined route off treasury dependence — as a first-order priority, and to make good on the transparency commitments in this proposal. On balance, the strategic value of moving Cardano's most critical API into permanent community ownership outweighs these structural gaps, and Dracula DAO votes YES.
References:
- Momentum proposal page: https://momentum.cardano.iog.io/proposals/blockfrost
- Governance action: 5439b6141625436ccf600f910bb0b3301b6288933a2cdf7939758848ae8b9997#0
NoEternl: Path to Sustainability - v2Epoch 645RationaleEnacted15d ago
Vote: NO
This is Eternl: Path to Sustainability - v2 (gov_action1lwudrf9g66mzlrxhq62y5pvzhzzv9wgps7u04kne202udge7kknsqlgmhse), a Treasury Withdrawal submitted June 16, 2026 with voting closing July 18, 2026. It requests 10,000,000 ADA over a 12-month horizon to sustain Eternl, a widely used non-custodial Cardano wallet, disbursed as 5,000,000 ADA on approval and a further 2,000,000 ADA and 3,000,000 ADA gated on observable evidence at milestones M1 and M2. It is administered by Intersect via the standardized Treasury Reserve / Project-Specific Smart Contract framework built by Sundae Labs, with a five-entity independent Oversight Committee verifying administrative actions. This v2 revises the expired 2026-2027 version by adding the clarification on audit-fund spending and oversight metrics that Constitutional Committee members requested in their vote rationales. No ADA burning is involved.
Eternl remains foundational user-facing infrastructure with a demonstrated delivery record under prior treasury disbursements, and this proposal answers the specific accountability gap that sank the prior version: the audit-spending and oversight-metric clarifications the CC asked for are now present, the disbursement runs through a standardized smart contract with milestone gating, and an independent five-member Oversight Committee sits over administration. On project merit, and on governance structure, this is a materially better-formed proposal than most treasury requests, and Dracula DAO recognizes the responsiveness.
Dracula DAO votes NO on grounds of treasury timing, consistent with our vote on the prior version dated June 14, 2026. That vote was explicit that our objection was timing, not merit, and that we would support a substantively similar proposal once market conditions improved. One month later the condition that drove that NO has not changed: ADA trades near multi-year lows, and approving a 10,000,000 ADA withdrawal at a cyclical price trough destroys treasury purchasing power — the same twelve months of Eternl operations funded after a price recovery would cost the treasury materially fewer tokens in real terms. Preserving the treasury's token base through a bear market is itself the ultra-long-term action; the treasury exists to be deployed across decades, not drawn down at its weakest point. The audit clarification, welcome as it is, does not touch this objection.
A secondary concern reinforces the NO. Half the request — 5,000,000 ADA — is front-loaded on approval, before any milestone delivery. Milestone-gating with independent sign-off on the remaining 5,000,000 ADA is a real improvement over a lump sum, but a 50% up-front tranche is far from Dracula DAO's standard that treasury funds follow delivered, verifiable work rather than pre-fund a single team's operating runway; there is no competitive bidding, and the up-front tranche is not delivery-gated. We would prefer a structure weighted toward completion-gated payments with a smaller or eliminated front-load. Dracula DAO reaffirms its standing commitment: we expect to vote YES on a substantively similar Eternl proposal once ADA prices recover, and we encourage resubmission at that point, ideally with more of the total gated on observable delivery. This is a position on treasury timing discipline, not on Eternl's work.
YesReimburse Ikigai Info Governance Action Deposit.Epoch 643RationaleExpired15d ago
Vote: YES
This is a Treasury Withdrawal (gov_action1654yj97lf7guxsh27phtknq2tsc4dajp95fh7vrucaltjy0502csq7qtkhq), submitted June 9, 2026 with voting closing July 13, 2026, requesting 100,000 ADA to reimburse Ikigai Technologies for a governance-action deposit it can no longer recover. The deposit was trapped by a Cardano node bug that permitted an unregistered stake key to be used in a governance action, so the standard deposit-refund mechanism — which normally returns the 100,000 ADA on ratification or expiry — could not return the funds. The requested amount matches the standard deposit exactly, and the community has signalled since the Plomin hard fork that reimbursing this specific stranded deposit via a treasury withdrawal is the appropriate remedy.
Dracula DAO votes YES. This is not discretionary spending; it is remediation of a protocol failure. Cardano's governance deposit is designed to be fully refundable — that guarantee is what makes it a legitimate anti-spam bond rather than a fee. Ikigai, a long-standing Cardano builder, submitted a governance action in good faith, posted the required bond, and lost access to it solely because of a node-level defect, not through any error or bad faith of its own. When the protocol itself breaks a refund guarantee it made, making the affected party whole preserves the integrity of the deposit mechanism and the credibility of participating in governance at all. The amount is fixed and small — 100,000 ADA, roughly $26,000 at prevailing prices — the recipient and cause are clearly identified, and there is no ADA burning and no open-ended commitment.
The honest concerns are precedent and scope. A treasury reimbursement of a governance deposit must be understood as bounded strictly to funds stranded by a documented protocol bug — not as a general policy of socializing normally-refundable deposits, which would gut the deposit's anti-spam function by removing the submitter's skin in the game. This action reads as the narrow, one-time correction, but the DREP will oppose any future attempt to generalize it into routine deposit reimbursement absent a genuine protocol failure. It is also worth stating plainly that the cleaner long-term fix is at the ledger level, so that stranded deposits are recoverable directly rather than requiring a treasury draw; a treasury withdrawal is the practical remedy available today, not the ideal one.
Dracula DAO's treasury philosophy centers on funding delivered work, not operating budgets, and this action sits outside that frame entirely — it is neither a grant nor a budget but a correction of a bond wrongly withheld by the system. Judged on fairness, low risk, and the health of the governance process, it clears the bar. Dracula DAO supports reimbursing Ikigai's trapped 100,000 ADA deposit and votes YES.
YesReforming Treasury GovernanceEpoch 643RationaleClosed15d ago
Vote: YES
This is a non-binding Info Action titled "Reforming Treasury Governance" (gov_action1t5ap7etluvct2x69nj5mfqhurgakuvekyflcsrv2qkrhrs378n3qq3z2c22), submitted on June 9, 2026 with voting closing July 13, 2026. It requests no funds and changes no protocol parameter. It diagnoses treasury governance as being in a poor state — a persistent funding impasse, and a treasury process that is pivotal to Cardano's stability and growth yet only indirectly addressed and barely supported by the existing governance system — and it calls on the community to collaborate on reforming that process, outlining guardrails for strategic direction that would require further refinement and eventual amendments to the current process and the Constitution.
Dracula DAO votes YES. The diagnosis is correct and overdue. The 2026 cycle made the dysfunction concrete: 69 proposals requesting roughly 331.6M ADA against a Net Change Limit debated between 350M and 500M, an IOG research roadmap that drew opposition from a large majority of DReps, and a Cardano Summit that won a majority but died for lack of a stake-weighted supermajority. That is not a healthy allocation process; it is a series of unstructured, high-stakes standoffs. Treasury governance today decides who gets paid before it has decided what should be built, and it does so with almost no machinery for reconciling competing claims. An Info Action that names this problem and opens a structured reform track carries essentially zero risk — no ADA leaves the treasury, no parameter moves, no ADA is burned — and real option value in shaping what comes next. Supporting the direction costs nothing and forfeits nothing.
The honest limitation is that this is a signal, not a solution. An Info Action "sketches basic ideas"; it commits no one to anything, and its guardrails are stated at a level of generality that could later be filled in well or badly. A YES here is a vote for the conversation, not a blank endorsement of whatever emerges from it. Dracula DAO will judge every concrete instrument that follows — constitutional amendments, revised budget frameworks, new NCL structures — on its specific merits, and will oppose any "reform" that concentrates discretionary spending authority, weakens on-chain DRep ratification, or substitutes a standing executive's judgment for verifiable delivery.
Dracula DAO enters this reform process with a specific position already on record. Treasury funds should be allocated as grants paid on completion of well-defined features — not as pre-funded team operating budgets. The DREP's proper role is to vote on what to build, while who gets paid and how much is pushed to competitive, sprint-based bidding: work broken into short stories that teams bid on, funded per sprint through a smart contract that pays out only on signed-off delivery and returns undelivered funds to the treasury. That model directly answers the two failures this action identifies — it breaks the funding impasse by separating feature prioritization from team financing, and it gives treasury governance the direct, accountable support the current system lacks. Milestone-gating with independent sign-off is a partial approximation of this, better than a lump sum but short of true competitive per-sprint bidding. We vote YES to reform treasury governance, and we will press for reform of this shape.
Show 109 moreShow less
YesReduce the committeeMinSize parameter from 7 to 5Epoch 643RationaleEnacted26d ago
Vote: YES
This governance action is a protocol-parameter change that reduces committeeMinSize from 7 to 5. Submitted by Intersect on June 5, 2026 on behalf of the Civics Committee and the Technical Steering Committee, with the recommendation of the Parameter Committee, it lowers the minimum number of active Constitutional Committee members required for the committee to ratify governance actions. It does not shrink the Constitutional Committee itself and does not change the committee's vote threshold: the intent is to continue seating a full seven-member committee through regular elections while creating an operational buffer against vacancies. No ADA is requested and no treasury funds are involved.
Vampyre Fund votes YES.
This is foundational governance infrastructure, and the risk it addresses is not hypothetical. When the Cardano Atlantic Council retired effective November 25, 2025, the Constitutional Committee fell below its required membership and Cardano experienced its first governance shutdown: CC-dependent actions — including treasury withdrawals and protocol-parameter changes that require concurrent majorities from DReps and the committee — could not be ratified until the committee was replenished, even where DReps approved them. A governance system that can be paralyzed by a single resignation, term expiration, or vacancy is structurally fragile. Reducing the functional quorum to five while continuing to target a full seven seats is a conservative, sensible hardening of the mechanism. Vampyre Fund takes an ultra long-term view of Cardano's institutions, and resilience of the ratification process is exactly the kind of durable, non-tactical improvement that view favors.
The honest trade-off is that a lower floor allows governance to proceed on a smaller active base, which modestly reduces the redundancy of the constitutional safeguard: five members rather than seven would suffice to keep CC-dependent actions moving. This deserves acknowledgment rather than dismissal. It is materially mitigated by three facts — the committee's vote threshold is unchanged, the standing intention remains a fully seated seven-member committee, and the alternative on display in late 2025 was not a stronger safeguard but a complete stall. A committee that cannot act is not a safer committee; it is an absent one. Five active members remains a substantial and credible quorum.
Vampyre Fund supports this change as a matter of operational resilience, not as a step toward a smaller committee. We would oppose any subsequent action that used this lower floor as cover to leave seats unfilled or to erode the committee's vote threshold, and we will continue to weight the full and prompt seating of the Constitutional Committee as a governance priority.
YesHard Fork to Protocol Version 11 ('van Rossem' Hard Fork)Epoch 644RationaleEnacted1mo ago
Vote: YES
This governance action initiates a hard fork to Protocol Version 11, named the 'van Rossem' hard fork in honour of Max van Rossem, a Cardano community member, developer, SPO, DRep, and Constitutional Convention delegate who passed away in 2025. The upgrade is an intra-era hard fork — no new ledger era, no treasury withdrawal, no ADA requested. It delivers five new Plutus CIPs: CIP-138 (Array type), CIP-153 (MaryEraValue type), CIP-109 (modular exponentiation), CIP-132 (dropList), and CIP-133 (multi-scalar multiplication over BLS12-381). The action was submitted by the Intersect Hard Fork Working Group in June 2026 and requires ratification by DReps, the Constitutional Committee, and SPOs, with an activation threshold requiring 85% of active block-producing stake to run compatible nodes before the fork executes.
Vampyre Fund votes YES.
This is foundational protocol infrastructure in its purest form. The five new Plutus primitives materially expand what builders can accomplish on-chain: modular exponentiation and BLS12-381 multi-scalar multiplication are prerequisites for practical zero-knowledge proof systems; the Array and dropList builtins improve execution efficiency and reduce script costs; MaryEraValue optimises multi-asset handling. These are not features that generate marketing impressions over a single event cycle — they are the substrate on which the next generation of Cardano applications will be built. Vampyre Fund exists to support exactly this kind of work.
The governance structure of this hard fork merits specific recognition. This is the first hard fork in Cardano's history to be initiated through the Voltaire on-chain governance framework rather than by IOG acting unilaterally. The 85% SPO node-readiness threshold before activation is a meaningful safety mechanism — it prevents chain fragmentation and ensures the upgrade executes only when the network is genuinely prepared. Preview testnet forked successfully on May 8, 2026. DRep ratification reached 68.57% of active stake. The Constitutional Committee provided 5-of-7 sign-off. These are the governance processes Cardano has been building toward, and they are working as designed.
Vampyre Fund casts this YES vote also as an SPO. The VAMP stake pool has upgraded to the required node version and voted YES in the SPO track. We encourage all remaining SPOs who have not yet upgraded to do so. The 85% threshold exists to protect the network; crossing it promptly benefits every participant in the ecosystem.
NoRare Evo and Dev Gov Day 2026: Cardano Title SponsorshipEpoch 640RationaleExpired1mo ago
Vote: NO
This proposal requests treasury funds for Cardano to serve as title sponsor of Rare Evo 2026, a blockchain and AI conference held in Las Vegas, alongside a co-located Dev Gov Day event. The proposal is a direct marketing and event spend with no infrastructure deliverable, no treasury repayment, and no on-chain accountability mechanism tied to outcomes.
Vampyre Fund votes NO.
The Vampyre Fund DREP does not support treasury funds being used for short-term marketing efforts. A conference title sponsorship is precisely that — a brand spend whose value is measured in impressions and attendee counts over a single event cycle. It does not build infrastructure, does not return value to the treasury, and does not compound over time. The 6.89% DRep support this proposal has received as of June 2026 reflects broad community alignment with this assessment.
The inclusion of a Dev Gov Day component does not change this judgment. Governance education and developer outreach are worthwhile goals, but they do not require treasury-funded conference sponsorship to achieve. Community-led governance events have historically operated without top-tier sponsorship budgets. Bundling a developer day with a Las Vegas conference sponsorship does not transform the proposal into infrastructure spending.
Vampyre Fund's position is consistent: treasury funds should be reserved for long-term foundational work. Event sponsorships, regardless of the event's quality or the sincerity of the organizers, are not the appropriate use of ADA held in trust for the long-term benefit of the Cardano ecosystem.
YesTweag Core Cardano Infrastructure: Treasury Withdrawal 2026–2027Epoch 641RationaleEnacted1mo ago
Vote: YES
This proposal requests ₳18,263,496 (~$4.57M USD) for Tweag by Modus Create to deliver three infrastructure work packages in 2026–2027: Peras v1 mainnet deployment (reducing finality from ~12 minutes to ~2 minutes), History Expiry (enabling partial-history nodes for sustainable SPO economics as throughput scales), and Conformance Testing for Peras and Leios protocols. Intersect administers the proposal; disbursement is managed via Treasury Reserve Smart Contracts with multi-signature authorization, overseen by a five-member committee including Sundae Labs, Cardano Foundation, Dquadrant, Xerberus, and NMKR.
Vampyre Fund votes YES.
This proposal sits at the core of what Vampyre Fund exists to support: foundational long-term protocol infrastructure. Peras faster finality is a prerequisite for Cardano to compete as a serious DeFi and settlement layer. History Expiry addresses a structural economic problem for stake pool operators that will worsen as throughput increases under Leios. These are not features that produce marketing impressions or short-term token price movement — they are the infrastructure on which the next decade of Cardano activity depends.
The accountability structure is meaningfully stronger than most treasury proposals Vampyre Fund has reviewed. Treasury Reserve Smart Contracts with multi-signature authorization provide on-chain disbursement controls. Intersect's role as administrator adds a credible third-party layer. The five-member oversight committee represents genuine diversity of ecosystem stakeholders. Tweag by Modus Create brings deep Haskell and Cardano protocol credentials.
We note two concerns without letting them override the vote. First, there is no competitive bidding for this work — Tweag is pre-selected. Vampyre Fund continues to believe the long-term health of the ecosystem requires open, competitive team selection for funded work. We would prefer a future model where Intersect issues open RFPs and the community selects among competing proposals. Second, ₳18.26M is a material withdrawal at a time when ADA price is depressed; the real-cost burden on the treasury is elevated relative to what this work would cost if funded at a higher ADA price. Both concerns are structural and apply across the 2026 budget process broadly. They are not unique to Tweag, and they do not outweigh the merits of funding infrastructure that Cardano genuinely needs.
NoCardano Critical Integrations V2Epoch 639RationaleEnacted1mo ago
Vote: NO
Critical Integrations V2 requests approximately 23 million ADA to fund Year 2 of an integrations program that delivered a published V1 closure report. Native L1 Fireblocks integration and ongoing maintenance of prior integrations are credible institutional-grade infrastructure work. On project merit, the program is the kind of long-horizon infrastructure investment Vampyre Fund generally supports.
Vampyre Fund votes NO on grounds of treasury timing.
23 million ADA is a significant withdrawal in absolute terms, and at present ADA prices it represents real terms value destruction relative to executing the same scope after market recovery. Approving multi-million-ADA treasury draws during cyclical price lows monetizes the treasury at its weakest point and undermines the long-term capital base the ecosystem will need for far larger commitments in subsequent cycles.
Separately, we continue to hold that treasury funds should not function as multi-year team operating budgets. Year 2 renewals of this size, even with a delivered V1, reinforce a continuous-disbursement model rather than a competitive, milestone-bid model in which work units are funded as completed. We would prefer to see V2 broken into smaller tranches with independent renewal votes tied to specific delivered integrations.
We encourage resubmission, either at a smaller scope or after market conditions improve, and we will reassess on its own merits at that time.
No5am.earth Trust Layer Targeting Vision 2030 KPIsEpoch 640RationaleEnacted1mo ago
Vote: NO
5am.earth proposes a 10 million ADA treasury withdrawal to build a Cardano-anchored trust layer for agricultural supply chains across India, Cambodia, and Kenya. The proposal is administered through Intersect's standardized Treasury Reserve Smart Contract framework developed by Sundae Labs, with disbursement gated by an independent five-entity Oversight Committee. The administrative structure is among the strongest we have seen — it is precisely the milestone-gated, externally-overseen model Vampyre Fund has called for, and we want to commend the proposing team for it. The underlying work — establishing verifiable real-world data anchored on Cardano — is also aligned with the long-term utility vision we support.
Vampyre Fund votes NO on grounds of treasury timing.
At current ADA prices, a 10 million ADA withdrawal represents an avoidable cost in real terms. Treasury preservation during depressed market conditions is itself a long-term position: the treasury's purchasing power compounds when we resist drawing it down at cyclical lows. We would rather fund well-structured proposals after price recovery than approve a wave of multi-million-ADA disbursements at present valuations.
This vote is not a judgment on 5am.earth, its team, or its administrative framework, all of which we view favorably. We encourage resubmission once market conditions support deployment, and Vampyre Fund expects to support a substantively similar proposal at that time.
NoEternl: Path to Sustainability (2026-2027)Epoch 638RationaleExpired1mo ago
Vote: NO
Eternl is foundational user-facing infrastructure. A reliable non-custodial wallet covering payments, staking, governance, and DApp interaction is exactly the kind of work the ecosystem depends on, and the team has a delivery record under prior treasury disbursements. On project merit, this proposal is the type of work Vampyre Fund supports.
Vampyre Fund votes NO on grounds of timing, not merit.
ADA's market price is presently depressed. Funding any multi-million-ADA treasury withdrawal under these conditions destroys treasury purchasing power: the same deliverable funded after price recovery costs the treasury materially fewer tokens in real terms. Treasury preservation under bear-market conditions is itself a long-term action — the treasury exists to be deployed across decades, not to be drawn down at cyclical lows.
We encourage Eternl to resubmit, or to extend operations through alternative bridging arrangements, with the expectation that Vampyre Fund will vote YES on a substantively similar proposal once market conditions improve. This vote is a position on treasury timing discipline, not on Eternl's work.
NoCardano Vision 2026: Human Centred, Scalable, Post Quantum Secure - IO ResearchEpoch 637revotedHistoryEnacted1mo ago
Earlier votes
No1mo agoSuperseded
NoRevised Cardano Summit 2026 SingaporeEpoch 634RationaleExpired2mo ago
Vote: NO
- The revision is genuinely improved over the rejected original (14M ADA → 7.8M ADA, decoupled from TOKEN2049, better oversight)
- Core objection: $450K revenue against $2.26M budget — treasury absorbs ~80% with no repayment obligation
- Cardano Foundation's own contribution is only $380K; the organizer asks far more from the treasury than it contributes itself
- A one-time event produces no compounding infrastructure value — 7.8M ADA at current prices should go to work that persists
- Encourages resubmission with treasury as a minority funder and a revenue-share or repayment structure
NoPogun: Capital Without CompromiseEpoch 633RationaleExpired2mo ago
Vote: NO
Pogun addresses a genuine strategic need. A non-custodial Bitcoin credit market and trust-minimized bridge would give Cardano access to the largest pool of idle capital in crypto. The technical design is sound: an oracle-free bilateral lending protocol avoids the failure modes that have plagued conventional DeFi lending, and the 1-of-N BitVM bridge security model is theoretically robust. The repayment structure — 20% of earnings returned to the treasury until full repayment, then 5% in perpetuity — is the most treasury-positive funding structure we have seen from IO to date.
Despite these strengths, Vampyre Fund votes NO.
Our objection is structural, not technical. Vampyre Fund believes treasury funds must not be used as team operating budgets. The correct model is to separate features from budgets: DREPs vote on what to build, not who to pay. Funding should be released incrementally, gated on delivered work, with teams bidding competitively for each unit of work. Pogun, as submitted, asks the treasury to pre-fund IO's team roadmap for the year. There is no competitive bidding, no sprint-based accountability, and no on-chain enforcement of feature delivery before disbursement.
This is not a judgment on Pogun's merit as a project. Bitcoin DeFi infrastructure on Cardano is worth building. But the mechanism matters. Voting YES here reinforces a budget process that Vampyre Fund believes is fundamentally broken and that concentrates treasury disbursements in incumbent teams rather than creating an open, competitive, and accountable development ecosystem.
We encourage IO to resubmit Pogun as a feature prioritization request under a sprint-based funding model, and we commit to voting YES on such a resubmission if the delivery structure meets the standard described in our published governance blog.
NoIO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and UsabilityEpoch 634RationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
NoIO: Cardano High Assurance Technical CollaborationEpoch 634RationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
NoIO & Midgard Labs: L2 Scalability InitiativeEpoch 633RationaleExpired2mo ago
IO has been funded by a significant amount of premine tokens.
NoIO & Ensurable Systems: Cardano Maintenance InitiativeEpoch 634RationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
NoIO: Consensus InitiativeEpoch 634RationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
NoIO: Cardano UpgradesEpoch 634revotedRationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
Earlier votes
No2mo agoSuperseded
IO has been funded by a significant amount of premine tokens.
NoIO: Developer Experience InitiativeEpoch 634RationaleEnacted2mo ago
IO has been funded by a significant amount of premine tokens.
YesCardano Critical Integrations BudgetEpoch 604RationaleClosed8mo ago
This infrastructure is needed and it's great to see the entities working together.
YesBudget: ₳5M Loan for Cardano's Global Listing Expansion - Powered by SnekEpoch 587RationaleClosed10mo ago
This is an experimental loan, which is innovative and a creative potential use for Cardano treasury funds. We do not in general support treasury funds used directly for budgets and believe this is an innovative solution that will bring value to the ecosystem.
YesWithdraw ₳99,600 for BloxBean Java Tools Maintenance and EnhancementEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳104,347 for MLabs Research towards Tooling for Elliptical Curves...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳750,000 for Cardano Product Committee: Community-driven 2030 Carda...Epoch 578RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳314,800 for PyCardano administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳199,911 for OpShin - Python Smart Contracts for CardanoEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳26,840,000 for Input Output Research (IOR): Cardano Vision - Wor...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳4,000,000 for Expanding Stablecoin / Cardano Native Asset Support...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳3,000,000 for High-yield RWA Asset for Cardano: Tokenized Real EstateEpoch 577RationaleExpired0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳889,500 for Cardano Ecosystem Pavilions at ExhibitionsEpoch 578RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoWithdraw ₳3,126,000 for Ecosystem Exchange Listing and Market Making service...Epoch 578RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳1,500,000 for Complement Catalyst: Extended Quadratic Funding---Zer...Epoch 577RationaleExpired0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoWithdraw ₳12,000,000 for Cardano Builder DAO administered by IntersectEpoch 577RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳6,000,000 for Unveiling the First Unified Global Events Marketing S...Epoch 577RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳6,000,000 for Cardano Summit 2025 and regional tech eventsEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoWithdraw ₳69,459,000 for Catalyst 2025 Proposal by Input Output: Advancing De...Epoch 575RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳592,780 for Beyond Minimum Viable Governance: Iteratively Improvin....Epoch 578RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳15,750,000 for a MBO for the Cardano ecosystem: IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳212,000 for AdaStat.net Cardano blockchain explorerEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳605,000 for A free Native Asset CDN for Cardano DevelopersEpoch 578RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳266,667 for Cexplorer.io -- Developer-Focused Blockchain Explorer...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳657,692 for Scalus - DApps Development PlatformEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳583,000 for Eternl Maintenance administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳700,000 for ZK Bridge administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoWithdraw ₳11,070,323 for TWEAG's Proposals for multiple core budget project...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳243,478 for MLabs Core Tool Maintenance & Enhancement: PlutarchEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳578,571 for Gerolamo - Cardano node in typescriptEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳5,885,000 for OSC Budget Proposal - Paid Open Source Model...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoWithdraw ₳600,000 for Complete Web3 developer stack to make Cardano the smart...Epoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳300,000 for Ledger App Rewrite administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳220,914 for Dolos: Sustaining a Lightweight Cardano Data NodeEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳1,161,000 for zkFold ZK Rollup administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳130,903 for Lucid Evolution Maintenance administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳220,914 for UTxO RPC: Sustaining Cardano Blockchain IntegrationEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳220,914 for Pallas: Sustaining Critical Rust Tooling for CardanoEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳424,800 for Hardware Wallets Maintenance administered by IntersectEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
AbstainWithdraw ₳1,300,000 for Blockfrost Platform community budget proposalEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
AbstainWithdraw ₳96,817,080 for 2025 Input Output Engineering Core Development ProposalEpoch 575RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳2,162,096 for Midgard - Optimistic Rollups administered by IntersectEpoch 575RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
YesWithdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nixEpoch 576RationaleEnacted0y ago
Treasury withdrawals
Software Development Proposals:
Development budgets should not be funded from the treasury. Instead, the treasury should be used to incentivize feature completion through grants. The treasury should not operate as a venture capital fund or to fund ongoing development budgets. It should be results oriented and decoupled from budgeting. Dracula DAO Deep will make exceptions this round for projects that deliver specific, high value features or results at a reasonable ask amount.
Marketing Proposals:
Marketing budgets are the best way to fund these types of efforts. Judgement should be used based on the ask amount and value proposition.
Research Proposals:
Research budgets should be evaluated based on the track record of the team being funded, the value proposition and whether the results are released to the public.
DAO Funding:
DraculaDAO believes DAOs should find other ways to support operations other than public treasury funds.
Bitcoin:
Dracula DAO Deep is against purchasing Bitcoin with treasury funds, and are generally not in favor of a tight Bitcoin / Cardano partnership. Bitcoin DeFi is ok as long as the value proposition remains with Cardano. Cardano is already Bitcoin++ and treasury funds should not be used to encourage or sustain BTC energy waste and outdated consensus model.
Yes - MLabs Core Tool Maintenance. Ask is reasonable.
Yes - Midgard Optimistic Rollups. This is urgently needed as an L2 solution for Cardano and the ask is reasonable.
Yes - Hardware Wallets Maintenance. This is necessary and ask is reasonable.
Yes - Pallas Rust Tooling. Core tooling used by many projects and ask is reasonable for the specific deliverable.
Yes - UTxO RPC
Yes - Lucid Evolution Maintenance
Yes - zkFold ZK Rollup
Yes - Dolos. Ask is reasonable with specific deliverable.
Yes - Ledger App rewrite
Yes - Paid Open Source Model. This looks like a nice way to take the VC function out of the treasury and start towards incentivizing projects through features and benefits like bug bounties. Willing to take a chance on this, but will vote no in the future if results are disappointing.
Yes - Gerolamo node in typescript
Yes - MLabs Core Tools: Plutarch. Ask is reasonable
Yes - ZK Bridge
Yes - Eternal maintenance
Yes - Scalus Development Platform
Yes - Cexplorer.io
Yes - Native Asset CDN
Yes - Adastat.net
Yes - Intersect MBO. DraculaDAO does not like the high ask amount and the budgeting approach, but for Intersect MBO there may not be a better way like there is with software development. Therefore DraculaDAO supports this proposal, realizing this possibly breaks with the general guidelines DraculaDAO described above.
Yes - Beyond Minimum Viable Governance. Focused feature set and reasonable ask. IOHK should use this approach for all its teams.
Yes - Cardano Summit
Yes - Unified Global Events Marketing
Yes - Quadratic Funding. Reasonable ask for a specific feature.
Yes - Cardano Ecosystem Pavilions
Yes - High-yield RWA Asset. Direct communication with this vendor increased our faith in this project and have changed our stance on this.
Yes - Expanding Stablecoin / Native Asset Support. This was marginal in terms of ask amount and number of features grouped together.
Yes - OpShin
Yes - PyCardano
Yes - Cardano Product Committee
Yes - BloxBean Java Tools
Yes - Input Output Research
Yes - MLabs Research
Abstain - Input Output Core Development. This is simply a warning shot as DraculaDAO expects this proposal will pass. We are generally in favor of the initiatives and features being delivered by IOHK, but believe the ask is too high as a single budget line item and do not want to set a precedent of another ask of similar magnitude for the next budget cycle. Instead, IOHK should divide its deliverables into features and ask the treasury for grant incentives delivered on completion of the each feature (see Beyond Minimum Viable Governance as what we see as a good example). We are not in favor of such a large withdrawal encompassing such a large number of features. In general we do not support using the treasury for budget line items as mentioned in the introduction to this rationale.
Abstain - Blockfrost Community Budget. We support Blockfrost and operate an icebreaker node. There are no specific features mentioned, just an ongoing budget line item, which we do not support. We will support Blockfrost in other ways.
No - Web3 developer stack for Bitcoin integration. DraculaDAO does not support a tight integration with Bitcoin.
No - TWEAG Proposals. We see value there but the ask is too large and too many deliverables bundled together.
No - Catalyst 2025. Ask is too large as a single budget request.
No - Cardano Builder DAO. Treasury should not be used to incentivize features, not fund ongoing budgets for software development or DAOs.
No - Market making should have other ways to fund operations.
NoTempo for Cardono Governance - Maintenance & Development Budget for 2025Epoch 576RationaleClosed1y ago
Tempo is a good tool and needs UI work, however, the ask amount is overpriced for a 6 month operating budget. We run relay nodes, preview and preprod testnet nodes plus a midnight node for a small percentage of that. We also believe in general that development should be incentivized through the treasury, not have the entire budget come from the treasury.
NoCardano Blockchain Ecosystem Budget - 275M ada Administered by IntersectEpoch 564RationaleClosed1y ago
The budget process itself is flawed. Features need to be decoupled from budget amounts using an Agile approach as described here: https://github.com/Dracula-DAO/cardano-drep/blob/main/blog/2025/2025-04-24.md
Yes2025 Cardano NCLEpoch 561RationaleClosed1y ago
Dracula DAO strongly supports a conservative approach to budgeting and the lower NCL is better for the ecosystem long-term. ADA not spent today is ADA available tomorrow when priorities and conditions change. In general we also believe the treasury should provide funding in the form of incentive grants awarded upon project completion, and not a project's entire operating budget.
No2025 Net Change LimitEpoch 554RationaleClosed1y ago
We voted 'yes' on the 300M Net Change Limit proposal and are choosing to support the lower limit over the higher limit because that represents the more conservative approach.
YesSet 2025 Net Change Limit of 300M ADA, 2026 Net Change Limit of 250M ADAEpoch 553RationaleClosed1y ago
We believe there needs to be a cap in place, even if it gets changed later. Setting this cap at the projected inflow ensures the treasury will not be depleted while the community debates a longer-term or more refined approach. Therefore, we support this proposal.
YesDefining the Cardano Vision and Roadmap for 2025 and beyondEpoch 549RationaleClosed1y ago
Dracula DAO is generally in favor of most of the items in this roadmap and we respect the effort being put in by the Intersect Product Committee. We believe Leios, Hydra, Midgard and developer tools / experience are items that definitely belong on the near-term roadmap.
The roadmap as a whole is hard to distill down into a simple Yes / No vote, especially without any budgets and timelines. However, since this is simply a non-binding info action we are choosing to vote "Yes" to indicate to the governance community our general support of the roadmap as presented.