Everlong

Problem

Everlong runs across three chains: Berachain, Katana and Base. Vaults are the centrepiece. A vault has to read the same way to a user whichever chain it sits on, so the differences between those chains cannot be allowed to surface as differences in the interface. And it had to stand on its own: its own product, its own surface, not a variation on something else.

Solution

I was the primary frontend author, working in the same four-engineer freelance team as Beraborrow. I built the application at beta.foreverlong.io: the vaults that sit at the centre of the product, the flows a user moves through around them, and the multichain surface that has to hold up the same way on Berachain, Katana and Base.

Outcome

Everlong is live. The app is at beta.foreverlong.io, with foreverlong.io as the marketing site and docs.foreverlong.io as the documentation, and vaults ship across all three chains.