The problem endorse.fun (Ethereum Endorsement Service) solves

Imagine a place where your social profile is not just a list of skills, but a dynamic, living testament to your contributions, backed by real people. That’s endorse.fun. Here, your endorsements are more than words—they're on-chain attestations, transparent and verifiable, with the option to tip, showing support for your work.

With endorse.fun, you build your reputation in a Web3-native way. This is not like traditional LinkedIn endorsements; it’s about enhanced transparency and portability. By participating, you help create a social graph and reputation layer for Web3, offering numerous benefits:

-Recognizing and Rewarding Web3 Contributors: Easily find and reward meaningful contributors in the Web3 space. Imagine discovering developers endorsed by top Web3 founders!

-Honoring Early Supporters: See clearly who your earliest and biggest supporters are, celebrating those who believed in you from the start.

-Leaderboard Highlights: Weekly and monthly leaderboards showcase and reward the most active endorsers and rising Web3 stars, motivating the community.

-Custom Algorithms for Social Insights: By building the social graph, you can identify top developers, artists, and more, and filter social posts on platforms like Farcaster and Lens.

-Earning Money and Reputation: Establish a system where individuals or groups can earn money and build a reputation, fostering a dynamic flow of support and recognition.

Join endorse.fun and be part of a community where your contributions are recognized, endorsed, and celebrated in a transparent, meaningful way.

Challenges we ran into

We encountered two challenges worth mentioning.

• The first challenge is related to the Airstack API, which we use for Social profile discovery (ENS, Farcaster, Lens). The API gives all addresses of a specific social identity that was searched for. This means, it also gives the custodial Farcaster user address and non-evm addresses connected to the Farcaster account (Solana). One of our requirements here was, to limit the endorsements and donations to addresses owned by the user (non-custodial). To achieve this, we are resolving the user address in the following order:
  1. We use the ENS address if available.
  2. We use the Lens address if available.
  3. We filter out all non-evm and Farcaster custodial addresses and use the first connected address that is still left. The reasoning behind this is, that we assume the user is in possession of all the accounts he has connected to his Farcaster account.
• The second challenge is related to performance, UX and API key security. To optimize the load times, reduce server load and secure our external services API keys, we used React server components inside Next.js together with caching fetch query requests. Established social profiles do not change often, so we use a revalidation time of 1 day for these requests. For querying our subgraphs on The Graph Network, we use a revalidation time of a 1 minute, so we don't serve old/stale data to the users. We will adjust these values as we gather more data points and user feedback.