🪼 Treasury Flow Application#65
Conversation
|
Hey! Expect our first round of feedback in the next week or two, and we’ll let you know what comes next. Fingers crossed you’ll ace every step and officially become part of the ink!ubator family! 🤞 In the meantime, if you have any questions, feel free to reach out. Thanks again for applying, and we’ll be in touch soon! 🚀 Best, |
al3mart
left a comment
al3mart
left a comment
There was a problem hiding this comment.
Hey @niklasp, thanks for the application!
I would be curious to know whether the existing precompile exposing pallet-assets as an ERC20 would suffice to cover your needs for your use case.
You can see the precompile here: paritytech/polkadot-sdk#8554
|
|
||
| > - What your project is _not_ or will _not_ provide or implement | ||
|
|
||
| - fungibles apis for smart contracts (we rely on |
There was a problem hiding this comment.
Would precompiles in Asset Hub suffice to cover your needs ?
I'm thinking if this app might be better exist deployed in AssetHub rather than in Pop Network. That should give it a more direct access to the treasury which might provide a smoother experience overall.
There was a problem hiding this comment.
Not having worked with it yet from what I know from this forum post I assume that pallet assets precompile would work and I will take that path. I also agree AssetHub is a better home for the contract.
There was a problem hiding this comment.
Alright! I have a similar belief that the provided precompiles shouldn't block your project.
There was a problem hiding this comment.
Should I change the description of the project accordingly or does this conversation suffice?
There was a problem hiding this comment.
Should I change the description of the project accordingly
Yes please
semuelle
left a comment
semuelle
left a comment
There was a problem hiding this comment.
Thanks for the updates. Happy to support this. I think the total FTEs should be 1.3125, but tbh the price seems fair either way.
| | **0d.** | Docker | We will provide a Dockerfile that sets up a complete frontend + contract environment for compiling, testing and interacting with the treasury flow contract and includes all changes made in Milestone 2 | | ||
| | 0e. | Article | We will publish an **article** on Medium or X that explains all features of the frontend application and smart contract functionality as well as how it could be used in existing tresuries. | | ||
| | 1. | User Feedback | We will prepare a form to collect user feedback and incentivize participation in order to find missing functionality and UX issues | | ||
| | 2a. | Contract Optimizations | After the audit, we will implement all proposed changes and focus on optimizing storage and contract upgradability | |
There was a problem hiding this comment.
Just clarifying that we don't actually have an auditor track (and hence no audits) for this cohort.
Apologies if this wasn't clear at the time you applied.
There was a problem hiding this comment.
Thank you for the comment. What would you estimate as a realistic cost of a simple audit? Or how would you approach that? The goal of the application is a treasury management where naturally many tokens will be stored and controlled so a safe contract would be very important. But I can also imagine moving auditing and optimization into a later stage, after we confirmed that people are actually using the app. Nonetheless I would direct funds to optimizing the contract for gas and security.
There was a problem hiding this comment.
This use case requires the audit prior to its production deployment, there's no doubt on that. Or at least it would provided a more robust case for its users.
However, I believe there are other initiatives in the ecosystem focused on providing ecosystem projects support with audits. Such as:
With that in mind maybe it would make more sense to explicitly include a bullet point referencing the usage of these ecosystem tools to cover the audit. We might be able to assist with introductions / conversations if needed.
Other than that, I'm quite happy with the proposal.
There was a problem hiding this comment.
I've addressed your feedback. Please take a look and let me know if it looks good.
|
I also found project with similarities which I added as a reference in 8605b5c |
|
The treasury proposal looks great! I like the use case. I just have some questions: (1) Did you see that we updated the guidelines for this cohort? Specifically: 
We added this for the second cohort to make it more visible to the wider community what is happening. (2) For the production deployment on AssetHub, do you perhaps already know someone that could use it? (3) Are you up for creating a YouTube walkthrough on how to set the treasury up? I think that would make it a bit more accessible for people attempting to use it. |
|
hey @cmichi, thank you for the comment (1) yes totally, thats why I have medium article in Milestone 2. And as this is a requirement I will also create a forum post. Do you have guidelines for that? Also added video walkthrough to the .md (2) Yes, WagMedia is interested. They do micro transactions of several DOT for content creators, as well as monthly salaries to directors. Have only spoken briefly to other DAOs and bounties (e.g. TheKus, UXBounty). I think there is need but it would require some BD as soon as finished. I am interested in really building a useful application and will surely reach out to different parties and. (3) see 1 |
cmichi
left a comment
cmichi
left a comment
There was a problem hiding this comment.
I'm happy to approve this application! Looking forward to it 😊 .
|
Congratulations! We are thrilled to officially welcome you to the Ink!ubator 2.0 program!! We can't wait to see the remarkable contributions you'll bring to the ecosystem. If you have any questions, concerns, or if you just want to brainstorm ideas, don't hesitate to reach out to us! As you join the Ink!ubator family, please remember that you are not alone on this journey. We are here to support you every step of the way. We believe in your potential and we can't wait to see where this journey takes us all. Congratulations once again and welcome aboard! |
|
Thank you very much. You will hear from me soon in a forum post detailing the project + roadmap |
|
I am reposting an update from a telegram discussion to inform all involves members about a delay in delivery: I am sorry to inform you that we have fallen back behind our planed schedule with the Treasury Flow application. Due to personal reasons and our current focus on different other ecosystem projects we are ~2.5 months late. That said we would still very much to continue our work that we already started. Continuing in October we would love to finish M1 until end of December / early January if you still want to give us the opportunity. But if there is other promising projects, we of course understand if you pass our grant to the next team |
|
Hi @niklasp |
|
@davidsemakula you mean separating frontend from contract? building contract first? |
Yes, exactly! |
|
Hey there! Please let me know when are you planning to deliver the Milestones Feel free to reach out to me via Telegram: @Toma_Cpp |
|
Hey @TtomaS7 sorry for taking a while to reply. With the current situation in Polkadot we do not think that the development of TreasuryFlow would bring any value to the Polkadot ecosystem and will not continue with the development. Happy if you find someone who can use the freed funds to develop something meaningful that can bring long term value to Polkadot and improve ink. Thank you for the support and trust in our application that far and sorry for having to cancel this. |
6 participants
This PR introduces our proposal for creating a treasury management smart contract with ink!v6 and a management react frontend.
We would love to hear your feedback on this application.