Hello there.
My name is Samanway.
I build Web3 and AI products.

Ansem, the Black Bull, is one of the biggest names in crypto, with over a million followers on X. He launched $ANSEM, and we built a game around it: a live war between bulls and bears where the battlefield follows the price of the coin.

When buyers are winning, the bulls push forward. When sellers take over, the bears advance. Soldiers, tanks, helicopters, jets and a king fight it out on the map around the clock, and everyone playing can see what everyone else is doing.

What you can do

• –Start playing for free, no wallet needed
• –Fight on the frontline and take out the bears' soldiers, tanks and helicopters with different guns
• –Train in the Fight Pit, where the first to ten kills against the trainer wins
• –Buy one of 48 plots in town and put your name on its flag
• –Fish for seven species at the Mill Pond, then sell your catch at the fish trader
• –Flip a coin at the Coin House: heads or tails, and if you call it right, you double your coins
• –Mint a soldier, tank or helicopter as an NFT and keep your name on the field for good. Units are limited: there will only ever be 1,000 Super Soldiers and 50 Gold Tanks

Where NFT money goes

Every Saturday at 12:00 UTC, 45% burns $ANSEM, 45% buys back and burns $AGAME, and 10% goes to the treasury.

Our own coin

$AGAME launched on pump.fun through ansem.io with no pre-mine, and at least 3% of the supply went to $ANSEM holders. It completed its bonding curve and reached around $60–70K market cap, with a lot of volume early on. You never spend it in the game; holders get airdrops based on their balance.

Who it's for

The community. There's even a donation feature built in.

What's next

An aggregator, built fully on Solana.

Links

Play ↗ansemgames.com ↗Whitepaper ↗

+2

I needed Instagram transcripts for work, and every tool wanted $11 a month. I wasn't paying that, so I built my own in about two hours.

What it does

Paste a link to a reel or short from Instagram, TikTok, YouTube, X or Facebook, and get a clean transcript with timestamps. Copy it, download it, or find it again in your history.

How it works

It pulls the audio out of the video and runs it through Whisper on Groq for speech-to-text.

What I learned

How speech-to-text APIs actually work, and a lot more along the way.

The funny part

Those $11-a-month apps were mostly a speech-to-text API with a nice screen on top. That's when I understood how a lot of software businesses actually work.

Try it

ReelScript ↗

I built Void after my wallet got hacked and I lost about $500. It's invoicing for freelancers who get paid in crypto, and the whole point is that your keys stay yours. We never see them.

What you get

• –A wallet the moment you sign up
• –An invoice builder, and a page you can send clients to pay
• –Payments detected on-chain automatically, in USDC or USDT on Base, Ethereum, Polygon, Arbitrum and Optimism
• –PDF invoices you can download
• –Zero custody, always

Meet Ash

Void's mascot reacts to everything. It juggles coins while loading, goes crazy when you get paid, looks unimpressed when an invoice is overdue, and trips and gets back up when something breaks. There's a whole sheet of 10 expressions, from focused to unbothered.

What's next

It's a side project for now. If people actually use it, I'll add emailed invoices, expense tracking, and eventually a full money toolkit for crypto freelancers.

Links

Try Void ↗The hack that started it

One of my weirder apps. Paste your startup idea, and it tells you honestly whether it's worth building.

What you get

Reactions from a mom, a builder, a YC partner and an investor, a Naval-style line of brutal truth, and scores for things like demand and uniqueness.

Why the name

Because of a quote I love: “The magic you are looking for is in the work you are avoiding.”

Try it

magic-in-public.vercel.app ↗

Building on blockchain is hard. You have to write smart contracts, deploy them, and fix them when they break. Owl AI was our attempt to make that easier: describe what you want in plain English, and get a working smart contract, dApp or website.

Why I started

I was 16, building on blockchain, and kept running into bugs and errors with no AI tool that really helped with smart contracts. So I thought: why not build a platform for developers like me?

What it did

• –Turn a simple English prompt into a smart contract, then deploy it
• –Deploy to different blockchains, both EVM and non-EVM
• –Find and fix bugs with help from AI
• –Work for people who don't code, not just developers

Built with

My friend Prashant

Launch

We announced it in a thread on January 29, 2025. It got 2,202 views.

Link

The launch thread on X ↗

A chess app where you put real money on your game. Bet $5, win, and you walk away with $10. It's live, and it works.

How it works

Fully Web3. You pay and get paid in USDC on Base, and log in or out with Privy.

Fair play

Games run on Lichess, so there's no cheating.

The mascot

A little pixel character in a hoodie called el.

Colours

Background#0A0A0A

Surface#141414

Cards#1A1A1A

Borders#262626

Accent#7EF7B8

Try it

Play ELO ↗

After Hashly Space, my friend Prashant and I built Habit Protocol at HackWithUttarPradesh 2025, where we were selected from around 25,000 participants. It was a blockchain app to help people build habits and stay accountable.

What happened next

We slowed down after the hackathon. I planned to keep building it at home, but I realised I didn't love the idea anymore.

Where it is now

Prashant did love it. He kept going and rebuilt it as Nexis. All credit to him.

Links

Nexis ↗Prashant, @0xPrashantt ↗

A voting platform where nobody can quietly change the result. The name says it: ek vote, ek sach. One vote, one truth.

The stage

In January 2024 we presented it at Gorakhpur Mahotsav, the big event in my district, in front of politicians and a full crowd.

What happened

We explained blockchain, how a vote gets recorded and why nobody can edit it afterwards. Most people couldn't follow it. To them it looked like our product did nothing, so the simpler projects you see at every event won instead.

What I took from it

If people can't understand what you built, it doesn't matter how good it is. That has stayed with me in everything I've made since.

Where it is now

Still alive. Satya Vote 2.0 runs on React with a Solidity contract on Sepolia, and RainbowKit and Wagmi for wallets.

Links

satyavote.com ↗GitHub ↗

A messaging app like WhatsApp, but built on blockchain.

A decentralized news idea. It came straight out of my obsession with who controls a story and why people believe what they believe. Why that matters to me.

For me, AI isn't just a chatbot. It's a research partner, a writer, a developer I can pair with, and more and more, agents that do real work.

Building

Coding with Claude Code, and shipping much faster than before

Creating

Content, visuals and videos

Organising

Notes, research and managing work in Notion AI and ClickUp

I found an old screenshot in my Google Photos from the GPT-3.5 days. I was asking it what to name the crypto Instagram page I wanted to start.

I make AI videos for brand clients, mostly on Higgsfield, using video models like Seedance 2.0 and Kling 3.0. I've made quite a few of them for different clients by now.

Cinematic ads

Realistic, ad-style videos with a character and a story, like a man in a cream suit making his way to a private jet.

Animated explainers

Something I learned recently: turning a topic into a short animated story, like one Bitcoin chart and two very different plans, the patient holder and the 10x trader.

If I had to draw how I think, it would look something like this. It runs whether I ask it to or not.

1. Observe→
2. Question→
3. Generate perspectives→
4. Simulate outcomes→
5. Decide→
6. Execute→
7. Observe result→
8. Replay→
9. Learn→
10. Adjust

There's the kind where you replay something again and again and just get stuck. And there's the kind where you replay it, study it, and walk away a little better. I've done both. I try really hard to be the second one.

After I talk to someone, I usually rebuild the whole conversation in my head:

• –What did I say?
• –What should I have said?
• –How did they take it?
• –What might they have felt?
• –What did they assume?
• –What would I do differently?

The point isn't to feel bad about it. It's to learn something for next time.

Before I start, I break it down with a few questions:

• –What are we actually trying to do?
• –Who is this for, and what do they want?
• –What could go wrong, and how else could this be read?
• –What happens after this decision?
• –Can it be done faster, or by someone else?
• –What's the smallest version that's still useful?
• –What's the upside, and what's the downside?

Delegating well is harder than it looks. I try to think about:

• –What exactly needs to happen
• –What context the other person needs
• –What they might misunderstand
• –What could go wrong
• –What success looks like

I collect a lot of information before I decide. Sometimes too much. My brain keeps coming up with edge cases, which means I often catch things other people miss, and also means I can spend way too long on decisions that don't really matter.

When it does matter, I play it out. If I do this, what probably happens? If I do that? How will the other person react? Then I pick.

Probably more than I should. Things like:

When a task keeps coming back, I look for a way to make it simpler, so my time goes to the creative part. When I find a better way of doing something, I keep building on it. And I don't have much patience for process that doesn't help anyone.

At some point I noticed that people don't always believe something because it's true. Sometimes they believe it because someone explained it better, and said it enough times. Watch two people argue opposite sides, and the better storyteller usually wins the room.

That's what pulled me into storytelling. I keep wondering:

• –How does a story spread?
• –Why do some stick and others don't?
• –When does hearing something often turn into believing it?
• –How much do creators shape what their audience thinks is real?

If you overthink like I do, trying to switch your brain off doesn't work. What helps is giving it better things to think about. A good movie or series drops you into someone else's head: their reasons, their choices, and what those choices cost them.

I don't love code for its own sake. What I love is the moment an idea turns into something real that people can actually use.

I work best near the person making the decisions. Not "here's one tiny task", but "here's the problem, help me figure it out", and then doing whatever it needs, whether that's code, content, research, growth or operations.

When someone I respect looks at something I made and says "this is really good", it tells me the thing is actually useful, not just fun for me to build. That keeps me going.

When I needed Instagram transcripts and every tool wanted $11 a month, I built my own in two hours instead. Turns out most of those tools were an API with a nice screen on top. Claude and curiosity beat any subscription. The whole story.

When I come across a new product, trend or creator, my brain starts asking:

• –Could this be a business?
• –How would it make money?
• –Who would actually use it?
• –How would I build it, and how would it reach people?

Usually good at

CuriositySpotting patternsSeeing other perspectivesPlaying out scenariosLooking back and learningThinking in systemsNoticing detailsExperimentingConnecting different fields

Where it goes wrong

OverthinkingSwitching context too muchTaking on too muchThinking before doingChasing interesting thingsPolishing details that don't matter

I want to understand everything. That's a good thing, and also a dangerous one, because there's always another project, tool, idea or person to go deep on.

I think my next step isn't being more curious. It's choosing where my curiosity is actually worth spending.

When we ran the meme coin, I had access to the money. A few people told me to just disappear with it. I didn't. The way I saw it, if we lose, we lose together.

I've never knowingly scammed anyone, and I'm not planning to start. Trust lasts a lot longer than quick money.

I don't want to be a generic influencer, crypto bro, or someone who only talks. I'd rather point at things I've actually built and done, including the ones that failed.

Nothing on this page is made up. If I don't know a date or a detail yet, you'll see a dash instead of a guess.

1. Learn→
2. Build→
3. Experiment→
4. Observe→
5. Reflect→
6. Improve→
7. Try again

I'd made some money online and put it into futures trading. I lost all of it. There was nothing left.

Why

I didn't really manage risk. Leverage makes that very easy to forget.

What I learned

Markets punish leverage and emotional decisions, and they do it fast.

What changed

I take risk a lot more seriously now.

At one point we were sitting on roughly $15–20K in profit. We waited for more, and the project died. The whole story.

What I learned

Profit on paper isn't profit until you take it. The one thing I didn't lose was people's trust.

Some of my early meme and content pages got taken down. I learned the platform rules the hard way, and kept experimenting anyway.

Someone posted a malicious link in a group, I clicked it, and about $500 disappeared from my wallet.

What I learned

How phishing actually works, why token approvals matter, why airdrop links deserve suspicion, and why you keep separate wallets.

What I did next

I built Void, a crypto invoicing tool where only you ever hold your keys.

I kept stacking things on top of each other: clients, products, accounts, school. Until it turned into 48-hour sprints.

The good part

I learned fast, shipped a lot and met a lot of people.

The cost

Constant context switching, less depth, and a real risk of burning out.

Where I am

Still learning this one.

There have been plenty. Each one made me a bit better at choosing the next one.