I keep coming back to a slightly uncomfortable question whenever a crypto project opens a Washington office. Who, exactly, is speaking, and with whose money? On October 1 a group built around Zcash filed to lobby the U.S. government on market rules, taxation, financial privacy, and the legal position of people who write software. The registration is dry. The timing is not. A market-structure bill had just failed to clear a procedural hurdle in the Senate, two tax proposals were moving at very different speeds, and a privacy-focused token had already crossed into a regulated exchange product earlier in the year. That combination is worth sitting with.
Pretty Good Policy for Zcash, shortened to PGPZ, registered as an organization employing an in-house lobbyist. Executive director Divij Pandya is the only person the filing expects to lobby. The description of the work is short enough to memorize: Zcash ecosystem development, developer protections, and financial privacy. Three legislative items are named. One is the Digital Asset Market Clarity Act, H.R. 3633. The other two are tax bills, the Aligning Digital Assets with Principles of Taxation Act and the Digital Asset Tax Certainty Act. None of that, on its own, rewrites a statute. It does put a privacy-coin constituency into a room that larger trading firms have occupied for years.
Why a Privacy Coin Wanted a Formal Washington Voice
PGPZ did not appear from nowhere in October. It emerged in June out of an earlier effort called Pretty Good Policy for Crypto, a policy project originally developed by Electric Coin Co. That earlier project ran recurring Washington roundtables for policy professionals and organized a congressional briefing on privacy-enhancing technologies back in 2023. Founder Paul Brigner has framed the newer organization as a dedicated policy voice, with the stated aim of giving Zcash serious, organized, and credible engagement in Washington. I have heard versions of that sentence from a dozen projects. The useful test is whether the paperwork, the budget, and the calendar match the sentence.
The group’s own description casts it as an independent policy organization focused on helping policymakers and regulators understand privacy-preserving digital money. The stated lanes are financial privacy, developer protections, public education, and responses to legislation or regulation that touches Zcash. It is not an official arm of the Zcash Foundation. The site says the organization operates independently and is not affiliated with or endorsed by the foundation. That distinction matters more than it sounds. Foundations, protocol companies, and grant-funded advocates get conflated in hearings, and a sloppy conflation can stick.
A filing does not pass a bill. It does tell you who expects to be in the room when the next draft is marked up.
Larger digital-asset businesses have already treated market-structure policy as a core spend. One major exchange put about $1.07 million into first-quarter lobbying tied to the market-structure bill and related crypto legislation. Against that number, a first-year grant of $750,000 looks modest. Modest is not the same as irrelevant. A small shop with a narrow brief can still shape a paragraph on developer liability or a footnote on shielded transactions, especially if the bigger shops are busy fighting over jurisdiction between market regulators.
What the Registration Actually Covers
Under the Lobbying Disclosure Act, the filing identifies PGPZ as employing an in-house lobbyist and names Pandya as the sole expected lobbyist. Effective date: October 1. The issues list is where the strategy shows. Market structure sits next to tax treatment and next to the softer, harder-to-draft themes of financial privacy and developer protection. In my experience, groups that list only a brand name tend to fade. Groups that list bill numbers tend to show up with amendments.
The three named items are not interchangeable.
- H.R. 3633 would build a federal market structure for digital commodities and split duties between the securities regulator and the commodities regulator.
- The Digital Asset Tax Certainty Act, H.R. 10357, was introduced on September 14 to change how the federal tax code treats digital assets.
- The Aligning Digital Assets with Principles of Taxation Act, often called the ADAPT Act, was introduced in the Senate on September 30 by Senator Steve Daines, aimed at clearer rules where blockchain activity does not map cleanly onto older financial transactions.
The registration lists those bills as current or anticipated lobbying issues. It does not say the group supports every line. That silence is deliberate, and it is the correct silence. A first filing that endorses an entire committee product usually ages badly.
A Grant, a Recusal, and a Spending Map
Zcash Community Grants approved the $750,000 request on August 31 after reviewing a one-year operating plan. Brigner, who sits on the grants committee and helped establish PGPZ, recused himself from the discussion. That recusal is the sort of procedural detail readers skip and counsel circles in pen. Community treasuries get accused, fairly or not, of funding insiders. A recorded recusal does not end the argument. It does give the organization a cleaner answer when someone asks.
The application splits the money in a way that tells you what year one is supposed to look like. Operating costs, staffing, and professional services take $400,000. Administrative support through the Financial Privacy Foundation is set at $125,000. Legal, lobbying, tax, accounting, and compliance support take $120,000. Policy events and workshops get $25,000. Travel, conferences, and congressional visits get another $25,000. The rest covers government-affairs tools, research, communications, and a contingency reserve.
| Budget line | Amount | What it is for |
| Operations and staffing | $400,000 | Day-to-day policy work and professional services |
| Administrative support | $125,000 | Support via the Financial Privacy Foundation |
| Legal and compliance | $120,000 | Lobbying, tax, accounting, and compliance help |
| Events and workshops | $25,000 | Briefings and policy gatherings |
| Travel and visits | $25,000 | Conferences and congressional meetings |
| Tools, research, reserve | Remainder | Communications, research, contingency |
The application specifically bars grant money from campaign contributions, partisan election activity, political donations, or promoting the market price of the token. The stated focus is conditions affecting the ecosystem, not the commercial interests of a single company. Whether that line holds is an execution question. On paper, it is the right constraint for a grant-funded advocate that does not want to be read as a price-support desk.
The Market-Structure Bill That Stalled
H.R. 3633 is the center of gravity. The idea is familiar to anyone who has watched this debate since the last Congress: treat a defined class of digital assets as digital commodities, draw a line between the securities regulator and the commodities regulator, and give platforms a statute instead of a pile of enforcement theories. The Senate Banking Committee advanced its version in May by a 15-9 vote after months of negotiation. Then September arrived.
On September 15 the Senate voted 49-50 against invoking cloture on the motion to proceed to H.R. 3633. Sixty votes were required. A motion to reconsider was entered afterward. That is not a final burial. It is a failed attempt to start formal debate, which in Senate math is often the whole game. Perhaps the most interesting aspect is how ordinary the failure looked. Not a dramatic policy reversal. A one-vote shortfall on procedure, in a chamber that has treated crypto market structure as both urgent and perpetually almost-ready.
PGPZ’s grant application says the group plans to watch developer liability, anti-money-laundering rules, sanctions, privacy, and financial surveillance. Where it thinks a rule could hurt privacy-preserving technology, it intends to propose amendments or other legislative language. That is a narrower mission than “pass the bill.” It is also a more realistic one. A new registrant is unlikely to drag a stalled market-structure package across a 60-vote line. It might still get a sentence about noncustodial software into a manager’s amendment if the package moves again.
Developer Protection Is the Quiet Fight
This is the part I would not skim. Zcash software uses privacy technology that can be deployed through noncustodial applications. PGPZ says it wants clear rules and safe harbors for developers and maintainers of that kind of software. The wider Washington argument is no longer theoretical. Lawmakers have spent the past few years asking how existing financial statutes apply to people who publish code, run relayers, or maintain open-source clients. A separate political push has already sought protections for blockchain and decentralized-finance developers. Privacy software sits at the sharp end of that argument, because the same features users call protection are the features investigators call opacity.
A safe harbor, if it is written poorly, becomes a loophole. Written tightly, it can separate a person who publishes noncustodial code from a person who takes custody of customer funds and ignores compliance duties. I have found that staffers respond better to that distinction than to slogans about cypherpunk history. The registration’s emphasis on developer protections suggests PGPZ knows which meeting it is trying to get.
- Define noncustodial software so the term is not a marketing label.
- Separate publishing and maintaining code from operating a money-services business.
- Keep sanctions and illicit-finance duties on actors who actually control funds or interfaces.
- Avoid language that treats every privacy feature as a presumptive evasion tool.
None of those four points is in the filing as drafted text. They are the shape of the argument the filing points toward. Readers should treat them as the policy problem, not as language already agreed.
Two Tax Bills, Two Different Clocks
Tax policy is the other half of the registered agenda, and it is moving on a different clock than market structure. H.R. 10357, the Digital Asset Tax Certainty Act, was introduced on September 14. Government records describe it as a reform of Internal Revenue Code provisions covering crypto. The House Ways and Means Committee approved an amended measure on September 16 by a 38-5 vote and ordered it favorably reported. That is a fast committee turn. Committee materials say the proposal touches mining and staking, reporting rules, and tax treatment meant to pull digital assets closer to rules that already apply to other financial assets.
The ADAPT Act arrived later. Senator Daines introduced it on September 30, describing clearer digital-asset tax rules and attention to places where blockchain transactions differ from traditional financial activity. PGPZ has not disclosed specific amendments for either bill. The form lists them without a support-or-oppose box filled in public view. That is normal at the registration stage. It is also a gap. A reader cannot yet tell whether the group wants broader reporting relief, narrower staking guidance, or language that treats shielded transfers differently from transparent ones.
Privacy coins make tax administration awkward, and pretending otherwise helps nobody. If a transfer can hide counterparty details from the public chain, the reporting question shifts toward the user, the wallet, or the service that touches fiat. A lobbyist who walks in with only “privacy is a right” will lose the tax staffer in the first ten minutes. A lobbyist who walks in with a workable reporting path for noncustodial users has a chance. Whether PGPZ has that path is not in the October filing. The first policy briefs will tell us.
What Changed for Zcash Before the Lobbyist Arrived
The policy push sits on top of two regulatory developments that already altered the U.S. picture. In January the securities regulator closed an investigation of the Zcash Foundation without an enforcement action. The review had started in 2023. Closure without a case is not a blessing of the protocol, and it is not a promise about future exams. It does remove a live cloud that had hung over one of the ecosystem’s main nonprofit bodies.
In August a major asset manager launched the first U.S.-listed spot Zcash exchange-traded fund, listing on NYSE Arca. A privacy-focused cryptocurrency inside a regulated exchange product is a strange sentence, and it is now a real product. The launch followed the closure of that earlier probe. Together, the two events make the lobbying registration less like a protest and more like an attempt to lock in a status that markets have already started to price.
I would not treat the fund as proof that Washington has made peace with shielded transactions. Exchange products answer a listing question. They do not answer an anti-money-laundering question, a sanctions question, or a developer-liability question. Those live in different agencies and, often, in different statutes. PGPZ’s issue list reads as if someone on the board understands that split.
The First Ninety Days, on Paper
A September 30 project update said the board had been seated and the federal lobbying registration filed. The application for tax-exempt status with the revenue service was still in progress with counsel. First-quarter targets are concrete enough to check later: at least 15 introductory meetings with policymakers, educational material for congressional offices, and at least one briefing or workshop. Later targets cover policy briefs, regulatory submissions, and repeat engagement with government offices.
An October 14 Washington fly-in and a Cypherpunk Policy Dinner are on the near calendar. The fly-in is meant to bring ecosystem representatives into meetings with Congress and, potentially, regulators to discuss Zcash-related policy. Dinners do not pass bills. They do put names to faces before a staffer has to brief a member on a privacy protocol most offices have never used. If you have ever watched a technical witness lose a room in the first answer, you know why the introductory meeting is not a vanity metric.
Year-one checkpoints worth watching: Registration effective: October 1 Fly-in and policy dinner: October 14 Introductory meetings target: at least 15 Tax-exempt application: still in progress as of late September Grant window: one year from the August 31 approval
There is a parallel technical calendar that has nothing to do with the filing and everything to do with what the advocates will be explaining. Developers have targeted November 5 for the NU7 mainnet upgrade, with testnet activation scheduled for October 6 and a final mainnet decision expected later in October. Policy staff do not need the upgrade spec. They do need a plain account of what changes for users, wallets, and any compliance assumption built on the old behavior. A lobbyist who cannot explain the upgrade in one page will get outrun by the people who can.
How This Sits Next to Bigger Crypto Lobbies
Washington already has a crowded crypto lobby. Exchanges want listing certainty and a single primary regulator. Issuers want a path that does not treat every token sale as a securities offering. Payment firms want bank-like access without bank-like capital rules. Bitcoin advocates often argue from commodity status and energy politics. A privacy-coin advocate is asking for something those groups can live without: room, in statute, for transactions that are not transparent by default.
That ask collides with a bipartisan instinct. Both parties have members who like innovation language and members who like sanctions language. Financial surveillance is not a niche concern after a decade of ransomware, fraud rings, and state-linked hacks. Any privacy argument that skips illicit finance will be treated as incomplete, because it is incomplete. The stronger version admits the risk and then argues about where controls should sit: at exchanges and on-ramps, at custodians, in targeted law-enforcement process, rather than in a ban on the software itself.
Coin-specific advocacy has a reputation problem, and it is earned. Too many “education” efforts have been marketing with a lanyard. PGPZ’s independence claim, the recusal, and the ban on using grant funds to promote price are attempts to look different. Critics will say a grant from a Zcash community program cannot be neutral about Zcash. They are not wrong that the funding source has a point of view. Neutrality was never the product. Credibility was. Those are different standards.
What Lawmakers Are Likely to Ask
If the 15 meetings happen, the questions will rhyme. I would bet on a short list.
- Who can see a shielded transaction, and under what legal process?
- What stops a sanctioned person from using the protocol if no intermediary is in the loop?
- How should a noncustodial developer be treated when a criminal uses published code?
- Does a spot exchange-traded product change the compliance story, or only the distribution story?
- Which lines of H.R. 3633 would the group amend, and which would it leave alone?
- How should staking, mining, and self-transfers be taxed if the chain can hide amounts?
A good advocate answers the hard one first. A weak one starts with a history of digital cash and hopes the clock runs out. The October registration does not reveal the answers. It reveals that someone is now paid, at least for a year, to have them.
Privacy, Surveillance, and the Sentence Nobody Wants to Write
Financial privacy is easy to praise in the abstract and miserable to draft. Ordinary people do not want every purchase on a public ledger. Governments do not want a payments rail that ignores sanctions. Both instincts can be true in the same week. Zcash was built around the claim that you can have digital cash with selective disclosure rather than total disclosure. Washington has mostly answered with suspicion, exams, and, in other privacy-coin cases over the years, delistings and enforcement theories aimed at mixers and obfuscation tools.
PGPZ is walking into that history with a grant and a dinner. The useful work, if it happens, will be boring: definitions, safe-harbor thresholds, reporting duties that attach to intermediaries, and explicit statements about what publishing code is not. The useless work will be adjectives. I have sat through enough policy briefings to know which stack gets remembered when a member has four minutes between votes.
Selective disclosure is a design claim. It becomes a legal claim only when someone writes down who must disclose, to whom, and when.
A practical test for any privacy-tech briefing
The group’s plan to produce educational material for offices is the right artifact, provided the material survives contact with a hostile question. One-page briefs beat slide decks. Examples beat metaphors. A worked hypothetical, with a lawful user and an unlawful user on the same protocol, beats a manifesto. If the October 14 fly-in produces that kind of paper, the registration will have done more than announce a brand.
Risks the Filing Does Not Mention
Every new registrant carries risks that do not appear on the form. The first is capture by a single narrative. If every meeting is about one token’s brand, staffers file the group under “issuer lobby” and stop returning calls when the bill text turns to general developer liability. The second is over-promising to the community that funded the grant. A year of meetings can look like failure if holders expected a statute. The third is the tax-exempt application still in progress. Structure and lobbying rules interact. Counsel is already on that file, which is necessary and not the same as finished.
There is also a political-cycle risk that has nothing to do with Zcash. Market-structure legislation has already slipped from committee momentum to a failed cloture vote. Campaign calendars compress floor time. A bill that needs 60 votes in the Senate does not become easier because a new advocate booked 15 coffees. PGPZ can still do useful work in that gap: comment letters, model amendments, relationships that survive a congress. Expecting the gap to close on this group’s timetable would be a misread.
A further risk is technical. NU7 is a protocol milestone, not a press release. If mainnet activation slips, or if wallet support lags, the policy story and the product story diverge. Advocates hate that divergence. Members notice it when a demonstration fails. The testnet date of October 6 sits days before the fly-in. That proximity is either convenient or a trap, depending on whether the people in the meetings can speak precisely about what is live and what is still a target.
How to Read the Next Disclosures
Lobbying disclosures are lagging indicators, but they are better than vibes. The next quarterly report should show whether Pandya remained the only lobbyist, whether outside firms were hired, and which issues actually consumed the time. A report that still lists the same three bills, with no grassroots spend and no campaign activity, would match the grant restrictions. A report that drifts into general “digital asset education” without bill numbers would suggest the brief got fuzzy.
Watch the paper trail outside the lobbying database too. Regulatory submissions, if they appear, will show the group’s real positions on surveillance and developer liability. Congressional briefing invitations will show whether offices took the educational offer seriously. Silence after the fly-in would also be data. Not every dinner becomes a hearing. Some become a contact saved in a phone and never used.
For holders and builders, the practical read is simpler. The community treasury has funded a year of policy capacity aimed at conditions around the protocol, with an explicit bar on price promotion and electioneering. That is a governance choice as much as a Washington choice. Other ecosystems have spent similar sums on conferences that did not change a comma of statute. The difference, if there is one, will show up in amendment text and in whether developer-protection language survives contact with illicit-finance negotiators.
A Note on What This Does Not Decide
Registration does not legalize anything that was illegal yesterday. It does not guarantee a safe harbor. It does not bind the securities regulator, the commodities regulator, the revenue service, or the Treasury bureau that writes anti-money-laundering rules. It does not make a privacy coin easier to list, or harder. The spot fund already exists. The foundation probe already closed without a case. Those facts stand whether or not PGPZ gets its fifteenth meeting.
What the filing does decide is representation. Zcash now has a named organization, a named lobbyist, a named set of bills, and a named pile of community money attached to a one-year plan. Larger firms will still dominate the dollar totals. They will not automatically speak for shielded transactions or for the maintainers of noncustodial privacy software. Someone else has volunteered for that seat. Whether the seat is used well is a question for the quarterly reports, not for the press release that accompanied the registration.
The Argument Worth Having
Strip away the acronyms and the dispute is old. Should digital cash be able to resemble physical cash, where the bank does not see the coffee purchase, or should every electronic transfer be reconstructable by default? Physical cash already answers that in one direction, with limits, reporting thresholds, and criminal law for what you do with the bills. Public blockchains answered in the other direction, often by accident: radical transparency as a side effect of verification. Privacy technology tries to unwind that side effect without unwinding verification.
Congress does not have to bless a particular coin to take a position on that design space. It does have to notice that market-structure bills, tax bills, and sanctions practice are already taking a position by omission. A rule that assumes every transfer is visible will misfire on protocols built to make some transfers invisible to the public. A rule that assumes every invisible transfer is illicit will misfire on ordinary users. PGPZ’s job, if it does the job, is to force that misfire into the open while the text is still movable.
I do not think a $750,000 grant settles the argument. I do think the absence of any organized privacy-coin voice made the argument easier to skip. The October 1 registration closes that particular excuse. Offices that want a briefing can book one. Offices that want to treat privacy software as out of scope will have to say so to someone’s face. That is a small change in a large capitol. Small changes are how most statutory sentences actually get written.
Between now and the November upgrade target, the interesting documents will not be price notes. They will be the educational one-pagers, any amendment language that leaks from meetings, and the quarterly lobbying report that either confirms a single in-house advocate or shows the operation scaling. The Senate’s 49-50 cloture vote remains the backdrop. Until someone finds eleven more votes, or a different vehicle, market structure is a drafting exercise with an uncertain floor. Tax language in the House is further along, which may be where a new registrant can matter sooner.
If you follow this space for the technology, keep the policy file next to the upgrade file. They are about to be explained in the same meetings, to people who will remember only the clearest sentence. The group that just registered has given itself a year, a budget, and a narrow brief. That is enough to be judged. It is not enough, yet, to be believed.
