The CLARITY Act, section by section

Build the CLARITY Act as structured data on Geo, organize everything the space already knows about it under the right sections, and tell the story of its path through Congress.

The CLARITY Act is the biggest crypto story of the autumn, and Geo already holds more than 700 claims and 45 stories about it. What it does not have is structure: nobody can see which claim belongs to which part of the bill, how each chamber voted, or who is fighting over which section. This bounty fixes that. You will model the bill, file the existing material under its sections, add what is missing, and build the page that tells the story.

This is a hard bounty: one curator, about six weeks. It rewards modeling judgment and sourcing, not volume.

What you build

  1. The bill. One Law entity (we give you its id). Fill: Legislative status, Legislative identifier, Date introduced, Web URL (congress.gov), Jurisdictions, Regulatory authority (SEC, CFTC), Introduced by (the sponsor), Sponsors (cosponsors). Every value that names a real thing is a relation to the existing entity, never text.

  2. The sections. 8 to 12 Topic entities, one per title or contested section: definitions and the decentralization test, SEC and CFTC jurisdiction, the stablecoin yield provision, section 604 developer protections, the presidential ethics provision, DeFi provisions, custody and banking, illicit finance, state preemption, effective dates. Each: a sentence-case name that says what it is ("CLARITY Act section 604 developer protections"), a 1 to 2 sentence description with the section number and what it does, Broader topics to the CLARITY Act topic, Web URL to the section text. The Law entity's Topics point to every section.

  3. The votes and milestones. Each roll call and procedural step as one short factual claim with the tally and the absolute date ("The Senate Banking Committee advanced the CLARITY Act 15 to 9 on May 14, 2026"), Is factual checked, a Source to the congress.gov record or primary report, Topics to the section it concerns and to the event topic. Several of these claims already exist: reuse them, do not re-mint. Cover at least: House passage, committee markup, amendments that passed or failed, cloture filing, the September 15 cloture vote and what followed, the House calendar.

  4. Filing the existing claims. Add Topics to at least 150 existing CLARITY claims so each sits under its section. Do not edit claim text. Keep a list of duplicates you find (we merge them).

  5. Who stands where. For each contested section, 3 to 5 named people or organizations per side attached to that section's debate proposition through Supported by or Opposed by, each with a verbatim quote and a Source. Public figures and organizations only. The lobbying letters (banking groups, law-enforcement coalition, crypto trade groups, policy shops) become Article entities with Web URL, Publish date and Authors, used as Sources.

  6. The story page. On the CLARITY Act topic: a "story so far" block of 6 to 8 sourced factual claims, a timeline of the milestones, a table of the sections, one table per contested section showing its claims, a Sources tab, a cover. Present it at the crypto community call.

Per-entity fields

Entity

Type

Fields (relations in bold)

The bill

Law (existing)

Legislative status, Legislative identifier, Date introduced, Web URL, Jurisdictions, Regulatory authority, Introduced by, Sponsors, Topics (the sections)

A section

Topic

Name, Description, Web URL, Broader topics (CLARITY Act)

A vote or milestone

Claim

Name (one sentence, tally, absolute date), Is factual = true, Sources, Topics

A position

Supported by / Opposed by relation on the section's proposition

Notable quotes, Sources

A letter or report

Article

Name, Web URL, Publish date, Authors or Publisher

Rules

  • Before you publish anything, share your plan with us: what you will create, what you will reuse (with Geo ids), your sources, and the outline of the page. We sign it off first.

  • Search before you create. The bill, the SEC, the CFTC, the senators, most claims and many sources already exist on Geo. Link them by id.

  • Relations, not text. Sponsors, regulators, sources, sections are all relations.

  • Every factual claim has a Source with a working URL that supports it. Primary sources (congress.gov, the letters themselves, official statements) over press.

  • Claims: one sentence, sentence case, no trailing period, no predictions, name the subject in full, absolute dates.

  • Topic descriptions: 1 to 2 sentences, no hedging.

  • Do not edit or delete existing entities beyond adding relations; list anything that needs fixing and we do it.

  • Publish your work to the Crypto space as proposals; we review and vote there and may ask for corrections.

Acceptance (mission-critical, all must pass)

Sections cover the whole bill and every contested provision has one · every vote and milestone claim carries a Source and a date · at least 150 existing claims re-filed, none re-minted · both sides represented on every contested section, with quotes and sources · no duplicate of an existing entity · the page reads as a story a non-expert can follow, not a data dump.

Reward and deadline: up to 500 points for a complete, accepted submission, quality weighted. Six weeks from allocation. One curator.


Comments (0)
Loading comments...