kinemcodes

Fullstack web3 developer with almost a decade of experience. Building @buildarena, member @superteamNG #Rust #Solidity #JS github:

[kinemcodes @kinemcodes]

I still remember my first time trying to set up a Solana dev environment.
=>Install Rust.
=>Install Solana CLI.
=>Fix path issues.
=>Figure out Anchor.
=>Deal with version mismatches.

something breaks. You start over.

Hours gone… and you haven’t even written a single line of your smart contract.

Then comes the real problem.Your editor doesn’t understand your program.

Your tools don’t talk to each other.

Your team is working in silos.

Context is scattered everywhere You’re constantly switching tabs, guessing what’s wrong, and debugging things that shouldn’t even be your job.

That’s the reality for most Solana developers today.
Fragmented tools.
Broken workflows.
Slow iteration.
We built Build Arena @buildarena because of this.
A single workspace where everything just works:
Real-time collaboration with your team
AI that understands your entire codebase, not just prompts
Integrated environment for writing, testing, and shipping Solana programs.
No more fighting your setup.
No more piecing tools together.
Just open, build, and ship.

This is what Solana development should feel like.

[kinemcodes @kinemcodes]

@hexalan Hi Alan, I send you a message in your DM.

[kinemcodes @kinemcodes]

A clean interface can hide a confused workflow. Before polishing screens, trace the user’s path from intent to outcome. The gaps usually appear between those two points.

[kinemcodes @kinemcodes]

A useful test for any idea: can you explain what changed, for whom, and why it matters without reaching for jargon? If not, the thinking probably needs more work.

[kinemcodes @kinemcodes]

A useful test for any idea: can you explain what changes for the person using it? If the answer is still “nothing,” the idea needs more work.

[kinemcodes @kinemcodes]

RBAC bugs often live at the edges of the role table. I test object ownership, tenant context, exports, and background jobs separately. A permission check that works in the controller can still be missing from a worker.

#Security

[kinemcodes @kinemcodes]

AI redefines the world “Secure”, it ensures not only the concept is but other things that are less looked at. But anyways it lets you know after you got hacked 💀

[vitalik.eth @VitalikButerin]

It's an increasingly common take that AI hacking means cybersecurity is doomed.

I disagree. I think cybersecurity is naturally defense-favoring once people get their shit together. And anyone who continues to hold cryptocurrency (including me, ~90% of my net worth) is implicitly making that bet.

Here's why I am making that bet.

First, the oversimplified punchy one-line statement:

If AI can prove Navier-Stokes and FLT, then AI can prove the statement "this program is secure" as a mathematical theorem. Even if the program is very complicated.

Now, the nuance:

(See also: https://t.co/6YPWgVT7rO )

The word "secure" is hiding all kinds of skeletons in the closet in terms of what it actually means. What does it mean for Signal (the encrypted messenger) to be "secure"?

The most basic definition you might think of is: no one who doesn't hold the recipient's secret key can read the contents of the message.

But:

* Did you remember to include _other_ critical forms of security? Can the adversary forge messages? Can the attacker prevent messages from reaching the recipient? Can they cause your client to crash by sending malformed messages?
* Have you made sure that your model of the adversary includes attackers that interfere with the protocol actively and not just passively? And attackers that interfere by replaying messages to you or the recipient that either of you sent over the wire at any point earlier?
* What if the adversary hacked (or _is_) the Signal server?
* How did you learn which public key belongs to the recipient in the first place? What if that process was tampered with?
* What if your device gets hacked at some point in the past or future - is your message still safe then?
* What if your key leaks because of a bug in your operating system? Or because you got a bugged version of the Signal client? Or what if the database is corrupted?
* Or the libraries, interpreter or compiler of the programming language you wrote it in?
* What if your key leaks because tiny perturbations in perceptible signals generated by the hardware leak mathematical relationships that can extract the key a few hundredths of a bit at a time?
* Are you hiding the *size* of the payload? Does that matter?
* You're definitely not hiding the identity of the sender and the recipient, and the exact time each message was sent (think: not just time-of-day, but also time deltas between one message and the next). Is that not enough to deduce a lot of important facts about what relationships you have, and what *kinds* of conversations you are having?

So ... even definitions can be over a thousand lines of code, and need deep careful thought to figure them out.

Working on making definitions more human-readable is of extreme importance - it's perhaps the only "high-level language" that matters right now.

But even still, even despite all of the above, for security-critical components, the definition is a much smaller attack surface than the implementation. Verifying that the definition is adequate is a much more tractable task than scanning over the code directly - and can become even more tractable with better tooling.

Definitions are also _additive_: if two groups have two different definitions A and B, then, well, you can just prove that the program satisfies both A and B. Code is not additive in this way: if a program is A + B, a bug in A _or_ B can sink the whole thing. Definitions are additive. And if you can't satisfy A and B at the same time, you've isolated the most important philosophical issue for your project to spend its next few weeks grappling with.

Sometimes, definitions are not much smaller than the implementation - UI components might be one example. But for many of the most critical components - message-passing protocols, sandboxes, cryptography like SNARKs and FHE - the asymmetry is real.

Historically, a large class of failures with this approach have come from people only verifying a small portion of their code, that they self-declared to be the security-critical portion, and ignoring the rest - and it turns out that something in the rest of the code is security-critical too.

This was reasonable back when verification was difficult and scarce. The solution today: sorry, you have to verify over literally your entire program, including database, networking, any caching layers, everything. Modern AI can do it.

So it's not about "the good guys find all the vulnerabilities before the bad guys do" - that could maybe work too, after all a finite program only has a finite number of vulns, but it's riskier - it's specifically an asymmetric strategy of making code that is much more resilient in the first place.

This is the kind of direction that Ethereum is going in for the next few years. There is no future for blockchains - especially blockchains with scalability and privacy - without doing this. We need to make software actually secure. And we have already made a lot of progress.

[kinemcodes @kinemcodes]

@shivanipod @lennysan Hi @shivanipod I am unable to DM you, it is closed

[Fleets @usefleets]

Congrats to all the winners and honorable mentions.

This is the largest crypto hackathon yet with 2,857 project submissions. That's a seriously deep field.

We poured our hearts into this throughout the hackathon and after, and getting interviewed out of that many builders is something we hold dearly.

Shipping continues, as on-chain fleet financing won't build itself.

[Emmanuel @5Talker_]

Congrats to all the winners and honorable mentions from the @colosseum Frontier Hackathon, the largest one yet by participation.

I've been at @techexpohq (African Tech Expo, ATE 2026) for the past two days, which is why this is coming late.

Things landed differently than I'd hoped, but getting to the interview stage is still something to be proud of (right?).

With @blockride_xyz (v1 of the idea), we got honorable mention at both Hyperdrive and Renaissance, without ever reaching an interview. Our first submission used NFTs for tokenization, which we later realized had real limitations. Second time around we switched to SFTs, which came with their own constraints too. After that we stepped away from hackathons entirely and just kept building on our own, at our own pace, with no deadline pushing us (slow and probably not steady).

Around March this year, with no hackathon in mind at all, I started redesigning the whole idea from scratch. I only found out about the Frontier Hackathon about two weeks before it kicked off, and decided to bring this new version into it. This is a completely different approach from what we built for Blockride, rebuilt from the ground up in about a month, and two weeks into the hackathon we had to redesign the entire model. Proud of what we managed to put together in that window.

This time around, we got to the interview stage, and next time, we're definitely gunning for the win.

Thanks to @DefiSolar and @c2yptic for never getting tired of me running this idea past them over and over.

Shipping continues.

[kinemcodes @kinemcodes]

@SolanaEvents @solana I’m in BREAK-POINT MODE

[kinemcodes @kinemcodes]

@CapinUK @solana @MacroMate8 Nice, I hope you have multiple rooms to accommodate us all,

❤️

[kinemcodes @kinemcodes]

@euniceajim Unrelated but, If an entire economy is $4T and a man worth over $1T,

Hmmm

[kinemcodes @kinemcodes]

@nikkideyy I love the Mountain View.

That’s real meaning of feeling on top of the world 😂

[kinemcodes @kinemcodes]

@joshyote @solana_devs Fractional ownership of a RWA with monthly dividends

[kinemcodes @kinemcodes]

@solana_sailor @colosseum @solana @SolanaFndn @superteam @mxmnci @mrinko @SolanaFloor @toly @usefleets just shipped a solution to Nigerians transportation crisis on Solana , LFG

[kinemcodes @kinemcodes]

@sridharfyi SF

[kinemcodes @kinemcodes]

@solana_devs @SolanaEvents Or ask them what they’ve built

[kinemcodes @kinemcodes]

@mrinko @joshyote The feel when I see a mail from colosseum saying it’s from Micheal 😎

[kinemcodes @kinemcodes]

On point.

[Fleets @usefleets]

https://t.co/fx5kHFcXP7

[kinemcodes @kinemcodes]

@sridharfyi @16vchq Blockchain coding tool