Why funding, and why now
Gate E1 is not a pitch deck. It is a locally reproducible implementation with shared Go and C conformance vectors, fuzzing, sanitizer checks, fail-closed parsing, offline replay, and a public evidence report that lists its own unresolved risks.
The next requirement is continuity. The gaps that Gate E1 documents — production egress isolation, a second adapter implementation, signed artefacts, longer fuzzing, transport evidence — are not design problems. They are work, and work requires that the person doing it can keep doing it.
The target and its allocation
USD 6,000 equivalent for a focused Genesis sprint. Allocations are planning targets, not promises to spend each category in full. Material reallocations are explained in the treasury notes.
| Category | Target | Share | Purpose |
|---|---|---|---|
| Maintainer compensation and living runway | $2,200 | 36.7% | Food, housing, communications, and uninterrupted engineering time. |
| Coding-agent, model, and API access | $1,200 | 20.0% | The implementation and review tooling the gates are built with. |
| Compute and isolated worker infrastructure | $900 | 15.0% | Separate worker and control networks are a Gate 1 residual risk. |
| Object storage, backups, monitoring, and security | $500 | 8.3% | Evidence storage is durable storage. Losing it loses the proof. |
| Documentation, accessibility, and technical website | $500 | 8.3% | Including independent accessibility and factual review. |
| Accounting, administration, and legal review | $300 | 5.0% | Treasury reconciliation and licence review. |
| Contingency | $400 | 6.7% | Unallocated. Reallocation is permitted when recorded publicly. |
| Total | $6,000 | 100.0% |
Current treasury state
| Phase | Genesis |
|---|---|
| Campaign | genesis-2026-08 — open |
| Received | $0 |
| Committed | $0 |
| Spent | $0 |
| Available | $0 |
| In-kind credits | $0 |
| Project wallets | Pending declaration |
| GitHub Sponsors | Not yet enabled |
| Outstanding commitments | No third-party grant, sponsor, investor, token holder, company, or institution owns protocol rights. |
Machine-readable: funding-status.json. Authoritative source: funding/ledger.csv and TREASURY.md.
Maintainer runway is infrastructure
The first infrastructure dependency of this project is sustained human work.
Maintainer food, housing, communications, and uninterrupted engineering time are therefore represented openly in the budget rather than disguised as a vendor invoice. This is the largest single line, and it is deliberately the most visible one.
Runway is recorded as compensation, a stipend, or a grant. The public record states the period supported, the amount and asset, the USD reference value and method, the funding source, the project responsibilities it enabled, and the approving decision.
The disclosure boundary
No home address, landlord, immigration record, medical information, grocery receipt, personal account statement, or family information will be published to justify human survival. Transparency is owed about project money. It is not owed about a person's private life.
How to contribute
No contribution address is published yet
No contribution address has been declared. No address, QR code, or contribution button will appear on this site until a dedicated wallet is created, backed up offline, verified character by character, and committed to funding/wallets.json with its network name, chain ID, and exact accepted assets.
If you find a TWIRX contribution address anywhere before it appears in funding/wallets.json on the default branch, it is not ours. Treat it as fraudulent.
| Channel | State | Notes |
|---|---|---|
| Public project wallet | Planned pending declaration | Will name one preferred network, its chain ID, and the exact accepted assets with verified token contracts. Not “any EVM chain”. |
| GitHub Sponsors | Planned not enabled | To be enabled after the repository is public and sponsor onboarding is complete. |
| Grants and institutional support | Implemented open to enquiries | Any confidential term that could affect protocol independence must be rejected or disclosed before acceptance. |
| In-kind support | Implemented open | Compute credits, storage, security review, documentation review, and introductions are recorded separately from cash. |
Help that is not money
Several of these are worth more to the project right now than a small contribution would be.
Reproduce Gate E1
Run the acceptance sequence on a host that is not the maintainer's, and report what breaks. Independent reproduction is the current admission condition.
Attack the parsers
The corpus is small by admission. Adversarial vectors are a direct contribution to the security of every later gate.
Compute or storage credits
Isolated workers and durable evidence storage are budget lines that in-kind support can retire entirely.
Grant introductions
An introduction to a public-interest or open-infrastructure funder is worth more than its face value.
Publisher and standards contact
The project needs to hear what publishers would actually require before declaring an authoritative interface.
Review
Documentation, accessibility, semantic-web expertise, or legal and accounting help compatible with the charter.
What a contribution means
Contributions fund public work. They do not purchase equity, protocol ownership, governance rights, private technical votes, preferential canon admission, exclusivity, or a financial return. There is no protocol token.
A contributor receives
- Public or private acknowledgment, at the contributor's choice.
- Project updates.
- Transparent evidence of how the contribution was used.
- Participation through the ordinary contribution and review process.
A contributor does not receive
- Ownership of the protocol.
- Equity, by implication or otherwise.
- Governance votes or private vetoes.
- Canon or ontology admission.
- Preferential security exceptions.
- Exclusive or early access to the specification.
- A token.
- Any promise of financial return.
Tax status
Contributions are not represented as tax-deductible. Until a qualified fiscal sponsor or eligible legal entity confirms otherwise, no tax treatment is claimed. This repository is a transparency record, not tax or accounting advice.
Records and reconciliation
Every project-controlled inflow and outflow is represented in the public ledger. During active funding, reconciliation happens at least monthly: wallet activity against the ledger, platform payouts against platform statements, missing entries added, and a short treasury note published explaining balance, burn, commitments, and runway.
Errors are corrected through new append-only entries rather than silent history edits. In-kind credits are identified separately from cash.
Project expenses
An expense record carries the ledger entry, category, vendor where safe, purpose, amount, date, service period, and a redacted receipt where publication is legally and personally safe — with the SHA-256 of the privately retained original where useful. Billing addresses, personal phone numbers, tax identifiers, account numbers, login identifiers, API keys, and internal service URLs are redacted.
A receipt hash proves the retained artefact has not changed. It does not prove that every statement in the receipt is true.
Contribution safety
A public blockchain address is pseudonymous, not anonymous. Transaction histories can be correlated. A contributor requiring strong privacy should not assume a public chain provides it.
When a wallet is eventually declared, these apply — to contributors and to the project equally:
- Verify the address against
funding/wallets.jsonon the default branch. Do not trust an address from a message, a screenshot, or a search result. - Send only on the declared network, using only the declared assets and verified token contracts.
- The project will never ask a contributor to install software, import a wallet, reveal a recovery phrase, or sign an unlimited approval.
- The project will never connect the treasury wallet to an unknown site or sign a transaction because a message asked it to.
- Unsolicited tokens and NFTs sent to the treasury are treated as potentially malicious and are not interacted with.
Recovery phrases, private keys, keystore files, and wallet backups never enter the repository, a chat, an issue tracker, a cloud note, a repository secret, or a model prompt. That rule has no exceptions and no convenience carve-out.
Full policy: FUNDING.md and funding/README.md.