Joined November 2025
97 Photos and videos
Pinned Tweet
We are incredibly proud, and participating in the @Colosseum Hackathon is another milestone for DarkDrop. I want to thank our community all the feedback and support. Good luck to all the judges as they review the entries. To all the other participants, good luck, and keep building. $DarkDrop
14
8
42
2,739
DarkDrop retweeted
Just applied to @MonkeDAO's monkefoundry with @darkdrop_sol. zk private transfers on solana, credit note architecture, no visible transfer instruction on-chain. sol usdc live, multiple published audits, colosseum frontier submitted. app in the works. solana needs privacy infra. let's build.
5
8
19
321
DarkDrop retweeted
Next Frontier categories I looked at: Payments/Fintech Security/Privacy 👇 Smaller than the previous macro areas, but closely connected → moving money better, protecting users and making privacy usable Payments/Fintech seems to be forming around: • Simple private payments Example: @looftapay, payments by username, email or X handle • Internet-native merchant payments Example: @paymento_io, a non-custodial x402 gateway for real commerce • Machine and agentic settlement Example: @ryvonetwork, a clearing layer for machine payments on Solana Security/Privacy seems to be forming around: • Private transfers Example: @darkdrop_sol, unlinkable private transfers on Solana • Continuous security checks Example: @JelleoLabs, continuous Solana program audits • Inheritance and recovery paths Example: @Heresprotocol, an autonomous death insurance protocol on Solana • Reputation and trust layers Example: @KRED_info, a reputation layer for crypto KOLs • Threat detection before users interact Example: @Sentrii_io, security analysis for links, repos and wallet interactions As more value moves onchain, payments, privacy and security stop being optional. What interesting projects did you find in these categories?
Next Frontier category I looked at: Infra 👇 279 projects entered this macro area across Developer Infrastructure, DePIN, Interoperability & Bridges, Validator/Staking Infra and ZK/Crypto Research After scrolling through the projects, this side of Frontier seems to be forming around a few clear infrastructure layers: • Prediction markets need deeper infrastructure Example: @predikt_gg, building infrastructure for prediction market data, liquidity and execution • Builders need Solana-native workbenches Example: @DaemonTerminal, an AI-native terminal and operator console for Solana • DePIN needs real-world data networks Example: @captur_go, a people-powered network for geospatial and location intelligence • Privacy needs encrypted execution Example: @encrypt_xyz, privacy infrastructure for Solana apps • DePIN needs more ways to connect real-world assets to onchain ownership Example: @hivebits_io, turning real bee farms into co-owned digital assets • Agent apps need payment and execution infrastructure Example: @agenttech, infrastructure for agent payments and execution • Onchain apps need notifications that do not leak user identity Example: @useheraldmail, privacy-preserving alerts for Solana apps Infra is usually less visible than apps, but a lot is clearly moving underneath And sooner or later, every great app needs strong infrastructure What Frontier infra project are you watching most closely?
35
22
110
15,105
DarkDrop retweeted
Solana Security Standard is 31 SOL-0XX rules from real audits bounty wins. Runs in your editor, CI, claude, cursor, semgrep - you write code, it flags the bug before it ships. github.com/Copenhagen0x/sola…
Currently running the jelleo ruleset for $DARKDROP. let's see. @JelleoLabs
10
9
43
11,066
Big progress on the $DarkDrop app. Various tests are currently being conducted to make DarkDrop even more user-friendly. Open the app, paste a wallet, hit send. On the other side, funds just show up. No claim codes, no copy-paste, nothing extra for whoever's receiving. The whole flow. send → it arrives → it lands in their wallet, privately, recipient unlinkable on-chain. Under the hood it's the same credit-note model #DarkDrop already runs, it will be a one tap experience on top of it and added a stealth layer so the recipient's address stays unlinkable. The cryptography runs on the phone itself, no servers in the middle. Real device testing and polish next, nothing to download yet. But the hardest part is done. More information on this will be available soon. $DarkDrop
6
13
26
513
This is the strongest fix of the day. Ran 8 adversarial cases against the relayer after the hardening pass, all 8 now fail exactly where they should. Replay attempts rejected. Wrong / missing memo rejected. Over-transfer rejected. Decoy instructions rejected. Destination validation enforced. Exact instruction count enforced. The important part isn’t just that the happy path works. It’s that the abuse paths don’t. That’s the difference between works in demos and something hardened for adversarial environments. Follow our path to Mainnet. Max privacy with Solana and USDC payments without on-chain traceability. 🔒🔒🔒 $DarkDrop
3
9
19
445
What is our typical Sunday like? Over the next while you'll see a batch of issues open up on the $DarkDrop repo. That's intentional, and it's a good thing. On GitHub an issue just means a tracked item: a finding, a hardening task, a note. It doesn't mean something's broken. It's the opposite, it means every piece of QA and review is getting logged in the open instead of living in someone's head. This is a security and QA pass ahead of mainnet. Most of what's getting filed is hardening and defense-in-depth, caught on purpose by digging for it, not live problems. More issues being tracked = more eyes = a tighter protocol. Building this in the open, nothing swept under the rug. Check out out GitHub: github.com/hitman-kai/darkdr… The move isn't "we have no bugs." The move is, find them on purpose, write every one down, and close them with a test that proves it's fixed. $DarkDrop's whole backlog is public, findings, repro steps, acceptance criteria, the works. knocking them off now. tracking documenting beats vibes every time. What we build is completely transparent, but your privacy isn't with DarkDrop. Try DarkDrop for yourself now. DarkDrop.app $DarkDrop
2
12
20
440
This time, we need your help to take DarkDrop to the next level. Tag different projects/people or repost this message to help us reach more people. A message from our Dev: I'm opening a permissionless trusted-setup ceremony for $DarkDrop, and we need contributors. Here's what that means and why it matters. DarkDrop uses Groth16 zk-SNARKs to make transfers private on Solana. But every Groth16 system has a catch: the proving keys can only be generated alongside a piece of secret randomness, "toxic waste." Anyone who keeps that secret can forge proofs and mint value out of thin air, silently. It's the single biggest trust assumption in any SNARK protocol. The fix is a multi-party ceremony. Instead of one machine generating the keys (and you having to trust it deleted the secret), the computation is passed from contributor to contributor. Each one mixes in their own randomness and destroys their share. The math guarantees that as long as just ONE contributor is honest, the toxic waste is unrecoverable, and the system is sound. That's why we need you, and why more is better. With one contributor, you have to trust them. With dozens of independent people, an attacker would have to compromise every single one to break it. Each honest contributor permanently strengthens the security of every proof DarkDrop will ever make. You're not doing us a favor, you're making the protocol trustless for everyone, including yourself. How it works: • It's permissionless — no roster, no gatekeeping. Anyone can contribute during the open window. • A contribution takes ~5 minutes: run one command, open a PR. Full guide in the repo. • Your secret never leaves your machine. For the security-conscious, a freshly-booted or air-gapped environment is ideal. • We finalize with a publicly-committed drand randomness beacon (run by the League of Entropy), picked in advance so no one (us included) can grind the outcome. For context: the Phase-1 setup we build on had 54 contributors. We'd love to give DarkDrop's Phase-2 a setup that's just as strong and diverse. The exact window dates and drand round will be posted in CEREMONY.md (our canonical public record). Follow for the go-live, and read the contributor guide here: github.com/hitman-kai/darkdr… If you care about privacy, ZK, or Solana, this is a high-leverage 5 minutes. RTs genuinely help us reach more independent contributors. Thanks in advance for taking the time to read, repost, and tag projects or people who might be interested. Much appreciated! $DarkDrop
3
14
23
476
Compiling isn't testing, and the most dangerous code is the fix you're most sure about. $darkdrop
Shipped a round of security hardening to $DarkDrop today. I ran a deep self-audit of the on-chain program and worked through 7 findings, relayer DoS hardening, a gasless-relayer edge case that could strip a user's ability to withdraw, deploy-process safety, plus a few maintainability/perf fixes. All 7 are fixed, deployed, and verified live on devnet across both SOL and USDC. But the interesting part. I almost shipped a bug in my own fix. One finding was about a value ("salt") the relayer could swap out, breaking a user's withdrawal. The obvious fix, read the salt from on-chain state instead of trusting the caller, looked correct and compiled cleanly. It would've bricked every MAX-PRIVACY withdrawal. The privacy pool intentionally stores a decoy salt on-chain; the real one only exists inside the ZK proof and is known only to the recipient. My clean fix would've checked the decoy, rejected valid pool withdrawals, and locked funds. I only caught it because I refused to trust it compiles. I spun up a local validator and ran the full recursive-privacy flow end-to-end: deposit → hidden claim → pool deposit → hidden pool claim → withdraw It failed exactly where the decoy salt lives. Real fix: try the on-chain salt first, then fall back to the caller's. Works for both standard and pool notes. Re-tested end-to-end on SOL USDC, then deployed. The lesson I keep re-learning are compiling isn't testing, and the most dangerous code is the fix you're most confident about. DarkDrop is still devnet this was an internal hardening pass, not a replacement for a real third-party audit. But every fund-touching path now has a live end-to-end test behind it. github.com/hitman-kai/darkdr…
7
14
374
DarkDrop retweeted
May 28
After two days reviewing more projects vying for the @solana Frontier Hackathon by @colosseum, here's another list of 16 more projects. I left many out; I'll have to make another list All very interesting, some with original ideas within the ecosystem, all with natural builders—this is only possible at Solana - @TradeFighters : Trading as a game - @TibaneLabs : Tools & utilities - @sol_pollinet : Offline transactions for wallets and dApps - @NoiseLabz : Music Platform - @EZPZFi : Market Predictions - @Clearsig_xyz : Self-custody wallet - @Sentrii_io : Hunting and Investigation AI Agent - @usebido : Monetization adds layer with AI Agents - @useHeysolana : Voice powering solana transactions - @darkdrop_sol : Anonymous Payment Infrastructure - @fraudsworth : The worlds first Market Intelligence Liquidity Fund - @DaemonTerminal : AI-native Solana dev environment. - @swappadex : Multi-Swap on Solana - @Lid_onchain : Creator commerce - @Rektofun : The PvP battleground for predictions Shoutout for all teams, builders of this list, tag below yours favs projects/builders of this Hackathon, i want know more
May 26
Here's a list of some projects vying for the @solana Frontier Hackathon for @colosseum I love the variety of projects, ideas, devs, and builders I've seen in these 16 projects, and they're only 16 out of 2857! This is absolutely insane - @cluckrush : Skill based PvP betting - @basedbidx : Token launch infrastructure - @SourFinance : Perps Dex - @noderails : Crypto Payment Infrastructure - @Versusonchain : 1v1 trading eSport - @DefiMarkets : Operating system for onchain strategies - @event_mesh : Enabling agents that listen - @myStableCorp : BusinessOnchain - @YontaLabs : Solana Indie Validator - @DeSocial_app : Decentralized Social Attention & Interaction Layer - @nomadfinanceio : Better Market Making for Public LPs - @notdotmarket : Pre-markets for the ICM era - @BlinksLabs : Private wealth investment strategies - @Heresprotocol : Privacy-Preserving death insurance Protocol - @VeerTx : Private SOL and USDC payments What other projects are participating in Frontier that are waiting to be discovered? Tag them below or mention the founder. I want to keep discovering more in Solana
38
28
107
11,786
For privacy enthusiasts, here’s a video that speaks for itself. For those familiar with DarkDrop, we’ll explain it again; for those who aren’t, we’re taking crypto privacy to a whole new level. In addition to Solana, USDC is now also available. On-chain transparency is a feature that enables verifiability. For payroll, OTC, and most of the reasons people actually move money, it’s like a glass piggy bank. Try it to believe it. $DarkDrop
4
15
19
358
$DarkDrop USDC integration end to end on devnet now live on Darkdrop.app Most ZK privacy on Solana follows the UTXO/note model (Privacy Cash, Light Protocol). DarkDrop uses credit notes, a separate claim stage between deposit and withdraw. Now extended to USDC besides Solana. ✓ 18 commits across program/relayer/frontend ✓ Verified live with Circle devnet USDC ✓ Recipient wallet never signs or pays fees We building real privacy.
6
11
28
766
Can u spot $DarkDrop? 👀
2,857 projects entered Colosseum Frontier I put them all in one image Looks like an entire ecosystem But it’s a single hackathon Build on Solana.
3
1
16
631
Check out the sneak preview of the USDC feature below. Soon, users will be able to choose to send Solana or USDC via DarkDrop. Of course, with max privacy function. This feature is taking longer than expected, and testing is currently in full swing. USDC will be available any moment now. Stay tuned. $DarkDrop
6
11
26
639
Are u guys summer ready!? DarkDrop Summer Solana Summer Privacy Summer Loading.......
4
10
26
498
DarkDrop dev @HitmanNoLimit has been building for 16h straight and debugging. USDC coming soon to DarkDrop. $DarkDrop
4
9
29
622
USDC payments coming soon to DarkDrop.
Foundation done, the mint provisioning flow is complete. initialize_mint_config initialize_mint_trees initialize_mint_vault The next instruction create_drop_spl is the first user-facing one, actually moves USDC into the vault. github.com/hitman-kai/darkdr…
6
6
24
713
DarkDrop is building the next generation of private transfers on Solana — enabling anonymous, encrypted “dead drops” with zero tracking and browser-native privacy tools. Using client-side encryption, burner wallets, and secure claim codes, DarkDrop allows users to send assets privately without exposing identities or transaction trails. Key Links: * Website: darkdrop.app *GitHub: github.com/hitman-kai/darkdr… Built on Solana. Designed for privacy. Ca: 6wKRRP1c2gkWESch723bmgCWiBYiYvn4krspZXdApump $DarkDrop
2
11
29
645
👇🏼👇🏼👇🏼
Privacy protocols come in two flavors: Custodial (Vanish, OTC desks): you deposit, they hold, they execute. Trust the operator. Non-custodial with relayer #DarkDrop: you deposit on-chain, generate a ZK proof that binds the recipient, the relayer just submits. Operator can't steal. The difference is everything. DarkDrop's relayer signs and pays gas. The recipient is locked into the proof itself. Worst case the relayer can do is refuse to submit, and then you submit the tx yourself, gas in hand. This is what "gasless but non-custodial" actually means.
1
4
19
806
Great breakdown from dev. Check it Try it Believe it $DarkDrop Darkdrop.app
Solana privacy tweets mention ZK ElGamal a lot. Worth being clear ZK ElGamal is real cryptography built by serious people at Anza. It's also been disabled on mainnet since June 2025 after two soundness bugs. That's not a knock on the work, finding bugs is how cryptography matures. But if your privacy protocol depends on a native program that can be turned off, your privacy depends on a feature flag. $DarkDrop uses Groth16 Poseidon over BN254, verified by code we ship and audit ourselves. No native program dependency. No feature gate. The cryptography lives in our program. That's the difference. 😉
5
4
23
732