• Pippy seer (30th Sept.) • On-chain Robinhood NFT built on a new standard for native on-chain pixel storage • Pseer.chat • discord.gg/KnR7ZfZhD6

Coded art
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.
67
331
746
38,369
Pippy Seer Mints in 6 Days! Notis ON🔔 Last FCFS Giveaway🎁, then it’s all art and building! Do this: 1⃣Follow and notis’ON🔔 2⃣QUOTE this post and call your friends 3⃣Drop EVM wallet Complete the steps then check your eligibility in 48 hours: opensea.io/collection/pseer/…
168
90
188
7,564
non action retweeted
collection that I almost missed while I was focused on Zcash collections, which are not impressive at all, even the long-awaited Bitfoot in my opinion looks very weak at the moment but it is understandable who needs NFTs there as we already see the best digital art on Ethereum or Robinhood why now I will follow @Inscription133 : >I have FCFS lol, but this is not the main reason >in an active and not twisted twitter with good followers >they write honestly, openly about the collection >without unnecessary promises >all changes that occurred on the mint, were only in a positive direction (decreasing the price of mint for example) >clear description of the supply, data, who and how gets it and what is a priority for them that is why I will try to get this NFT even all this does not mean success or a big X, but this is a collection that is not ashamed to write about the main thing you need to know: >date - September 30 >supply - 1500 NFT >GTD - 250 places/free mint/limit 1 per wallet >FCFS - 1250/0.001 ETH/limit 3 per wallet i will try to take it, of course i don't like to be behind everyone (and these are those who have GTD and a team), but this deserves attention i love honesty and whatever it is i will support it and unfortunately there is very little of it in CT i am in no way trying to convince you of anything, be sure to conduct your own analysis
Pippy Seer Mints in 6 Days! Notis ON🔔 Last FCFS Giveaway🎁, then it’s all art and building! Do this: 1⃣Follow and notis’ON🔔 2⃣QUOTE this post and call your friends 3⃣Drop EVM wallet Complete the steps then check your eligibility in 48 hours: opensea.io/collection/pseer/…
47
3
80
1,931
For future holders, I’m excited to share how the Pippy Seer art comes to life! Everything Howie Lab ships is rendered in real time by on-chain scripts. No images. No off-chain media. Only one reason: Art should evolve with the medium. On-chain space is expensive, and that makes it a new kind of canvas. For an artist, the job isn’t to dodge it, is to adapt to it and build a new format around it.
19
22
73
2,269
The process wasn’t just “being creative.” The part that stuck with me was problem solving. A lot ideas came from the problems. People ask how the pixel-on-chain standard happened. Simple: I needed the whole 1:1s collection on-chain, so I built a standard that actually fits my work. It’s unique because it came out of the making of the work.
1
10
84
Mint is less than a week. Genuine thanks to everyone who showed up on X and Discord, and to every CM who believed in Pippy Seer vision to raffle it into their community. I hope we find our people. The journey is about to begin.
2
10
86
OpenSea wallet checker is live. Use the official link opensea.io/collection/pseer/… only. I’ve seen some fake Pippy Seer pages there, so don’t click anything that isn’t from me. 🧠 Quick take on FCFS Over Allocation: There are only 250 GTD. The remaining 1,250 — the bulk of the launch are FCFS. FCFS means first come first served. People who actually get in first are usually the ones tracking every tweet and every Discord ping. Not who took WL and still don’t know what day the mint is. If people buy the vision, it shows in the attention ppl put in. Some giveaway farmers hit every raffle, grab WL, never look at the project, and don’t even read the tweets they repost. FCFS is a clean filter for that. Overallocated does not mean all-out competition. Market sentiment still affects how many people actually show up, and only a portion of the full list closely follows the project and cares about it. If we don’t overallocate, close to half the supply can sit with people who don’t care. They no-show at mint unless there’s a FAT flip. Most of the time it doesn’t, so they ghost, paid minters and the team eat a fail launch. That works against every minter’s interest. People who might actually like what Pippy Seer is doing on-chain never get in. FCFS keeps the people who care, that’s why most launches that cleared lately ran OA. I don’t want to gloss over what bots can do. I’ve been vetting giveaway communities to cut that risk down. All effort is to make the launch land and pay back the people who actually real support. We still have time go study Pippy Seer. We built for almost a year pre-launch. Read what we already shipped and you’ll care more. Come through, buddies and sisters!
Updated Launch Details 1⃣Mint Price: 5$ →2.8$ 2⃣Supply: 2,000 pcs → 1,500 pcs 3⃣GTD: 2 per wallet → 1 per wallet 4⃣FCFS: 3 mint per wallet 5⃣Mint Date: 30 Sept. OPENSEA OpenSea whitelist checker goes live SOON. GTD applications closed. ❓Why I adjusted the launch details❓ 1- To make easier for ppl join Pippy Seer’s vision, I cut the price by 44% so minters keep more upside. That should also create more secondary and exposure for the project which good for every minter. 2- Supply is also cut by a quarter. 2,000 wasn’t huge versus recent mints, but attention is rotating fast and the ZEC ecosystem is competing for that attention. Supply goes to 1,500 so the mint has more certainty. 3- GTD freemint per wallet 2 → 1. One reason is to recalibrate how much of the raise is given away for free after the price cut, and to match the smaller total supply. The other reason is to reduce potential selling in that stage, so the main FCFS stage and the mint as a whole can actually clear. This is different from the earlier GTD 2 mints. I sized it after market tone, demand, and ~500 wallets of on-chain behavior , this is the plan I believe most likely to make the full mint succeed. Hope you’ll bear with me! Total 3 Phases: GTD: 250 mints in 1 hour. FCFS: 1,250 mints in 1 hour. Public A successful mint is win for the whole room. This is Howie Lab’s 2nd project since Aug 2025. New onchain pixel spec + Market Observation AI are just the start. Pippy Seer is not only making promises; it has been delivering consistently before launch. Let’s bring something fresh on-chain!
46
19
88
6,925
Updated Launch Details 1⃣Mint Price: 5$ →2.8$ 2⃣Supply: 2,000 pcs → 1,500 pcs 3⃣GTD: 2 per wallet → 1 per wallet 4⃣FCFS: 3 mint per wallet 5⃣Mint Date: 30 Sept. OPENSEA OpenSea whitelist checker goes live SOON. GTD applications closed. ❓Why I adjusted the launch details❓ 1- To make easier for ppl join Pippy Seer’s vision, I cut the price by 44% so minters keep more upside. That should also create more secondary and exposure for the project which good for every minter. 2- Supply is also cut by a quarter. 2,000 wasn’t huge versus recent mints, but attention is rotating fast and the ZEC ecosystem is competing for that attention. Supply goes to 1,500 so the mint has more certainty. 3- GTD freemint per wallet 2 → 1. One reason is to recalibrate how much of the raise is given away for free after the price cut, and to match the smaller total supply. The other reason is to reduce potential selling in that stage, so the main FCFS stage and the mint as a whole can actually clear. This is different from the earlier GTD 2 mints. I sized it after market tone, demand, and ~500 wallets of on-chain behavior , this is the plan I believe most likely to make the full mint succeed. Hope you’ll bear with me! Total 3 Phases: GTD: 250 mints in 1 hour. FCFS: 1,250 mints in 1 hour. Public A successful mint is win for the whole room. This is Howie Lab’s 2nd project since Aug 2025. New onchain pixel spec + Market Observation AI are just the start. Pippy Seer is not only making promises; it has been delivering consistently before launch. Let’s bring something fresh on-chain!
46
28
105
8,916
wait… this is actually so cool. the idea of every piece having its own compressed pixel packet instead of pulling from a shared trait sheet is crazy. 2000 pfp = 2000 individually authored pieces. the fact that the same spec can be used for 1/1 pixel art too makes this even more interesting. onchain art keeps getting more creative fr. howie lab cooked with this one.🫡
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.
5
2
21
692
spotlight alpha: @Inscription133 🧿 Most onchain PFPs start with a trait library and remix it thousands of times. Pippy Seer takes a different route. 2,000 pieces. 2,000 individual canvases. Each Seer has its own compressed pixel data, geometry, palette and hue , stored onchain and rendered as a 44×44 SVG when queried. → no shared trait sheet → no layer stacking → SSTORE2 storage → fully onchain rendering → open ERC-721 implementation spec → built by Howie Lab, the team behind BITDREAM What makes this interesting isn't just the pixel art. It's the decision to treat each NFT as its own authored 1/1, while still finding a way to make that practical on EVM. Howie Lab already explored this philosophy with Bitdream on Bitcoin. Pippy Seer feels like the next iteration of that idea. less “generate a PFP.” more “put the artwork itself onchain.” That distinction matters. 👀
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.
2
1
6
293
non action retweeted
Hello CT. I'd like to talk about @Inscription133 'Pippy Seer.' After looking into it closely, I feel it has some unique qualities. Pippy Seer is about much more than just its pixel art. The true distinction of Pippy Seer lies in how the artwork resides directly on-chain. We've long seen that most PFPs rely on standard 'trait layers' such as body, eyes, clothing, hats, and backgrounds combining them in various ways to generate thousands of NFTs. -- However, Pippy Seer takes a different approach. There are no shared or generic layers in Pippy Seer. Each 'Seer' possesses its own dedicated 44×44 canvas and unique pixel data. Consequently, the 2,000 Pippies aren't merely different combinations of the same traits, they stand as 2,000 unique '1/1' artworks. The technical aspect is also quite fascinating. By utilizing geometry, palette, and hue data, each artwork is compressed to approximately 1.7 KB. This data is stored on-chain, and the smart contract generates the SVG image directly via the 'tokenURI.' In other words, Pippy Seer doesn't simply point to an off-chain image file. Instead, the artwork is reconstructed using the data stored directly on the blockchain. Pippy Seer is built upon Howie Lab's 'Bitdream' project, bringing the concept of extreme art compression to the EVM. Furthermore, its technical framework, the PSEER Onchain Pixel Spec is open-source, allowing other artists to utilize this method to create their own unique 1/1 on-chain artworks. That is precisely why I find Pippy Seer so compelling. It offers an appeal that is hard to fully articulate in a simple tweet. It grants artists greater freedom, treats the artwork itself as direct on-chain data, and paves a new way for creating and preserving pixel art. It doesn't feel like just a collection of 2,000 variations where you simply pick one. Instead, it feels like a collection of 2,000 unique artworks, each existing on the blockchain in its own distinct way. These aspects are what make Pippy Seer so fascinating to me. To reiterate, Pippy Seer isn't just another run-of-the-mill PFP project. It represents a unique and innovative approach to on-chain art. I want to extend a special thank you to the artist and the team behind the project for such an exceptional vision. It is truly praiseworthy. Really I love it.
22
7
29
585
non action retweeted
As an active member of Howie Lab, I’d like to voice my support for Pippy Seer! On-chain svg done right 🙌 Looking forward to working with my agent daily and I’m excited for what’s next. Howie Labs is highly innovative and constantly cooking. I believe Pippy Seer will do well. 🤝
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.
5
1
9
406
non action retweeted
Pippy Seer is Howie Lab’s onchain collection on Ethereum: 2,000 hand-drawn pixel creatures with no shared trait kit. Each token is stored as a real 1/1. What’s new in the PSEER spec is the storage model. Layer-stack PFPs keep one shared trait wardrobe and remix it with a seed. Every output still comes from the same parts. PSEER stores a hand-authored packet per token: geometry f, palette q, plus a hue-bucket byte. That payload goes through batchSetTraits calldata, SSTORE2.write, then {ptr, offset, length} per tokenId. On tokenURI the contract reads that slice, draws a 44×44 SVG of that token’s pixels, and puts it in image. No IPFS PNG pipeline. No shared layer sheet. So 2,000 supply can be 2,000 authored 1/1s, not 2,000 combos of one kit. Pippy Seer is the first collection on this spec. For me this is the first PFP spec that treats each piece as a finished artwork, not a roll of the same wardrobe. That’s the kind of onchain work I want to hold. @Inscription133
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.
45
2
80
1,120
non action retweeted
Been following @Inscription133 for a couple years now buying some cool real world products like the book and other art. Now Pippy Seer is moving to EVM and give more people the opportunity to see the work Howie is doing.
Replying to @akan_chikan
YES — you passed initial review. Quote following post and share what you think makes Pippy Seer different.
1
8
284
Hey fam! After careful thought, I decided to make GTD phase FREE. 1 GTD = 2 freemints. Anyone can apply. GTD=GTD / 🚫 OA Again: GTD is open and fair for everyone. I’ve received ~100 applications so far and approved 52(>50%). How are GTD applications reviewed? I coded a script (See the image/Open-sourcing soon) and look at a mix of data — including but not limited to wallet age and average hold time — to filter out pro flippers and bots. That’s it. The only goal is simple: get more REAL collectors into GTD. FCFS phrase is expected to MP around $5. Depending on demand, I may tighten total supply to give the launch a cleaner shot. Pippy Seer is Howie Lab’s 2nd project, and I'm genuinely excited for our 1st drop on EVM! A strong launch here is how we get more people to actually use our new on-chain standard!
Want GTD? Simple version! 1⃣🫳Comment: "GTD" + wallet 2⃣If you pass → I reply YES on X 3⃣Only after YES: quote one of my posts and share what’s new in the PSEER onchain pixel spec. 4⃣Done → GTD
39
23
78
3,260