Funnel / Job Boards / Email: Reply to Job Applicants


Here is how I reply to job applicants that come in via email thanks to the job board listings. I’ve noticed some devs join various telegram channels, asking to hire them. Ideally this copy will get translated to a landing page on that’ll guide all.

In my emails, the links are all tracked using short links:

How does the funnel look like?

  1. Someone in the world needs work, he visits or

  2. He stumbles on the job posts.

  3. He doesn’t know yet that Zenon funding is governed by pillars on-chain, so he applies and says something in the lines of “I’m ready to work asap!” — we get the application via email.

  4. We reply with the email below.

This is called inbound marketing as we’re positioning opportunities in traffic sources where people are closest to converting. In this case they’re looking for jobs, and hence visit job boards.

Always reach for low hanging fruits first.

The whole will eventually be streamlined with landing pages on the The more organized we are with docs and resources for newcomers, the easier this’ll all become. will make sure to architect the best highways for inbound traffic :slight_smile:

The next level would be retargeting and re-engaging with candidates to convert them into contributors.



Thanks for your interest in contributing to Zenon Network’s development.

My name is mehowz, I was previously contributing to THORChain and helped that community grow from a $15M market cap to many billion between 2019-2021 thanks to various successful campaigns and the development of the website. My expertise is growth hacking.

In 2022 I moved on from THORChain and joined the ZenonOrg team. We’re a pillar-operating organization, meaning that we run validator pillars (nodes essentially) in the Zenon Network. ZenonOrg’s mission is to develop distribution networks and marketing systems for the Zenon ecosystem. You’ll see us roll out a new website soon, which’ll tie itself with a variety of marketing funnels to onboard new participants into the Zenon Network.

As a first priority, we’re looking to onboard:

  • Developers (I’ll get to dev needs later in this email).

  • Delegators , they’re essentially ZNN token hodlers which delegate their ZNN to pillars via the Zenon syrius desktop wallet in exchange for protocol-emitted reward splits, shared between the pillar and delegator (the pillar decides the % split). The more delegation weight a pillar has, the more the pillar increases in rank which further increases his chance of producing momentum heights and earning more, (top 30 weighted pillars earn more than others). This network design invites pillars (like ZenonOrg) to create new value for the ecosystem in order to gain support from delegators.

As a second priority, we’ll be looking to onboard more:

  • Pillars and Sentinels. They help secure the network. As of today there’s about 82 pillars and 153 sentinel nodes in the network. There’s a cost to deploy these, details are highlighted here.

  • Liquidity Providers to the wZNN/BNB pool on PancakeSwap. wZNN can later be converted to ZNN via the bridge (the bridge code is linked here, useful for any dev who wants to develop the wQSR bridge which we explain later in this email).

  • Stakers, they earn QSR tokens for time-locking their ZNN to staking.

  • Marketers, we’re working on distribution architecture and systems to unify a performance-focused marketing community. The idea is to guide the marketing community towards a proof-of-performance ethos.

Going back to the developer needs. The anonymous core developers of the Zenon protocol have been working for over 3 years, and written over 1.3M lines of code. They open-sourced quite a bit of the code on Github due to their progressive objectives to decentralize the network (modelled around the values of and ethos of Bitcoin). They’re expecting the community to take lead on many of the much needed core developments.

They launched a program called Accelerator-Z (aka A-Z), which allows anyone to write a proposal and request funds to carry out the work, whether it be development, marketing etc. Proposals are submitted in the syrius desktop wallet, while pillars use the wallet to vote (on-chain) in-favour or against. Once a quorum is reached, the proposal either passes or gets rejected, and then the proposal leader is asked to submit a 2nd proposal for his work phase (which goes through the same round of on-chain voting). Most A-Z submissions have been dev-oriented due to the pressing development needs initiated by the Hyperspace program.

As a first priority, the Zenon network needs:

  • SDK’s for the following languages:
    — Python
    — Swift
    — Java/Kotlin
    — Javascript/Typescript (in-progress)
    — Rust (in-progress)
    — Go (in-progress)
    — C/C++ (in-progress)
    — C# (in-progress)
    — Common Lisp (in-progress)

As a 2nd priority:

Interoperability solutions so that there’s more liquidity that can enter and exit. For that we need:

  • A wQSR BSC bridge (analog to the wZNN bridge) and an ETH bridge for ZNN and QSR. Bridges should be as trustless as possible hence we’d need someone with cryptographic know-how on multi-party-computation to design a solution how pillars can effectively manage and maintain bridge liquidity in a secure way. QSR (known as Quasar) is an asset that’s fused to z-addresses to generate Plasma. This locks the QSR to the address and forms a Proof of Stake, at the same time creating the energy to fuel transactions. So in a way you do have to pay for transactions by buying and fusing Quasar, but that Quasar can be unfused at any time after an initial short lock time and is not depleted through the action of creating Plasma. The Quasar/QSR you put in to fuse is what you get back when you un-fuse. The Plasma generated through fusing is algorithmically determined to ensure the network stays stable and cannot be spammed - there will never be enough plasma in the network to congest it. Everyone only gets a portion of the throughput depending on how much QSR is staked. The PoW is apparently very difficult so its effects are negligible.

  • Atomic swaps and related technologies (HTLCs). It’s an alternative which George is already working on but afaik it would also require pillars to hold custody of BTC.

  • Wrapped assets like zBTC to transact them feelessly via the Zenon Network of Momentum (NoM). This also requires asset pooling by pillars and secure transaction signing. I don’t know how this would be implemented but MPC might play a role here too to improve tx authorization security. On a side note, the syrius desktop wallet allows the easy minting of ZTS (Zenon Token Standard) tokens.

  • Cross-chain bridges (with other L1/L2 networks)

  • Merge mining so that BTC miners can also earn ZNN with the same mining algo.

This is basically the foundation - liquidity can flow in and out in a secure and efficient way and devs can use different programming languages to interact with Zenon NoM.

As a 3rd priority:

Now that that’s covered, we need to look at what is needed from a product / zApp perspective that allows product devs to build meaningful applications on top of Zenon NoM.

  • Smart Contract Runtime - Absolutely critical for any zApp. The core team developers suggested WASM. We don’t have anyone yet with the capability to implement WASM (Web Assembly). Based on this devs can now build end-user applications (like swapping services, NFT projects or whatever). Discussions regarding the topic can be found in these forum topics.

As a 4th priority:

In order for these zApps to support potentially millions of users, the Zenon NoM protocol has to advance from Alphanet to Betanet and implement sentinels so that higher scalability and transactions per second is achieved.

Note that not all interoperability solutions need to be realized in order for the network to move ahead to other priorities. It just facilitates the flow of capital and reduces entry barriers. A few trustless bridges + atomic swaps or wrapped assets are already more than enough.

Priority 4 will likely happen before priority 3 (as it’s theoretically scheduled for end of year), and a gant-style Phase 2 can be a very long phase that overlaps 3 and 4.


You applied to the WebAssembly / Smart Contract Runtime job post, which is listed in the 3rd priority. Any advancement in the priorities listed are welcomed.

You can read more about Hyperspace x Accelerator-Z in the forum topic, it includes a link to the template most applicants use to develop an A-Z proposal in the Accelerator-Z category. We welcome you to browse through previous submissions using to see which were approved and funded.

Zenon is a network-governed decentralized entity. No single entity or brand can decide whether one will get funded (as a network of pillar validators vote on proposals on-chain), but looking at historical submissions and on-chain approvals, developers are highly prioritized and more-often-than-less funded for work. Developers just need to write good proposals and show commitment. Given the low market cap of the $ZNN token this is the time to earn some ZNN via the A-Z program. The $QSR token doesn’t have any markets yet other than an OTC channel due to the lack of a wQSR bridge as highlighted above.

Here are some important Telegram channels to join:

Ideally we believe the best space is on the ZenonOrg forums as it’s easier to track the progressions of conversations. We welcome you to join them and browse the Developers category.

If you have any questions, feel free to email us back at or DM us via our ZenonOrg handle. You can find me personally on Twitter and Telegram.


Special thanks to @Shazz who got me up to speed on network priorities after I recovered from my hospitalization, and great job @vilkris for and @0x3639 with the resources you’re pinning in the forums!


Thank you for your drive and initiative man, it’s an absolute pleasure watching you work!

1 Like

This is awesome, thank you for your dedication!

1 Like