Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2025 Stellar Development Foundation
Subscribe to the Newsletter
By Tansu - Soroban Versioning
Bring decentralization back to Version control System with Soroban providing transparency, integrity and security.
After a successful POC phase. Tansu is starting to show our vision and can be played with on Testnet.
We have an ambitious proposal for the Build award. Besides the road to mainnet and real adoption, we have two objectives:
Projects will have access to their own Decentralized Autonomous Organization (DAO). The community of a project will be able to vote on new features or organizational changes. There are several SCF open source projects we might be able to leverage. The project will have a wallet and the DAO will be used to control the funds allocation. There are going to be mainly two pools. The first pool is dedicated to developers. Funds will be automatically distributed to active maintainers based on specific criteria. The rest of the funds would be managed by the DAO for other purposes such as compensating non-developers, infrastructure costs, or even organizing events. The use of a complex system of redistributions typically used in web3 projects, such as Quadratic Funding (QF), will be evaluated.
Tools will be implemented to add/remove maintainers programmatically based on the on-chain status of the project. To that end, we are already leveraging Soroban Domains and will continue to do so and see how we can extend our partnership. Discussions are in progress to get a standard around metadata for instance.
Other personas will be added on-chain as to give other responsibilities. This will further increase projects' transparency and give all participants some visibility.
Release process on-chain. From triggering the release to registering it.
Add a level of trust per hash. Combining time based rules with additional factors such as voting from maintainers, to mark specific hashes as more trusted: this introduces a finality concept and enables consumers of the contract to use specific trust levels depending on their own risk profile. We will evaluate the possibility to combine this concept with an automatic update of the hash. This would allow a fully trustless mode of operation. Linked to that, we will add tools to reject a hash. As maintainers can get compromised, it is important to have means to indicate that a project and person is compromised.
Finally, users will be able to subscribe to projects to get news about new trusted releases, security related issues and DAO events.
Behind projects, we have people. We want to add profiles for people registered on-chain and recognise their contributions. We will leverage the solution from Trustful and build yet another sustainable partnership between SCF projects.
Badges are not vanity tokens. They will play an essential role in defining permissions on the protocol. Linked to the DAO, badges will reflect the level of trust the community has in someone.
Yes
$99.4K
Besides completing the tranches, the success of our project will primarily be measured by the number of open-source projects registered. Moving past registrations, we will look at how often on-chain data is updated and how our dApp is used. Note that we will never use any invasive tracking solution on the dApp and only GDPR compliant solutions will be considered.
On the community side, we hope that Tansu will enable more decentralized communities of developers to exist. Ultimatly, we wish for the whole development lifecycle to happen in a decentralized way, outside of solutions like GitHub.
Last but not least, if our project can successfully detect a security incident and warn users effectively, it would be a huge win.
As a public good project, we don't yet have concrete monetisation plans. At that point we are more interested into providing monetisation tools to support the projects on our platform. The Support button will allows people to show their support in XLM to a project and if they wish, give a tip to the platform. Monthly options will also be made available and could generate a constant revenue stream.
As we add new features, driven by community feedback, we might add more enterprise oriented features. At that point we are thinking about adding some fees to specific contract calls and features in the dApp itself.
Regardless of a hypothetical monetization, we have a strong commitment toward open-source and our code will remain public. We will ensure that there is a great documentation so that anyone can freely Quickstart our infrastructure and build on top of it as they wish. Consulting Manao GmbH, our company, will also be open for consulting services on Tansu and related technologies.
Pamphile presented Tansu to a "community call of the mind" where it was well received. People have also been engaging positively on our project page. We started a collaboration with the Trustful team. And we have been interacting with the Soroban Domains team to propose a specification for an Ersatz of a SEP1 file.
Besides these public communications, Pamphile also interacted with prominent members of the Stellar community and they shared their enthusiasm.
Tansu is just starting on testnet and we just kicked of the public communication phase as we have something people can actually use now. We hope that in the following weeks we will get more traction.
The planning outlined below, and in the other tranches, assumes an average level of effort of 15 per week per person for a total duration of 6 months making it sustainable in terms of development engagement for all parties. For simplicity, the start of the tranche is represented as W1-for Week 1. While the developers have some affinity, backend/frontend/contract, all developers will be involved on all aspects of the proposal.
We expect to deliver a MVP within 2 months.
Consulting Manao's mission is to supports open-source software by provide consulting services around open-source
solutions. It has worked with various organizations such as NASA ROSES, CZI, NumFOCUS, SimDec and
Quansight. And suported the work of Pamphile T. Roy for 3 years on the following activities: SciPy core maintainer;
SciPy's Contributor Experience Lead; SALib's core maintainer; Member of Scientific Python Ecosystem's Steering
Committee; Member of NumFOCUS' Security Committee; Co-chair of NumFOCUS' Small Development Grant
Committee; Co-lead of x2 CZI grants (EOSS5-0000000176 and EOSS-DI-0000000031); Investigator on several
grants: AMD, NumFOCUS, NASA ROSES.
Tupui
By Tansu - Soroban Versioning
Tansu - Soroban Versioning