Zemo - Your Web3 Inbox

Hey all!

We’re back at it again. Today, I’m very excited to announce that we re-opened our proposal to build Zemo.

What’s new?
We made some changes based on prior feedback. Our team is now leaner. And therefore the cost to build Zemo is lower.

Applicant background

Our team collectively has 10+ years experience shipping Bitcoin, Zcash, and crypto applications. We have worked professionally on blockchain projects funded by world-class investors. We specialize in building decentralized applications that are easy to use. Chris is well known for building the server that powered OpenBazaar and Haven.

Description of Problem or Opportunity

Shielded messaging has risen to become a popular use case in the Zcash community. In order to grow and expand this use case, we need apps that are specifically designed for messaging.

Many of us already send shielded messages to each other with small tips. We’ve found it’s a great way to onboard new users into the Zcash ecosystem. However, we’re still using apps that were designed for payments.

Zemo is messaging first, powered by Zcash.


(not actual Zooko messages)

Proposed Solution

Zemo is your Web3 inbox powered by the Zcash blockchain. It’s the first Zcash mobile app created specifically for messaging. It’s monetizable, permissionless, open-source, decentralized, end-to-end encrypted, immutable and full self-custody – your keys, your messages.

Use Zemo to monetize your inbound messages and/or send private message.

Solution Format

We’ll release Zemo as an Android & iOS app in the app stores that include: threaded conversations, basic user profiles (optional: avatar and name), payments, fast syncing, and intuitive UI/UX. We’ll also create a landing page at https://zemo.app.

Technical approach

The UI/UX design of Zemo will happen in-house by Ziga. We’ll share Figma prototypes with the community for feedback. This process has already started.

As for the code, we’re building the app on React Native. We’ll use ZECwallet’s code as a starting point to ensure the app syncs quickly and functions well.

In order to provide a better messaging experience, we’ll rework ZECwallet where needed. For example, each message will be encoded with the user’s display name, avatar hash from IPFS and z-address (optional, for replying).

To ensure there is interoperability between Zcash payment and messaging apps, we’ll coordinate with other wallet devs and ECC to ensure our approach is suitable for everyone to build upon.

All of our work will be released as open-source software on GitHub.

How big of a problem would it be to not solve this problem?

Messaging is already a growing use case in the Zcash community. Not building apps that are designed for messaging is a missed opportunity. Zemo will grow and expand our community — one message at a time.

Execution risks

Most of the challenging pieces for Zemo are around the messaging components. We’re going into this expecting some unexpected challenges to creep up. At worst, we expect this could slow us down, but hopefully not by too much.

Unintended Consequences

If messaging turns out to be a popular use case, we run the risk of flooding the blockchain with micropayments. If L1 does not scale well, micropayments on Zcash may be priced out due to rising fees.

Theoretically, Zemo could eventually move to a L2, if needed.

Evaluation plan

Upon completion, a user can send/receive private messages, view threaded conversations, send Zcash payments, set basic profile information (display name and avatar) and use Zemo as their Web3 monetizable inbox.

Schedule and Milestones

Our team is available to start working on Zemo in March. We estimate the project will take 6 months to complete. Please see milestones for additional details.

Budget

We’ve structured our milestones as monthly payouts to ensure each team member can cover their living expenses.

Monthly cost
Staff: $30,000 x 6 months = $180,000

At 40hrs a week, the cost per person per hr is $93.75.

14 Likes

I’ll post the link to the proposal on the zfgrants website once it is live. Waiting for it to be approved.

2 Likes

Question: How do you plan to store the metadata (avatars, usernames, etc)?

Criticism: The whole “Web3” marketing speak and then limiting this to only be accessible on an Android or iOS phone feels maligned, in my opinion. Web3 is a meme term, IMO, but the next evolution of the currently corporate-incentivized web needs to be accessible from a browser for everyone. Not by requiring access on devices controlled by trillion dollar companies.

Final thought: Price tag seems a bit rich for a forked version of ZECWallet with ZECPages functionality in it.

1 Like

The avatars will be stored on IPFS. We’re considering using a pinning service to keep them fresh. Display names will be encoded into the actual messages. This is what we currently have planned, subject to change. Also, these would be optional — not forced to upload an image or set a name.

I’m not going to comment on the Web3 term. It’s up to everyone to decide if they like the term or not.

6 Likes

The proposal is now live:

4 Likes

I think the price tag is not high to ship high quality & smooth mobile apps on both app stores.

8 Likes

FWIW time estimate of 6months looks reasonable to me.

5 Likes

I’m a fan of encrypted messaging services. The proposal seems reasonable to me and I would be happy to access the service when it becomes available. If it’s built on Zcash technology, it’s worth it.

5 Likes
  1. It’s React Native.
  2. It’s purportedly borrowing heavily with ZECWallet’s React components (and other JS code: zecwallet-lite/src at master · adityapk00/zecwallet-lite · GitHub)
  3. It’s React Native…

Additionally: Remember this grant? Elemental ZEC – UI Component Kit and Payment Processor. Would this wallet be using any of that or are these just two silo’d projects? I don’t know how much @ziga’s stuff influences that project or vice versa, but it would seem like a missed opportunity to not re-use things here.

@ziga is a decent designer. I noticed much of the community being dazzled by the nice designs they saw with the zeme.team website and it was funded and built. Unfortunately, once that project was “completed”, no focus was spent on the marketing part of it so it left to rot in a corner on the internet.

That is what I’m afraid of here. It’s going to be incredibly hard to:

  1. Onboard new users to ZEC (KYC => exchange => fiat => ZEC)
  2. Get them to download this wallet
  3. Get them to consistently fund it with money so they can use it when they run low
  4. Continue to grow the network

From " Unintended Consequences", you mention:

So you’re basically admitting you don’t know if this will be popular, but if it is (and let’s hope it is if it gets funded) , it would need to move to an L2 that probably wouldn’t be supported for another couple years.

If/when this thing needs updates are you going to update it for free? Will you ask for another grant?

I really struggle to envision how you intend to grow a messaging app on a blockchain with already a lot of friction for the common person to use. Signal is much easier, and has a wider moat at this point given most of my friends and family are on it.

I would be more interested in seeing this becoming a new reddit or 4chan with boards like ZECPages than yet another chat app.

1 Like

Additionally: Remember this grant? Elemental ZEC – UI Component Kit and Payment Processor. Would this wallet be using any of that or are these just two silo’d projects? I don’t know how much @ziga’s stuff influences that project or vice versa, but it would seem like a missed opportunity to not re-use things here.

As mentioned in the proposal, we’re planning to use the ZECwallet code base as a starting point, which is also funded by ZF/Zcash grants. We can’t guarantee we will make use of every library that has been previously funded by the grant team. We’ll use what makes sense for our application.

@ziga is a decent designer. I noticed much of the community being dazzled by the nice designs they saw with the zeme.team website and it was funded and built. Unfortunately, once that project was “completed”, no focus was spent on the marketing part of it so it left to rot in a corner on the internet.

Correct, we completed the ZT project as it was defined in the grant proposal. Actually, I put in quite a lot of extra effort tipping creators for many months after ZT launched. Most of the tips came directly from my own personal funds because I returned $4,000 to ZF.

I do all of the moderation work unpaid and I still run the website today approving/disproving posts weekly without payment.

I plan to continue to promote ZT through my Twitter channel. I’m committed to helping creators get paid for their work. If you want to help too, please contact me.

So you’re basically admitting you don’t know if this will be popular, but if it is (and let’s hope it is if it gets funded) , it would need to move to an L2 that probably wouldn’t be supported for another couple years.

No, I’m not admitting that. My point was if messaging becomes very popular on Zcash, we would run the risk of rising network fees. Zemo will definitely get usage. Exactly how much usage is impossible to determine. It’s a product that will grow as general crypto and Zcash adoption grows. I don’t expect L2s will be necessary any time soon. Zcash has a lot of available block space for the foreseeable future.

If/when this thing needs updates are you going to update it for free? Will you ask for another grant?

I’m sure we’ll end up putting in many hours of unpaid work after Zemo launches supporting bug fixes and whatnot. We’ve already put in more than a month of unpaid work into planning Zemo, creating design prototypes, branding, and teasing the idea on social media.

Additional features, major network upgrades, etc. would take more coordination and additional follow-on grants.

I would be more interested in seeing this becoming a new reddit or 4chan with boards like ZECPages than yet another chat app.

Zemo is not trying to be a reddit or 4chan service. We’re focusing on creating a monetizable Web3 inbox.

4 Likes

I personally like this grant. Messaging is pretty popular and payments are pretty popular. I think Venmo is kind of a good comparison for this app. People only really send Venmo payments when they have to pay someone, but the message part is a very popular feature for making payments fun or at least informative.

The main difference here is that people would use Zemo with a messaging-first mentality. Although this may not always be the case, since it could be a go to place to be able to pay your close friends who you have a history of paying or messaging.

Plus I like the idea of bringing in more designers to the wallet space. More and diverse wallets is also good for decentralization.

The main question is how popular will Zcash-based messaging really be? It may grow and become a mainstay feature of Zcash, or evolve in ways that couldn’t be predicted. It may also be something only used by the few hundred people that are out there that love playing with Zcash txns.

Best of luck!

6 Likes

Thank you for the thoughtful response @David_Heisenberg

I personally like this grant. Messaging is pretty popular and payments are pretty popular. I think Venmo is kind of a good comparison for this app. People only really send Venmo payments when they have to pay someone, but the message part is a very popular feature for making payments fun or at least informative.

The main difference here is that people would use Zemo with a messaging-first mentality. Although this may not always be the case, since it could be a go to place to be able to pay your close friends who you have a history of paying or messaging.

:+1:

You make some good points. Zemo is messaging and payments built into one. I think of Zemo as messaging first, but it’s really both payments and messaging. The app experience will be designed to feel like a basic messaging experience.

Users can decide to use Zemo as their go-to Zcash payment app for social payments (Venmo style) or use it as a casual messaging app with others in the Zcash community, friends, family, etc.

Plus I like the idea of bringing in more designers to the wallet space. More and diverse wallets is also good for decentralization.

This is why we’re excited to build Zemo. We’re prioritizing memos first, payments second. We’re attempting to use Zcash’s functionality in a different way, paving the way for a new wave of growth of usage for Zcash.

The main question is how popular will Zcash-based messaging really be? It may grow and become a mainstay feature of Zcash, or evolve in ways that couldn’t be predicted. It may also be something only used by the few hundred people that are out there that love playing with Zcash txns.

The good news is we’ve seen many people on social media wanting to try shielded payments/messages on Zcash. Zooko, myself and others have easily onboarded hundreds of people with a shielded message and a few cents worth of Zcash.

This acquisition strategy could grow Zemo to its first 1000+ users.

It may grow and become a mainstay feature of Zcash, or evolve in ways that couldn’t be predicted.

If we onboard crypto influencers to start a Zemo inbox, it could be a great way for them to monetize their attention. A monentizable inbox (with web3 properties) is a new idea that could catch on.

I’ve also started to think about how bots could play a role in the experience. Devs could create text based games that are used on the Zcash blockchain. For example, there could be a blackjack bot that requires a payment of 0.1 ZEC to start a game. Send a message to the bot’s z-addr and the bot will play the game against you. We’re not planning to build these, but really anyone could spin up their own infrastructure to create bots that require zcash payment to use.

It may also be something only used by the few hundred people that are out there that love playing with Zcash txns.

To put things into perspective, the number of fully shielded txs per month on Zcash is somewhere around ~5,000.

If Zemo had 100 daily users, each sending 5 messages per day, we would produce 15,000 shielded txs per month. ~3x the current monthly average.

5 Likes

Re the criticism about devices, what’s your feeling about how Signal works? It’s an app on devices, but there’s also a desktop version. It doesn’t work in a browser. Would this be more appealing if desktop for major OS’s including *nix were one of the available options?

2 Likes

If there was enough demand to bring Zemo to desktop, we could eventually build an electron app for Mac, Windows and Linux.

Web is a lot more challenging because of the key management issues.

3 Likes

I understand the concerns of ZCG but I think this application of Zcash is something I’d still like to see explored. I cant speak for ZCG but for the price the lack of a web version is a concern.

I think until we have access to a browser based wallet (e.g. zephyr?) I’d argue we delay any duplicate effort on private key management. I have no idea if this would sway ZCG in anyway but would a react-native-web version with view-keys only be possible within the scope of this project? Also providing users the ability to provide links to the web view etc?

Just my 2 zats as a potential users :relaxed:.

2 Likes

I understand the concerns of ZCG but I think this application of Zcash is something I’d still like to see explored.

Thank you for the suggestion @GGuy. The concerns from ZCG haven’t been communicated to me yet, so I’d prefer to give them a chance to weigh in before I comment on the additional features suggested. :slightly_smiling_face:


Considering how complex this project would be, I was expecting there would be some type of direct communication with the grant committee to discuss the proposal in more detail.

Due to the character limitations on the grant proposal website, we didn’t mention many of the additional features that we were planning to include in the proposal, such as:

  • Multiple user profiles per wallet
  • Toggle between user profiles
  • Dark theme / light theme (auto detect)
  • Multiple language support (English, Spanish, Russian, etc)
  • Multiple fiat currency support
  • Biometrics security (touch id, face id)
  • Block user (the app store requires additional functionality for social apps)
  • Manage block user list w/ unblock ability
  • Introducing new format for messaging (the current reply-to approach used in other wallets is not ideal)
  • Real-time messaging
  • User avatars stored on custom IPFS gateway (create our own infrastructure or use service provider)
  • Settings ability to change to different IPFS gateways
  • Auto restore avatar / name when restoring from seed
  • Settings ability to disable displaying/fetching avatars (for extra security)

I’m probably forgetting some other features.

4 Likes

loving it :heart_eyes:
hope this goes through

1 Like

Sorry for the delay in sending a forum posts that elaborate ZCG’s questions about Zemo. First, let me say that I personally love the enthusiasm and the track record you have of completing grants with ZCG. In my personal opinion, the concerns around Zemo is more about correctly evaluating cost, use case timing, and coordination with others. I will outline the specifics points we had questions about below:

  1. Quick anecdote: I have been an advisor to Status for at least 4 years. Status is a mobile crypto wallet and messaging platform that uses a decentralized messaging framework for censorship resistant conversations. Status has not seen very much growth/adoption, even when there are loud complaints from various crypto communities for alternatives to Discord and Slack. Although I feel like their team had great ideas and were super early innovators, things didn’t pan out because building, maintaining, and marketing a messaging app is very difficult.
    Status’s messaging platform in their app did not require payment, but it seems like Zemo’s would if they were publishing shielded memos to the chain. It is hard for me, personally, to see people replacing Signal and other messengers with E2E messaging with Zemo when it will cost $. Even if the costs are fractions of a penny at first, shifts in ZEC price or explosions in adoption will make the messaging costs rise, especially with heavy use. You mention potentially moving to L2s, but in my opinion L2s are just getting their grounding in other ecosystems like Ethereum and it has taken years for building and adoption.

  2. You mentioned in the grant you plan to coordinate with other wallet devs and the ECC. Have you connected with anyone from either of those groups yet and what was their feedback? This will be helpful because you also mentioned in the grant that you want your code to be open sourced and for others to build on it.

  3. ZecWallet is a barebone, minimalist Zcash app for sending payments. How do you plan on repurposing the app? Specifically, would you be making upstream changes to ZecWallet, would users need to download both a ZecWallet App and a Zemo app, and would there be an import function for keys from the ZecWallet app to import to the Zemo app?

  4. Has your team deployed mobile apps? If yes, please list them.

  5. As the potential launch will be in 2nd half of the year, do you plan to support Unified Addresses by default?

  6. Conversation apps are complex and we would like more details of implementation beyond a few paragraphs of intro.

  7. Modifying the existing ZecWallet codebase to Messaging first is manageable, what often gets overlooked is the cost of ongoing maintenance. Who is going to keep up to date with the fixes for the underlying codebase? What would those costs look like after the 6 months funding period?

  8. ZecWallet’s future is uncertain as @adityapk00 has taken a step back, how do you plan on maintaining a fork a customized codebase that is partly diverged from the upstream lightwalletd backend service? Who will be responsible to maintain the app in the App Store/Play Store?

  9. You mention in the grant “Shielded messaging has risen to become a popular use case in the Zcash community.” What information are you using to back up this statement?

  10. How would you be licensing your software and how does your license interact (if at all) with ZecWallet’s?

  11. What is the rationale for using IPFS for the avatars? Pinning in IPFS is still dependent on a server deciding to pin the avatar and if you plan on holding that data forever it is no better than an AWS server for for the sole purpose of storing pictures. Many NFTs on Ethereum use IPFS for their images and now no longer have access to the images for the NFTs because the startup who made the NFT decided to stop pinning the image.

  12. How many team members will be working on Zemo? The budget seems high for a 2 person team based on some previous grants that have been administered.

Thank you for taking the time to read through this and respond. Sorry again for the delay!

10 Likes

Sorry for the delay in sending a forum posts that elaborate ZCG’s questions about Zemo. First, let me say that I personally love the enthusiasm and the track record you have of completing grants with ZCG. In my personal opinion, the concerns around Zemo is more about correctly evaluating cost, use case timing, and coordination with others. I will outline the specifics points we had questions about below:

I appreciate the good words and the apology. :beers:

Quick anecdote: I have been an advisor to Status for at least 4 years. Status is a mobile crypto wallet and messaging platform that uses a decentralized messaging framework for censorship resistant conversations. Status has not seen very much growth/adoption, even when there are loud complaints from various crypto communities for alternatives to Discord and Slack. Although I feel like their team had great ideas and were super early innovators, things didn’t pan out because building, maintaining, and marketing a messaging app is very difficult.
Status’s messaging platform in their app did not require payment, but it seems like Zemo’s would if they were publishing shielded memos to the chain. It is hard for me, personally, to see people replacing Signal and other messengers with E2E messaging with Zemo when it will cost $. Even if the costs are fractions of a penny at first, shifts in ZEC price or explosions in adoption will make the messaging costs rise, especially with heavy use. You mention potentially moving to L2s, but in my opinion L2s are just getting their grounding in other ecosystems like Ethereum and it has taken years for building and adoption.

Thanks for sharing. Status is a great app. I’ve been a user for years.

You mentioned Status has not seen very much growth/adoption. It’s probably important to define what you mean by “very much”. I did some digging into Status’s quarterly reports, and Status seems to be showing impressive growth by my standards. In their Q1 2021 report, they’ve stated they grew by 830,000 users across 190 markets.

It is hard for me, personally, to see people replacing Signal and other messengers with E2E messaging with Zemo when it will cost $

I agree. Free messaging will always win out for casual conversations. With that said, I don’t feel we’re competing on the same use case. Zemo introduces new use cases due the nature of having payments built into each message. Think of Zemo more as a way to monetize your attention vs conducting casual conversations.

For good reason, you or I wouldn’t freely share our private Signal handles or email address on social media. It would result in an enormous amount of people filling our unpaid inboxes. Zemo encourages people to do just that. The whole idea is for people to share their z-addr publicly so that more people can write to them. It’s a paid inbox that people must pay to write to. Each inbound message comes with an incentive. I refer to it as a Web3 inbox.

You mention potentially moving to L2s, but in my opinion L2s are just getting their grounding in other ecosystems like Ethereum and it has taken years for building and adoption.

It’s been exciting to see the recent developments in L2 tech. I estimate that Zemo would need somewhere around ~1M daily active users in order to fill all of L1’s capacity as it exists today. Realistically, that’s not going to happen anytime soon.

You mentioned in the grant you plan to coordinate with other wallet devs and the ECC. Have you connected with anyone from either of those groups yet and what was their feedback? This will be helpful because you also mentioned in the grant that you want your code to be open sourced and for others to build on it.

There have been some very casual Twitter conversations floating out there, but nothing concrete yet. We have this work scheduled for our 1st milestone.

The biggest rough edge to smooth over here is how we’re currently using the ‘reply-to’ approach used across wallet apps, which is not a viable solution. We plan to coordinate on how to improve Zcash memos for messaging and develop a more practical standard each wallet provider can inherit.

ZecWallet is a barebone, minimalist Zcash app for sending payments. How do you plan on repurposing the app? Specifically, would you be making upstream changes to ZecWallet, would users need to download both a ZecWallet App and a Zemo app, and would there be an import function for keys from the ZecWallet app to import to the Zemo app?

Zemo will be coded from the ground up. We plan to use ZecWallet mostly as a reference. In the end, there will be more differences than similarities, and therefore it makes more sense to start from a fresh codebase. With that said, we do expect we can cherry pick a lot of good code from ZecWallet to streamline our process. There’s no need to reinvent everything.

Users won’t need ZecWallet installed in order to use Zemo. Zemo is a full standalone app.

Yes, we’re planning that a seed from other wallets can be imported into Zemo. Zemo underneath the messaging-like UI is still a full wallet app, but with a different presentation layer.

For example, importing a seed with multiple z-addresses into Zemo would break each address into a unique user profile in Zemo. Toggleing through z-addresses on Zemo would switch between different user profiles.

Has your team deployed mobile apps? If yes, please list them.

Yes, many. I’ll reach out and provide a list.

As the potential launch will be in 2nd half of the year, do you plan to support Unified Addresses by default?

I’ve put a lot of consideration into UAs and I’m currently unsure if they’ll be great for messaging purposes. For the record, I could be wrong on this topic. The information regarding UAs is still relatively sparse so I may be misunderstanding how they work.

For messaging purposes, a single Z-addr can be used indefinitely and we can ensure a memo can always be delivered to a Z-addr. However, due to the nature of UAs being associated with T-addr, I’m worried they may need to be recycled after every use and there are cases where memos can’t hop between the T to Z transaction. Again, I may be misunderstanding the nature of UAs here, so please anyone feel free to chime in and correct me if I’m wrong.

Conversation apps are complex and we would like more details of implementation beyond a few paragraphs of intro.

Happy to explain more. I think i’ll try to break this out into a separate response. Or if anyone from the committee has specific questions, feel free to add them below.

Modifying the existing ZecWallet codebase to Messaging first is manageable, what often gets overlooked is the cost of ongoing maintenance. Who is going to keep up to date with the fixes for the underlying codebase? What would those costs look like after the 6 months funding period?

We’re looking to work with a blockchain platform that is committed to investing in messaging as part of their core utility. I’m open to discussion on how best to explore funding option beyond the initial proposal.

For example, Zemo could turn into a non-profit approach that is fully funded by the ecosystem.

Or we can attempt to turn it into a business to attract VC money. I’m personally more interested in the former approach, but open to ideas if anyone has any.

ZecWallet’s future is uncertain as @adityapk00 has taken a step back, how do you plan on maintaining a fork a customized codebase that is partly diverged from the upstream lightwalletd backend service? Who will be responsible to maintain the app in the App Store/Play Store?

Whatever happens to ZecWallet shouldn’t change the course of how Zemo works in any way. We’re fully capable of managing our own codebase. We would however be reliant on lightwalletd.

You mention in the grant “Shielded messaging has risen to become a popular use case in the Zcash community.” What information are you using to back up this statement?

Anecdotally many users in the community have used Zcash for shielded memos / love notes / etc. No real way to bring metrics into how many people are doing it right now, but people have expressed a lot of excitement in exploring this use case more.

I personally share my Z-addr from time to time on Twitter and I get flooded with messages from the community. It’s really a special experience. I’ve also onboarded 100+ people in this way through a simple message and a few cents in Zcash. The reaction is usually positive.

How would you be licensing your software and how does your license interact (if at all) with ZecWallet’s?

MIT license across the board.

What is the rationale for using IPFS for the avatars? Pinning in IPFS is still dependent on a server deciding to pin the avatar and if you plan on holding that data forever it is no better than an AWS server for for the sole purpose of storing pictures. Many NFTs on Ethereum use IPFS for their images and now no longer have access to the images for the NFTs because the startup who made the NFT decided to stop pinning the image.

Fair points. However, IPFS is better than a cloud storage provider in this case because it does at least give the option for additional gateways. It could potentially be a good idea to have the grant committee or ZF to also run a gateway to ensure there is longevity in the avatars.

How many team members will be working on Zemo? The budget seems high for a 2 person team based on some previous grants that have been administered.

We’re a 2 member team.

Can you please reference the previous grants you are referring to? Specifically mobile app grants? I poked around the grants platform earlier and it appears our hourly rate was significantly less than other mobile app grants.

Chris is a blockchain wizard. He’s built backed services for Bitcoin, Bitcoin cash, Filecoin, dabbled in Avalanche, Ethereum and other platforms. He wrote the server component for the decentralized ecommerce network called OpenBazaar, which also was ported to a mobile app and was called Haven. He was lead dev for https://bchd.cash/ and created the Bitcoin cash mobile app https://neutrino.cash/. Even if Zemo doesn’t play out, we would be very lucky to onboard him as a dev into the Zcash community.

I’m a former director of design on crypto applications. I’ve lead design on many mobile applications. I was an early employee at many top-tier venture backed startups, one which was acquired by a fortune 500 company. I started my career as a software engineer and continue to write front-end code mostly in react and react native.


Thank you for the detailed questions. Having more dialog like this with the committee would be super useful so that we can continue to properly explain our proposals.

5 Likes

To elaborate on some of the points in more detail, Hudson, I’d like to suggest we steer the focus away from trying to determine if Zemo could surpass Signal in usage at some point. In my opinion, this comparison is not the point of our application. We’re trying to grow shielded usage on Zcash with new use cases. We’re not trying to compete and/or surpass leading platforms right now. Our goals should be prioritized around Zcash usage and adoption.

If you don’t mind, I’d like to ask the committee a few questions —

  1. Do you feel Zemo could help grow the Zcash community?
  2. Does Zemo offer an attractive way to onboard new users into using Zcash?
  3. Does Zemo expand the utility of the ZEC asset in meaningful ways?
  4. What are the downside risks if Zemo doesn’t achieve meaningful growth?
  5. If Zemo becomes a leading tool in the Zcash ecosystem, will the committee stand by us and continue to fund development?
  6. Are there ways ZF, Zcash community grants, etc. can contribute to driving usage of Zemo? e.g. Messaging parties on Twitter Spaces, Ambassador program promotion, etc.

I wouldn’t want to build Zemo without the full support of the grant program. If we want Zemo to succeed, we’ll need more than money from the committee and community.

Thank you for your consideration.

4 Likes