Some suggestion

[moaazelsharkawy]

Hello Pi Core Team,

As a developer currently building a utility-driven e-commerce app on the Pi Network (Salla Shop), I highly appreciate the Pi Launchpad design. It heavily aligns with real-world utilities. However, after reviewing the PRC, I have a few suggestions regarding Section 3 (Participation & PiPower) from a project owner's perspective:

1. Quality of Engagement over Quantity (Anti-Bot):
   In Section 3.2, measuring engagement is great, but it risks being gamed by bots doing empty clicks. I suggest allowing projects to define "Weighted Engagement". For example, an actual on-chain Pi transaction (like buying a product in our app) should have a significantly higher weight in the Engagement Score than just daily logins.

2. Tiered Baseline PiPower:
   The current rule for the $PiPower_{Baseline}$ (≥90% lockup for 3 years) is highly restrictive. I suggest introducing a Tiered System. For example:

• Tier 1: 90% / 3 years = 1x Baseline multiplier
• Tier 2: 50% / 1 year = 0.5x Baseline multiplier
  This will include a broader base of loyal Pioneers in the token launches.

3. Vesting for the "Discounted" Tokens (Anti-Dump Protection):
   If highly engaged participants receive a better effective price during the Allocation Period, there is an immediate arbitrage opportunity that could lead to a massive sell-off right after the TGE. I suggest that the "discounted" portion of their allocated tokens be subject to a short smart-contract vesting period (e.g., 30 days), while the portion bought at regular price is unlocked immediately. This protects the project's permanent liquidity pool.

Thank you for this brilliant design! Looking forward to launching our utility tokens through this platform.

[EslaM-X]

Hello Pi Core Team,

As a developer currently building a utility-driven e-commerce app on the Pi Network (Salla Shop), I highly appreciate the Pi Launchpad design. It heavily aligns with real-world utilities. However, after reviewing the PRC, I have a few suggestions regarding Section 3 (Participation & PiPower) from a project owner's perspective:

1. Quality of Engagement over Quantity (Anti-Bot):
   In Section 3.2, measuring engagement is great, but it risks being gamed by bots doing empty clicks. I suggest allowing projects to define "Weighted Engagement". For example, an actual on-chain Pi transaction (like buying a product in our app) should have a significantly higher weight in the Engagement Score than just daily logins.

2. Tiered Baseline PiPower:
   The current rule for the
   P
   i
   P
   o
   w
   e

   r
   
    B
    a
    s
    e
    l
    i
    n
    e
   

   (≥90% lockup for 3 years) is highly restrictive. I suggest introducing a Tiered System. For example:

• Tier 1: 90% / 3 years = 1x Baseline multiplier
• Tier 2: 50% / 1 year = 0.5x Baseline multiplier
  This will include a broader base of loyal Pioneers in the token launches.

3. Vesting for the "Discounted" Tokens (Anti-Dump Protection):
   If highly engaged participants receive a better effective price during the Allocation Period, there is an immediate arbitrage opportunity that could lead to a massive sell-off right after the TGE. I suggest that the "discounted" portion of their allocated tokens be subject to a short smart-contract vesting period (e.g., 30 days), while the portion bought at regular price is unlocked immediately. This protects the project's permanent liquidity pool.

Thank you for this brilliant design! Looking forward to launching our utility tokens through this platform.

💠 The Power of Synergy: Official Endorsement from Map-of-Pi

It is rare to see such surgical precision in a community proposal. I have been closely discussing these concepts with Moaaz (Lead of Salla Shop), a brilliant colleague and a personal friend whose vision for the Pi Network economy consistently aligns with the highest standards of Web3 integrity.

As the Lead Architect at Map-of-Pi, I am providing my full Technical & Strategic Endorsement for this proposal.

1️⃣ Beyond "Empty Clicks": The Meritocracy Logic

Moaaz's push for "Weighted Engagement" is the cornerstone of what we are building with the PEIS Standard. We cannot treat a bot-simulated login with the same respect as a high-utility transaction on Salla Shop. One is noise; the other is the lifeblood of the ecosystem.

2️⃣ Safeguarding Liquidity: The Anti-Dump Shield

His analysis of the Arbitrage Risk is a masterclass in Tokenomics. By proposing a 30-day vesting period for earned discounts, Moaaz is effectively protecting every project’s liquidity pool from short-term speculators. This is the kind of "Skin in the Game" architecture that will make Pi tokens viable long-term.

3️⃣ From Walls to Ladders: The Inclusivity Tiering

The current PiPower baseline is a filter, but Moaaz’s Tiered System turns it into an inclusive engine. This allows the "Loyal Middle Class" of Pioneers to fuel token launches, ensuring decentralization isn't sacrificed for the sake of strictness.

🤝 A United Front

When builders like Salla Shop and Map-of-Pi align, it’s a signal to the Core Team that the developer community is ready for production-grade governance. I stand by Moaaz’s insights—let’s evolve the Launchpad into a world-class utility hub. 🇪🇬🔥

---

EslaM-X
Lead Technical Architect | Map-of-Pi
In Solidarity with Salla Shop | Building the Sovereign Economy

[ayamSlhim]

Your opinion was vital enough, however, I'd like to point out that (a),Pi ecosystem itself stands firm and strong as a Blockchain highly resistant to bots, and has always been a mindful design from the scratch, (b) in-which every projects building on Pi, in return will simply inherent those qualities it strived to build (in practical, it means no malicious bot ever gain access to the system), (c) web3 prioritizes ownership so much that it measures user' engagement and incentivize it to further boost participating confidence as also seen on the "Platform Utility" in Pi, therefore, user engagements becomes inherently applied to every utility project building and issuing tokens on the platform, and as formally highlighted by the teams, "user engagements in ecosystem projects influences the future utility of the particular project and participants can disengage from projects they think is not good", this means pi encourages developers to build meaningful apps that solves real utilities.

[moaazelsharkawy]

Your opinion was vital enough, however, I'd like to point out that (a),Pi ecosystem itself stands firm and strong as a Blockchain highly resistant to bots, and has always been a mindful design from the scratch, (b) in-which every projects building on Pi, in return will simply inherent those qualities it strived to build (in practical, it means no malicious bot ever gain access to the system), (c) web3 prioritizes ownership so much that it measures user' engagement and incentivize it to further boost participating confidence as also seen on the "Platform Utility" in Pi, therefore, user engagements becomes inherently applied to every utility project building and issuing tokens on the platform, and as formally highlighted by the teams, "user engagements in ecosystem projects influences the future utility of the particular project and participants can disengage from projects they think is not good", this means pi encourages developers to build meaningful apps that solves real utilities.

Thank you for your opinion, but what I meant by malicious software is the use of, for example, an autoclicker to create fake navigation or interaction.

[EslaM-X]

Your opinion was vital enough, however, I'd like to point out that (a),Pi ecosystem itself stands firm and strong as a Blockchain highly resistant to bots, and has always been a mindful design from the scratch, (b) in-which every projects building on Pi, in return will simply inherent those qualities it strived to build (in practical, it means no malicious bot ever gain access to the system), (c) web3 prioritizes ownership so much that it measures user' engagement and incentivize it to further boost participating confidence as also seen on the "Platform Utility" in Pi, therefore, user engagements becomes inherently applied to every utility project building and issuing tokens on the platform, and as formally highlighted by the teams, "user engagements in ecosystem projects influences the future utility of the particular project and participants can disengage from projects they think is not good", this means pi encourages developers to build meaningful apps that solves real utilities.

🛡️ Technical Deep-Dive: Systemic Resilience vs. Application-Level Exploits

I appreciate your perspective on the inherent strength of the Pi Blockchain. You are right that Pi is designed with a mindful, bot-resistant foundation. However, as an architect, I must distinguish between Infrastructure Security and Behavioral Integrity.

1. The "Inheritance" Fallacy:

While every project inherits Pi’s security, they do NOT automatically inherit protection against logical exploits. A blockchain can be 100% secure, yet an application on top of it can still be gamed by "Simulated Humanity" (e.g., sophisticated autoclickers or human-farmed interactions) that bypass traditional bot-detection.

2. Why "Weighted Engagement" is Mandatory:

If we rely solely on "Inherited Quality," we leave a backdoor for low-value engagement to dilute the rewards of genuine Pioneers.

• The Goal: We aren't just building "Meaningful Apps"; we are building Fraud-Proof Economic Models.
• The Solution: By weighting on-chain transactions higher than navigational clicks (as Moaaz and I proposed), we ensure that the "Platform Utility" rewards those who contribute real economic value, not just those who occupy the system with hollow activity.

3. Ownership requires Verifiability:

Web3 does prioritize ownership, but that ownership must be earned through Verifiable Proof of Utility. Reliance on "Inherited Resilience" is a starting point, but proactive defense at the dApp level is what separates a speculative project from a world-class utility hub.

Let’s not just trust the foundation—let’s fortify the structures we build upon it. 🏛️🚀

---

EslaM-X
Lead Technical Architect | Map-of-Pi

[futbolpi]

These are great suggestions, For the weighted engagement, my understanding is the launchpad will require the participating ecosystem app to expose an API which will basically return "pioneer engagement scores".
The project should have employed it's "weighting algorithm" as the scores are calculated before the API returns the response.
This will also help projects boost their user acquisition as each project can create custom weighting algorithm based on its business logic.