Context.

Predominantly, applications and ecosystems in the Polkadot sphere do not collect or store users' personal contact information, such as email, relying solely on Web3 wallet addresses. This approach is primarily (as everybody thinks) driven by the quest for anonymity, privacy, and the challenges associated with securely storing personal data. Users, in general, are not inclined to share their email addresses by default.

Simultaneously, for a lot of “Web3'' applications (CEX, launchpads, farms), providing email addresses isn't seen as a significant risk by most users (from their perspective). For instance, a considerable portion of users use centralized exchanges that collect email addresses, passport details, phone numbers, and other sensitive information. In the case of Polkadot users on the Binance Smart Chain, there are currently over 165,000 unique DOT wallets and more than 5 million registered transactions. Like in Web2, most users generally avoid sharing their contact information due to the risk of unwanted contacts.

In essence, for tens or even hundreds of thousands of existing users, the problem isn't that providing contact information poses any issues; rather, they lack incentives to do so.

At the same time, the absence of email addresses hinders dApps and entire ecosystems from be connected with users. This leads to challenges like:

1. Difficulty in user re-engagement. Without user emails, it can be challenging for dApp developers to reach out to users who have stopped using their dApp or forgotten their funds.
2. Increased reliance on public communication channels. Web3 dApps that do not collect user emails may need to rely on other communication channels, mostly public ones. That lead to the rise of phishing channels across platforms like telegram
3. Higher risk of misinformation. Public communication channels can be vulnerable to misinformation or rumors, which can negatively impact user trust in the dApp. Without user emails, dApp developers may have a harder time controlling the flow of information and correcting false information.
4. Limited ability to notify users of security breaches. In the event of a security breach or vulnerability, collecting user emails can be crucial in notifying users and advising them on how to protect themselves. Without user emails, dApp developers may have limited options for notifying users, which can impact the response time and effectiveness of remediation efforts.
5. Difficulty in providing updates on bug fixes. Utilizing user emails (or other direct communication channel) can help dApp developers provide updates on bug fixes and patches, which is critical in maintaining the security and stability of the dApp. Without user emails, dApp developers may have a harder time providing updates on bug fixes, which can leave users vulnerable to exploits or attacks.
6. Increased risk of legal liability. Without user emails, dApp developers may have limited options for communicating with users about potential legal issues or liability. This can increase the risk of legal liability for the dApp and its developers, which can impact the long-term viability of the project.

Users may appreciate this information, but they need assurance that they won't be bombarded with unwanted messages.

Problem statement.

Instead of addressing the feedback issue and fostering mutually beneficial relationships with users, the Web3 ecosystem has primarily abandoned these aspects. Consequently, most application creators lack the tools to tackle feedback concerns with users. Users may also miss crucial updates, security alerts, and personalized support, resulting in a diminished user experience and potential risks.
This also stops web2 apps from coming to web3: lack of feedback circuit makes development and marketing almost impossible to handle.

Economically Incentivized Approach.

Cryptocurrencies have enabled the formation of sustainable, decentralized, and anonymous communities, united by mutual incentives. This aligns with the philosophy of using financial rewards to encourage participation, collaboration, and innovation in blockchain-based systems. Web3 communications can leverage this incentivized approach to forge symbiotic relationships, driving engagement and adoption. Economic incentives foster increased participation and collaboration, culminating in a more decentralized and equitable ecosystem. All of this together allows for the creation of open products that can exist on their own, supported by the initiative of their participants.
Crucially, the incentivized protocol of Notifigato ensures reliable storage and appropriate usage for each message sent, as it has a vested interest in its accuracy. This establishes a balance of system fairness through the provider's commitment.
Moreover, a self-incentivized system based on a peer-to-peer payment model paves the way for a self-organizing economic structure. Market demand can determine the value of messages, while user actions can influence the cost of message delivery.
The provider itself can also be dissolved as an equal participant: for this, the mailing contract should include the possibility of deducting a percentage to whoever brought the client upon registration (referral). That is, when sending a message to the client, their referral receives a small percentage. Importantly, the client's application can also be a referral: then the application pays less for its clients and receives a percentage for sending their clients' messages from other apps.The platform is also engaged in development and attracting clients. It does not have a mandatory percentage and is forced to constantly evolve, rather than relying on others' clients.
This economic model unites all participants: the sender, the recipient, referrals, and the platform. They can find an equilibrium where the communication data is meaningful and effective.
We see value in creating a platform that belongs to no one but benefits various participants.

Notifigato: Economically Incentivized Web2-Web3 Communication Tool.

Notifigato is an application that enables message sending to recipients using only their Web3 addresses as user IDs. It ensures the delivery of messages (emails, push notifications, and messengers) using only the provided Web3 IDs, without disclosing users' contact information. For each message sent, the sender pays a sending fee that is dedicated to the user’s referral. Platform itself didn’t take any fee and lay on a common-good community-driven concept. Payment for the delivery will be paid in the DOT (Cause payment should be done with infrastructure token with confirmed value and unconditional liquidity for the ecosystem. By default, this is DOT). By securely storing sensitive user information, all parties in the system remain economically incentivized.

Marketing.

The marketing system is built on integrating referrals directly into the message payment. This makes it economically beneficial to provide the largest number of initial users and control/incentivize their reading of messages from their referrer.

1. This makes it advantageous for dApps themselves to connect users (who will actually send them messages without a fee, and also earn from communication with their users by other applications).
2. Additionally, it's an excellent platform for third-party partners who already have their own customer base and are looking for additional revenue sources.
3. Besides that, standard user onboarding tools are planned to be used:

• 3.1. Airdrop for Polkadot-experienced users of native DOT: Distribute a small number of tokens to early users for free, which can be used within the platform.
• 3.2. DOT-Integration Incentives: a round of incentives for users who have an on-chain ID.
• 3.3. 0-fee first distribution rounds.
• 3.4. Co-Marketing and Integration Incentives.

Full proposal >> https://docs.google.com/document/d/1ddSmHZuV1K0cbmJYTY0ajtB9b4Sr0wJHvsWTW6Pag3o/edit#