2024. 5. 19.

2024. 5. 19.

2024. 5. 19.

Big Shipment Edition

Big Shipment Edition

Big Shipment Edition

Step Aside, Pablo⚡️

Step Aside, Pablo⚡️

Step Aside, Pablo⚡️

Bug Reporting Mission

Early-stage projects thrive on early user feedback, which is why we recently built a Forms mission that allows projects to collect feedback from users. While a generic mechanism to collect feedback is useful, projects oftentimes want to collect specific feedback on prodouct functionality—if something doesn’t work, it needs to be fixed 🐞

For this reason, we built a Bug Reporting mission, which allows users to provide bug reports and earn whitelist amount/tokens for their efforts. The Bug Reporting mission is basically our Forms mission, with three major tweaks:

  1. Pre-populated Questions instead of an empty form: Bug reports should be submitted in a standardised format.

  2. Allow users to upload files to answer a question: The ability to resolve bugs often hinges on developers seeing the exact user journey; screenshots and screen recordings help.

  3. A ticketing system in addition to Analytics: When feedback is collected via a form, the collected data needs to be displayed in an easily-digestible fashion. When bugs are reported, we also need a ticketing system that allows (a) deleting of reported bugs that are non-issues & (b) resolving bugs that have been taken care of.

The main benefit of this feature is that projects can rely on a single tool to collect and reward bug reports, rather than having to set up their own makeshift solution with a combination of five different tools.


ZAP Vault Mission Type

To recap, ZAP Vaults unlock exclusive benefits on ZAP. This includes daily token emissions, NFT Drops, and early access to features. ZAP Vault holders are an attractive community for projects launching on ZAP to tap into. As a result, it makes sense to allow missions specifically geared towards Vault holders. The flow looks like this:

  1. Project sets up a ZAP Vault mission on ZAP

  2. User verifies on-chain that they hold a Vault

  3. User receives reward from project (token/whitelist amount)

  4. User starts engaging with the project

Not only does this flow allow projects to get attract attention of ZAP Vault holders, but Vault holders also get to eat benefits exclusive to them 🍝


Variable Reward Logic

We generally believe in keeping things simple. However, adding complexity isn’t always bad.

Users on ZAP receive rewards for completing missions. Up until now, reward amounts followed a straight-forward logic. For example, a user who holds more than one Vault, receives 100 XP.

Easy to understand, but quite limiting. To solve this constraint, we’ve introduced variable reward logic which can follow either a linear or tiered logic:

  • linear: A user receives 100 XP for every Vault they hold.

  • tiered: A user receives 100 XP per Vault for holding the first 1-3 Vaults. Then, they receive 200 XP per Vault for holding 4-6 Vaults, and so on.

You get the idea 💡 While we’ve added complexity to the reward logic, we’ve certainly not made added any unnecessary fuzz for our users. One additional line to the UI, nothing more 🤌



Twitter Views Mission

Saving the best for last 😈 This one was inspired by our friends over at Pacmoon, who have been killing it on Twitter. If you’re following the space, you’ve heard of and seen Pacmoon on your timeline. They elegantly incentivise Twitter users and content creators to post about them in return for some Pacmoon tokens—which clearly works.

Naturally, we had to build our own system that encourages people to post about ZAP and lets them earn XP for our airdrop. How exactly does it work? Basically, you can earn XP by posting about ZAP on Twitter—all you need to do is make sure your Twitter handle is connected on ZAP and your dashboard will start racking up XP.


Bugs

Check out our public board here

This week in numbers

🐞 Bugs outstanding: 61
🔨 Bugs fixed this week: 3

Damn, another mental shift from the team. This is what happens when you’re building cool sh!t and are having lots of fun along the way. We can’t wait to show you what we’ve got cooking next week—it will be a beautiful sight to behold 🖼️

Love
Carlo, Ralph, Xiao Xu, Salt, Badge, Prodigo, Kunal (ZAP Product Team)

Bug Reporting Mission

Early-stage projects thrive on early user feedback, which is why we recently built a Forms mission that allows projects to collect feedback from users. While a generic mechanism to collect feedback is useful, projects oftentimes want to collect specific feedback on prodouct functionality—if something doesn’t work, it needs to be fixed 🐞

For this reason, we built a Bug Reporting mission, which allows users to provide bug reports and earn whitelist amount/tokens for their efforts. The Bug Reporting mission is basically our Forms mission, with three major tweaks:

  1. Pre-populated Questions instead of an empty form: Bug reports should be submitted in a standardised format.

  2. Allow users to upload files to answer a question: The ability to resolve bugs often hinges on developers seeing the exact user journey; screenshots and screen recordings help.

  3. A ticketing system in addition to Analytics: When feedback is collected via a form, the collected data needs to be displayed in an easily-digestible fashion. When bugs are reported, we also need a ticketing system that allows (a) deleting of reported bugs that are non-issues & (b) resolving bugs that have been taken care of.

The main benefit of this feature is that projects can rely on a single tool to collect and reward bug reports, rather than having to set up their own makeshift solution with a combination of five different tools.


ZAP Vault Mission Type

To recap, ZAP Vaults unlock exclusive benefits on ZAP. This includes daily token emissions, NFT Drops, and early access to features. ZAP Vault holders are an attractive community for projects launching on ZAP to tap into. As a result, it makes sense to allow missions specifically geared towards Vault holders. The flow looks like this:

  1. Project sets up a ZAP Vault mission on ZAP

  2. User verifies on-chain that they hold a Vault

  3. User receives reward from project (token/whitelist amount)

  4. User starts engaging with the project

Not only does this flow allow projects to get attract attention of ZAP Vault holders, but Vault holders also get to eat benefits exclusive to them 🍝


Variable Reward Logic

We generally believe in keeping things simple. However, adding complexity isn’t always bad.

Users on ZAP receive rewards for completing missions. Up until now, reward amounts followed a straight-forward logic. For example, a user who holds more than one Vault, receives 100 XP.

Easy to understand, but quite limiting. To solve this constraint, we’ve introduced variable reward logic which can follow either a linear or tiered logic:

  • linear: A user receives 100 XP for every Vault they hold.

  • tiered: A user receives 100 XP per Vault for holding the first 1-3 Vaults. Then, they receive 200 XP per Vault for holding 4-6 Vaults, and so on.

You get the idea 💡 While we’ve added complexity to the reward logic, we’ve certainly not made added any unnecessary fuzz for our users. One additional line to the UI, nothing more 🤌



Twitter Views Mission

Saving the best for last 😈 This one was inspired by our friends over at Pacmoon, who have been killing it on Twitter. If you’re following the space, you’ve heard of and seen Pacmoon on your timeline. They elegantly incentivise Twitter users and content creators to post about them in return for some Pacmoon tokens—which clearly works.

Naturally, we had to build our own system that encourages people to post about ZAP and lets them earn XP for our airdrop. How exactly does it work? Basically, you can earn XP by posting about ZAP on Twitter—all you need to do is make sure your Twitter handle is connected on ZAP and your dashboard will start racking up XP.


Bugs

Check out our public board here

This week in numbers

🐞 Bugs outstanding: 61
🔨 Bugs fixed this week: 3

Damn, another mental shift from the team. This is what happens when you’re building cool sh!t and are having lots of fun along the way. We can’t wait to show you what we’ve got cooking next week—it will be a beautiful sight to behold 🖼️

Love
Carlo, Ralph, Xiao Xu, Salt, Badge, Prodigo, Kunal (ZAP Product Team)

Bug Reporting Mission

Early-stage projects thrive on early user feedback, which is why we recently built a Forms mission that allows projects to collect feedback from users. While a generic mechanism to collect feedback is useful, projects oftentimes want to collect specific feedback on prodouct functionality—if something doesn’t work, it needs to be fixed 🐞

For this reason, we built a Bug Reporting mission, which allows users to provide bug reports and earn whitelist amount/tokens for their efforts. The Bug Reporting mission is basically our Forms mission, with three major tweaks:

  1. Pre-populated Questions instead of an empty form: Bug reports should be submitted in a standardised format.

  2. Allow users to upload files to answer a question: The ability to resolve bugs often hinges on developers seeing the exact user journey; screenshots and screen recordings help.

  3. A ticketing system in addition to Analytics: When feedback is collected via a form, the collected data needs to be displayed in an easily-digestible fashion. When bugs are reported, we also need a ticketing system that allows (a) deleting of reported bugs that are non-issues & (b) resolving bugs that have been taken care of.

The main benefit of this feature is that projects can rely on a single tool to collect and reward bug reports, rather than having to set up their own makeshift solution with a combination of five different tools.


ZAP Vault Mission Type

To recap, ZAP Vaults unlock exclusive benefits on ZAP. This includes daily token emissions, NFT Drops, and early access to features. ZAP Vault holders are an attractive community for projects launching on ZAP to tap into. As a result, it makes sense to allow missions specifically geared towards Vault holders. The flow looks like this:

  1. Project sets up a ZAP Vault mission on ZAP

  2. User verifies on-chain that they hold a Vault

  3. User receives reward from project (token/whitelist amount)

  4. User starts engaging with the project

Not only does this flow allow projects to get attract attention of ZAP Vault holders, but Vault holders also get to eat benefits exclusive to them 🍝


Variable Reward Logic

We generally believe in keeping things simple. However, adding complexity isn’t always bad.

Users on ZAP receive rewards for completing missions. Up until now, reward amounts followed a straight-forward logic. For example, a user who holds more than one Vault, receives 100 XP.

Easy to understand, but quite limiting. To solve this constraint, we’ve introduced variable reward logic which can follow either a linear or tiered logic:

  • linear: A user receives 100 XP for every Vault they hold.

  • tiered: A user receives 100 XP per Vault for holding the first 1-3 Vaults. Then, they receive 200 XP per Vault for holding 4-6 Vaults, and so on.

You get the idea 💡 While we’ve added complexity to the reward logic, we’ve certainly not made added any unnecessary fuzz for our users. One additional line to the UI, nothing more 🤌



Twitter Views Mission

Saving the best for last 😈 This one was inspired by our friends over at Pacmoon, who have been killing it on Twitter. If you’re following the space, you’ve heard of and seen Pacmoon on your timeline. They elegantly incentivise Twitter users and content creators to post about them in return for some Pacmoon tokens—which clearly works.

Naturally, we had to build our own system that encourages people to post about ZAP and lets them earn XP for our airdrop. How exactly does it work? Basically, you can earn XP by posting about ZAP on Twitter—all you need to do is make sure your Twitter handle is connected on ZAP and your dashboard will start racking up XP.


Bugs

Check out our public board here

This week in numbers

🐞 Bugs outstanding: 61
🔨 Bugs fixed this week: 3

Damn, another mental shift from the team. This is what happens when you’re building cool sh!t and are having lots of fun along the way. We can’t wait to show you what we’ve got cooking next week—it will be a beautiful sight to behold 🖼️

Love
Carlo, Ralph, Xiao Xu, Salt, Badge, Prodigo, Kunal (ZAP Product Team)

More Updates

Subscribe to Updates

Add your email below to receive an email for every newly launched feature we announce.

Subscribe to Updates

Add your email below to receive an email for every newly launched feature we announce.

Subscribe to Updates

Add your email below to receive an email for every newly launched feature we announce.