Pythentity Initiative

Ideas Bank
1

Abstract

The proposed Pythentity Initiative is a community-driven, web3 reputation system, centered around the Pyth Community, designed to:

  1. Recognize and reward engaged community members.

  2. Deliver value to partner protocols.

  3. Multiply the network effect within the Pyth Ecosystem.

Aligned with Pyth’s vision of transforming global finance, it prioritizes sustainable and meaningful engagement and long-term conviction, rather than short-term farming and speculation.

Participants will be awarded a score based on various scoring components. For the proposed Minimum Viable Product (MVP), the scoring components will be:

  1. Pyth Discord Roles

  2. $PYTH Staking (Governance and OIS)

  3. Partner Token Staking (e.g. W, JUP)

In future, this may be expanded to include further scoring components such as Educational Activities, Social Media/Content Contribution, DeFi Usage and Discord Roles in Partner servers.

As a community-driven initiative that is supported by the Pyth Community Council, it is proposed that a grant of $PYTH tokens be awarded to a group of developers from the community to undertake this project.

Rationale

Web3 and DeFi is often characterized by speculative behavior, with airdrops attracting farmers rather than committed users, bringing limited value to protocols and hampering the overall adoption of web3.

The Pythentity Initiative aims to address this by creating a system to:

  1. Recognize and reward deserving users

  2. Provide partner protocols access to users who are engaged for the long-term

Rationale for scoring based on Discord roles
Reliable first-level identification of quality contributors in the community, while excluding whales and institutional holders who are unlikely to engage on Discord. Secondary benefit: Encourages meaningful contribution in the community.

Rationale for scoring based on token staking
This system rewards belief in the future of Pyth (and partners) and incentivizes sustained protocol engagement. The focus on staking also makes the system less farmable, since users are unlikely to be willing to stake large positions for long durations in protocols that they don’t truly believe in. The focus on staking duration helps smaller accounts remain competitive, while also rewarding early supporters. Secondary benefit: Creates demand for $PYTH token (and partners’ tokens) and encourages long-term staking.

Proposed Plan and Feasibility

As part of this experimental phase, the proposed MVP will include the following features and use cases:

For individual users
Users’ Solana wallet addresses will be the main unique identifier.
Pythenians NFT ownership will be a requirement to participate (anti-sybil measure).
Pythentity Score will be generated from:

  1. Discord Profile: Points for roles on Pyth’s Discord.

  2. $PYTH Staking: Points for staking (Governance and OIS) duration and amount.

  3. Partner Token Staking: Points for staking tokens of Pythentity Partners, also considering duration and amount.

For partner protocols
Partner protocols have a unique opportunity to connect with highly engaged, long-term focused members of the Pyth community. To join as a Pythentity Partner, protocols would typically be invited to collaborate by offering some kind of value or benefit to the community.

For management of internal distributions within the community
Besides being a platform for partner protocols to deliver incentives to Pythentity users, the scores and rankings may also be used internally within the Pyth Community Grants program. This is the base use case, even if the initiative fails to attract significant partner participation.

Projected Impact on the Pyth Community and Ecosystem

For the community

  • Increased rewards and access to those who deserve it most.
  • Increased incentive to join the Pyth Discord and engage meaningfully.
  • Prioritizes and rewards loyal users over speculators and farmers.

For the ecosystem

  • Allows partner protocols to reach a high-quality group of users. Since users are incentivized to stake the partners’ tokens (to improve their Pythentity scores), it drives ongoing engagement and interest in the protocol.
  • Increased demand for $PYTH, partner tokens and Pythenians NFTs.

Implementation and Next Steps

Gathering feedback
Feedback and suggestions are appreciated.

Selection of community developers
Developers from the Pyth Community who have the interest and technical expertise may express their interest to participate in the development of the Pythentity Initiative.

Grant allocation to compensate the selected community developers for their work
After some internal consultation with Pyth developers, a cost estimate was derived based on the scope and scale of the MVP. The estimate was derived based on these parameters:

Time to complete for an experienced full-stack developer = 4 weeks (including development, testing and feedback)
4 weeks full-time work (4 x 40hrs) = 160 hrs
Hourly dev cost (USD) = $50
Total dev cost (USD) = (160 hrs x $50) = $8,000
$PYTH required (assume $0.12 per $PYTH) = 66,667 $PYTH
$PYTH grant requesting = 80,000 $PYTH (~20% buffer)
Timeframe to completion = 3 months for 4-5 contributors (buffer included)

9 Likes
2

This is a great idea! Love to see such popping up from the Pythians.

One Q:

To not have protocols free-ride this work (and get all the most engaged Pythians info/details), I’d assume the data (scores of everyone) will be hidden/obfuscated? As in, I can connect my wallet and only see my score but I would not be able to see the other ones?

Or were you thinking about also having a leaderboard a la Kaito? If the latter, I would be afraid people would just scrape that data and free-ride.

8 Likes
3

Yes, you’re absolutely right.

For the MVP, the plan is to have the scores of everyone (leaderboard) hidden. Each user would only be able to see their own score and rank when they sign in with their wallet.

6 Likes
4

I would love to participate in the creative process, help with the front end and backend as well, at the moment I need paid work and also a portfolio on web 3

4 Likes
5

Hey Pyth Community! :waving_hand:

Read through the Pythentity MVP specs - looks like a solid project. 5+ years DevOps + Python background here, can definitely handle the infrastructure side of this.

What I’d Cover:

  • CI/CD & Deployment: Docker containers, proper staging/prod setup, automated deployments that actually work

  • Database: PostgreSQL optimization for 3K users + daily score updates. Proper indexing, backups, and yeah… someone’s gotta VACUUM that thing regularly or it’ll bloat like crazy :grinning_face_with_smiling_eyes:

  • Monitoring: Prometheus/Grafana stack for all those moving parts (Discord bot, Twitter API, Solana RPCs). That <2sec page load requiremnt needs monitoring from day one

  • Security: Rate limiting, secret management

  • Automation: Bulletproof cron jobs for daily score updates with proper failure recovery

Why I’d Be Useful:

Python + DevOps combo means I actually understand the code I’m deploying.

The Challenge:

Real-time wallet connections, blockchain data aggregation, external API orchestration - this is exactly the kind of technical puzzle I enjoy solving. The anti-sybil focus is smart too.

Happy to discuss architecture details or answer questions about the ops side!

7 Likes
6

I absolutely LOVE this idea.

Beyond the MVP i can forsee quite a few utility addons to this that could give a lot back to Pythenians holders via the Community Council.

A leaderboard (and score?) based on your participation could be used to meaningfully give back to those community members who continue to help build the Pyth Network.

Can’t wait to see what everyone is able to bring to this!

7 Likes
7

I’ve read through the Pythentity Initiative MVP proposal, and I feel confident about its potential to drive meaningful engagement and reward long-term commitment in the Pyth ecosystem. The focus on Discord roles, $PYTH/partner token staking, and Pythenians NFTs as an anti-sybil measure is a smart way to prioritize quality contributors.

I’d love to contribute as a dev, bringing 10+ years of senior software dev experience in web3 and full-stack development. I can cover the creation of a web app from development to deployment in production with a colleague.

Check out my portfolio at thierry.bio. I’ve worked with Kain and Grant Warwick (SNX/Infinex/ILV) and I work on the Impact Awards Discord Bot used by Pyth, where I’ve been hands-on for over 6 months, collaborating with CCs weekly.

Tech Stack Proposal:
To make development agile and encourage wide community participation, I suggest a Node.js Express backend paired with a React frontend (using Material UI probably) and MongoDB for a NoSQL database. This stack is lightweight, widely adopted, and perfect for web3 apps like Pythentity. It’s great for rapid prototyping; checkout one of my past project at nice2win dot com using this stack. Finally, it’s accessible to many devs, which could boost team collaboration and contributions.

Contribution Plan:

  • Backend: Build a robust Node.js/Express API to handle Solana wallet authentication, Pythentity score calculations (based on staking duration/amount and Discord roles), and partner protocol integrations. MongoDB will manage user data and rankings efficiently, while staying agile if we need to change up the way we store data. We will follow industry standard for security. Use official third-party APIs for Discord and other source of official data (Solscan maybe?).
  • Frontend: Create a responsive React dashboard with Material UI for users to view their scores, staking details, etc We’ll integrate web3 libraries for seamless Solana wallet connects and real-time data display with websockets.
  • Extras: Implement cron jobs for daily score calculation and other fun stuff.
  • CI/CD & Deployment:

    • CI/CD with GitHub: Set up GitHub Actions for automated testing, linting, and building of the codebase. Every PR will trigger unit tests and code quality checks to maintain stability. On merge to main, GitHub Actions will build and push Docker images to a container registry for deployment.

    • AWS Hosting: Deploy the app on AWS for scalability and reliability, using an Application Load Balancer to handle traffic.

    • Auto DB Backup and Stability: Configure MongoDB Atlas (or AWS-hosted MongoDB) with automated daily backups to Amazon S3, with a retention policy for recovery and compliance.

This setup aligns with the 3-month timeline for a 4-5 person team and keeps the MVP focused yet scalable.

What I Bring to the Table:
My web3 expertise means I’m comfortable with blockchain manipulation (e.g., querying staking contracts, verifying NFT ownership) while ensuring the system stays anti-farmable. My work on the Impact Awards bot gives me deep insight into Pyth’s community and inner workings too.

Moreover, I’ll leverage my PM/Product Owner experience to implement an Agile Scrum framework. I’ll set up a task board (e.g. GitHub Projects), define user stories, and run weekly sprints with scrums to ensure collaboration, track progress, and address blockers.

Team Gaps:
We’d need a designer for top-notch UI/UX and a couple of QA folks to stress-test the MVP. I’m confident we can find these talents within the Pyth community to complete the team. Also, looking forward to see if another dev can get behind this plan!

Finally, I’ve been happily working with @Chop and other CCs and would definitely like to increase my presence into the Pyth sphere with this project!

5 Likes
8

I love the idea And I see a huge potential

It would be my honor to participate as scrum master and full stack dev

Thank you for sharing the great opportunity :bright_button::heart:

5 Likes
9

This will enhance user engagement and help propel the Pyth Network to the next levels, not alone of course but as a big piece to the larger puzzle. :wink:

4 Likes
10

Dear Pyth Community,

It’s fantastic to see that the DAO is now recognizing and rewarding engaged community members. :heart_eyes: I have been actively building websites and tools to benefit $PYTH holders. While I may not be the most experienced developer here, I am highly motivated and fully committed to contributing in any way I can—volunteer work included—to help Pyth grow and succeed.

I truly love this project and am passionate about its vision. I have been self-learning full-stack development, and I am eager to contribute my skills in ReactJS, Next.js, TailwindCSS, or backend technologies like Supabase and Convex. I am ready to help wherever needed.

I am excited to be an active part of this community!

6 Likes
11

Ripper of a proposal mate!

I also like your idea of each person only being able to see their score and rank (maybe even where they rank in different categories?)

So much promise to an idea like this for both Pyth community and potential users of Pythentity.

Plenty of options for building out on the MVP over time too!

4 Likes
12

I fully support the idea!
I think this is a Win Win for the Pyth Community and to partners as well!

I also love seeing Pythian community members going out and helping to build this thing! There is no better candidate to build the Pythentity Iniatiative than our own community members!

I probably cannot help on building it but i can definitely volunteer on testing the platform!

5 Likes
13

This is a great initiative, love the idea of Pyth partners also being involved in this! Feel like this might drive more attention to what Pyth and Pyth’s Community are building.

Pythenians team is ready to help with building this out!

5 Likes
14

Community members unite here to build something magnificent! Fire proposal, Arguer!

Hands down, this is something new and interesting and have actual practical utilization!

4 Likes
15

This is an awesome Proposal . Th fact that this encompasses Community contributions via discord roles , ecosystem alignment and rewarding long term believers in the respective tokens is great.

If i could add one suggestion during the execution phase would be to include the option of adding mutiple wallets. Users are likely to have staked their PYTH , JUP or W in different wallets me being one .

3 Likes
16

grizzlyland. Good point. Staking with different wallets is more for security reasons rather than farming. Who knows—if one wallet is compromised, we still have others. We can provide an option for community member to create an aggregated profile for staking across multiple accounts.

On top of that, I also think that the Pythenians NFT should not be a compulsory requirement for rewards. We have community members who believe in the Pyth Network but do not believe in NFTs in general.

If we want to implement an anti-sybil measure, we can add tighter conditions such as: only those who have staked for more than six months will be eligible. Holding the Pythenians NFT could then boost the final rewards with a multiplier.

3 Likes
17

A HUGE opportunity to build a support system for genuine users.

Funded By Pyth Community Grants

Idea from the community, for the community, built by the community, to reward the community.

Community.

But in all seriousness, this idea has huge potential, and I cannot express in words how excited I am to see this thing take shape

1 Like
18

i would love to see this thing work out, knowing how servers are rampant with low quality farmers. Just a few things i need some clarity on.

  1. We want to avoid whales, but the amount staked being a criteria for score, kinda makes it easy for whales to just farm them.
  2. i would be super curative with the partner staking, for example i understand earning scores for wormhole staking, but merely providing points for using protocols not run by the foundation in my opinion should have a reciprocal advantage, for example if we score users LPing on meteora, it would make sense for me to get boosted APRs in return as a pythentity holder, something along those lines. i am just giving an example, it could be any reciprocal benefit.
  3. I don’t think a mere holding of pythenians should be a requirement for individual users, like people having to spend 2 sol on an nft to be considered.
    please correct me if i am wrong, or misunderstood anything, that being said, i would really like this initiative to become a plausible solution for rewarding and providing access to users who deserve it the most, thanks!
19

For 1, one way around this is using an exponential / diminishing returns curve instead of linear scoring. Score = √(stake) → 100 stake = 10 points, 10,000 stake = 100 points (so 100× more stake gives only 10× more score). Or use log scaling: Score = log₂(stake + 1) → 100 stake ≈ 6.6, 10,000 stake ≈ 13.3 (so 100× more stake gives only 2× more score).

For 3, no strong opinion here, but maybe gated for the alpha/beta version? Then once out of beta, Pythenians or not could use/access. And impact on scoring, IMO, we can also find a way like applying a coefficient (i.e multiplying your score by x1.1 or x1.25 ; need to find the sweet spot).

2 Likes
20

yeah great idea, i like the sound of it, it should work out fine. Just need to find a sweet spot and we gucci