qedgen.dev valid
QEDGen
Describe what your Solana program must guarantee in `.qedspec`. QEDGen finds the bugs your tests miss, then generates the proofs, property tests, and CI to keep them fixed. Supports Anchor, Quasar, Pinocchio, and native sBPF assembly — and audits existing programs without a spec: `qedgen probe` hypothesizes the invariants the code appears to enforce, and `qedgen ratify` turns confirmed ones into an executable spec (`qedgen adapt` / `qedgen spec --idl` are deprecated in favor of this flow). Insta
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T06:13:49.102Z. Cached copy · Source on qedgen.dev
# QEDGen
> Describe what your Solana program must guarantee in `.qedspec`. QEDGen finds the bugs your tests miss, then generates the proofs, property tests, and CI to keep them fixed. Supports Anchor, Quasar, Pinocchio, and native sBPF assembly — and audits existing programs without a spec: `qedgen probe` hypothesizes the invariants the code appears to enforce, and `qedgen ratify` turns confirmed ones into an executable spec (`qedgen adapt` / `qedgen spec --idl` are deprecated in favor of this flow). Install with `npx skills add qedgen/solana-skills`. Works with any coding agent supporting the Agent Skills spec.
A `.qedspec` is the single source of truth. It can live in one file or span multiple files with upstream spec dependencies. From it, QEDGen generates program code, property tests, Kani harnesses, Lean 4 proofs, and CI workflows.
## Docs
- [llms-full.txt](https://raw.githubusercontent.com/qedgen/solana-skills/main/docs/llms-full.txt): **Start here if you're an agent** — opens with a Quickstart (install + first action), then the full reference (every CLI command, the workflow, the Lean support-library API, proof patterns, and worked examples)
- [README](https://raw.githubusercontent.com/qedgen/solana-skills/main/README.md): Installation, usage, CLI commands, and requirements
- [SKILL.md](https://raw.githubusercontent.com/qedgen/solana-skills/main/skills/qedgen/SKILL.md): Spec-writing workflow, support library API (including sBPF), proof patterns, tactic rules, and error fixes
- [CLAUDE.md](https://raw.githubusercontent.com/qedgen/solana-skills/main/CLAUDE.md): Build commands, architecture, crate structure, and development guide
- [references/cli.md](https://raw.githubusercontent.com/qedgen/solana-skills/main/references/cli.md): Full CLI reference for every `qedgen` subcommand
## Examples
### Rust / Anchor
- [Escrow spec](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/rust/escrow/escrow.qedspec): Two-party token escrow (access control, state machine, arithmetic safety, CPI correctness)
- [Escrow Lean](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/rust/escrow/formal_verification/Spec.lean): Generated Lean proofs for the escrow spec
- [Escrow-split spec](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/rust/escrow-split/escrow.qedspec): Multi-file version of the escrow showing spec composition across handlers and interfaces
- [Multisig spec](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/rust/multisig/multisig.qedspec): M-of-N threshold signer gating with replay protection
- [Lending spec](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/rust/lending/lending.qedspec): Collateralized lending market
### sBPF Assembly
- [Transfer spec](https://raw.githubusercontent.com/qedgen/solana-skills/main/examples/sbpf/transfer/transfer.qedspec): Native sBPF lamport transfer (input validation, balance checks)
- [Transfer Lean](https://raw.github
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| codacy.com | Codacy | documentation Cybersecurity Developer tools | — | 60 | ✓ | ||
| qasource.com | QASource | documentation Developer tools Business software | US | 53 | ✓ | ||
| firepan.com | Firepan | documentation Cybersecurity Developer tools | US | 45 | ✓ | ✓ | |
| variance-authority.dev | Variance Authority | documentation Open source projects Developer tools +1 | — | 46 | ✓ | ||
| averlang.dev | Aver | documentation Developer tools | — | 46 | ✓ | ✓ | |
| gensyn.ai | Gensyn | documentation AI and machine learning Developer tools | — | 56 | ✓ | ✓ | |
| qodex.ai | Qodex.ai | documentation AI and machine learning Developer tools +1 | US | 54 | ✓ | ||
| fetchsandbox.com | FetchSandbox | documentation DevOps and observability Developer tools | — | 46 | ✓ |
Machine-readable: GET /v1/resolve?q=qedgen.dev · GET /v1/domain/qedgen.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage qedgen.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for qedgen.dev:
1. POST https://agentwebmap.com/v1/sites/qedgen.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://qedgen.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/qedgen.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/qedgen.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.