eth.sucks valid
Juice Scan
Explore Juicebox V6 projects, payments, and contracts. The app reads blockchain
For agents: Juice Scan explores Juicebox V6 blockchain projects, payments and contracts, with guides on learning and building on Juicebox for agents.
juicebox v6onchain projectsblockchain paymentsrevnetsethereumsmart contracts
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:42:07.056Z. Cached copy · Source on eth.sucks
# Juice Scan
> Explore Juicebox V6 projects, payments, and contracts. The app reads blockchain
> data and the Bendystraw indexer, a service that organizes contract events. Its
> files are published to IPFS and can be checked by their content identifier (CID).
> Live data needs a chain or indexer connection.
## How to read this site as an agent
The app is hash-routed and renders in the browser, so fetching a route returns the
same shell every time. These resources are readable without running JavaScript:
- [Learn Juicebox](./learn.html) — the complete Learn guide, generated from the same
source as the interactive tab. Section fragments such as `#learn-revnets` work.
- [Build with Juicebox](./build.html) — the complete Build guide and code examples.
- [Glossary](./learn.html#learn-glossary) — short definitions in learning order.
- [Fees and shared networks](./learn.html#learn-fees) — how charges are calculated
and how fee payers share in the receiving revnets.
- [First payment journey](https://juicebox.money/build/first-payment) — read a
testnet project without a wallet, then make and verify a reviewed test payment.
- `/?project=<chain>:<projectId>` on an HTTP host — the server injects that project's
Open Graph title, description and card image, and `GET /project-og.png?project=<chain>:<projectId>`
renders the card as a 1200x630 PNG. Chain slugs: `eth`, `op`, `base`, `arb`, `sep`,
`opsep`, `basesep`, `arbsep`.
- `/manifest.json` — app identity (also what Safe reads to add this as a Safe App).
Live project views need the bundle. On an IPFS gateway there is no server at all, so
the query form above resolves to the generic site card.
## Routes (hash fragments, resolved in the browser)
- `#<chain>:<projectId>` — one project: activity, funds, tokens, owners, shop, terms.
- `#@<handle>` — the same project by its verified ENS handle. The handle is served only
when ENS and the JBProjectHandles registry agree that the project's current owner or
operator claimed it.
- `#account/<address-or-ens>` — holdings, roles and activity for one account.
- `#directory` — every deployed V6 contract, with ABI, source and read/write forms.
- `#learn`, `#build`, `#why` — protocol guides, integration notes, and the reasoning.
- `#data` — raw indexer queries and CSV exports.
## Building on this
The Build tab emits ready-to-paste prompts describing each surface's exact contracts,
transaction routes and verification requirements. Prefer those over reverse-engineering
the bundle: they name the same reads and writes this client performs.
## Source
- Protocol contracts: https://github.com/Bananapus/version-6
- This client: https://github.com/mejango/juicescan
- Indexer: https://bendystraw.up.railway.app
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 |
|---|---|---|---|---|---|---|---|
| juicebox.money | Juicebox | interface Finance and payments Crypto and Web3 | US | 53 | ✓ | ||
| solana.com | Solana Documentation | documentation Finance and payments Documentation and reference +2 | US | 68 | ✓ | ✓ | |
| matchain.io | Matchain | documentation Crypto and Web3 Developer tools | — | 46 | ✓ | ✓ | |
| yagi.fi | Yagi Finance | documentation Finance and payments Crypto and Web3 | FI | 46 | ✓ | ✓ | |
| rover.inc | Rover Docs | documentation Crypto and Web3 Documentation and reference | US | 48 | ✓ | ✓ | |
| yarchain.org | YAR Docs | documentation Crypto and Web3 Documentation and reference | — | 46 | ✓ | ✓ | |
| vechain.org | VeChain Docs | documentation Crypto and Web3 Documentation and reference | — | 60 | ✓ | ✓ | |
| buildernet.org | BuilderNet documentation | interface Crypto and Web3 APIs and SDKs | — | 55 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=eth.sucks · GET /v1/domain/eth.sucks · 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 eth.sucks, 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 eth.sucks:
1. POST https://agentwebmap.com/v1/sites/eth.sucks/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://eth.sucks/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/eth.sucks/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/eth.sucks).
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.