[RFC] Fluidkey Distribution of SUMR Tokens

1. Summary:

This RFC proposes exploring a small-scale SUMR distribution campaign via Fluidkey score, leveraging the recent integration with the Lazy Summer Protocol in their optimized auto-earn feature, their privacy-preserving account system and active user base. The initiative could serve both as a marketing pilot and a way to increase SUMR visibility as token transferability approaches.


2. Context & Motivation:

Fluidkey has demonstrated impressive growth:

  • $250M+ transfer volume
  • 500K+ privacy-preserving addresses generated
  • ~15k users

They also run ongoing distribution campaigns where users can claim various tokens (e.g.: ENS, AERO, rETH, cbBTC, MORPHO, SAFE, etc.). This presents an opportunity to align SUMR with an innovative ecosystem partner while introducing new users to our DAO and governance model.

There has been around 1700+ unique addresses that claimed highlight tokens over the past 2 months.

As SUMR moves toward transferability, early exposure through targeted campaigns could help:

  • Increase awareness & recognition of SUMR
  • Onboard a cohort of technically engaged, privacy-forward users
  • Strengthen our marketing and community presence

Fluidkey’s impact on Lazy Summer Protocol from 2025-08-20 (16:13):

  • TVL brought in: 16.11M$
  • TVL that came in and stayed: 221.88k$
  • amount of users (ever): 142
    • stickly (having 1+ balance): 83
    • heavy (having 1k+ balance): 26

Thank you @techsqrt for providing these initial data points.


3. Proposal:

  • Pilot campaign: distribute up to 100,000 SUMR total (example size, open for discussion) via Fluidkey’s claim mechanism.
    • Users could claim a small allocation (e.g., up to 10 SUMR), depending on their Fluidkey Score eligibility.
      • Unused funds should be returned back to the Lazy Summer DAO treasury.
  • Strengthen collaboration between Fluidkey’s privacy tooling and Lazy Summer’s Protocol community/governance identity.

3.1 Considerations:

  • Budget: small, symbolic allocation vs. larger incentive.
  • Timing: likely best aligned with SUMR transferability event (TTE).
  • Messaging: needs to clearly frame this as recognition + outreach, not yield farming.
  • Measurement: evaluate uptake, new wallet activity, governance participation.

4. Next Steps:

  • Gather community sentiment on whether a Fluidkey campaign is a valuable experiment.
  • If positive, refine campaign size, timing, and messaging.
  • Coordinate with Fluidkey team to scope technical requirements.

5. Informal Support Indicator:

Would the community support piloting a Fluidkey SUMR distribution as part of the transferability readiness & marketing roadmap? What size and scope feels appropriate?
@Recognized_Delegates, @TR-WG, @Sixty, @samehueasyou, @Eren_DAOplomats

  • In support of the SUMR distribution via Fluidkey
  • Against the SUMR distribution via Fluidkey
0 voters

—jensei

3 Likes

generally love this idea, spread the token far and wide to users who ostensibly will understand the value.

1 Like

Love this RFC - thanks @jensei . We’re fully supportive of a targeted SUMR drop via Fluidkey Score (per-user caps, unused funds returned) timed around transferability. Especially given the great integration we just completed. The 100k SUMR pilot sounds right, but on the exact amount I’ll let you decide on this. Big +1 from Fluidkey - excited to make it happen!

2 Likes

Thank you for this RFC @jensei.Fully supportive of this. A small-scale distribution with Fluidkey is a smart way to get $SUMR into the hands of a technically engaged and privacy-aware user base before the token goes live.

2 Likes

Thanks @jensei for putting this proposal together :raising_hands:

Well, I’m for it — with the current very little “keep ratio” of FluidKey users (most opt into auto-earn, but only a small fraction of the original TVL actually stays in LazySummer auto-earn for now). Both FluidKey and LazySummer DAO have a shared motivation to give users recognition and incentives to remain engaged for a while :light_bulb:

I’d also highlight that, practically, airdropping SUMR would likely be carried out on FluidKey’s side — since they preserve privacy at the account layer. Their score should definitely be relevant here — but if needed, I can also provide a detailed LazySummer-score for each user (proportional to revenue created).

2 Likes

I am supportive of this proposal for the reasons stated above. We should aim to achieve the broadest distribution possible, and this proposal aims to achieve just that. Agree with others that the 100k number is just right. Looking forward to scoping this out further with the Fluidkey team.

1 Like