Humans are a tribal species which inevitably congregate into groups of people with some minimal sense of shared identity, often based on geography or shared values and goals. As the world becomes more digital, online group membership will increasingly define someone’s reputation and network. As the value of these group relationships increase, the need to govern them and prove membership will also increase.
Tools for managing groups can be implemented as core system contracts on FIO, all connected to and defined by a multisignature ownership of a private FIO Domain. This could also be called a “DAC” (Decentralized Autonomous Community) or “DAO” (Decentralized Autonomous Organization).
Group owners and members of a group. Groups can be anything from a neighborhood, a city, a crypto trading group, a club, or any number of people with a shared goal or identifying characteristic.
What problem of the customer are we trying to solve?
On-chain cryptographic proof of membership in an exclusive group that has no single point of failure. Built in, on-chain governance for the members to elect group admins on a multisig to own a private FIO domain and enforce the verification process for membership in the group and on-going validation of active membership.
Why is it important this problem is solved?
There is currently no easy way for groups to identify their members with an on-chain mechanism that is blockchain-agnostic and provides value to the members (as FIO Addresses do). Private FIO Domains can do this well, but it creates other challenges around how that domain is managed, how ownership of that domain over time can change, and how the group members decide who will act as admins for the group. Without a mechanism to do this, the trust in the private FIO Domain and the exclusive value it creates for the group member identification is diminished.
Note: Please also see the additional benefits section at the end of this document. The Foundation Board has need of very similar features.
How will this product/initiative solve this problem?
By providing group tools for group members to elect admins who, via a set voting period, are added to the multisig control of the account which owns the private FIO Domain, groups can coordinate more effectively, clarify their membership criteria on an ongoing renewal basis, and remove single points of failure for the group. This model includes:
application for membership
member application for admin candidate
member voting for admin candidates
vote processing for admin election
multisig permission adjustment on the domain owner account
a nice interface to represent it all
What KPIs will you track to determine if you are solving this problem?
Number of groups using private FIO Domains to define group membership
Number of FIO group members within a FIO group
In addition (for FIO’s benefit):
Number of FIO Domains registered through this program
Number of FIO Addresses registered through this program
I live in El Valle en Los Prados and have the @elvallelosprados private FIO Domain. If we had a mechanism to verify residency (maybe in partnership with the HOA), we could assign a FIO Address to the residents at the neighborhood domain. This could be a real name like lukestokes@elvallelosprados or a pseudo anonymous name like skywalker@elvallelosprados or somethign random like 12345ABCDEF@elvallelosprados. Upon some agreed upon schedule (annual HOA dues?) residency could be verified. Membership to the DAO would be based on that validation process. “Active” FIO addresses on a private domain managed by a DAO would only be true if they had a current, active membership to the DAO. If someone moves out of the neighborhood, they would still own their self-sovereign NFT FIO Address, but it would be considered “inactive” and only demonstrate they once were a resident of the neighborhood.
I’m a member of the QuakerDAO, a crypto group for UPENN alumnus. We could create a DAC for this group and assign their quakerdao domain to them. I could then have lukestokes@quakerdao to prove I’m a member of the group. I could register as a custodian candidate or vote for existing candidates who would then be elected to manage the account that owns the quakerdao via multisig. If there are any community projects or dues that are needed, the multisig DAO can manage those funds using FIO Requests. Having a FIO Ad @quakerdao
Many gaming communities have very strongly connected players who form guilds and have their own online meeting places, websites, membership dues, and more. Introducing them to crypto currency through the use of a FIO Group might be a successful business development strategy for FIO while providing a useful mechanism for them to keep track of their membership.
The Foundation for Interwallet Operability Board already has needs for a voting system as described here https://fioprotocol.atlassian.net/wiki/spaces/~268441363/pages/15368275 and here https://fioprotocol.atlassian.net/wiki/spaces/DAO/pages/33947824 . If we build this for everyone’s use and not just the Foundation, it can have far more value for the network. Though other solutions may be simpler in the near term for Foundation voting (offchain candidate registration, vote tally from sending funds to specific addresses created for each candidate, etc), they won’t create any additional potential value for the network. Due to the time constraints of the first election, there may not be time to build this FIO Group functionality for the first vote in April.