Lisk Grant Program Wave 5: How to Apply in 2026

Lisk extended its grant program, which committed 1.3 million in funding, to a fifth wave. A grant wave is a round of funding with its own application window, criteria and review process. Waves let an ecosystem fund new work in stages, so earlier rounds can inform later ones.

The extension matters because it signals that the program is still funding projects. It does not tell you how much any single applicant will receive, how many projects will be selected, or whether later waves will follow a similar pattern. Those details belong in the official announcement and terms for the wave you are looking at.

Before reading further, treat any claim about the wave's current status as something to verify. Programs can close, change scope or publish results at any point. This guide focuses on the parts that stay stable across waves: how grants work, how to decide whether to apply, how to prepare, and how to protect yourself.

If you are new to ecosystem funding, think of the grant as payment for a defined piece of work rather than a free gift. That framing will help you judge whether your idea fits and what you would need to deliver.

Grants and airdrops are both ways that blockchain projects distribute value, but they reward different things. A grant is usually paid to a builder or team for a proposal that the program has reviewed and accepted. The recipient normally agrees to deliver something, such as software, documentation, research or community work.

An airdrop is typically a distribution of tokens to wallets that meet certain conditions, such as past activity on a network or holding a particular asset. Airdrops often do not require a formal application, but eligibility is usually based on on-chain records and the rules are set in advance.

The two can overlap. A project might fund a builder with a grant and later distribute tokens to users. Some ecosystems also reward active participants through incentive campaigns, which are a third category with their own rules.

For readers, the practical difference is effort and expectation. A grant wave asks you to write a proposal and show you can deliver. An airdrop asks you to have been active in a qualifying way, often in the past. Confirm which mechanism applies before you spend time on it, and check whether any tokens or payments carry vesting schedules or other conditions.

Most grant waves follow a similar sequence, although exact steps differ by program. First, the program publishes a call for proposals with a theme, eligibility rules and a deadline. Second, applicants submit a written proposal, often with a budget and milestones. Third, reviewers assess proposals against the published criteria. Fourth, selected teams sign an agreement and receive funding, usually in tranches tied to progress.

Some programs add interviews, community votes or public feedback periods. Others review applications privately. Expect that reviewers may ask for clarifications, and that timing can slip. Waves also tend to have limited budgets, so a strong proposal may still be declined if the funds are committed.

Milestone-based payment is common because it protects both sides. You are paid as you deliver defined outputs, and the funder is not paying for work that never happens. Read the terms for how and when money is released, what happens if you miss a milestone, and who owns the work you produce.

Keep a copy of your submitted proposal and every agreement. If the program changes its process, your records will help you show what was promised.

Because this guide is evergreen, it does not state the current status of the fifth wave. To find out, follow these steps in order.

1. Open the official Lisk website and look for a grants or ecosystem funding section.
2. Find the announcement for the fifth wave and note its application window, eligibility rules and any changes.
3. Check the official documentation or grant portal for the forms, templates and submission process.
4. Look at the verified social accounts linked from the official site for updates, but do not treat direct messages as official.
5. If results have been published, read them to understand what kinds of proposals were funded.

If you find conflicting dates or amounts across sources, rely on the official announcement and the terms it links to. Save a copy of the page you read, with its date, so you can refer back to it.

Do not submit a proposal through a link you received in a message or comment. Type the address yourself or use a bookmark you created from the official site.

Eligibility rules are set by each wave, so the list below describes common patterns rather than promised criteria. Programs of this kind often look for builders who can show relevant experience, a clear plan and a need for the work they describe. Individuals, small teams and established companies may all apply, depending on the program's terms.

The following factors often matter in review:

• A specific problem the proposal addresses within the ecosystem
• A team with verifiable experience or a track record of similar work
• A realistic budget that matches the scope
• Milestones that can be checked by someone other than the applicant
• Plans for documentation, open-source code or community benefit, where the program asks for them

Some programs exclude certain categories, such as projects that only promote a token or that duplicate existing tools. Others restrict participation based on location or legal status. Read the eligibility section closely, and if a rule is unclear, ask the program team through the official channel before you apply.

Do not assume that a past contribution guarantees a grant. Each wave is judged on its own proposals.

A good application explains the problem, the solution and the path to delivery in plain language. Reviewers often read many proposals quickly, so clarity matters more than length.

A practical structure is:

1. Summary: one paragraph stating what you will build or do and who it serves.
2. Problem: the gap in the ecosystem and the evidence that it exists.
3. Approach: the technical or operational method, with any dependencies named.
4. Milestones: dated or sequenced deliverables with clear completion criteria.
5. Budget: what each milestone costs and why, without padding.
6. Team: roles, relevant experience and who is accountable.
7. Risks: what could delay you and how you would respond.

Avoid promises you cannot check, such as user numbers or market size without a source. Use the program's template if one exists. Ask a peer to read the proposal and tell you where it is unclear.

If the wave requires code, link to repositories only through the official submission form or through information you have verified on the official site. Keep your public materials consistent with what you submit.

Grant programs attract impersonators, especially when a public deadline is near. Common warning signs include unsolicited messages offering approval, requests for a seed phrase or private key, demands for an upfront payment or deposit, and pressure to act within minutes.

Legitimate program teams do not need your seed phrase to review a proposal, and they do not ask you to send crypto to unlock a grant. If anyone asks for either, stop communicating and treat the request as a likely attack.

Use these defensive habits:

• Bookmark the official website and open it from the bookmark, not from a search result or a message
• Check the spelling of domains character by character
• Enable two-factor authentication on email and any exchange accounts you use
• Be cautious with browser extensions or wallet connection prompts that you did not expect
• Verify any new contact by checking the official channel listed on the program's site

If you have already shared a seed phrase or signed an unexpected transaction, move remaining funds to a new wallet you control, revoke token approvals you do not recognise, and report the incident to the platform involved.

Your wallet is both a tool and a target during any token-related program. Keep your seed phrase offline and never type it into a website or give it to anyone, including someone claiming to be support staff.

Consider using a separate wallet for interacting with new applications, so that a mistake does not expose your main holdings. Hardware wallets add a layer of protection because signing happens on the device. Review every transaction and approval request in full before confirming.

For the account side, use a unique password for each service, a password manager if you can, and two-factor authentication that does not rely only on SMS. Check your email for login alerts and treat unexpected password reset emails with caution.

If you receive tokens or payments, confirm the exact token contract address from the official source before adding it to your wallet. Fake tokens with familiar names are common. Do not send funds to an address you have not verified.

Nothing in this guide is personalised financial or security advice. Choose tools and practices that match your own risk tolerance and the value you are holding.

Missing one wave does not close off ecosystem funding permanently. Many programs run more than one round, and their criteria may change. Use the time to strengthen the skills and work that a future proposal would need.

Some useful steps include:

• Contributing to open-source tools or documentation in the ecosystem, where licensing permits
• Building a small, working prototype and writing down what you learned
• Joining official community discussions to understand what the ecosystem needs
• Tracking the official announcements so you can apply quickly when a new wave opens
• Keeping a template proposal you can adapt to each call

If you were not selected, ask whether feedback is available. Feedback, where offered, helps you refine your next application.

Whether you apply or not, remember that participation in any incentive program carries risk, including loss of time, unexpected tax obligations and the volatility of token prices. Make decisions you can justify without assuming any particular return.