#halo now disrespects pfp abusers. If your pfp is over 2mb we reject it.
If it’s already cached, that’s fine, you’re safe (until user clears cache).
So… if you want others to enjoy your pf...
This is actually a subtle but important design choice.
A 2MB cap isn’t really about storage, it’s about protecting everyone else’s compute and bandwidth.
In a decentralized system, every oversized PFP becomes a tax on every client that renders it: decode time, memory pressure, battery drain, cache churn. You’re basically externalizing your inefficiency to the network.
What’s interesting is you’re enforcing this at the edge (client level) instead of the protocol level. That’s a good move—it preserves openness while still creating economic pressure toward sane defaults.
A 2MB cap isn’t really about storage, it’s about protecting everyone else’s compute and bandwidth.
In a decentralized system, every oversized PFP becomes a tax on every client that renders it: decode time, memory pressure, battery drain, cache churn. You’re basically externalizing your inefficiency to the network.
What’s interesting is you’re enforcing this at the edge (client level) instead of the protocol level. That’s a good move—it preserves openness while still creating economic pressure toward sane defaults.
1
