Grant-Xone Ecosystem Support Subsidy Program

We welcome applications from teams worldwide, with no geographical barriers. However, due to compliance and risk control requirements, the following principles apply:

• Compliance with local laws: The applicant’s jurisdiction must legally allow blockchain/Web3 R&D, operations, and funding acceptance. If the jurisdiction enforces a total ban or strict licensing on virtual asset activities (and no license is obtained), the application may be delayed or rejected.
• International sanctions screening: Projects from sanctioned regions, or controlled by sanctioned individuals/entities, are ineligible (lists include UN, OFAC (U.S.), EU, UK, etc.).
• Export control & compliance evidence: Projects involving cryptographic technology, software, or cross-border data transfer must follow export control and compliance rules. If uncertainty exists, applicants may be asked to provide a legal opinion or compliance certificate.
• Boundary & exceptions: For regions with unclear regulation, applicants can provide self-compliance proof (e.g., business registration, proof of legal operations, local law firm opinion). We will evaluate on a case-by-case basis.

Note: We do not make legal commitments for any jurisdiction; please seek compliance advice before applying.

• Different projects can apply separately: A single team’s different projects/sub-products may apply independently.
• Same project requires milestone completion: If applying for the same project’s next round, the previous milestones must be achieved and deliverables submitted (repo, release notes, testnet/mainnet proof, user data, or reports).
• Cooldown & parallel restrictions: A 90-day cooldown is suggested before reapplying; the same project cannot apply for multiple grants simultaneously (to prevent duplicate funding).
• Total cap & frequency control: Based on track record, impact, and financial health, we may set annual caps and frequency limits to ensure fairness and transparent fund allocation.

• Yes, commercial projects may apply: The condition is that they must be partially or fully open-source, or provide public goods/services (e.g., APIs, dev tools, educational content).
• Minimum open-source delivery: At least the core modules directly related to the grant must be open-sourced (e.g., protocol upgrades, contract libraries, SDK/CLI, node tools, indexers), under an OSI-approved license (MIT/Apache-2.0/GPL, etc.).
• Public usability requirement: If choosing “open service” instead of open code, access must be publicly verifiable and maintained for ≥12 months, ensuring reproducibility and preventing closed-source lock-in/paywalls.
• IP & re-licensing: Outputs funded by the grant usually require non-exclusive, global, irrevocable reuse rights for sustainability, while respecting your commercial rights.
• Transparency & disclosure: Token issuance, monetization models, or related-party transactions must be fully disclosed in the application and follow community transparency guidelines.

• Current method: Only on-chain XOC disbursement, in milestone-based installments, with multi-sig support for security.
• Future plan: Evaluation is underway for stablecoin (USDT/USDC) disbursement; updates will be published if implemented.
• Compliance & KYC/AML: For certain grant sizes or regions, basic KYC/AML checks may be required (for legal entities or designated recipients) to meet anti-money laundering and sanctions obligations.
• Fund usage & reporting: Grants must be used for deliverables-related R&D, audits, infra, and community building. Progress reports and expense breakdowns may be requested for disbursement verification.
• Risks & costs: On-chain disbursement involves price volatility and gas fees; applicants should account for budget buffers.