Fhenix goes mainnet this October. For years, transacting onchain came with a tradeoff: participate in open, composable markets and, with it, surrender the privacy of your financial activity. Dual mode turns what was once an inevitable tradeoff into a property of your asset itself. For the first time, the same asset can be public when you want and confidential when you need- without sacrificing composibility or fragmenting liquidity. The era of dual mode money is here, more soon.

Yes , You are still early ! arklis.app Drop wallets

As onchain art maxi, Howie Lab started with “Bitdream”: We rebuilt crayon marks in code and rendered them on sats via recursion, so an 800KB bitmap lands as ~1.5KB, about 1/600th the size. For 👾Pippy Seer we pushed that idea onto EVM: 2000 PFPs with no shared layer sheet, packed to use as little blockspace as we could. Instead of simulating brushstrokes, we encode EACH canvas. Every piece packs into a payload—geometry f, palette q, plus a hue-bucket byte—sent in the calldata of batchSetTraits. The contract SSTORE2.write it and stores {ptr, offset, length} per tokenId. On tokenURI, it reads that slice—not the original tx—draws 44×44 SVG rects, and puts the result in image. Each token holds its own packet, so the cap of 2,000 can be 2,000 authored 1/1s, not trait layer combos. That’s the bind with layer-stack PFPs: one wardrobe, endless remixes, everything still looks related. Here there is no trait kit—only a 44×44 grid and packet size—so query-time render is that token’s pixels as SVG. I open-sourced this as an ERC-721 implementation spec; fork the repo and ship 1/1 pixel work the same way. Blockspace is expensive; per-token compressed packets beats remixing one shared trait sheet. Pippy Seer isn’t another degen mint. It’s the first collection on this spec. A pixel-native way to store and render 1/1s onchain.