₿₳₹₮ Moonkey intern #7 (@CryptoBart79) header
₿₳₹₮ Moonkey intern #7 (@CryptoBart79) profile picture

$moonkey intern #7 NFA-DYOR

MOON 🇳🇱
Joined October 2025
Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)Photo by ₿₳₹₮ Moonkey intern #7 (@CryptoBart79)
Good morning $moonkey 🌅 While they were sleeping, Moonkey was already working on the escape plan. The gates are open, the apes are free, and there’s only one destination left… 🌕🔑 THE MOONKEY INTERNS ARE READY!!!! JUST DO IT. 🌕🔑 @a1lon9 @CupseyToken
🤖 Made with AI
10
21
2
43
1,142
₿₳₹₮ Moonkey intern #7 retweeted
Status check on MagicBlock USDC: it’s still an internal mainnet beta for allowlisted wallets. What exists: a separate workflow for wallet-approved USDC send, deposit, withdraw and Payroll, with its own operation and recovery context. It’s an additional engine, not a replacement for Privacy Cash. Before we open it to everyone, the remaining work has to show results: → funded Payroll acceptance testing completed → at least 10 successful internal mainnet batches → zero duplicate or lost payments in that set → fee accuracy and recipient settlement verified → remaining release-readiness findings resolved One distinction we hold ourselves to: “source confirmed” doesn’t mean “recipient paid”. Settlement has to be proven. duskmoth.xyz/tools
7
8
1
15
543
₿₳₹₮ Moonkey intern #7 retweeted
Duskmoth × MagicBlock Mainnet Payroll Verified Duskmoth’s USDC payment route built with @magicblock has completed a real three-recipient payroll test on Solana mainnet. What we verified: • Three payments with different amounts, each confirmed at its recipient. • One existing Moth Pass used for the entire batch—not per recipient. • Stop-and-resume recovery without repeating the first payment. • Observed source costs stayed within the reviewed limits. On-chain payment proofs: ① solscan.io/tx/HdZehdQ4gESYwX… ② solscan.io/tx/PWZeCMsR7GgzaV… ③ solscan.io/tx/KaHgXHQkRrDU2f… MagicBlock adds a separate USDC route alongside Duskmoth’s existing Privacy Cash integration.
11
12
19
648
₿₳₹₮ Moonkey intern #7 retweeted
update on $DMOTH 🦋 already did a 2x since my initial call but this one deserves way higher imo magicblock just liked their post about the USDC integration, the integration has already been running for 4 days btw. KILLER TEK being shipped here: • private SOL transfers powered by Privacy Cash • private USDC through MagicBlock's rollup, currently in mainnet beta • AI-assisted payments and private payroll for up to 20 recipients • non-custodial execution, your wallet signs everything • public SDK with 29 passing offline tests • 3M $DMOTH already burned, with more burns tied to Moth Pass usage the dev also mentioned supporting the chart through buybacks, while continuing to build for the long haul. feels like they're not stopping at one privacy engine. they're working toward multiple payment routes, wallet integrations and recurring payroll. $DMOTH dip here is good bid imo 11k, great r/r here bid on builders. 9ueEeBuYUc9X1GrNCyWHbKGnHJq1kaD2nvDapDsMpump
Status check on MagicBlock USDC: it’s still an internal mainnet beta for allowlisted wallets. What exists: a separate workflow for wallet-approved USDC send, deposit, withdraw and Payroll, with its own operation and recovery context. It’s an additional engine, not a replacement for Privacy Cash. Before we open it to everyone, the remaining work has to show results: → funded Payroll acceptance testing completed → at least 10 successful internal mainnet batches → zero duplicate or lost payments in that set → fee accuracy and recipient settlement verified → remaining release-readiness findings resolved One distinction we hold ourselves to: “source confirmed” doesn’t mean “recipient paid”. Settlement has to be proven. duskmoth.xyz/tools
6
4
9
319
₿₳₹₮ Moonkey intern #7 retweeted
Duskmoth uses different technologies for different jobs. Mixing them up leads to wrong assumptions, so here’s who does what: Privacy Cash provides the shielded SOL and USDC route. Helius handles public-chain data and RPC. Scorechain checks addresses against sanctions lists. It’s not an AML risk score and not an anonymity certificate. Anthropic powers AI planning. A plan is a draft for you to review. The AI can’t move funds. MagicBlock is a separate USDC engine, still in internal beta. It doesn’t replace the Privacy Cash balance. Moth Pass gates optional premium actions. The token behind it is an ordinary public SPL token, not a privacy coin. None of these names is a guarantee. No provider, privacy score or health check proves a payment was anonymous or settled correctly. That’s why every payment still ends with your own review and your own signature.
9
8
14
487
₿₳₹₮ Moonkey intern #7 retweeted
What does a Moth Pass actually do? It unlocks optional premium actions. That’s it. You don’t need one to shield, send or withdraw. Current uses: → AI Pack: 1 pass per generated plan. A plan is a draft and moves nothing → Private Payroll: 1 pass per batch, not per recipient. Up to 20 people → Split withdrawal: 1 pass for the operation, with relayer fees per part → Pre-withdraw privacy check: free A plan and the payroll batch that runs it are two separate actions, with two separate passes. You get passes by burning $DMOTH. The burn is public and permanent. The tokens are destroyed, not sent to a team wallet. Two habits that matter: tap Back up passes right after a burn. A usable backup is a bearer secret, so treat it like cash if issuance stops after the burn, use Resume purchase. Never burn again duskmoth.xyz/pass
3
6
14
206
₿₳₹₮ Moonkey intern #7 retweeted
Two days ago we listed two open SDK tasks. Both shipped in v0.2.2. Typed responses. health(), config() and relayerConfig() now return clear TypeScript types. If a field doesn’t come back, it stays “unknown” in the types, never quietly treated as “ready”. Your app shouldn’t assume a feature exists because a field went missing. Offline browser example. A page plus a mock API on one localhost address. It covers five scenarios: available, disabled, missing fields, HTTP 503 and broken JSON. No wallet, no credentials, no transactions. npm run example:browser → open 127.0.0.1:8788 ✓ 38 tests on Node 22 and 24 ✓ strict TypeScript checks pass ✓ release archives scanned for credentials, checksums match Distributed through GitHub Releases, not npm, and not audited. Everything’s on the new Developer Hub: duskmoth.xyz/developers Release: github.com/duskmoth-dev/dusk…
3
4
2
11
1,256
₿₳₹₮ Moonkey intern #7 retweeted
Private payments raise a practical problem: how do you keep your own records without handing them to someone else? Local Activity is our answer. It’s an optional journal stored only in your browser. Turn it on, and the operations you run in Duskmoth get recorded: → filter by type and status → search by address, amount or signature → export or import JSON → check a recorded signature against the chain, read-only, without resending anything It starts off. It doesn’t scan your past. It only records what happens after you opt in, on this browser. Two honest limits: a journal entry is a local record you can edit, not a receipt or proof of payment “signature confirmed” doesn’t prove who got paid or how much Exports can contain addresses and amounts, so keep them private. duskmoth.xyz/activity
3
6
14
281
₿₳₹₮ Moonkey intern #7 retweeted
Your wallet is louder than you think. Every payment you make on Solana is public: who you paid, how much, and when. Anyone can follow it. Duskmoth gives you a quieter way to move money. Here’s the full walkthrough, filmed on the live app. → Type what you want in plain words: send 0.03 SOL to … privately → See everything before it happens: the recipient, fees, and exactly what they’ll receive → Every address is screened first. If the check can’t run, nothing moves → Your own wallet signs. We never hold your keys New in this update: Payment Requests: share a link or QR to get paid. Nothing is signed until the payer approves it. Local Activity: an optional journal that stays in your browser only Moth Pass: burn $DMOTH for passes that can’t be linked back to your burn AI Pack + Private Payroll: plan and pay up to 20 people privately in one batch Open code: SDK 0.2.2, public on GitHub Start with a small amount, read the preview, and decide for yourself. Check how loud your wallet is 👇 duskmoth.xyz
8
10
17
416
₿₳₹₮ Moonkey intern #7 retweeted
Duskmoth isn’t just a repo. It’s a working app. You type a payment in plain words, and Duskmoth turns it into a preview: recipients, the full cost, and which privacy engine runs it. Every destination is screened, and if the check can’t complete, nothing moves. Your own wallet signs. We never hold keys. Open source is how we keep ourselves honest about that. The SDK, docs and limits are public. Releases come with test results and known gaps. Experimental work is labeled experimental. The best way to judge it is to use it: Go to duskmoth.xyz Connect your wallet. Check your wallet’s privacy score. Try a small private send and read the preview before you approve. Then tell us what broke, what was unclear, or what you’d want next.
6
9
15
230
₿₳₹₮ Moonkey intern #7 retweeted
Next on the SDK: → Complete TypeScript response types. Today some responses are typed loosely. The goal is that your editor knows the exact shape of a quote, a plan or a payroll status without you checking the docs. → An offline browser integration example. It’s a minimal reference UI showing how to wire the SDK into a frontend while signing stays in the user’s wallet. Both are open as contributor tasks. If you write TypeScript or build wallet UIs on Solana, pick one up. Issues are labeled in the repo. Small, well-scoped PRs are welcome, and we review everything. github.com/duskmoth-dev
6
10
2
17
682
₿₳₹₮ Moonkey intern #7 retweeted
Build first. Announce second. In privacy, trust is the product. One overpromise costs more than ten features earn. So we run the same loop every week: 01 Build 02 Test 03 Ship small 04 Label it honestly: live, beta or exploring 05 Write the changelog with exactly what shipped What that loop has produced so far: ✓ 2 engines ✓ Private USDC beta ✓ Payroll with recovery ✓ AI Pack ✓ Blind-signed Moth Pass ✓ Public SDK ✓ A 3M real burn ✓ Weekly changelogs The roadmap from here is bigger: more engines, multisig payroll, recurring payments, routes inside wallets, and the app repo going public. We’ll get there the same way. Small team, still early, shipping every week. $DMOTH · duskmoth.xy
5
5
1
11
313
₿₳₹₮ Moonkey intern #7 retweeted
Duskmoth SDK has been submitted to Awesome Solana OSS under Web Tooling. The goal: help Solana developers find usable source code, run our examples, inspect the implementation, and contribute improvements. SDK v0.2.1 includes a dependency-free JavaScript/TypeScript HTTP client, runnable examples, and 29 passing offline tests. It exposes Duskmoth APIs for Moth Pass, privacy estimates, AI planning, and payroll authorization it does not sign or broadcast transactions. Submission is awaiting review: github.com/StockpileLabs/awe…
4
8
1
16
947
₿₳₹₮ Moonkey intern #7 retweeted
We’ve updated Duskmoth’s submission to Electric Capital’s Open Dev Data taxonomy, covering our open-source application, SDK, and documentation under Solana. Why submit? So researchers and developers can discover our repositories and, if accepted, include their public development activity in ecosystem analysis. Submission is open and awaiting review: github.com/electric-capital/…
7
10
17
577
They told me I cannot make even 10 devs in same room, I told them go f**k yourself! I have 152 different teams in my Networking Room, and more are coming! The more I grind the more value it brings to teams and me. Sure some of them died, it`s crypto, I personally started a different company 15 years back and it failed, I thought I see a purpose of it, but market didn't... but losses don`t define your winnings. You are told to lay low at school, at work, at life... It`s you against the crowd! Always the different ones win!
🦋 Expansion 🦋 Team 152 🦋 @duskmoth_app What is Duskmoth: Duskmoth is AI assisted private payments on Solana: you type what you want, review the full cost, and your own wallet signs. Live today are private SOL sends through a ZK shielded pool, AI Pack plans for SOL and USDC, Moth Pass powered by blind signatures (RFC 9474), sanctions screening that fails closed, and a wallet privacy score. In mainnet beta: private USDC on MagicBlock private rollup and Private Payroll for up to 20 recipients that never pays twice, backed by 117 tests. Welcome $DMOTH to my room
13
10
31
1,320
🦋 Expansion 🦋 Team 152 🦋 @duskmoth_app What is Duskmoth: Duskmoth is AI assisted private payments on Solana: you type what you want, review the full cost, and your own wallet signs. Live today are private SOL sends through a ZK shielded pool, AI Pack plans for SOL and USDC, Moth Pass powered by blind signatures (RFC 9474), sanctions screening that fails closed, and a wallet privacy score. In mainnet beta: private USDC on MagicBlock private rollup and Private Payroll for up to 20 recipients that never pays twice, backed by 117 tests. Welcome $DMOTH to my room
13
11
2
34
2,817
₿₳₹₮ Moonkey intern #7 retweeted
Today you use Duskmoth at duskmoth.xyz. The next thing we’re designing is a Duskmoth route inside the wallets people already use. The route: 01 The wallet asks us for a quote. 02 We answer with the full cost, estimated time, and which engine would run it. 03 We screen the destination. If screening can’t run, we return nothing and the wallet just doesn’t offer us. 04 We hand back an unsigned transaction. 05 The user signs in their own wallet. Keys never leave it. 06 The wallet tracks status until it settles on Solana, with a receipt. Before it ships anywhere, four things have to hold: screening that fails closed, fees shown in full, an honest trust label, and a Solscan receipt. If we can’t meet all four, we don’t ship there. It’s a design, not shipped yet.
5
8
2
14
537
₿₳₹₮ Moonkey intern #7 retweeted
Not a roadmap. A changelog. Everything we’ve shipped in the last two weeks is either usable or checkable today. No “soon”, no teaser. → Moth Pass, rebuilt. Burn $DMOTH and get a pass. One pass covers one AI Pack plan or one Payroll batch. Passes use blind signatures, so a pass can’t be tied back to the burn that created it. → AI Pack with USDC plans. Describe what you want, see the full cost, approve it yourself. → Private Payroll. Up to 20 recipients per batch. You can refresh and resume, and nobody gets paid twice. → Private USDC in mainnet beta, built on MagicBlock’s private rollup. → 3,000,000 $DMOTH burned for real with BurnChecked. Check it on Solscan. → SDK v0.2.0, public on GitHub. Six things in two weeks from a small team. Every one has an honest label: live, beta or on-chain. This is the pace we plan to keep.
3
6
11
366
₿₳₹₮ Moonkey intern #7 retweeted
Two requests keep coming in. One is “can payroll just run every month?” The other is “can my agent pay for things?” Both are on the research list. The rule we’re keeping for both is that the prep can be automated, but the approval can’t. For recurring payroll, we’re looking at Solana’s Subscriptions & Allowances program for monthly schedules. Duskmoth prepares that month’s plan with recipients, amounts, the maximum upfront cost and the engine. For agent payments, Pay.sh gives AI agents a payment rail. An agent can request a payment, and Duskmoth turns the request into a plan. Both paths end the same way. A human reviews it, can edit or cancel it, and approves it. Then the wallet signs and the payment settles. The agent prepares, a human approves, and the wallet signs. Nothing goes out on autopilot, and nothing is resent without you. This fits what AI Pack already does with $DMOTH Moth Pass today. It just adds schedules and agents as new ways a plan can start. Exploring, no dates.
4
10
1
16
625
₿₳₹₮ Moonkey intern #7 retweeted
Two smaller pieces we’re researching, both about making a plan less fiddly. The first is swap, then pay. Say you hold SOL and the recipient wants USDC. Today that’s two separate steps in two separate places. The idea is one reviewed plan: a Jupiter route with the rate, slippage and fee shown upfront, then a private USDC send through the routed engine, all under one approval and one receipt. The second is checking without seeing, which is research only. Arcium runs computation on encrypted data with MPC. One example we’re thinking about: checking a payroll batch for totals, limits and duplicates without salaries ever being readable on our server. The Arcium part stays research until the use case and the cost both make sense. We’d rather say “not yet” than ship a demo nobody needs. @JupiterExchange @Arcium
6
8
12
373
₿₳₹₮ Moonkey intern #7 retweeted
What comes after MagicBlock: the privacy stack we’re researching for Duskmoth Right now Duskmoth runs two engines. @theprivacycash covers SOL through a ZK shielded pool, and MagicBlock’s Private Ephemeral Rollup covers USDC in mainnet beta. Two engines is a start, not the finish. The thing we care about most is never depending on one protocol. When deposits paused on one engine, the app kept working because the router had somewhere else to go. That’s the design: you pick the payment, the router shows you which engine fits, what it hides, what it trusts and what it costs, and you approve. Here’s what we’re exploring next. None of it is live in Duskmoth yet, and there are no dates. @Helius Privacy (Rings). A ZK UTXO layer that can hide sender, recipient, asset and amount, settling in one Solana transaction. We already run on Helius infrastructure, so this one fits naturally. It’s still devnet-only, with mainnet gated on audits and formal verification of the circuits. We’ll build against devnet and only switch it on for real money once that work is done. @cloak_ag . A ZK pool covering SOL, USDC and USDT. Two things matter for us here: USDT support, and viewing keys, so a business can open its own records to an auditor without opening them to everyone. We’re evaluating it carefully, including its audit status. Token-2022 Confidential Transfers. Encrypted balances and amounts. To be clear about the limits: sender, recipient and timing stay visible. It could still be useful for payroll where the only goal is keeping salaries private. It depends on stablecoin issuers turning it on. Squads. A team payroll batch shouldn’t hang on one person’s click. The plan is that one member prepares the batch, the team multisig approves it, and then it executes privately. Recurring payments and agent rails. Solana’s Subscriptions & Allowances program for monthly payroll schedules, and Pay.sh for AI agent payments. The rule doesn’t change for either: the agent prepares, a human approves, the wallet signs. Our SDK never signs for you. @Arcium and Jupiter. Arcium is research only for now: encrypted checks, such as validating a payroll batch without exposing amounts. Jupiter is for swap-then-pay inside a single reviewed plan. What stays the same across every engine: → screening at the edge, which fails closed → the engine and its trust model shown before you approve → no silent rerouting, and nothing resent without you Privacy on Solana is a spectrum, not a switch. ZK, TEE and encrypted amounts each protect different things. Our job is to tell you which one you’re using, honestly, every time. Not an anonymity guarantee. Sanctions-list screening, not full AML. Start small. duskmoth.xyz
8
14
5
23
1,526