I assumed Twin.fun's pricing worked the way most bonding curves do, a straight line where each new key costs a little more than the last in some simple, predictable way. Then I opened the actual pricing and fees documentation and the math humbled me a bit.

The price for any trade comes from a sum of squares formula, not a straight ramp. You take the cubic relationship between the old supply and the new supply, subtract the two, and scale the whole thing down by a fixed constant, 1,600,000 to be exact, before it turns into an actual ETH amount. It is a curve that accelerates harder the deeper into a twin's supply you buy, not a gentle, even slope.

I tried running the math by hand for a twin sitting at 40 keys already sold, just to see how steep things actually get. The jump from key 40 to key 41 costs noticeably more than the jump from key 4 to key 5 ever did, and the gap between early buyers and late buyers widens fast once a twin starts climbing past its first few dozen sales.

The other detail that caught me off guard: you cannot launch a brand new twin by buying just 1 key. At zero supply, the contract requires purchasing a minimum batch upfront before the curve even starts moving. No single key creation option exists, the twin only comes alive once that opening batch clears.

Honestly that is kind of sigma energy from a design standpoint, it forces every twin to start with a real chunk of committed buyers instead of 1 curious wallet testing the waters with pocket change. It also means the floor price right out of the gate is never trivially cheap.

OpenGradient does hide actual complexity behind a simple sounding bonding curve pitch, the math under Twin.fun is closer to a cubic growth formula with a forced minimum buy in than the basic linear curve most people picture when they hear the term.

@OpenGradient $OPG #opg
$RAVE $SLX