Poland Foundation Grant Application Packet
Why this packet exists
This packet turns the current Superteam Poland / Solana Foundation grant application into a concise, proof-led version that better fits how the grant is actually judged:
- proof of work over credentials
- speed over perfection
- clear decentralization and censorship-resistance value
- DAO tooling, payments, developer tooling, and education relevance
It is written to be copied into the grant form with minimal editing.
Verified program facts
From the active Poland grants listing:
- the corridor is open to builders in Poland
- the grant size can range from `$1` to `$10,000`
- reviewers prefer fast, executable work over broad speculative roadmaps
- proof of work matters more than credentials
- the grant explicitly names:
- decentralisation
- censorship resistance
- DAO tooling
- developer tooling
- education
- payments
This is why the submission should read like a shipped DAO tooling and payments product with a short execution delta, not like a research memo.
Recommended project title
**PrivateDAO**
Recommended one-liner
**Private governance and treasury execution on Solana, packaged as a real product.**
Recommended problem and solution
PrivateDAO solves three practical gaps in current Solana DAO operations:
- governance decisions are still too public and leak sensitive intent too early
- treasury execution is often operationally unsafe or weakly reviewable
- mobile and non-technical operators still struggle to use serious governance tooling
PrivateDAO solves this by packaging a privacy-first governance and treasury system on Solana Devnet with:
- commit-reveal voting for private governance
- timelock-controlled treasury execution
- wallet-first web governance
- Android governance access
- confidential payout and treasury-motion rehearsal
- reviewer-safe telemetry, trust, and diagnostics surfaces
The project is already live on Devnet and open-source. The grant would accelerate the remaining path from strong Devnet proof to mainnet-ready release discipline.
Why this fits the Poland Foundation grant
Decentralisation
PrivateDAO gives communities coordination and treasury tooling that reduces dependence on ad-hoc off-chain governance and opaque admin execution.
Censorship resistance
The system keeps governance and treasury logic on Solana rails, with explicit custody and authority hardening toward a production-grade release path.
DAO tooling
This is the strongest fit. PrivateDAO is fundamentally DAO coordination, governance, voting, treasury execution, and review tooling for real communities and operators.
Developer tooling
The product already exposes:
- proof packets
- telemetry packets
- diagnostics
- track workspaces
- open-source repo and docs
These surfaces help other builders understand and build on the same governance stack.
Payments
PrivateDAO already supports treasury-motion and confidential payout corridors on Devnet, which makes it relevant to grant, contributor, payroll, and treasury-based payment use cases.
Education
The public routes, story surface, and documentation already function as onboarding material for judges, builders, and ecosystem participants.
Strongest proof-of-work links
- Live product: `https://privatedao.org/`
- Start route: `https://privatedao.org/start/`
- Govern route: `https://privatedao.org/govern/`
- Story route: `https://privatedao.org/story/`
- Analytics route: `https://privatedao.org/analytics/`
- Security route: `https://privatedao.org/security/`
- Services route: `https://privatedao.org/services/`
- Poland grant workspace: `https://privatedao.org/tracks/poland-grants`
- Canonical custody proof: `https://privatedao.org/documents/canonical-custody-proof/`
- Reviewer telemetry packet: `https://privatedao.org/documents/reviewer-telemetry-packet/`
- Capital readiness packet: `https://privatedao.org/documents/capital-readiness-packet/`
- GitHub: `https://github.com/X-PACT/PrivateDAO`
Recommended grant amount
**$10,000**
This ask is justified if it is framed as the shortest path from a live Devnet product to a credible mainnet release candidate.
Recommended delivery plan
Milestone 1: reviewer-safe production hardening pack
**Timeline:** Week 1
**Objectives**
- finalize a production-grade grant packet and trust packet
- close remaining custody intake and multisig preparation artifacts
- strengthen telemetry, payout evidence, and wallet/runtime review surfaces
**Deliverables**
- updated grant submission packet
- updated trust and telemetry packets
- stricter custody and mainnet blocker packet linkage
**Success signal**
- reviewers can inspect product, trust, telemetry, and blockers without leaving the public site
Milestone 2: audit and authority readiness closure
**Timeline:** Week 2
**Objectives**
- move the governance program into external review
- complete authority multisig and custody preparation
- lock the release checklist around timelock and execution safety
**Deliverables**
- external review intake submitted
- multisig / custody preparation packet updated
- release checklist tightened around authority and timelock controls
**Success signal**
- no unresolved critical launch blocker without a linked next action and evidence route
Milestone 3: real-device and settlement evidence closure
**Timeline:** Week 3
**Objectives**
- complete the real-device wallet matrix
- improve source-verifiable settlement receipts
- publish updated telemetry/export evidence
**Deliverables**
- broader real-device wallet runtime evidence
- refreshed settlement evidence
- updated analytics and telemetry export packet
**Success signal**
- judges can inspect runtime and payout evidence as product surfaces, not internal notes
Milestone 4: mainnet release candidate or audited Devnet completion
**Timeline:** Week 4
**Objectives**
- perform mainnet cutover only if audit and custody closure are complete
- otherwise publish a fully hardened Devnet-complete release candidate with explicit blockers
**Deliverables**
- mainnet release candidate if conditions are closed
- otherwise a publicly reviewable, grant-complete Devnet release package
**Success signal**
- the project is either mainnet-ready or truthfully release-candidate-ready with no hidden blockers
Recommended primary KPI
**Success = reviewers can verify a coherent product, proof, telemetry, treasury, and trust corridor from the public site, with the remaining mainnet blockers explicitly bounded and actively shrinking.**
Supporting metrics:
- wallet-first governance flow works on Devnet
- telemetry export corridor remains live and reviewable
- confidential payout corridor remains evidence-backed
- custody/mainnet blocker count is reduced with linked evidence
- product remains accessible on web and Android surfaces
Honest boundary
Do not claim:
- finished external audit
- fully closed production multisig / custody ceremony
- completed monitoring closure
- complete mainnet real-funds readiness
Claim instead:
- live Devnet product
- open-source proof of work
- strong DAO tooling and payments fit
- credible mainnet path with explicit blockers
Best application posture
The strongest version of this grant application is:
- concise
- product-first
- proof-linked
- honest about blockers
- specific about why the capital accelerates decentralization, censorship resistance, DAO tooling, and payments
Best supporting packet set
- `/tracks/poland-grants`
- `/services`
- `/trust`
- `/documents/poland-foundation-grant-application-packet`
- `/documents/funding-readiness-scorecard`
- `/documents/mainnet-blockers`
That is more convincing than a feature list or an overconfident mainnet claim.