#239 InvArch Tinkernet - Funding for a Multi-Signature Solution
The InvArch Network team seeks to provide the ecosystem with a new multi-signature solution, named Saturn, available to every parachain & implementable throughout any dApp on those parachains. This multi-signature solution will be made so that it can be easily adopted by existing wallets in the ecosystem & be immediately implemented to provide a superior multi-signature solution to the Dotsama ecosystem compared to external solutions such as Gnosis Safe.
Multi-party ownership solutions are the core of nearly every project being developed by the InvArch Network team, which has heavily influenced the design of the network’s infrastructure. While sharing our proposed multi-signature implementation with other builders & community members throughout the ecosystem, we have received tremendous interest & support. We also had a meeting with a member (Ricardo) from Parity Technologies in the past regarding our solution and received positive feedback on its capabilities.
The current multi-signature implementations available for builders in the ecosystem either rely on the current implementation used in the original multi-sig Pallet developed by Parity (which is limiting) or by developing their own custom solutions (which is time-consuming & costly). The ecosystem also lacks account-recovery capabilities & the ability to onboard & off-board new members of a multi-signature implementation. This is a very restricting problem, with concerns being shared across the Kusama community. We would like to change this current reality.
What we are proposing to build for the ecosystem is designed to service the entirety of Kusama & its parachains. We are providing it in a way that individuals will never need to purchase TNKR (optional, though) & can use KSM. This is an open-source solution for Kusama and a solution that we truly believe will be a big boost for the ecosystem. We are confident that if trusted by the community to deliver this solution, Kusama will go from having one of the worst multi-sig experiences in Web3 to one of the best, if not the best. Public interest in the potential for our multi-sig has been shared by the community in the past, and we would be extremely grateful if the community will signal their support for us to build this for Kusama.
Show More
anthony_rixThe team creates powerful, innovative products. Actively develops web3
sergogo97I'm a long-time ambassador of the project and I really want to see the launch as soon as possible. After all, we've done a cool and great job for it! :3
Much needed, the current multisig pallets are not ideal IMO and we need a better solution for the substrate side of the ecosystem. Voting Aye
Usable multi-signature solutions are nice :) But if I understand correctly people would be limited to use it though InvArch? are there plans to work together with other parachains to integrate the technology? isn't a bit optimistic to expect people to move their Kusama activity to your chain just because you are going to add support for KSM?
The really powerful thing about Saturn is that its use wouldn't be limited through the InvArch Tinkernet. Using XCM, we are able to act as a Service Parachain for the ecosystem. Rather than limiting what we provide as exclusive features on our chain, we empower Kusama & its parachains by extending these features to them; almost as if they were native features & functions on those chains.
Quoting Gabe here:
Ownership is handled in TInkernet, it's easier to compare them to collectives, except they can be created similarly to how you create an NFT collection instead of predefined in the runtime. Multisig IDs are assigned from an incremental integer and addresses are derived from that integer (plus a fixed hash so it doesn't conflict with anything else).
The addresses in the XCM connected parachains are derived in their runtime, either with their own derive function or with the same function we use (which then gives the account in the other chain the same address as the account in Tinkernet). The virtual account is akin to smart contract virtual accounts, but with the ID instead of the contract code being used for the derivation.
This was in response to a question from our discussion post, the thread can be found here.
We are optimistic that teams throughout the ecosystem will support our multi-sig solution; however, stakeholders will not need to move their activity off Kusama. We've already spoken to ecosystem wallet teams regarding the ability to support the Saturn SDK through their user interfaces and can attest that this support will happen.
While we will be reaching out to certain Kusama parachain teams who are interested in testing out the power of Saturn, I believe the most important aspect here is to build a solid solution & prove its value on Kusama. Given the chance to prove its potential, then adoption can increase & I anticipate seeing Saturn adopted by other chains, all it takes is an HRMP channel & a little dev work. Then stakeholders on other Kusama parachains can experience Saturn on those chains, either through dApp interfaces or ecosystem wallets.
The ability to pay fees using KSM is designed to make the initial process of setting up a Saturn multi-sig seamless & to ensure that what we are building is as genuinely designed in the interest of Kusama network stakeholders & provides a fluid experience where KSM is all that is needed.
arxangelsantaI can provide a unique opportunity and connect your project management with funds and DAO from the Aptos blockchain. Together we can come up with a unique thread and be mutually beneficial to each other. If the offer is interesting, please send me an email to arxangel31161@gmail.com. because it is impossible to reach you through the project.
Hello team,
Your treasury proposal was approved and funded more than 3 months ago. Could you please take the time to share an update on your progress with the Community by posting a comment in this referendum post?
Please keep in mind that, as part of treasury proposals’ lifecycle, a final report is due at the completion of all milestones to evaluate the success of the initiative. You can find a template for the treasury proposal report here.
Thank you for your consideration.
Hello Team,
Just a reminder to share your latest update(s) with the community on the referendum post for the record and future reference.
Thanks.
Hello everyone!
I am happy to share our report on this proposal.
We submitted our proposal for the creation of the Saturn Multisig & SDK, and successfully delivered on all of our outlined deliverables in the proposal. There was a bit of a budget shortfall, but we managed. In the end, Saturn has become a widely anticipated solution & product for the ecosystem.
We proposed, we promised, and we delivered. Thank you again to everybody who supported us & helped to make the creation of Saturn become a reality. Now, the ecosystem has the infrastructure to realize the best-in-class multisig experiences in the industry!
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist
Discover similar proposals
