Future Plans
Benefits of being early
We plan to provide various goodies to incentivize joining the network early:
Special Discord roles
OG passes
Higher weights for .frens scores
Websites supporting the .frens network
At the moment, the protocol is supported by Ordbit. They plan to provide other interested parties API access to display the .frens network.
Higher level connections
Besides only relaying on directly trusted addresses, second level addresses (trusted addresses of your trusted addresses) can enable larger network effects.
Searching for friends
Rather than saving your friends addresses in a spreadsheet, we aim to connect to existing social Ordinal/Bitcoin providers like ord.io to find your friends and their main addresses.
Re-Inscriptions
Using the same sat to update/delete your .frens ID via re-inscriptions. This makes a lot of sense because it, first, saves some postage and, secondly, seems in general the more elegant way to handle multiple inscriptions belonging to the same entity.
Rare Sats
Real ordinals connoisseurs may want to deploy their .frens IDs on a special sat. We feel you! Ideally, you combine a rare sat with re-inscriptions.
Integrating .sats Names
A natural integration will be with .sats names. We highly suggest to add your primary sats name (that you plan to hodl) in the notes.
Inscribing from your ord wallet
We plan to cover .frens inscriptions from community members running their own node.
Weights
Weighing should make the social graph more informative and reliable. To reduce the computational burden, the weights only need to be re-calibrated every 100 blocks for instance.
Weighting parameters:
Addresses that are referenced more often receive a higher weight. This parameter fosters active participation in the Ordinals/Bitcoin space.
Addresses that were deploying a .frens ID earlier, earn a higher weight. This provides an incentive to participate early on.
Addresses receive a larger weight the longer they have been included in a .frens ID. This encourages long-term connections.
Addresses that hold more inscriptions receive a higher weight. An address that only holds one .frens ID but no further inscriptions would have a negligible (zero) weight. This minimizes the impact of multiple wallets to inflate the overall ranking.
Reciprocity is a bonus (you include an address to your .frens ID, and this address inscribes a .frens ID including your address as well). This value real connections rather than admiring some popular community members ("ordfluencers").
Addresses ranked higher in individual .frens IDs receive a higher weight. This prevents mass connections to inflate ranking. The decreasing weight for additional addresses should also minimize the incentive to add too many addresses
For instance in case of parameter 6., address i receives the following weight:
with:
rank: first address has rank 0, second address has rank 1, ... the n-th address has rank n-1
n: number of addresses in the deploy (or most recent update) inscription
Governance
Once established, the community should have a role in governing the protocol in the long run. There are two reasonable approaches:
Regular snapshots of wallets with a verified .frens ID
A (BRC-20) token drop to all wallets with a valid .frens ID after some build-up phase
The second option may create more hype and faster adoption but is also prone to adverse side effects (like creating several .frens IDs with different wallets).
Note that there is NO short-term plan to drop a BRC-20 token at the moment.
In the very, very long term, the power to change the protocol should be handed over to an Ordinal-governed DAO.
Last updated