An open discussion about embedding GA events into SYRIUS desktop for marketing purposes

My intentions aren’t to be disruptive. I have no agenda other than to support people like @mehowbrainz who should be enabled as much as possible.

I’ll leave it up to him to assess if Wallet Connect allows to track the necessary events.

Thank you for pointing out my potential misunderstanding about WC’s nature, I was under the impression it requires additional installation before researching it further. Will keep reading up on it then

Thanks for all the feedback, I will be studying available options and coming back with an assessment as to which are valid and which aren’t. From hindsight, the onboarding user experience may be tarnished with some of the proposed ideas, or they outright may not at all be what’s required here. I will do my best to try to validate them. If they work then great – otherwise I’ll have to fallback on original ideas. This shouldn’t be the end of the performance marketing vision, but could very well be if some in the community decide to alienate the needs for a data-driven marketing framework.

The ZenonOrg team is however disappointed with many of the irrational opinions shared throughout this debate. It expected much more from the proclaimed openness of the project. Calling forks as non-sense when a viable full solution with WC hasn’t been validated yet, is actually non-sense in itself.

The brand has invested quite a bit into the Zenon ecosystem with liquidity, its Pillars and investment in my employment and development of the Zenon.Org brand. It also expected a much more rational outlook on the problem it’s trying to solve for the greater good of adoption and AZ funds. Thank you to all supporters and rational minds.


A rational solution is the only solution, one that aligns both with the vision of this project and the needs of a data-driven marketing framework - that’s why I provided rational arguments and a viable alternative.

  • Why built-in tracking is bad? No comment.
  • Why wallet forks are non-sense? They will confuse new users, better make a separate wallet that has built-in tracking.
  • Why is WalletConnect a better idea? Check the answer below:

Let’s understand how WalletConnect will fit into this marketing framework:

  1. Integrate WC protocol into Syrius and create a tab where users can manage their WC connections (e.g. similar to TrustWallet or any other WC enabled wallet)

  2. Create a WebApp on a sub-domain e.g. where users can login with WC (Syrius either needs to be listed in the Desktop section or users can copy the QR code and paste it into Syrius)

A web page will always be easier to interact with than a desktop app. Take into account that Syrius is no ordinary crypto wallet, it’s pretty complex and can be an overwhelming experience for a regular user

2.1 If they have Syrius installed, they will open it using the WC URI
2.2 If they don’t have Syrius installed, they will be redirected to a page where you’ll be able to track their download: (e.g. check out how Zerion wallet works: Zerion – Smart & Social Web3 Wallet)

  1. Connect to their ZNN address and give WC permissions to sign. In this step you’ll be able to add and listen to this address for on-chain events (stake, delegate, etc.)

  2. It’s even possible to create push notifications like “Hey, if you delegate to this Pillar now, …” Push | WalletConnect Docs

  3. Even more complex stuff that can go beyond this marketing framework: Chat | WalletConnect Docs

WalletConnect is more than a simple add-on. In my opinion it will add value by opening Zenon to the Web3 public.


Thank you for the effort simplifying and explaining to us the onboarding process.

Would it be possible to add step #3 directly in syrius after the regular onboarding process of saving the passphrases etc ? I’ve read somewhere a dev suggesting that a new binary could be created for each download. Would it be possible to inject the WC user information in the syrius binary for each user so that the ‘WC login’ can be completed directly inside syrius?

My concern goes something along the lines of, given is currently an informational onboarding website, there is no incentive like on Zerion to go back and login because a user wants to use the web app. As you pointed out, the user might be overwhelmed with syrius and then he needs to remember: "oh shit, what was I doing, oh yeah surfing, let me go back and read more, oh its telling me to connect the wallet, nah I’ll do that later let me learn more about staking’ potentially losing his on chain information.

3 Likes → download Syrius → setup new wallet → link Syrius address with using WalletConnect → track user on-chain activity

Think of like a DApp and Syrius like Metamask. You give it permissions to read your wallet and potentially sign/authorize transactions.


I think this will make more sense if we use it with an extension rather than a desktop app.


Using an extension is simpler than using a mobile/desktop wallet: you don’t need WalletConnect because you can communicate with the web page directly via the browser.

1 Like

To link the syrius address an incentive would likely be needed, e.g. we could offer fusing some plasma for the new user if he/she does that


Some people are willing to do engagement missions for fake points. Mehowz has ideas for incentives as well, including what you’ve proposed.

The practice of tracking user actions on-chain for marketing purposes is viable and already employed by other platforms, though I’m surprised we want to follow this trend.
The WC suggestion is conducive to our goal of interconnecting with the broader web3 ecosystem and could enable other Zenon organizations to create webpages/applications that interface with the NoM.

On the other hand, this does create some work for ZenonOrg and will significantly delay their marketing plans. Additionally, the solution depends on Syrius developers to test, integrate, and deliver the WC functionality. Given our current pace of development, I’m hesitant to even estimate a timeline.


If the community is OK with a proposal to integrate WalletConnect into Syrius, I’m ready to make it happen in a reasonable timeframe.

I’ll make a new thread to discuss the WalletConnect integration.


will this impact the 0.0.6 release?

No, why do you think so?

At this stage I cannot guarantee that I’d make use of the proposed WC method, we’ll be evaluating all options including forks of wallets. This isn’t a race for us, it’s about identifying the path of least resistance. Though nothing can stop you from submitting an AZ proposal @aliencoder, it would be non-sense to try to prevent such things (or forks).


I’m here to help you and that’s why I tried to find a better solution in the first place. It’s not even in my power to stop you, the decision to merge code into the official codebase is in the hands of the team.

However, what we can do is to make sure that the changes proposed are aligned with the vision of the project and the expectations of the community.


mehowz proposal:

  • Anyone can toggle out of anon analytics during the syrius desktop installation. Problem solved.
  • No need to hope for users to connect to the dApp using WC (even with incentives in place).
  • Enables in-product analytics which can be used to improve the product long term (UX, feature usage, app usage metrics etc).
  • 18 voted yes, 8 voted no in Discord.

aliencoder proposal:

  • Sets precedent for 0 in-product analytics, ever. Will rely on a slower feedback loop: written/verbal/personal assumptions feedback.
  • Sets precedent of “non-sense” for others to fork syrius products, even though it’s inevitable to happen sometime.
  • Values an ideology over the value in-app analytics could drive for growth of the network and improvements it could make to the syrius desktop product.
  • Although the WalletConnect method is valuable for all kind of dApps to interact with syrius desktop, it creates the risk that users will not connect using WC and as a result putting marketing tracking in a limbo (regardless of the incentives offered). “Did they end up installing? Don’t know. Did they delegate? Don’t know. The connection with WC wasn’t made, so we’ll never know.” … It’s only chance is that the marketing funnel sets the expectation of the WC connection very early and repeats it so that the user thinks it’s almost requirement (very much less misleading/intrusive than my option’s toggle :roll_eyes:).
  • Other marketers will be able to create their own versions ideas like Attribute, marketing frameworks etc. Every brand will control their own marketing tools.

I don’t agree with the ideology that non-intrusive anon tracking or forks are “non-sense”. That’s not the Zenon ethos.

For the sake of settling this issue and moving forward, ZenonOrg will vote in favour for the WC method, and will do its best to find a way to make it all work with the slightly more difficult experience to capture analytic tracking (WC connection requirement). It’s a shame that syrius products won’t ever get analytic data to help shape a better experience.


Any chance we can just implement the solution with the least friction and highest probability to facilitate adoption while leaving aside ideologies/dogmas 99% of all end users won’t ever care about? Especially if it still offers a puristic alternative to the 1% who do?

99% of web3 solutions experience near zero adoption because engineers believe to know better what end users should want. Let’s not make that same mistake please.

I’ll do my best to find a marketing flow which converts using @aliencoder’s method. Wen WC in syrius?


Finishing some bug fixes for Syrius and after that I’ll proceed with the WalletConnect integration.


Great, I’m open to collaborate on features if you need help.

Here’s my marketing vision, and what I’ll be working on next: Zenon.Org Marketing Vision