Tansu for developer communities
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:
- Offer a decentralized platform for developers to maintain and interact with projects;
- Add an emphasis on people behind projects through the use of reputation badges.
Decentralized organization
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.
The people behind the code
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.
