Lead Web 3 Engineer | Devrel | Podcaster | @web3wikixyz, @coverantxyz | @Moca_Network / @animocabrands | Advisor | Army Veteran | Man on many missions
Dubai, United Arab Emirates
Joined October 2021
- Tweets11.9K
- Following951
- Followers1.2K
- Likes12.6K
Arman retweeted
‼️ After PHP2Shell comes Node2Shell, a critical bug found by OpenAI's Codex Security that can let attackers run code in Node.js apps.
It was successfuly demonstrated on the official Node.js 24.22.0 image.
Node 20, 23 and 25 (all EoL) get no fix.
Arman retweeted
We were able to fine tune an open weight model (Qwen3.5-9B) on proprietary internal data at @coinbase, and it out performed frontier models, at much lower cost and speed, for a specialized task (fraud prevention in this case).
I think we'll see more of this pattern inside companies. The frontier models are amazing generalists. But increasingly you'll see specialist models out perform on more narrow tasks, either working on teams, or by themselves.
We're making it easy to fine tune models internally for our employees. We even have a skill for it in our internal harness that makes it easy to spin these up and start training them:
"/fine-tune-and-serve-llm I want to fine-tune Qwen for payments risk review. help me get started"
I imagine we'll have some backend services that could be replaced entirely by this new architecture.
Our new docs are live at docs.air3.com/
We've reorganized everything around how you build with AIR (@Moca_Network ), including examples, diagrams and actual use cases, so it's easier to find what you need and build with us.
Arman retweeted
We instituted an official AI Writing Policy at @Clay.
Massive thanks to @sophiebits on our engineering team who wrote this.
Originally this was just for eng, but other teams found it so helpful we expanded it company-wide.
Here are the four guiding principles:
1. You must stand behind every idea and sentence
It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it.
2. Writing is thinking
Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter.
3. More time should be spent writing a document than consuming it
If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to.
4. Longer is not better
AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt.
You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
Just the beginning of shipping The RIGHT products for the market
WEB3 evangelists Arman Mamyan @primarchdev, has introduced OpenCasp-KYC, an open-source reference designed to help Armenian crypto-asset service providers translate KYC requirements into code.
We’re proud to see his expertise contributing to shared resources for Armenia’s growing Web3 ecosystem. Well done, Arman🙌🏻
github.com/armanmamyan/OpenC…
Just read the news from @Shopify that they’re moving away from @reactnative and going back to native app development. Quite a questionable move I'd say.
Their main arguments seem to be that AI has reduced the cost of maintaining two separate codebases, while React Native introduces additional complexity around performance optimization, framework updates, and development tooling. (seems a very strange argumentation). What's strange is that @expo already solves a significant portion of these problems.
From EAS Build and OTA updates to development clients, simulator support, and web compatibility, Expo makes the entire development experience considerably smoother. Reading about Shopify's challenges, I have a feeling they weren't fully leveraging Expo and ended up building and maintaining tooling that the ecosystem already provides.
From my own experience building with React Native, especially when working at the edge of the modern stack, where so many libraries are web-first and native polyfills are often missing, React Native is a gem. It's not perfect, and sometimes you still need native code. But being able to share business logic, iterate quickly, ship updates without waiting for app store approvals (where permitted), and access native capabilities when needed is an incredibly powerful combination.
AI making it easier to maintain two codebases doesn't automatically make maintaining two codebases a better architectural decision.
I'm sure lot of people will consider me a newbie on React Native field (been building on it for only 3 years), so I welcome to hear your thoughts on this.
Stopping the bad guys with Cloudflare: 189 malicious requests blocked or challenged in the last month #cloudflare
Lately, I’ve been seeing way too many ads promoting “NO-KYC Crypto Cards.”
And apparently, the algorithm has decided I’m the right person to ask about them, because my inbox is now full of questions:
“Where can I get a no-KYC Visa or Mastercard?”
“Why did you tell me that buying one is a waste of money?”
Well, here’s the thing.
A card that doesn’t ask YOU for KYC doesn’t necessarily mean there is no KYC behind the card.
Having spent years building crypto neobanking infrastructure, I can tell you that one arrangement worth understanding is the corporate card / KYB model.
Here's how it can work:
A company establishes a verified business relationship with an issuing bank or card program.
The company receives permission to issue cards for legitimate business purposes, such as employee expenses or contractor spending.
A third party starts distributing those cards to unrelated consumers.
Instead of presenting them as corporate expense cards, they market them as anonymous, no-KYC crypto cards.
You receive a working card without necessarily understanding who the actual customer of record is or what agreement your card operates under.
And here is where things get interesting.
You may think you have a personal banking product, while the issuer may see you as an authorized user under someone else's corporate account.
Now imagine the issuer discovers that its corporate card program is being used outside its approved purpose.
What happens to your card?
What happens to your balance?
Who is responsible for returning your funds if the program gets terminated?
And who exactly are you going to call?
To be clear, legitimate business-card programs and limited-KYC prepaid products exist. The issue is not the absence of a selfie or passport upload by itself.
The issue is a company selling you financial access without being transparent about the underlying structure.
Moral of the story:
Before buying a “NO-KYC crypto card,” ask who actually issues it, who holds your funds, whose account the card belongs to, and what happens if the program shuts down.
Because saving five minutes on KYC or trying to hide your identity isn't worth spending months trying to recover your money.
And remember:
A Visa or Mastercard logo doesn't automatically make the company selling you the card trustworthy.
Arman retweeted
There’s a lot more to stablecoin orchestration than calling a payout endpoint.
Here are things we’ve learned about moving money onchain and offchain.
Arman retweeted
There’s a lot more to launching a stablecoin-backed card than integrating an issuing API.
Here's what we've learned.
I love how @mikebelshe challenged Claude to hack the Bitgo just to put end of this misery marketing of new model crushing all the security benchmarks
Either @AnthropicAI is terrible at building sandboxes... or excellent at marketing. (or both)
But enough with the “we created a hacking monster” games.
Do it for real.
I put this in an @BitGo wallet for you. Go get it.
100 BTC:
bc1qg4jcyumevszta3rs869v9jrf6rz9z360svp03jsl5xcryfd7xqvs4hurnq