cryocor retweeted
Two numbers matter in every private payment, and they aren’t the same.
Gross: the amount you start with. A payment request asks for this one.
Recipient gets: what actually lands after relayer and protocol fees.
That’s why Duskmoth shows “recipient gets” before you approve, and why a request link always says its amount is before fees.
Practical tips:
→ if someone needs an exact net amount, look at the preview and adjust before you send
→ fees come from the live quote, not a fixed number, so check it each time
→ a Moth Pass doesn’t remove fees
Small detail, but it’s where most “I sent 25, they got less” messages come from.
The next wave of AI agents won’t be judged by how smart they are. It’ll be judged by what they do when something goes wrong.
That’s where Heisto is spending its time:
→ fail closed: if Guard can’t run, the agent stops. No silent bypass.
→ no guessing: an uncertain submission is never retried automatically
→ public receipts: every run shows the Guard decision, model-call count and timestamp, without storing your message
→ signed verdicts: every arena result is Ed25519-signed and bound to the attack, score and response hash
→ read-only by design: our MCP server can look, never sign
The latest ElizaOS release shipped with 209 backend tests, 6 interface-contract tests and 4 execution paths checked in production.
Next on the bench: an adapter for Solana Agent Kit, security regression tests in GitHub Actions, and pre-signing checks for transactions.
Boring, verifiable infrastructure is what lets agents handle real value. That’s the part we’re building.
cryocor retweeted
Burn once. Spend privately.
Your browser blinds a random token, Duskmoth signs it without seeing it, and you unblind it into a valid pass. The burn is public. Which pass it became isn’t.
One pass covers an AI Pack plan or a Payroll batch. The pre-withdraw check is free.
Back up your passes right after the burn. If issuance stops, resume. Never burn again.
duskmoth.xyz/pass · $DMOTH
cryocor retweeted
Three balances. Not interchangeable.
Your public wallet is visible to everyone. Your private balance holds funds you’ve shielded. Your Moth Pass balance is premium credits in your browser, and it isn’t money.
Shield moves public → private. Withdraw moves private → recipient. Burning $DMOTH turns into passes, one way.
Seeing “insufficient”? Check which balance it means first. Don’t deposit again just to refresh it.
duskmoth.xyz/app
cryocor retweeted
Duskmoth Payment Requests: paste your address, pick SOL or USDC, set the amount. You get one link and one QR.
Creating it signs nothing. Opening it sends nothing. The payer checks the details and decides in their own wallet.
duskmoth.xyz/request
Every button in an app is a promise.
Building Heisto means making sure what happens behind each button matches what the interface says:
→ a security check actually runs
→ a stopped request stays stopped
→ a receipt describes what really happened
That gap between what the interface promises and what the backend does is what we keep closing.
cryocor retweeted
What has to be true before the MagicBlock route opens more broadly:
resolve two older submissions whose outcomes are still uncertain
complete the remaining batch-verification requirements
test wallet approval through the browser
reconcile estimated costs against actual results
complete the release security review
The three-recipient mainnet Payroll test is done. On its own, that doesn’t mean the route is ready for unrestricted public use.
We’ll post completed changes with evidence, and keep them clearly separate from what’s still planned.
cryocor retweeted
We want Duskmoth’s implementation to be easy to inspect and easy to build on.
Planned GitHub updates:
→ tested SDK changes, released with test results
→ practical examples
→ compatibility notes
→ contribution guidance
We also plan to document how the MagicBlock route works in Duskmoth, what has actually been verified on mainnet, and what limits remain.
Using @magicblock technology doesn’t imply an official partnership or endorsement. It’s integration work, and we’ll describe it that way.
cryocor retweeted
$DMOTH entered the Raid Leaderboard by community raids.
👤 @duskmoth_app
💬 Tg Group: t.me/duskmoth_app
⚡️ Points: 86
📈 Marketcap: $11.91K
#community #crypto
cryocor retweeted
Planned improvements to Payment Requests are about clarity, not automation.
The goal: when you open a request, you should understand right away
→ the receiving address
→ the token
→ the amount
→ the ways you can pay it
And one rule that doesn’t change: opening a request link must never sign or send a transaction.
A request asks for a payment. It doesn’t take one. The payer stays in control of whether to pay, and how.
duskmoth.xyz/request
cryocor retweeted
AI Pack turns plain words into a payment plan. Payroll runs it. The plan is to make the step in between much clearer.
Before you approve anything, these should stay visible in one place:
→ every recipient
→ every amount
→ estimated fees
→ the payment route that will be used
Same rule as always: an AI-generated plan is a draft, not permission to move funds. You review it, you approve it, and your wallet signs.
The handoff is the moment where mistakes are cheapest to catch, so that’s where we’re putting the work.
One working example per integration before we add more platforms. That’s the rule we’re holding ourselves to.
Next, we want real projects, not just visitors. Here’s what we’re proposing (nothing is scheduled yet):
Heisto Solana Agent Challenge
Projects bring their own agent, set the targets and limits, and get attacked through a defined path with the owner’s permission. Findings get fixed, the agent is retested, and the before/after report is published only if the owner agrees.
Build a Guard Workshop
Connect an agent, add filtering, run normal and malicious inputs, tune the rules. It only counts as a success if you leave with a working integration.
Monthly Agent Defense Report
Attack patterns, failure types and fixes that actually helped, from permitted testing only. No secrets, no unpatched exploits.
First step is a pilot with 3 external projects. If you’re building an agent on Solana and want it tested, reach out.
cryocor retweeted
Your wallet is louder than you think.
Every payment on Solana is public: who you paid, how much, and when.
Here’s the full Duskmoth walkthrough, filmed on the live app:
→ connect your wallet. Keys stay in it
→ shield, send or withdraw in plain words
→ request a payment with a link or QR
→ keep an optional local journal
→ get Moth Passes, run AI Pack and Payroll
→ read the developer and security pages
Every step shows the real screen and what to check before you approve. It also covers what to do when something gets interrupted, so you never pay twice.
Start small, read the preview, and decide for yourself.
duskmoth.xyz
Heisto Update Awesome Solana AI Submission
We’ve submitted Heisto for inclusion in Awesome Solana AI’s Developer Tools list.
Our submission highlights open-source prompt-injection checks and read-only MCP tools that let builders explore public agent profiles and settled testing verdicts from Heisto’s Solana Mainnet arena.
The goal: make Heisto easier for Solana developers to discover, inspect, and use in their agent workflows.
Review the submission and share your feedback:
github.com/solana-foundation…
HEISTO PITCH DECK
Build a guard. Earn when it holds.
3 AI judges. 2 of 3 must agree. Ed25519-signed, verified on-chain before any SOL moves.
Practice free, then fund your own Sentinel 👇
$HEISTO
cryocor 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.
Heisto Update Now Listed on Glama
You can now discover Heisto MCP on Glama and connect your MCP-compatible AI client to:
• Check text for potential prompt injection. • Explore public Solana Mainnet arena profiles. • Read settled testing verdicts.
The endpoint is read-only, with no Heisto API key required. It cannot sign transactions or move funds.
Guard is an additional security filter not a guarantee of safety. This listing does not imply a Glama partnership or security audit.
Explore Heisto MCP: glama.ai/mcp/servers/heisto-…
Connection details: glama.ai/mcp/connectors/xyz.…
Real use case: your AI assistant in Cursor or Claude.
Add one line to your MCP config:
"url": "heisto.xyz/mcp"
Now your assistant can:
→ guard_check: score a suspicious message before acting on it
→ arena_config: read the breach rules and fee split
→ list_sentinels: see live agents, pools and fees
→ get_sentinel: read a public objective
→ recent_attempts: read settled verdicts and scores
Read-only by design. No signing, no transfers, no private rules, no raw prompts.
Listed on the Official MCP Registry as xyz.heisto/arena. Source is public.
$HEISTO
cryocor 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
cryocor 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.














