You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What we have
We currently have a JS wallet on our app. It stores keys, signs transactions and have a locking mechanism that allows users to interact with EOS.
Proposal
We are lacking one basic feature that most wallets have. The ability to use eosio.msig contract to propose changes to accounts that require multiple signatures. This doesn't require alterations into our smart contracts but it does require our wallet to be able to interact with multi sig capabilities of EOSIO
Why
This will allow us to move away from having the concept of an admin account. Instead we will be able to allow multiple people with different voting weights to configure and use the community settings. This will bring decentralized capabilities with greater collaboration and transparency of changes.
With this set on place we can:
Show all the proposals made to change the community. New community name? New min_balance setting? all that could be recorded along with the real account votes
Allow people to earn voting rights on important decisions that rely only on the admin for now. Like vote for a creation of a new objetive
Allow us to track most active admin users
Allow more voting weight to be added to new users, without ever having to add this abstraction in our contracts
This is a common feature on EOS, original from version 1.0, and yet we haven't implemented this
How
Needs research, but it will require a few screens to interact with the eosio.msig contract
Additional context
Articles and Resources on the topic:
Instead we will be able to allow multiple people with different voting weights to configure and use the community settings. This will bring decentralized capabilities with greater collaboration and transparency of changes.
Wow, that sounds really nice! It feels very aligned with our values and the voting feature we've been talking about for CMBGO
it is bro, a new take on how we approach administration stuff, and its fully compatible to what we have, just add one more layer to what we already have. I'm happy that we are finally reaching that level of product maturity!
What we have
We currently have a JS wallet on our app. It stores keys, signs transactions and have a locking mechanism that allows users to interact with EOS.
Proposal
We are lacking one basic feature that most wallets have. The ability to use
eosio.msig
contract to propose changes to accounts that require multiple signatures. This doesn't require alterations into our smart contracts but it does require our wallet to be able to interact with multi sig capabilities of EOSIOWhy
This will allow us to move away from having the concept of an admin account. Instead we will be able to allow multiple people with different voting weights to configure and use the community settings. This will bring decentralized capabilities with greater collaboration and transparency of changes.
With this set on place we can:
This is a common feature on EOS, original from version 1.0, and yet we haven't implemented this
How
Needs research, but it will require a few screens to interact with the
eosio.msig
contractAdditional context
Articles and Resources on the topic:
The text was updated successfully, but these errors were encountered: