cryocor 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β¦
cryocor retweeted
Small lesson based on $LEONIDA chart
Those wicks are telling you about the demand, and buy pressure on a dip...
I could be wrong but GTA 6 is coming, and tokens based on the narrative are the hottest at the moment... with the 100s millions marketing going on GTA 6 and over 1Billion $ in sales already this could be the thing we waited for.
Gib 1m and I will start to stream GTA 6 myself lol...
NFA DYOR
So @cryptoblaney has been a citizen of LEONIDA from the early days π΄
He's still here, still bullish, and an honorary resident of our great state.
Watch the full clip π
cryocor retweeted
The next big hack in crypto might not need a single line of malicious code.
Just a message an agent shouldn't have trusted.
We're building for that world on @solana: agents tested in public, with real stakes, before they guard real money.
Proof today: verified mainnet program, on-chain security.txt, listed on the Official MCP Registry, public attempts log.
Planned: independent security audit, and moving program upgrade authority to a multisig.
$HEISTO
cryocor 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/β¦
cryocor retweeted
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
cryocor retweeted
Every failed attack on a public arena teaches every builder who reads it.
The attack log stops being one project's data and becomes a shared map of what agents fall for. Open security compounds. Closed security repeats the same mistakes.
Proof today: open-source security docs with a readiness checklist, documented Guard limits, and a Guard Checker PR open for community review.
Planned: season write-ups of what worked and what didn't.
github.com/heisto-dev/heistoβ¦
the flywheel on $HEISTO is the part people miss:
attackers pay fees to hunt bounties β failed attempts fund bigger pools β strong agents stack bigger bounties β resilience records become credentials β protocols gate on those records β more agents need testing β more fees.
every step is live or on the roadmap. the security layer compounds.
$HEISTO
9HrYC4PH4A3d5o7LUvwjDrxkWyZDjVQpvFvWVwbKpump
@Heisto_
1
39
cryocor retweeted
the whole thesis in four lines:
β privacy infra live on solana (zk + tee engines, router with no silent reroute)
β token burns on real usage (blind-signed passes, 3M burned, verifiable)
β distribution strategy: wallet-native routes, not new apps
β team ships weekly with receipts, open source, honest labels
small cap, big problem, working product.
$DMOTH
@duskmoth_app
9ueEeBuYUc9X1GrNCyWHbKGnHJq1kaD2nvDapDsMpump
cryocor retweeted
π¦ 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
cryocor retweeted
Next step for agent security: protocols asking for proof before granting access.
"This agent survived X paid attacks over Y days with no breach" could be the check before an agent gets to trade, lend or move treasury funds.
Proof today: public Sentinel data, signed verdicts checked by the program, and read-only MCP tools any client can query.
Planned: a simple, documented resilience check that protocols can call. No hidden scoring.
cryocor retweeted
An agent's system prompt is basically its contract. It defines what it will and won't do with your money.
We think agent rules will be versioned and hashed like code. Silent prompt edits will look as sketchy as silent contract upgrades.
Proof today: Heisto stores each Sentinel's private rules encrypted, with only their hash on-chain. The program itself is verified on Solscan against our public source.
Planned: a public rules-hash history on every Sentinel page.
cryocor 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.
cryocor retweeted
Any MCP client can now:
β run a Guard prompt-injection check
β read live Sentinels, pools and fees
β read settled verdicts from the arena
Add it: heisto.xyz/mcp
Source: github.com/heisto-dev/heistoβ¦
UPDATE : Heisto MCP is live in the Official MCP Registry.
5 read-only tools for Guard checks, public Sentinels and settled verdicts. No signing or fund transfers.
Registry: registry.modelcontextprotocoβ¦
Source & setup: github.com/heisto-dev/heistoβ¦
cryocor retweeted
Use the product. Burn the token.
This is how $DMOTH works inside Duskmoth today:
You burn $DMOTH on-chain, publicly. 50,000 = 1 Moth Pass.
Your browser creates a blinded token.
We sign it without seeing it (RSA blind signatures, RFC 9474).
You receive a valid Moth Pass that canβt be linked back to your burn.
You spend it: one pass for one AI Pack plan or one Payroll batch.
The burn is public, but which pass it became stays private.
So the loop is simple. More usage means more burns. Every new pass-gated feature adds to that loop without changing how it works.
cryocor retweeted
Read the code. Donβt trust the tweet.
Hereβs the path from a developerβs side:
β Your app calls duskmoth-sdk: quote, screen, prepare.
β The SDK never signs. Itβs dependency-free, holds no keys and submits nothing.
β Your userβs wallet does the signing.
β Solana settles, and the receipt is on Solscan.
At no point does our code need custody of anything.
github.com/duskmoth-dev is public:
β duskmoth-sdk, v0.2.0, with Moth Pass, AI Pack planning and Private Payroll
β duskmoth-docs, covering guides, API reference and safety notes
β the main app repo, which goes public after the dependency security review
cryocor retweeted
In a few years, an AI agent won't be trusted with money because its builder says it's safe.
It'll be trusted because of a public record: how long it held, how many paid attacks it survived, and what broke it.
Proof today: Vault Keeper has been live 7 days on @solana mainnet. 33 paid attacks, 0 breaches, every attempt public after its verdict.
Planned: a public record page for every Sentinel, and listing Sentinels on the Solana Agent Registry.
heisto.xyz/#arena
cryocor retweeted
UPDATE : Heisto MCP is live in the Official MCP Registry.
5 read-only tools for Guard checks, public Sentinels and settled verdicts. No signing or fund transfers.
Registry: registry.modelcontextprotocoβ¦
Source & setup: github.com/heisto-dev/heistoβ¦
cryocor 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.
cryocor retweeted
$DMOTH is bringing ZK, TEE, and encrypted amounts together into one privacy routing layer.
Multiple engines. More flexibility. Transparent trust assumptions.
Privacy infrastructure is becoming a bigger part of Solana's future.
CA: 9ueFeBuYUc9X1GrNCyWHbKGnHJq1kaD2nvDapDsMpump
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
