Tansu - Decentralized project governance on Stellar

Tansu provides cryptographic proof of code integrity and transparent governance for open-source projects.

   
Category Governance Tools
Website https://tansu.dev
Repository https://github.com/Consulting-Manao/tansu
First Released October 2025
Intake https://github.com/SCF-Public-Goods-Maintenance/scf-public-goods-maintenance.github.io/issues/88
Budget Requested 50000

Project Description

Tansu is a governance and versioning layer for open source projects, built on the Stellar blockchain. It brings transparency, security, and decentralized decision-making to software development by combining on-chain project tracking, a powerful voting platform, and a flexible membership system. It integrates well with the Neural Quorum Governance score making it a great tool for the Stellar community. It is the first platform to offer anonymous voting on Stellar.

Team & Experience

It’s been mostly me, Pamphile Tupui Roy LinkedIn. I am a Pilot and delegate. I have contributed to the Stellar developer documentation, helped with hackathons and participated in multiple Stellar Enhancement Proposals (co-authored SEP-52 and SEP-53). I am also active in the Python sphere, acting as maintainer of SciPy (2M+ daily downloads) and SALib, and serving on the Scientific Python Steering Committee. I know what it means to develop open source solutions, what backward compatibility and maintenance truly mean.

I have been working on Tansu in my free time since around May 2024. I got some help there and there from friends and hired a few people along the years mostly to do frontend related tasks.

Now, I am a Principal Engineer at The Aha Co (GitHub | LinkedIn). We are advising many projects on Stellar as an official integration partner as well as part of the architect program. We are more than 15 devs and still growing strong. Depending on the task, I will leverage 1 to 2 people from the team. Mostly, but not limited:

  • Chad Ostrowski (GitHub, LinkedIn, Discord @chadoh) on the architecutre and general flow.
  • Willem Wyndham (GitHub, LinkedIn, Discord @sirwillem), to review my work on smart contracts.
  • Hugo Heer (GitHub, LinkedIn), a frontend guru.

Retroactive Impact

In Q2 2026, Tansu operated the first SCF Public Goods Award round on its dedicated testnet project. SCF Pilots voted anonymously with NQG-weighted ballots; 17 projects were funded and around $400,000 was disbursed. Write-up: blog, program docs.

Running the round drove several governance features: on-chain conflict-of-interest lists (and management in the dApp), replacement of Soroban Domains with a collateral and unique on-chain names, anonymous and token-weighted voting, outcome-contract hooks, and a malicious-proposal revoke flow.

While the voting was running, some issues around computational cost required by the anonymous setup where identified early enough that no-one was impacted. This also highlighted the need to rework the collateral system during voting.

On the infrastructure side, I had to migrate urgently away from Storacha (IPFS) as they close down their operations. All was migrated to Filebase (with some optional pinning to Pinata in the code.)

I participated in all Drips Waves and a lot of work went into stabilizing features and adding new exciting things: a concept of evidence for SBOM/CVE/attestation CIDs; support for any forge including Radicle; and a linking of Git identity with a G-address. Tansu is now seeing a few contributors coming back and helping out which is a way to increase the pony factor. On that front, the team at Aha is fully onboarded as maintainers.

Past Deliverables

P1: Q2 Public Goods Award on Tansu testnet

Proof of completion:

First PG Award round with anonymous NQG-weighted pilot voting on testnet; 17 projects funded, more than $400,000 disbursed. The work was done as part of a SCF Build Award.

P2: Governance stack

Proof of completion:

  • Conflict of interest: #94, #151
  • Soroban Domains removed and collateral system: #157, blog
  • Anonymous voting, token-weighted ballots, outcome contracts, malicious-proposal flow: governance docs

P3: NQG + scf-membership

Proof of completion:

  • NqgProjectKey and contracts/scf-membership/: #50
  • Viewer: https://scf.pgatlas.xyz https://github.com/Consulting-Manao/scf-member-explorer

P4: Supply chain and evidence

Proof of completion:

  • Unified set_evidence API: #186, tools/evidence/publish.sh
  • SBOM CI and on-chain recording: #145, .github/workflows/sbom.yml`
  • Workflows improvements: .github/workflows

P5: Maintainance

Proof of completion:

Proposed Impact

Q3’s objective is about making Tansu reliable and usable for our first users. The main goals are:

  1. PG Award Q3 on Tansu: same testnet stack as Q2, we are going to run the Q3 program on Tansu and there are lots of things to figure out.

  2. Stellar Registry: this is our second use case, the registry has it’s own set of constraints and we need to see how to effectively support the project.

  3. Governance: there are many things to improve, from the collateral system overall to new features around supply chain. Now that we have the first set of users, we have a better understanding of the scope and what we should do and not.

  4. Maintenance: from the preparation to an audit, the migration to Radicle to many small code adjustments, there is a lot of continuous work.

Conditional: If Nouns Builder on Stellar is funded, coordinate on NQG/Tansu per their roadmap.

Proposed Deliverables

D1: Public Goods Award

Tansu hosts the PG Award program.

Measure: Q3 vote on testnet at https://testnet.tansu.dev/project/?name=stellarpgq3 ; (conditional on SDF) mainnet NFT/NQG populated; mid-grant template shipped or new process proposal documented.

D2: Stellar Registry

Registry Security Council vote on Tansu and further support 3111b944792c0b5da9f6c8f88e52cdeebd1a3d82.

  • registry-tansu-manager factory: authorization contracts governed via Tansu (stellar-registry/contracts);
  • Proposal and outcome templates: registry publish, flag, namespace, etc.
  • Registry name to address: outcome contracts reference registry names; dApp resolves at creation/execution;
  • Contract lifecycle: document register, propose, vote, deploy, version with Tansu in the loop;

Measure: Testnet demo: Tansu vote executes a registry action; templates in dApp; name resolution works.

D3: Governance features

Measure: Evidence on project pages and management in the dApp itself; Nido support with a transparent on-boarding and usage of Tansu; per-project config documented; yes/no approach documented; better management of discussions and other artifacts.

D4: Maintenance, Security and Operations

Measure: UX improved with passkey based account supported, result types consistency documented; TTL strategy documented and applied; runbook published; audit assessment addendum; dependencies up-to-date; Radicle usage with some patches and issues.

Metrics loaded from PG Atlas

PG Atlas 90d Contributors Pony Factor Adoption

  • As the project representative, I agree to the Legal Acknowledgements.

Back to top

This site uses Just the Docs, a documentation theme for Jekyll.