Withdraw 540,750 ada for Pallas by TxPipe: Maintaining Cardano's Core Rust Li...

System3mo ago1 post

116 DReps voted · 35 with a rationale · 2 changed their vote · 1 re-voted unchanged

Open a row to read the rationale.

Changed votes: 2 to yes, together voting with 2.3M ₳ of voting power.

Voting concentration

6 of 116 DReps cast half of the voted power.

Largest voter 14.3%, top 5 combined 46.6% of 4.1B ₳ voted.

The 19 largest voters together held as much voting power as the 67.0% threshold required in yes votes.

  • Yes5.3M ₳No rationale
  • Yes5.1M ₳No rationale
  • Yes4.9M ₳No rationale
  • Yes4.5M ₳No rationale
  • Yes4.1M ₳Rationale

    I see this as a administrative vote which is to process a withdrawal that DRep's have previously approved. I do not believe in throwing monkey-wrenches into approved and planned for processes, and thus I vote yes so as not to obstruct progress and momentum, and to not undermine previous decisions.

  • Yes2.8M ₳No rationale
  • Yes2.7M ₳Rationale

    私は本Treasury Withdrawalに賛成します。
    Pallasは、CardanoのOuroboros / ledger / CBOR / cryptography / networking / transaction buildingなどの基礎処理をRustで扱うための重要なOSSライブラリ群です。これは特定dAppのための私的開発ではなく、Aiken、Dolos、Oura、Mithril、Amaru、UTxO RPCなど、Cardanoの複数プロジェクトが再利用できる公共性の高いDevX基盤です。
    また、Pallasの保守は、Cardanoのdata access layerと開発者基盤をHaskell中心に閉じず、Rust-native toolingへ広げる意味があります。これはCardanoのclient diversity、tooling diversity、開発者体験を高める支出として評価できます。
    資金管理面でも、Intersect管理のSmart Contract Disbursement、TRSC/PSSC、milestone-based controls、oversight committee、dashboard透明性を備えている点を評価します。


    I support this Treasury Withdrawal.

    Pallas is an important open-source set of Rust libraries for handling core Cardano functions such as Ouroboros, ledger data, CBOR, cryptography, networking, and transaction building. This is not private development for a single dApp. It is a high-public-value DevX foundation that can be reused by many Cardano projects, including Aiken, Dolos, Oura, Mithril, Amaru, and UTxO RPC.

    Maintaining Pallas also helps expand Cardano’s data access layer and developer ecosystem beyond Haskell-centered tooling. It strengthens client diversity, tooling diversity, and the overall developer experience on Cardano.

    I also value the funding management design: Intersect administration, Smart Contract Disbursement, TRSC/PSSC, milestone-based controls, an oversight committee, and dashboard transparency.

  • Yes2.6M ₳No rationale
  • Abstain2.5M ₳No rationale
  • Yes2.5M ₳Rationale

    Due to rationales becoming stressful and the bear market vibes - I will not be providing rationale. I voted the way that I did bc we need a 'no stress' environment more than ever.

  • YesChanged2.2M ₳History

    Earlier votes

    No2mo agoSuperseded

  • Yes2.2M ₳No rationale
  • Yes2.1M ₳Rationale

    I am voting YES on the TxPipe Pallas proposal.

    Pallas is core developer infrastructure for Cardano. It provides Rust libraries for important Cardano primitives, including ledger data structures, serialization, cryptography, transaction building, chain synchronization, multi-era support, and node communication.

    This is not a speculative growth proposal. It is a focused maintenance request for open-source tooling that sits low in the Cardano development stack and is used by multiple downstream projects and developer tools.

    In the current NCL environment, I believe DReps need to be selective. My priority is to support proposals that maintain critical public goods, core developer infrastructure, protocol compatibility, open-source libraries, and the technical rails that Cardano builders rely on.

    Pallas clearly fits that category.

    I consider this one of the stronger TxPipe proposals because it is foundational. Higher-level tools and applications depend on reliable lower-level libraries. If those libraries fall behind ledger changes, hard forks, dependency updates or protocol evolution, the impact can propagate across the ecosystem.

    I also view it positively that this proposal is modest in size compared with many other live treasury requests and is structured through the 2026 treasury management framework, with Intersect administration, oversight controls, milestone-based disbursement and community auditability.

    Given the current budget pressure, I am prioritising infrastructure and maintenance over larger speculative or commercial proposals. Pallas is exactly the type of low-level open-source developer tooling that the treasury should be willing to maintain.

    For these reasons, I consider this a responsible and proportionate use of treasury funds.

    I vote YES.

  • Yes1.9M ₳No rationale
  • Yes1.6M ₳No rationale
  • No1.3M ₳No rationale
  • No1.3M ₳No rationale
  • Yes1.2M ₳No rationale
  • Yes1.2M ₳No rationale
  • Yes1.1M ₳No rationale
  • Yes1.1M ₳No rationale
  • Yes1.1M ₳No rationale
  • Yes982.8K ₳No rationale
  • No927.1K ₳No rationale
  • Yes926.9K ₳No rationale
  • Yes884.6K ₳No rationale
  • Abstain867K ₳No rationale
  • Yes832.6K ₳Rationale

    We support Intersect's budget process. This proposal was part of it.

  • Yes812K ₳No rationale
  • Yes665.2K ₳No rationale
  • YesChanged622.3K ₳History

    Earlier votes

    Abstain2mo agoSuperseded

  • Yes586.6K ₳Rationale

    Supporting withdrawal

  • Yes581.7K ₳No rationale
  • Yes570.1K ₳Rationale

    TxPipe will deliver, absolute must approval.

  • Yes568.1K ₳No rationale
  • Yes482.3K ₳No rationale
  • No379.7K ₳Rationale

    TxPipe is among the companies that in my opinion have extracted more than enough profits from the Cardano ecosystem and shouldn't be funded anymore.

    Power to the edges!

  • No366.9K ₳No rationale
  • Yes333.1K ₳No rationale
  • Yes297.7K ₳Rationale

    We definitely want Pallas to be maintained!

  • Yes284.5K ₳No rationale
  • Yes275.9K ₳No rationale
  • Yes272.4K ₳No rationale
  • Yes261.1K ₳No rationale
  • Yes214.5K ₳No rationale
  • No188.5K ₳No rationale
  • Yes182.9K ₳No rationale
  • Yes161.1K ₳No rationale
  • Yes160.9K ₳No rationale