Web3 engineer focused on making Web3 product usable. Building projects, exploring Defi and documenting what I have built and learnt along the way.
Joined January 2021
- Tweets6.2K
- Following1.6K
- Followers1.7K
- Likes16.6K
Pinned Tweet
I came across a prayer somewhere, and since then, my mind unconsciously goes back to it in moments of reflection. The prayer goes like this:
“God show me how good it can get, surprise me with opportunities I never expected, connect me with people I never knew I needed, take me to rooms I never imagined going on my own, help me to leave survival mode and start living in growth mode, I releases every fear that keeps me attached to unproductive struggle, may my past not interfere with my future and may fear not hold me back from doing great things. Let me work in your light. Amen”
Alchemist retweeted
We all gotta self-custody our money now, can't trust anything that you can't audit with your own AI.
Thats why we wrote the signing logic for @1shotapi embedded wallet in pure javascript with no dependencies.
Hopefully the browser vendors are a little safer that PHP
Two critical vulnerabilities have been identified in PHP, a widely used programming language that powers websites and web applications. These vulnerabilities (CVE-2026-109618 and CVE-2026-109619) could allow malicious cyber actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.
The FBI urges organizations to take the following steps now:
➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
➡️ Immediately update affected PHP installations following the guidance on php.net. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or ic3.gov. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information, follow PHP’s announcement on php.net, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.
ALT Critical vulnerability alert for PHP Core with CVE-2026-109618 and CVE-2026-109619, CVSS score 9.2, urging immediate patch and threat hunting.
"The demand to pay with crypto is real. The gap between holding crypto and spending it is where checkout loses people."
That thesis led me to build Morva(morva-frontend-zeta.vercel.a…) at the UXmaxx hackathon on @encodeclub, where it placed 2nd. Since then, almost everything I’ve built has been about checkout, from Morva to Jupa(jupa-z9gc.vercel.app/) on @arc .
And the numbers keep telling the same story:
65% of crypto owners would rather pay with crypto, yet crypto is just 0.19% of global transaction value
30% of users quit at “Connect wallet”
1 in 6 crypto payments arrive for the wrong amount
10–20 min payment windows bounce late payments
$14B+ lost to scams in 2025, so people fear signing anything
Then I went through @ilblackdragon’s list of ideas he wants to see built on @NEARProtocol , and one caught my eye immediately: a universal checkout powered by intents.
That’s the missing piece. The buyer says what they want to pay, and solvers handle the chains, tokens and routing across 35 chains. No wrong network. No underpayments. No expired invoices. No gas.
The demand is already here: 88% of US merchants get asked about crypto payments. What’s missing is the checkout.
Something’s coming. Watch out.
NEAR HACKATHON is now live with $250K+ in prizes.
No signup. Just ship a public repo + public demo post between November 1st & Nov 14, 23:59 UTC.
Build on NEAR Intents, chain signatures, chain abstraction, NEAR AI Cloud, & more.
Full details:
Alchemist retweeted
Let me be completely raw & honest with you beni, nothing in life comes easy.
Winning a hackathon isn’t just about being good at shipping a build. It’s about playing the game smart too. If you haven’t won in months, I highly recommend doing this:
1. Pick teams that actually care about builders.
Don’t just build alone in your room. Talk to their developer team. Find bugs in their tools & tell them. Show them your project before the deadline & ask for feedback. Most judges rush through demos, but if someone on their team likes your work, they will fight for you in the judging room.( This worked 99% times for me 3 different ecosystems ).
2. Use THEIR toolings, not random ones.
Judges want to see you use their tech in action. Did you use their wallet? Their code? Their endpoints or toolings? If you enter an OKX hackathon using tools built for Solana chain, you are wasting your own time. Give them exactly what they want to see.
3. Check out other submissions before submitting.
Search the timeline to see what others made. Pick the top 3 or 4 projects from returning hackaton winners most especially, ask yourself & your coding agent: Is their project better than mine? If yes, don't give up, stay up a few more hours & add a cooler feature that beats them. If your project is clearly better than the top 5 builders on your list, you have a huge chance at winning a prize.
4. Don't quit if you lose.
Don't delete your repos but double down and keep building in public. A great example is what @kenn_ronin did with Muse Mirror. When ecosystem teams see you never quit & keep improving, they will start paying attention to you.
5. Hackathons are just the start.
Hackathons are only for quick money to get you started as a founder. Build something real people actually use, even if it’s just 10 to 50 users. Save the prize money you win, focus on your one best app & attend real-life crypto events to meet people. Even getting a small $50k grant can completely Kickstart your motion or change your life.
I know it can be tough sometimes, having no money, staying up all night & feeling like giving up. But nobody who had won from the past or winning now is smarter or more special than you. Keep your head down & fight.
Alchemist retweeted
NEAR HACKATHON is now live with $250K+ in prizes.
No signup. Just ship a public repo + public demo post between November 1st & Nov 14, 23:59 UTC.
Build on NEAR Intents, chain signatures, chain abstraction, NEAR AI Cloud, & more.
Full details:
We need to chain Jethro, he is moving like rent is due😅.
Solid project man👏👏
1/
NIM just got a day job 💼
KhalkosPay is a mini app inside @nimiq Pay that lets you:
🛒 Buy NIM with local money (Supported in 11 countries including the US)
🏦 Cash it out to naira
📞 Do that by literally having a call with AI
🎁 Wrap NIM in giftcards
Here’s everything it does 🧵
Who’s coming to @gdgjos2 DevFest Jos tomorrow?
Looking forward to meeting fellow builders and creatives, sharing ideas, and seeing what everyone’s working on.
If you’ll be there, let’s connect!
#DevFestJos #GDGJos
Alchemist retweeted
Here is what Pact looks like, end to end on @monad mainnet
A sponsor pays in ETH on Arbitrum. @auroraisnear delivers it as USDC to the event's vault on @monad. The payee signs in with @dynamic_xyz, accepts with a Mera passkey, and gets paid on any network of his choices.
No bridge. No seed phrase.
#MonadMetropolis
One thing I have been very intentional about while building Pact is ensuring that users can interact with the product seamlessly without worrying about blockchain complexity or needing to understand how blockchain works.
An event organizer shouldn’t need to understand wallets, gas, signatures, or smart contracts to create a payment agreement.
A photographer, caterer, speaker, or contractor shouldn’t need to install a browser extension, save a seed phrase, or learn Web3 before they can accept work and get paid.
That’s why we combined @dynamic_xyz and @monad mera.
@dynamic_xyz gives Pact a familiar entry point: people sign in with the email identity they already use. That verified identity lets us securely match a payee to the right agreements, invoices, and payments.
Mera turns that identity into a passkey-secured Pact account. Face ID, Touch ID, or a device passkey becomes the authorization layer for accepting agreements and approving the movement of money.
@dynamic_xyz answers: “Who is this person?”
Mera answers: “Did this person authorize these exact terms?”
Together, they allow Pact to provide verifiable agreements and secure financial authorization without exposing users to the machinery underneath.
No seed phrases.
No wallet extensions.
No gas management.
No blockchain vocabulary in the core flow.
Just sign in, review the agreement, approve it, and get paid.
That’s the kind of blockchain product we’re building with Pact: one where the infrastructure is powerful, but almost invisible.
#metropolis
Here is what Pact looks like, end to end on @monad mainnet
A sponsor pays in ETH on Arbitrum. @auroraisnear delivers it as USDC to the event's vault on @monad. The payee signs in with @dynamic_xyz, accepts with a Mera passkey, and gets paid on any network of his choices.
No bridge. No seed phrase.
#MonadMetropolis
One thing I have been very intentional about while building Pact is ensuring that users can interact with the product seamlessly without worrying about blockchain complexity or needing to understand how blockchain works.
An event organizer shouldn’t need to understand wallets, gas, signatures, or smart contracts to create a payment agreement.
A photographer, caterer, speaker, or contractor shouldn’t need to install a browser extension, save a seed phrase, or learn Web3 before they can accept work and get paid.
That’s why we combined @dynamic_xyz and @monad mera.
@dynamic_xyz gives Pact a familiar entry point: people sign in with the email identity they already use. That verified identity lets us securely match a payee to the right agreements, invoices, and payments.
Mera turns that identity into a passkey-secured Pact account. Face ID, Touch ID, or a device passkey becomes the authorization layer for accepting agreements and approving the movement of money.
@dynamic_xyz answers: “Who is this person?”
Mera answers: “Did this person authorize these exact terms?”
Together, they allow Pact to provide verifiable agreements and secure financial authorization without exposing users to the machinery underneath.
No seed phrases.
No wallet extensions.
No gas management.
No blockchain vocabulary in the core flow.
Just sign in, review the agreement, approve it, and get paid.
That’s the kind of blockchain product we’re building with Pact: one where the infrastructure is powerful, but almost invisible.
#metropolis
Thank you! 🙏 @dynamic_xyz is the first thing every organizer and payee touches in Pact. Familiar Google or email sign-in, and each payee only sees agreements made for their verified email.
Alchemist retweeted
🚨New bounty alert🚨
The PayWithBlink Video Challenge is LIVE!
Pay for something with Blink, record your experience, post on X, Instagram & TikTok, and win a share of $300 in prizes! 💸
Ready to show us how you #PayWithBlink? 👀
trytetra.xyz/bounties/pay-wi…
Alchemist retweeted
Join the Blink Video Challenge starting today…
1. Join the challenge: Register on our bounty platform: trytetra.xyz/bounties/pay-wi…
2. Get the full campaign details: Join our Telegram channel: t.me/useblinkapp
Use Blink. Pay with Blink. Show the experience. Win!
Alchemist retweeted
One thing I have been very intentional about while building Pact is ensuring that users can interact with the product seamlessly without worrying about blockchain complexity or needing to understand how blockchain works.
An event organizer shouldn’t need to understand wallets, gas, signatures, or smart contracts to create a payment agreement.
A photographer, caterer, speaker, or contractor shouldn’t need to install a browser extension, save a seed phrase, or learn Web3 before they can accept work and get paid.
That’s why we combined @dynamic_xyz and @monad mera.
@dynamic_xyz gives Pact a familiar entry point: people sign in with the email identity they already use. That verified identity lets us securely match a payee to the right agreements, invoices, and payments.
Mera turns that identity into a passkey-secured Pact account. Face ID, Touch ID, or a device passkey becomes the authorization layer for accepting agreements and approving the movement of money.
@dynamic_xyz answers: “Who is this person?”
Mera answers: “Did this person authorize these exact terms?”
Together, they allow Pact to provide verifiable agreements and secure financial authorization without exposing users to the machinery underneath.
No seed phrases.
No wallet extensions.
No gas management.
No blockchain vocabulary in the core flow.
Just sign in, review the agreement, approve it, and get paid.
That’s the kind of blockchain product we’re building with Pact: one where the infrastructure is powerful, but almost invisible.
#metropolis
Pact's funding flow now works end to end on mainnet ✅
A sponsor opens a funding link and pays from wherever their money is: ETH on Arbitrum, XLM on Stellar.
A community donor can support an event from wherever their money is.
@auroraisnear Intents routes and converts it, and it lands as USDC in the event's own vault on @monad.
No bridging.
One thing I have been very intentional about while building Pact is ensuring that users can interact with the product seamlessly without worrying about blockchain complexity or needing to understand how blockchain works.
An event organizer shouldn’t need to understand wallets, gas, signatures, or smart contracts to create a payment agreement.
A photographer, caterer, speaker, or contractor shouldn’t need to install a browser extension, save a seed phrase, or learn Web3 before they can accept work and get paid.
That’s why we combined @dynamic_xyz and @monad mera.
@dynamic_xyz gives Pact a familiar entry point: people sign in with the email identity they already use. That verified identity lets us securely match a payee to the right agreements, invoices, and payments.
Mera turns that identity into a passkey-secured Pact account. Face ID, Touch ID, or a device passkey becomes the authorization layer for accepting agreements and approving the movement of money.
@dynamic_xyz answers: “Who is this person?”
Mera answers: “Did this person authorize these exact terms?”
Together, they allow Pact to provide verifiable agreements and secure financial authorization without exposing users to the machinery underneath.
No seed phrases.
No wallet extensions.
No gas management.
No blockchain vocabulary in the core flow.
Just sign in, review the agreement, approve it, and get paid.
That’s the kind of blockchain product we’re building with Pact: one where the infrastructure is powerful, but almost invisible.
#metropolis
Pact's funding flow now works end to end on mainnet ✅
A sponsor opens a funding link and pays from wherever their money is: ETH on Arbitrum, XLM on Stellar.
A community donor can support an event from wherever their money is.
@auroraisnear Intents routes and converts it, and it lands as USDC in the event's own vault on @monad.
No bridging.
Alchemist retweeted
Your first users probably won’t magically find you.
@pareen’s advice: DM 200 people, talk to everyone who replies, and bring the early believers into one group chat.
Listen closely, ship what they ask for, and keep the conversation active.