Threshold
Dear Proposer,
Thank you for your proposal. Our second vote on this proposal is AYE.
The Medium Spender track requires 50% quorum and simple majority of non-abstain voters according to our voting policy. This proposal has received five aye and two nay votes from ten members, with two members abstaining. Below is a summary of our members' comments:
The voters expressed a range of opinions on the referendum, with some supporting the initiative as a necessary public good aimed at enhancing privacy within the Polkadot ecosystem. Many acknowledged the project's potential but raised concerns about the lack of clarity regarding funding, repayment mechanisms, and future proposals. While some voters emphasized the need for community adoption and marketing efforts, others called for more detailed financial transparency before proceeding. Overall, there was a consensus on the importance of the project, albeit with significant reservations.
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
I am voting AYE and I am personally supportive of a retroactive funding proposal for the Incognitee app, primarily because the team delivered a working product that I am using and find valuable. It solves a real problem for users who want to decouple token transfers in a privacy-preserving way. Previously, users (including myself) had to mix tokens through CEXs, which is both less convenient and more costly—not to mention the fact that the CEX would still know all your details. On top of that, they seem to have put thought into making their solution compliant with regulation, addressing one of the main concerns critics often raise about privacy tools. The extension to stables prove also to be very valuable especially once they become increasingly important in real-world payments.
In my opinion, this type of privacy solutions are a core use case for second-layer technologies, and this implementation leveraging TEEs offers a practical way to achieve reasonable security. Supporting this retroactively sends a strong and positive signal to other teams: it's possible to build first and be rewarded later. In that sense, Integritee did everything the right way. They've developed a quality product, delivered it before asking for funding, and included a soft-loan mechanism that could allow the Treasury to recoup some of the costs. I think supporting this kind of approach sets the right precedent and shows that the ecosystem values real-world delivery and responsible funding strategies and it is worth for developers to go that path.
I haven’t gone into the full cost structure, but based on utility and delivery alone, this is a strong case. I also encourage others to try the app firsthand—it’s a solid piece of work.
Nye.
In your Full Proposal Document link, I found the Usage Analysis.
The usage number does not look good. It is way too small to provide any valid privacy.
https://assethub-polkadot.subscan.io/transfer?address=14UsSvuFHWMTNhjkHcRt9gw1TogeWzg6zydVsHqK9EXhWHy9&token_category=native&token_category=asset&token_category=foreign_asset&page=1&page_size=25
Just not something I expect for at least year.
I feel it as a very bad sign and doubt the neccessarity of continuing support from treasury.
Hope my comment can warn the team and leads to your prosperity.
PS: No offence, I know integritee is a good porject working on TEE topic.
Edited