Polkassembly Logo

Head 1
Head 3
Head 4
Head 2
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Medium Spender
Requested:41.94K DOT
Rejected

Polkasafe - Milestone 2 - Retroactive funding proposal

15Un2...qosB4

inMedium Spender
2 years ago
multisig
retroactive
BeneficiaryBeneficiary:

15Un2...qosB4

(41.94K DOT)

image

About Polkasafe
PolkaSafe is a business tool built on top of substrate’s multisig pallet, designed to provide a seamless user experience and robust security features for managing assets on the Polkadot ecosystem. Inspired by some of the best multisig wallets available in the Ethereum ecosystem, we have created a product that offers a comprehensive set of tools and features to ensure the safe and efficient management of your assets on the Polkadot network.

Why did we build Polkasafe?
Effective treasury management is essential for ensuring the financial stability and sustainability of any organization, fostering enhanced operational transparency, and facilitating prudent fund management with significantly diminished risk. The emergence of cryptocurrencies has catalyzed the evolution of an innovative, alternative financial ecosystem, distinct from traditional systems that have historically underserved a considerable segment of the global population.
Organizations today often utilize multiple cryptocurrencies for conducting transactions, both inbound and outbound. However, they currently face a dearth of sophisticated tools that empower them to efficiently manage their treasuries across various chains and multisig wallets. This challenge necessitates the development of innovative, practical solutions that coalesce disparate books spanning multiple blockchain networks and wallets into a unified organizational system.
PolkaSafe endeavors to address this critical need by offering organizations a comprehensive suite of advanced, user-friendly solutions that harmonize their treasury management processes across multiple chains, including Polkadot, Kusama, and their respective parachains. By amalgamating diverse blockchain networks and multisig wallets into a singular, cohesive platform, PolkaSafe paves the way for a more streamlined, efficient, and secure approach to digital asset management, thereby empowering organizations to navigate the complexities of the rapidly evolving crypto-financial landscape with confidence and dexterity.

Polkasafe <> Polkassembly
Polkasafe team joined hands with Polkassembly to work together to create House of Commons.
Polkassembly team had been mentoring the Polkasafe team from their inception. But as the Polkasafe team struggled to complete the project on time, we at Polkassembly, extended our hand, welcoming Polkasafe team members to join the Polkassembly team and build this product together, laying the foundations of the House of Commons.

Milestone/Proposal 1 update
Polkasafe’s first treasury proposal was made in October’22 in Kusama. The idea was to build a comprehensive product solving for all potential use cases of multisig within the ecosystem.
All tasks were completed and detailed list can be found in the original proposal here.

Development beyond proposal 1 milestones:
Milestone 2
(Completed)

The first proposal and its milestones focussed on building a good product with a great UX. We achieved that, but went beyond to make the product 10x better. Let’s see the tasks we have completed and features we support now:

  1. Link multisig
    -- Just connect your wallet and we fetch and show all multisigs associated with that wallet, for you to choose and link with ease.

  2. Proxy Support
    -- Allow users to easily set proxy for multisig wallet
    -- Introduce checks and nudges if proxy is not set
    -- Allow users to add and remove signatories in 2 steps using proxy

  3. Additional network support(SDK & App)
    -- Polkasafe now supports Polkadot, Kusama, Asset Hubs on Kusama & Polkadot, Rococo & Westend.
    -- The app also supports other networks like Astar & Aleph Zero but work done for them is out of scope for this document.

  4. Custom Call data transactions
    -- Create a transaction using custom call data and still benefit from easy signing, notifications to signers, transaction notes, etc.

  5. Create extrinsic and sign as multi
    -- Want to create a complex, custom transaction? No need to go to Polkadot.js to do it. Just use Polkasafe and create any transaction to be signed as multi.

  6. Address category and additional info
    -- Users can now store additional information about signatories like discord, telegram, email
    -- Wallet Addresses can be categorized with tags like - Product, Full-Time, Marketing, etc.

  7. Transaction Tags and additional metadata
    -- Create settings page for Creation & Management of categories
    -- Allow user to add transaction categories and sub-fields when creating transaction
    -- Display relevant data to all signatories in Queue, History and Notifications

  8. Notification bots
    -- In-app notifications are usually best suited for Mobile apps, hence we had the need to develop notification solutions beyond in-app
    -- Discord, Telegram, Element & Slack bots allow you to set up any preferred channel for notifications and make your multisig experience 80% more effective.
    -- Email alerts

  9. Multi-currency support -
    -- Signatories can often be from/in different parts of the world and they would prefer to see treasury details in their native currency value, hence we added support for 10 different global currencies, allowing each user to have a more personalized experience.
    -- Supported currencies are - USD, GBP, EUR, CHF. AED, JPY, AUD, CAD, INR

  10. Shared Address Book -
    -- Based on community suggestions we built a shared address-book for seamless experience for all signatories of any multisig account.
    -- Users can also add new addresses and save them privately.
    -- Shared addresses can also have a private nickname(visible only to the signatory who sets it)

  11. Extend SDK support for all new features like custom transactions, call data signing, batch transactions and more.

  12. Transaction Batching(Bulk payouts)
    -- Users can make bulk-payments to multiple addresses in one single transaction
    -- Users will be able to add category and transaction tags, making it easier for other signatories to review and sign the transaction
    -- Use cases include salary payments, reimbursements, grants, airdrop, etc.

  13. Apps
    -- Apps are an attempt at increasing multisig usage within the ecosystem by enabling developers to add multisig support to their dApps.
    -- Current apps - Subsocial, Polkassembly, Astar Staking dashboard
    -- Upcoming - (In discussion) -Stellaswap

  14. Polkassembly app
    -- Polkassembly app was a deep integration done with the Polkassembly product enabling multisig usage within the product
    -- Sign-in with Polkasafe
    -- This sets it as a standard for anyone trying to use the Polkasafe SDK for enabling multisig sign-in in their app.
    -- Vote with Multisig
    -- Users can cast a vote on any proposal with their Polkasafe account, using any of the ecosystem wallets.
    -- Other signatories will get a notification on their preferred channel(Discord, Telegram, Slack, Element), requesting them to sign and execute the transaction.
    -- All this data is available to all signatories in Polkasafe, with complete proposal context and Polkassembly links, to understand the details of the transaction they are signing.

  15. Videos for tutorials
    -- Multiple videos have been made by the team explaining each feature of the product and helping users to understand and use Multisigs in the Polkadot ecosystem. You can find them here and the videos have been linked to specific product sections in the docs as well.

  16. SDK Docs
    -- Comprehensive documentation has been done for SDK and is available here.
    -- This has helped developers extensively while they integrate the Polkasafe SDK to bring Polkadot’s multisig functionality to their dApp.

  17. 2FA login
    -- Polkasafe now supports 2FA for your accounts, making it even more secure to use 🔐

We would like the community to share product feedback and feature requests with us here in this discussion post or reach out to us on hello@polkasafe.xyz

Milestone 2 proposal has been created retroactively after completion of all tasks and Milestone 3 defines our roadmap for the product and we look forward to making Polkasafe the most-versatile multisig solution in the entire Polkadot ecosystem, enabling safe, secure self-custody of assets, and create a dApp ecosystem that supports multisig wallets using the Polkasafe SDK.

Detailed proposal, task list, and budget details can be found here.

Proponent - 15Un2AyaqUa46UvCkzAsijBy6dwyrCiF7rkVyKnT6WZqosB4

Requested allocation - 194,050 USD

Website: https://polkasafe.xyz

Twitter: https://twitter.com/PolkaSafe

Docs: https://docs.polkasafe.xyz/

SDK: https://github.com/polkasafe/polkasafe-sdk

SDK Docs: https://polkasafe.gitbook.io/polkasafe-sdk/

Github: https://github.com/polkasafe/polkasafe-ui

Thankyou,

Regards.

Polkasafe Team

Comments (7)

13h2U...e6Nn9

2 years ago

I truly appreciate the value that Polkasafe brings to the Polkadot ecosystem, especially at this moment of our need. We manage multiple multisigs right now and i have had to struggle with pjs for far too long unfortunately. I think we can all agree that Polkadot needs UX solutions like Polkasafe desperately.

I think Multix is doing some cool stuff especially with the speed and "clicky-ness" of their product but the UX, mainly the inability to hold any other data on top of what pjs already does and us having to communicate internally about every transaction is a down-turner for me, and it just didn't feel as polished, on testing the product we found a bug where if you send funds from the "manual extrinsic" feature, it sends a different amount than what I input in the field (please fix this @tbaut)

We support the proposal and wish the team the very best.

14DsL...yxGDP

2 years ago

We should encourage project teams to apply for retroactive funding for the work has been done and evaluate the proposal based on the delivered work. This reduces the risk and cost of the tresury.

In this case, we have a working product that solves many issues for multisig users. I believe this is the kind of software development project that the treasury should support.

Load more comments
PleaseLogin to comment

Confirmation Period

3

of 3

Decision Period

28 / 28 days

Confirmation Period

0 / 4 days

Summary

0%

Aye

AyeNay

0%

Nay

Aye (71)0.0 DOT

Support0.0 DOT

Nay (84)0.0 DOT

Voting Data

Approval%

Support%

Threshold0.00%

Threshold0.00%

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy