Sometimes a body of work arrives quietly. Sometimes it arrives with urgency.

Last week, I was inspired to deeply visited the work of Romanian sculptor Constantin Brâncuși — not only to expand my horizons, but to see if I, too, might—thanks to this new exploration—deliver some new element of my personal story through the Brâncuși lens.

As I stand tippy-toe upon the shoulders of this artistic giant and lean in to look upon his world with inspired eyes that I, too, may chime in on a tribute to him along with my peers, what delights me most of what I can imprint of Constantin Brâncuși is his discipline of refinement into abstraction. The distillation of noise and into the supple amplification of essence—like any memory of a person we hold, whole and complete in its abstraction, and yet not the whole story.

This is an interactive work of art, and a blind mint of singular works of ABSTRACTIA in a series within the larger work.

Open Letter to Our Players (With a Side-Eye to Certain Ex-Partners)

Hey Blaqqat frens, framily, partners and lovers,

Quick heads-up from the front lines: Our apps and games—including everyone's favorite balloon-popping revenge simulator, Ms. Petty (you know, the one formerly known as HATER or H8R)—have vanished on account of that one platform we were using did a sudden death sunset without adequate time for developers like BLAQQAT—that's me—to do anything smooth about it. For me the event was overnight. No DM, no warning, no "thanks for being an early builder, here's how to cash out yoru coins," no nothing. Just... poof. Like the execs hit the big red "sunset" button while yelling "YOLO!" and then immediately went on a team-building retreat to forget we existed.

Eighteen months of work—gone in the time it takes to cancel a monthly server subscription. Classic move from within the ethos where there is ostensibly deep neglect where a founder's choices to inform platform builders is rooted in a sense of value for something I call "builders equity". Sweat equity isn't something only founders invest. I get it: building empires on rented land is risky. We all want to be independent yet we all want to benefit from the promise of the network effect, yet when the platform extracts from its holdership like a landlord rather than treating each holder like a valued overseer of a section of map, it's more challenging than it needs to be for us to gain traction. One after another devaluing experiences in a row can make a person feel like they don't want to trust anyone for anything

looks around at all the different blockchains

... How can we blame anyone for feeling like it's hard to trust these days?
Nevermind about disingenuity, I'm talking about the viability of an organization to keep doing what its doing for the next 3-5 years—how likely are they to suddenly demand you either drop kick or adopt exploitative or ethicically misaligned terms of service; it's an important decision and requires a workflow to make the transition, if you've been using said platform for a long time.

But here's the punchline—they didn't actually sink BLAQQAT. I was already side-eyeing the vibe, flicking my tail, quietly packing our digital bags of code, and researching a move to a more loveable (and less capricious) hood where I hear the catnip is free-flowing. We knew platforms come and go like dinner smells, so we aren't about to let the table go without the BLAQQAT brand of circus antics and bizarre fun.

Right now we're in a short you-can-play-it-now hiatus while I rebuild and relaunch Ms. Petty and the rest of the BLAQQAT games character crew across multiple platforms. We're spreading out faster than rumors in a group chat—because apparently the best revenge is not just petty balloons, but making sure no single "oops we sunsetted everything" can nuke the fun again. We're hustling toward a more permanent setup where we actually have a say in the rules.

This isn't goodbye; it's a "brb, dodging crypto-founder rug-torpedoes."

Thanks for riding into this bizarre victory with us. Your scores, your streaks, your glorious pettiness—it's all fuel. I'll shout from this rooftops again the second I have something to show you.

Stay petty, stay patient, and remember: some islands sink, but the balloons? They always rise.

Already getting the laser pew pews juiced up with new sounds so busting will be more satisfying than ever. Onward to the spoils!

Maxximillian Blaqqat

Hello, friends. I’m Maxximillian of BLAQQAT. I build for people who are busy, curious, and easily interrupted. In other words, all of us.

As I gather my insights in preparation for my upcoming tour date to join my favorite builders at the most iconic builder conference on the planet at ETH Denver.
I distilled a valuable observation for founders and builders that I selfishly could hardly wait to share with you—since, after all, some of my readers are some of my favorite artists, buidlers and developers too.

** Poof. ** It just happened.

Tell me where you disagree: onchain is better when we ask for a signature only when it creates deeper meaning for the user—their claim, their published post, their acquisition—and give tiny haptic “you’re good” cues for everything else. Translation: it's less about what should go onchain and more about the question of: Wen should thingy go onchain?

Answer: Only at the moment when it benefits the user—that's you, it's me, it's us.

A tiny cue is all that's needed most of the time to reassure the visitor, not an actual transaction receipt. The cue should be simple. It says, “You did it.” It says, “You’re good.”
It lets the moment keep moving. It’s the instant proof that acknowledges and affirms the person in front of the app.

We already know what kills momentum.
You open an app to do one small thing.
Before you blink: connect wallet, another application wants to open, scan a code, find another device, switch network, approve spending, go back to the application, sign another Tx. You didn’t complete a journey. You got mugged by a workflow. The user isn’t wrong to abandon. The sequence is grab-ass and exhausts the user with superfluous requests to their own immediate goal.

Signatures don't have to be superfluous. I see them as sacred—let's save them for vows.
They are the close-up in a film—used when the stakes are real, when the moment should be remembered in stone. Let us not initiate a Tx just because that's how everybody does it or just because we can generate some extra data.

Actual necessity and immediate value for the user, or avoid forced Tx.
Forcing new users to register before exploring to boost vanity metrics? Nah.
If the visitor/player/app user wants to bookmark anything, or customize anything—that is the irresistible point where we offer them a Tx to sign. If they don't need to sign the Tx to satisfy their immediate goal—tiny cue the correct moves with haptics and banner messages and let the person move on, saving their preferences and data locally until they choose to put a ring on it by bringing it onchain with a Tx.

Okay, fine then—how do we decide when to offer a mint or initiate a Tx?

First: can the log be stored locally? If not or it costs money, adds an asset, or changes a permission—ask for a signature. If the session preferences and activity can be stored locally without bother—tiny cue.

Second: is ownership changing? If custody switches, or a new contract is born—signature. If it’s just interest signaling, progress, or intent—tiny cue plus session receipt.

Third: must outsiders verify it? Only if you absolutely must involve another app, like an auditor, or buyer needs trust without trusting you—signature. If the record exists only to improve your UX—tiny cue and session receipt until the user opts-in onchain.

Fourth: do laws require it? If compliance demands an immutable trail—signature. If not—tiny cue and session receipt.

Fifth: will a signature break the flow? If the user is still finding their footing—on a bus, inconsistent wifi, minute one—do not throw a transaction at their face. Tiny cues now; offer the signature later, when the story is ready for ink.

You’re exploring a music drop. You tap play, and the visuals come alive. You tap a bookmark to save it. That’s curation. Until you decide to save it with a title we can discern it's not ready for the ledger or important enough for posterity. The app can provide a haptic and a small, local receipt: “Saved.” That’s all that’s needed.

You finish a remix you love. You want your name on it. That’s the moment to sign the Tx. The signature is the autographed concert tee after the concert. It doesn’t bully the warm-up.

Another one. You buy a kettle. The package has microscopic type and a QR code that smells like phishing. You just want to descale your kettle, not join a mailing list. You scan the IRIS hologram. A wordless scene shows how to do exactly what you need. You get a tiny cue - a message that your model was recognized and your steps were saved to your device. No signature required for pairing this preference to your device. If you later register a warranty, then you create an account and will be offered a Tx to sign.

Would you KYC just to browse at the gas station mini market? No, or no? No, right? Asking people for their wallet address when they have yet to express intent to buy anything is equally unalive.

First, let people explore. No signin gate. No wallet connect. Show the toy. Let them touch it. Curiosity doesn't have to be an accountable engagement.

Second, when they act with intent: change from the default username, or customize their profile in any way, capture it off-chain and hand them a session receipt. A bookmark. A line in their account activity that says, “We saved your spot.”

Third, when the moment matters—ownership, sharing, publishing—offer a signature with a clear payoff. Use a full sentence. “Sign to make this yours.” “Sign to publish for others to view.” Do not say “Sign for security.” That’s not a reason; that’s a shakedown.

Fourth, bundle. Gather the small data inputs into one profile as the user carries on with whatever they do. Trade multiple prompt nags for one meaningful transaction that populates all their data onchain when the user is ready to put a ring on it.
Mercy disguised as design.

That’s not Web3. That’s paperwork cosplay.
Tx the vows; thumbs up tiny cues for the errands.

Use off-chain event logs with unique IDs. Put them in the user’s account page. Make them visible. They are receipts.

Use session markers. When someone starts on mobile and wants to finish on desktop, send a magic link. The link says, “We kept your progress.” That sentence is a tiny receipt. It turns a stall into a promise.

Use sponsored transactions when the moment truly matters, so the user signs the Tx and completes their task without being turned away for not having gas when the Tx wasn't the point.

And make the words kind. Microcopy can read like moral philosophy haiku. Rise to the challenge of increased user confidence in just a few words.

“Locked. Saved. You’re good.”
“Want to make it permanent? One quick sign.”
“Prefer desktop? We sent a link.”
“Cancel is fine. We saved your work.”

Wallet-first gates for read-only moments.
Meaningless payloads disguised as “security.”
QR code ping-pong mid-task.
Onchain spam for vanity metrics.
Interfaces that treat “Cancel” like failure.

Time-to-first-win drops.
Signature drop-offs drop.
Completion after tiny receipt rises.
Support tickets with “wallet” shrink.
The bundle becomes one signature that feels like a coronation instead of a toll.

“You are transferring an asset.”
“You are granting a permission.”
“You are creating a record for archival purposes.”
Use human-readable messages. If a person can’t skim and know what they’re signing, you built a ritual without a meaning.

Music: explore off-chain, earn tiny receipts for creative steps, sign once to publish your take or claim your edition. The signature seals authorship. The rest celebrates progress.

SaaS: learn with a wordless guide, get tiny receipts for completed steps, sign later to register and unlock service. Instruction is a gift; registration is a contract. Do not confuse 403 activities for husbandry.

Community: accrue earned points off-chain as you participate, sign the Tx one time at season’s end to anchor your total or redeem perks.

Can the user get a first win without a signature?
If not, why not—custody, rights, law, or habit?
Can we bundle three or more steps into one signature later?
Do we give a tiny cue at every meaningful step?
Is the signature message short, honest, and readable?
Do we offer a desktop handoff when mobile fights back?
Do we sponsor the one signature that truly counts?

This kind of consideration is visitor-first. This is disciplined courtesy. Nunchi for product UX: read the room, reduce the noise, respond to user intention with the one right move, fast. Krav Maga for product docs: identify the move and lead the user to execute it with minimal onchain Tx requests, initiating a transaction only when the user (not only the platform) benefits by the onchain activity. In other words it's grab-ass to force people to sign in just to look around. Is your brand a self-adulating grab-ass brand? Or is your brand a trusted cultural treasure where people opt-in because they wanna?

People remember how an online or telephone experience with a brand—or even a commercial!—makes us feel, whether or not we spend time thinking about it, and as a consumer we remember how a product experience makes us feel, for better and for worse.

What do you want? Here it is. You did it! Something else?
When the moment has weight for the user, and they want a receipt, we offer the Tx op.
Until then—no shakedowns, no kyc, no cannibalism—just momentum toward their goal.

And when the moment calls for a record, the ledger is ready to offer the receipt.

Maxximillian BLAQQAT™️ is a composer-founder who treats product like performance and software like stagecraft. Her work spans music, interactive art , dynamic immersive experiences. Building product experiences that feel human-first, technical second. She designs for momentum, story, ease and delight: fewer obstacles, clearer moments, and experiences that reward curiosity without extracting it.

As an artist and builder, she moves fluidly between studio, codebase, and community—scoring albums, crafting browser-native music experiences, and architecting tools that invite participation without friction. She’s obsessed with architecting peak experiences we can feel long after the event: wordless guidance that reads like choreography, interfaces that behave like good hosts, and records that become permanent only when permanence is the point. Her north star is simple: create work that stands up in a gallery, holds up in production, and welcomes people who are busy, curious, and easily interrupted—meaning everyone.

LUCID IRIS™️ replaces unreadable packaging with a safe, elegant, wordless AR walkthrough—triggered by a unique on-product hologram (the IRIS). No tiny text. No QR-phishing. No language barrier. Just a fast “you’re good” moment that shows how to use the product, with optional on-chain receipts when ownership or rights actually matter.