DRepActive

Pallamus

drep1ytsj...pc2fqmyr

205,609 ₳205.6K ₳voting power

5 delegators<0.01% of active voting power

About

Objectives

I will support a decentralized, secure, and economically sustainable Cardano. My priorities are transparent governance, responsible treasury stewardship, critical protocol research and infrastructure, support for capable builders, and broader real-world adoption. I will judge proposals on their merits, constitutional alignment, measurable ecosystem value, cost, milestones, delivery capacity, and accountability. I favor structured debate, amendment, milestone-based funding, progress reporting, audits where appropriate, and sunset clauses over obstructionism or blank-check spending. The institutions supporting Cardano should coordinate transparently, while the community retains governing authority.

Read moreShow less

Motivations

I have participated in the Cardano ecosystem for more than five years and believe its research-driven engineering, decentralization, security, and formal governance give it lasting value beyond short-term market cycles. I am registering as a DRep because delegated voting power carries a duty to study proposals, explain decisions, and remain answerable to ADA holders. I want governance to be principled without becoming rigid, skeptical without becoming destructive, and supportive of growth without abandoning fiscal discipline. Delegators should always be able to understand why their representative voted yes, no, or abstain.

Read moreShow less

Qualifications

I am an IT Infrastructure Engineer, developer, crypto and blockchain participant, DIY technology enthusiast, and amateur radio operator. I hold a degree in political science and history, giving me a practical interest in constitutional design, representative government, institutional incentives, checks and balances, and public accountability. My technical background helps me assess infrastructure, security, implementation risk, operational readiness, and delivery claims. My years in Cardano have given me familiarity with its governance, treasury debates, research roadmap, ecosystem institutions, DeFi, community concerns, and long-term development priorities.

Read moreShow less

Governance record

Participation50%Voted on 6 of 12 concluded actionsAhead of 53% of 337 active DReps
Votes with rationale100%9 of 9 votes with rationaleAhead of 93% of 320 active DReps with votes
Vote timingDay 8.0Median point after submission across 9 timed votes
Voting pattern
9votes
  • Yes6 (67%)
  • No2 (22%)
  • Abstain1 (11%)

No vote changes

Percentiles compare active DReps with at least five concluded actions since their registration. What these numbers mean

Voting power trend0.7%vs last epoch
204.1K ₳238.6K ₳5Epoch 648Epoch 656
13.7%over 9 epochsDelegators5+1over 9 epochs

Recognition (4)

Identified
Iron Streak
Bronze
Early Bird
View all 4 badges

Activity

Want to see how your own views compare? Find a DRep who votes like you.

AbstainShould stakePoolTargetNum (k) be raised from 500 to 1000? (SPO poll)Submitted epoch 656View rationaleActive16h ago

ABSTAIN — I see merit in exploring an increase of stakePoolTargetNum from 500 to 1000, particularly if it can improve stake distribution and create greater opportunity for independent SPOs. However, I am not yet convinced that doubling k will necessarily translate into greater operator decentralization rather than simply a larger number of pools.

Before supporting a future parameter change, I would like to see clearer analysis of its likely effects on operator concentration, delegation behavior, pool economics, and smaller SPOs.

I therefore abstain on this poll while remaining open to supporting the change if the evidence demonstrates a meaningful decentralization benefit.

YesReduce minPoolCost to 75 adaSubmitted epoch 654View rationaleActive16h ago

YES — I previously supported reducing minPoolCost from 170 ADA to 75 ADA when it was included in the earlier parameter-update action. That proposal did not take effect because the bundled action failed to meet the required SPO threshold.

My position on the underlying parameter change has not changed. Lowering minPoolCost gives smaller stake pools greater flexibility, reduces the fixed-cost burden on their delegators, and can support a more competitive and decentralized stake-pool ecosystem.

Because this proposal addresses the minPoolCost change directly and separately, I support it and vote YES.

NoWithdraw 11,787,063 ada for the OpenZeppelin Stack administered by IntersectSubmitted epoch 654View rationaleActive16h ago

NO — I recognize the potential value OpenZeppelin can bring to Cardano and I support efforts to strengthen the ecosystem’s developer infrastructure and security tooling. However, I am not convinced that the requested 11,787,063 ADA expenditure has been sufficiently demonstrated to be distinct from existing or ongoing Cardano ecosystem initiatives.

At this level of expenditure, the burden of proof should be high. The community should have a clear accounting of what capabilities already exist, what work is currently underway elsewhere in the ecosystem, what specific gaps remain, and why this particular scope requires an additional treasury commitment of this magnitude.

The proposal includes milestone-based controls and oversight, which I acknowledge positively. However, good administration does not by itself resolve questions of potential duplication, scope, necessity, or overall value to the treasury.

Until those questions are addressed with greater clarity, I cannot justify this withdrawal. I am therefore voting NO.

YesReimburse Ikigai Info Governance Action Deposit.Decided epoch 656View rationaleExpired29d ago

I voted YES on the proposal to reimburse the Ikigai governance action deposit.

I initially withheld my vote because I did not believe the proposal, on its own, provided enough evidence to justify reimbursement from the Cardano Treasury. When treasury funds are involved, especially in cases involving an individual loss or mistaken transaction, I believe DReps should require clear and independently verifiable evidence before approving reimbursement.

Following additional discussion, supporting information was provided that clarified the relationship between the original governance action, the deposit address, and the relevant withdrawal activity. After reviewing that information, I believe there is sufficient evidence to establish that the reimbursement request is legitimate.

It is also important to distinguish between a protocol failure and user error.

Based on the information provided, this does not appear to have been a Cardano protocol bug or a failure of the governance system itself. Rather, the loss appears to have resulted from user error within functionality that is operating according to the current CIP-1694 design and specification.

That distinction materially affected my decision.

I do not believe the Cardano Treasury should become an automatic insurance mechanism for mistakes made by users. Establishing such an expectation could create an unhealthy precedent in which ordinary operational errors are routinely transferred to the broader community.

However, governance also requires judgment. Not every situation can be reduced to a rigid rule without considering the specific facts involved.

In this instance, the circumstances have been documented sufficiently, the relevant transactions and addresses can be examined, and the amount being requested corresponds to the governance action deposit involved. I therefore believe reimbursement is reasonable and proportionate.

My support should not be interpreted as establishing a general policy that every lost governance deposit should be reimbursed. Future requests should continue to be evaluated individually and should meet a meaningful evidentiary standard.

At minimum, I believe reimbursement requests should demonstrate:

A clearly identifiable governance action and deposit.
Verifiable transaction history linking the funds to the claimant.
A credible explanation of how the funds became inaccessible or were lost.
Evidence sufficient for independent review by DReps and the community.
A reimbursement amount directly tied to the demonstrated loss.
No indication of fraud, manipulation, or an attempt to shift ordinary financial risk onto the Treasury.

This proposal now satisfies those concerns sufficiently for me.

An important part of responsible governance is also being willing to change a preliminary position when new evidence becomes available. My initial concern was the absence of adequate supporting information. Once members of the community provided additional context and evidence, continuing to oppose the proposal simply because I had previously expressed skepticism would have served no useful governance principle.

DRep voting should be based on evidence, not attachment to an earlier position.

For those reasons, I believe approving this reimbursement is fair, reasonable, and consistent with responsible treasury governance.

Vote: YES

NoGovernance Incentives Framework 2026Decided epoch 656View rationaleExpired1mo ago

Vote: NO

I am voting NO on the Governance Incentives Framework 2026 proposal in its current form.

I want to be clear that I am not opposed to the underlying objective of this proposal. Cardano governance needs sustainable participation, and the questions surrounding DRep engagement, voter participation, concentration of voting power, and the long-term sustainability of governance actors are important ones.

I also believe there is value in researching whether carefully designed incentives could improve governance participation without undermining decentralization.

My concern is with the level of specificity provided for the funding request itself.

The proposal requests more than ₳4.2 million from the Cardano Treasury to research, model, test, and pilot potential governance incentive mechanisms. I understand that the purpose of this work is to determine what an effective incentive framework might ultimately look like. I therefore do not expect the proposers to already know the final reward formula or permanent compensation model before the research is completed.

However, there is an important distinction between leaving the final research outcome open and leaving the structure of the funded experiment insufficiently defined.

Before authorizing a Treasury withdrawal of this size, I believe DReps and ADA holders should have greater clarity regarding how the funded pilot will operate, how Treasury funds will be controlled, and what safeguards will govern the experiment.

In particular, I would like to see clearer answers to several questions.

How will participants in the real-ADA incentive pilot be selected?

What eligibility requirements will apply?

How much of the overall Treasury request is specifically intended for incentive distribution, and how much is allocated to research, administration, development, community engagement, data collection, and other expenses?

How will ADA used in the pilot be distributed among participants?

What limits or caps will be placed on individual distributions?

Who will have authority over those distributions, and what oversight will exist over that process?

What safeguards will prevent conflicts of interest between the parties designing, administering, evaluating, and potentially benefiting from the incentive system?

What mechanisms will be used to prevent gaming, superficial participation, vote farming, or behavior designed primarily to maximize rewards rather than improve governance quality?

How will the pilot avoid reinforcing the very concentration of voting power that the proposal identifies as a concern?

What objective criteria will determine whether the pilot is successful, unsuccessful, or produces mixed results?

What conditions would cause the experiment to be modified, paused, or terminated?

What happens to ADA that is budgeted but ultimately not required?

How will expenditures and distributions be reported to the community throughout the project?

These questions matter because incentive systems can change behavior in ways that are difficult to reverse once financial expectations become established.

Cardano should be especially careful when introducing monetary incentives into governance. Poorly designed incentives could encourage participation in quantity while reducing participation in quality. They could reward activity rather than judgment, create new opportunities for gaming, advantage already dominant governance actors, or unintentionally encourage further concentration of delegated voting power.

The proposal itself recognizes many of these risks, which is one reason I believe the subject deserves serious research.

But recognizing those risks also strengthens the argument for clearly defining the boundaries and safeguards of the experiment before Treasury funds are approved.

A research proposal does not need to predetermine its conclusions. It should, however, clearly define the experiment being funded.

For a Treasury withdrawal exceeding four million ADA, I believe the community should be able to understand with reasonable precision what is being purchased, how funds will be deployed, what financial controls will apply, how success will be measured, and how the community will be protected if the experiment produces unintended consequences.

At this stage, I do not believe the proposal provides enough clarity in those areas for me to responsibly support the withdrawal.

This should not be interpreted as opposition to governance incentives themselves.

I am open to the possibility that governance incentives could eventually play a useful role in Cardano. Meaningful governance participation requires time, research, analysis, communication, and accountability, and there is a legitimate discussion to be had about whether those contributions should be compensated.

But supporting the research question does not automatically mean supporting every funding structure proposed to investigate it.

Treasury governance requires us to evaluate not only whether an idea has merit, but whether the specific request before us is sufficiently defined, accountable, and proportionate.

My responsibility as a DRep is not simply to determine whether I like the intended outcome. It is also to determine whether I can reasonably explain to my delegators what their Treasury is funding and what protections exist around that expenditure.

In this case, I do not yet believe I can do that with sufficient confidence.

For those reasons, I am voting NO in its current form.

I would be willing to reconsider a revised proposal that provides greater detail regarding the pilot design, participant selection, distribution mechanics, spending controls, oversight, conflict-of-interest protections, anti-gaming safeguards, measurable success criteria, reporting requirements, and treatment of unused Treasury funds.

Governance experimentation can be valuable, and Cardano should continue exploring ways to improve participation and decentralization.

But experimentation funded by the Treasury should have clearly defined boundaries and accountability from the beginning.

Before committing more than ₳4.2 million, I believe we should understand not only why this research is worth pursuing, but also how the experiment will be conducted, how Treasury ADA will be controlled, who may receive it, under what conditions, and with what safeguards.

Until those questions are answered more clearly, I can't responsibly support this Treasury withdrawal.

Show 4 moreShow less
YesUpdate Constitutional Committee 2026Decided epoch 654View rationaleEnacted1mo ago

I am voting YES on the Update Constitutional Committee 2026 governance action.

This action implements the outcome of the 2026 Constitutional Committee election by updating committee membership to reflect the candidates selected through the established DRep voting process.

For me, this vote is not about whether I personally agree with every view, statement, or action of every individual elected. It is about respecting a legitimate governance process and honoring its verified outcome.

Decentralized governance only has meaning if the community is willing to accept the results of the processes it has agreed to use. Elections cannot become symbolic exercises where results are respected only when they align with our individual preferences.

The Constitutional Committee has a specific and important role within Cardano governance: determining whether governance actions comply with the Cardano Constitution. Its purpose is not to dictate policy or replace the judgment of DReps, SPOs, or ADA holders, but to serve as an independent constitutional safeguard within the broader governance system.

Updating the committee in accordance with the election results also supports continuity, accountability, and the orderly transfer of governance responsibility.

I have seen no compelling evidence that the election process or its outcome was invalid, nor any reason to reject the implementation of the results.

Decentralization does not happen simply because the protocol allows it. It happens because the community deliberately practices it. That includes participating in elections, respecting their outcomes, and allowing Cardano’s governance institutions to evolve through transparent community-driven processes.

For those reasons, I vote YES.

YesName the Protocol Version 12 hard fork “von Bergen“Decided epoch 651View rationaleClosed1mo ago

I am voting YES to name the Protocol Version 12 hard fork “von Bergen” in recognition of Fabian von Bergen, known throughout the Cardano community as Zyroxa.

Fabian represents the kind of contribution that decentralized ecosystems depend upon: long-term participation, education, community involvement, stake pool operation, and a willingness to engage openly in discussions about Cardano’s direction and governance.

Cardano is not built solely by founding entities, developers, or large organizations. It is also built by the people who spend years helping others understand the network, operating infrastructure, participating in governance, and strengthening the community from the ground up. Recognizing contributors like Fabian reinforces that principle.

I also believe there is value in preserving the history of the people who helped shape Cardano along the way. Naming protocol upgrades after meaningful contributors gives future generations of the ecosystem an opportunity to ask who those people were and why their work mattered.

My YES vote applies specifically to this Info Action and the proposed naming of Protocol Version 12 as “von Bergen.” It should not be interpreted as approval of the technical contents of Protocol Version 12 or of any future Hard Fork Initiation governance action associated with it. Those decisions should be evaluated separately on their own technical, constitutional, security, and governance merits.

Decentralization does not happen simply because a protocol allows it. It happens because a community deliberately practices it. Honoring individuals who contributed their time, knowledge, infrastructure, and effort toward that goal is appropriate.

For those reasons, I support naming Protocol Version 12 the “von Bergen” hard fork.

YesReduce minPoolCost to 75 ada and increase Plutus Memory Limits (Part 2)Decided epoch 653View rationaleExpired1mo ago

I am voting YES on this governance action because I believe both proposed parameter changes are reasonable, evidence-based, and supportive of Cardano’s long-term decentralization, scalability, and ecosystem growth.

The first component of this proposal reduces minPoolCost from 170 ADA to 75 ADA. I support this change because the current fixed minimum cost can place a disproportionate burden on smaller and independent stake pool operators, particularly those that produce relatively few blocks per epoch.

As staking rewards gradually decline over time, a fixed minimum pool cost represents an increasingly large portion of the rewards generated by smaller pools. This can make those pools less attractive to delegators, even when they are technically well operated and contribute positively to Cardano’s decentralization.

Lowering minPoolCost does not force stake pool operators to charge only 75 ADA. It simply lowers the protocol-defined minimum. Operators remain free to set a higher fixed cost if that better reflects their operating expenses, infrastructure requirements, or business model.

I believe this added flexibility is important. Cardano should avoid creating economic conditions that unintentionally favor only large pools or large multi-pool operations. Smaller independent operators are an important part of a healthy and geographically distributed staking ecosystem, and protocol parameters should not create unnecessary structural disadvantages for them.

I also recognize the concern that lowering the minimum could create competitive pressure for operators to reduce fees below sustainable levels. That concern is valid and should continue to be monitored. However, because the parameter establishes a minimum rather than a mandatory fee, I believe operators and delegators should have greater freedom to determine what fee structures are appropriate.

The second component of this proposal increases Plutus memory limits. I strongly support this change.

The proposal increases transaction memory from 16.5 million units to 17.5 million units and block memory from 72 million units to 77.5 million units. These increases provide additional execution capacity for more sophisticated Plutus scripts and applications.

Cardano’s application ecosystem continues to evolve. DeFi protocols, aggregators, lending platforms, DEXs, complex multi-script transactions, and other applications increasingly require greater computational resources. Providing developers with additional memory capacity gives them more room to build sophisticated applications without unnecessarily constraining functionality at the protocol level.

What I particularly support is the measured way this increase has been approached.

The previous memory increase was implemented first, observed under real network conditions, and then evaluated before proceeding with the next stage. That is exactly how protocol parameter changes should be handled.

Rather than making aggressive changes based only on theoretical demand, Cardano has the ability to increase capacity incrementally, observe network behavior, evaluate utilization, and proceed based on evidence.

The fact that transactions have already made use of the additional memory provided by the previous increase demonstrates that this is not simply an arbitrary increase in theoretical limits. There is real demand for additional execution capacity.

At the same time, the proposed increases remain within Cardano’s constitutional parameter guardrails. Those guardrails exist to protect network performance, block propagation, validation times, and node accessibility. Expanding capacity while respecting those limits represents a responsible balance between scalability and network safety.

This proposal also illustrates one of the strengths of Cardano’s governance and development philosophy: protocol parameters can evolve gradually as network usage changes, rather than requiring disruptive redesigns or reactive decisions.

I do have one reservation regarding the structure of this governance action. The minPoolCost reduction and Plutus memory increases address two largely unrelated areas of the protocol—stake pool economics and smart contract execution capacity.

As a general governance principle, I would prefer unrelated parameter changes to be submitted as separate governance actions whenever practical. Separate actions provide clearer voting signals and allow DReps and SPOs to evaluate each issue independently.

However, in this case, I find both individual changes sufficiently justified on their own merits, so the bundling does not prevent me from supporting the action.

Reducing minPoolCost provides greater economic flexibility for stake pool operators and may help smaller pools remain competitive, supporting Cardano’s decentralization.

Increasing Plutus memory limits expands the capabilities available to developers and applications while following a cautious, incremental, and evidence-based approach.

Both changes reflect responsible protocol stewardship rather than unnecessary experimentation.

For these reasons, I vote YES on the governance action to reduce minPoolCost to 75 ADA and increase Plutus memory limits.

YesWithdraw 120,000,000 ada for AlphaGrowth’s Cardano PRIMEDecided epoch 650View rationaleEnacted1mo ago

I am voting Yes on AlphaGrowth’s Cardano PRIME proposal because Cardano has spent years building strong technical infrastructure, but that infrastructure has not yet translated into the depth of liquidity, stablecoin activity, users, fees, and sustained DeFi participation the ecosystem needs.

The 120 million ADA request is substantial, so my support is not based on writing AlphaGrowth a blank check. PRIME uses a phased structure that begins with a public ecosystem audit and gap analysis before large-scale capital deployment. Roughly three-quarters of the budget remains behind a Month 4 release gate, subject to review by an independent Operating Group. The proposal also separates AlphaGrowth’s recommendations from oversight and custody, includes milestone-gated releases, quarterly reporting, conflict-of-interest protections, independent audit funding, and triggers for returning unused or unearned funds to the treasury.

I also support the proposal because its goal is not merely to purchase temporary TVL through short-lived incentives. It is designed to identify why capital is not entering or remaining in Cardano, close infrastructure and market gaps, deepen liquidity, support native builders, and create economic activity capable of surviving after incentives taper. Success should be measured not only by headline TVL, but by stablecoin liquidity, users, transactions, fees, productive markets, and sustained capital retention.

There is execution risk, and approval must be followed by continued scrutiny. However, Cardano cannot expect DeFi growth without making serious, accountable investments in liquidity, integration, distribution, and market development. In my judgment, PRIME provides enough oversight, performance alignment, and staged accountability to justify giving the program the opportunity to deliver.

For those reasons, I vote Yes.

On-chain profile details

DRep ID
drep1ytsj...pc2fqmyr
Payment address
addr1qxdf...tqkgzqhg
Registered since
Aug 6, 2026
Last metadata update
1mo ago
Data freshness
On-chain data as of 16h ago