Grants: how to apply
- Copy the proposal template (section 7 of the grants document): team, category, description, use case on EmpoorioChain, technical plan, pallets used, KPIs, timeline, experience, special requests.
- Open a pull request adding
docs/grants/proposals/PROJECT_NAME.mdto the chain repository. - Open an issue titled
[GRANT] PROJECT_NAME — Category X. - The team acknowledges within 48 working hours.
One proposal per team per round. No fully closed-source projects; no direct forks without substantial changes. Existing projects wishing to integrate with EmpoorioChain are welcome.
Hackathon: how to submit
A repository link and a demo (video or live, ≥ 5 minutes) through the event's submission form, before the 48-hour deadline. The repository must be public and contain a README with reproduction steps.
KPIs every project must meet
| KPI | Minimum |
|---|---|
| Testnet transactions | ≥ 100, verifiable on EmpooScan |
| Source | Open, publicly accessible |
| Demo | ≥ 5 minutes showing the main flow |
| Documentation | README with reproducible deployment |
| Native pallet | At least one (not only EVM) |
Missing a KPI has no financial penalty — there are no funds — but the project is not listed as completed and receives no public mention.
Disqualification
Using testnet DMS for fraudulent or spam activity on chain.
Timeline (first grants round, as designed)
Call open week 1 · applications close week 3 · committee review weeks 4–5 · notification week 6 · onboarding weeks 7–8 · development through the following quarter · final demo at the end of it.
Status
Neither process is open. The grants document's own correction block says the programme cannot be announced until its faucet and explorer exist. A team can prepare a proposal today against the template; the PR will be reviewed when the call opens.
The event this page announced
Was another ecosystem's hackathon. The process above is EmpoorioChain's, and it is designed to be followed rather than admired.
Based on TESTNET_GRANTS_PROGRAM.md §4–6 and TESTNET_HACKATHON_PLAN.md.


