EFP’s core reusable mechanism is the portable list: an NFT-addressed list of account relationships that other apps can interpret without owning the user interface.
The most important analytic detail is the split between Owner, Manager, and User. This turns a simple “follow list” into an authority system where custody, edit power, and represented identity can diverge.
EFP separates the list NFT from the List Storage Location, which means the canonical relationship object can point to different execution/storage environments over time.
Primary Lists are the real graph-forming surface. The protocol does not treat every list equally; follower counts and the social graph derive only from lists explicitly marked primary and matched to the intended user.
Tags such as block, mute, and top8 show that EFP is not only about positive follows. It is also a portable preference and moderation primitive.
The List Records docs are intentionally conservative: just version + record type + data bytes, with only address records enabled now. That narrow base keeps the primitive legible while still leaving room for richer future record types.
Specific source signals worth retaining
Intro docs: best high-level explanation of the EFP List NFT, roles, list storage location, primary lists, and how followers/following are computed.
Roles docs: strongest statement that Owner control over storage location is the most security-critical authority.
List Records docs: important because they show how open-ended the protocol could become while also warning that clients must validate arbitrary manager-supplied record data.
List Metadata docs: useful for understanding how Manager and User roles are actually stored and read onchain.
GitHub org / app / docs repos: confirm that EFP is being developed as an ecosystem primitive rather than as a closed social product.
Why this entry belongs in the corpus
It adds a strong social-graph / identity-stack primitive to the corpus and helps bridge wallet identity, account relationships, and downstream ranking systems.
It pairs well with OpenRank because EFP can supply portable graph data while OpenRank-style systems can compute recommendations or trust scores over graphs like these.
The reusable insight is that social protocols centralize less around the visible feed and more around hidden authority surfaces: who owns the list object, who edits it, how storage is pointed, which list counts as primary, and how clients interpret tags.