UIP-006: Dropping the Effective Number from 3 to 1
Abstract
Right now, the number of vouches required to become a Union member is 3. This requirement is called the “effective number.” This proposal will change the effective number from 3 to 1. It’s important for protocol health for the global average number of edges per node to be >1. With this proposal we plan to drop the hard requirement to 1 and monitor where the actual averages end up.
Motivation
The goal of changing the effective number is to facilitate user interaction with the protocol. Dropping the effective number affects two aspects of user interaction: onboarding and follow-through.
- Streamline onboarding: Dropping the effective number to 1 allows for current members to onboard their community members quickly, and promotes local network growth.
- Increase membership follow-through: A current issue with the effective number being 3 is that if someone is missing one or two of the vouches required to become a member, they are less likely to follow through on membership completion. This problem also gates people from vouching for others. Reducing the amount of vouches required to become a member will result in a higher rate of membership completion.
Specification
Change the ‘effectiveNumber’ in SumOfTrust from ‘3’ to ‘1’.
Backwards Compatibility
Existing Union members with 3 or more vouches should still work as previously.
Test Cases
Tests and simulations can be found here: Link to PR
Implementation
Set the ‘effectiveNumber’ of SumOfTrust to ‘1’ by calling ‘SumOfTrust.setEffectiveNumber(1)’ Link to PR: https://github.com/unioncredit/UIPs/pull/12
Security Considerations
One of the implications is that if only one member is vouching for you, and someone else is borrowing against that person’s vouch, your total amount of available credit could go down to 0. The possibility of a member’s available credit being dependent on only one credit provider should encourage the user to onboard more members as underwriters, and incentivize users to not rely on a sole credit provider.
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
0xCbD1...65beEb | 100M | FOR |
0xBABE...c97438 | 10M | FOR |
0x7a0C...022Be4 | 8M | FOR |
0x0C38...1CE763 | 9,341 | FOR |
0xEDDd...30f90a | 318 | FOR |
VOTE POWER
Proposal Status
- Published Onchain
0xCbD1...65beEb
- Wed July 20 2022, 04:16 amVoting Period Starts
- Sat July 23 2022, 05:32 amEnd Voting Period
- Sat July 23 2022, 07:10 amQueue Proposal
- Mon July 25 2022, 06:54 amExecute Proposal
Current Results
1-FOR
118.01M
2-AGAINST
N/A Tokens
3-ABSTAIN
N/A Tokens
