Pythentity Initiative

[arguer]

@grizzlyland

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 .

Thanks @grizzlyland! Valid point. For the MVP, which will essentially still be an experimental phase, it will likely be limited to just one wallet. However, the intent would be to allow users to bind multiple wallets in future, including other types of wallets (EVM, SUI, etc.). But there will probably still be a reasonable cap to the number, as more wallets means greater technical complexity and potential for vulnerabilities/loopholes.

[arguer]

@scp @Imgonnatakeapyth I appreciate the feedback about the Pythenians NFT requirement, and it will definitely be something that will be carefully considered as we move forward.

As @KemarTiti mentioned, it is one simple way to create gated access during this experimental/beta phase. As a community-driven initiative, I don’t think it’s unreasonable to give the privilege of “early access” to Pythenians - which itself is another community-driven initiative that embodies our community identity well. We also noted that a high percentage of our most engaged community members (the main target audience) are already Pythenians holders.

Having said that, I realize that there are loyal and engaged community members who may not own the NFT. And in my personal opinion, I don’t think the Pythenians ownership should be a prerequisite for participation when we progress past the MVP/experimental phase.

[arguer]

@Imgonnatakeapyth

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.

@Imgonnatakeapyth I like how you are thinking. And yes, this whole concept assumes that there will be reciprocal benefits from partner protocols, as I alluded to here:

@arguer

1. 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 (i.e. Pythentity Users).

As we’re still in the early stages of development, I didn’t want to be too prescriptive about what kind of benefit we’re expecting.

I mentioned W and JUP as two examples of partner token staking as they are two protocols that are deeply integrated with the Pyth Ecosystem, and have well-established staking programs/communities. Awarding points to W/JUP stakers from the start may be a good strategy to attract early users, creating an initial critical mass of participants to make this initiative attractive to potential partners, and kickstarting the cycle of value.

[Imgonnatakeapyth]

thank you for sharing your perspective, appreciate it! i am really looking forward to see this in action!

[Chop]

Awesome discussion.

I’ve created the tekton (builder) role in Discord. I’ve given all interested ppl here a special channel where we can discuss next steps and start executing!

Any further people looking to help out and get involved may request the role to be applied here.

[VVD]

Curious if its may be possible offchain for the simplisity

Also wondering that the metrics will be pulled from x api?

[pstar]

For the Impact Awards project within Pyth, we’ve been using the X API so definitely we should use the same sub to pull data for Pythentity and maybe keep a database combined for both projects

[TheDinarian]

I am genuinely impressed by the Pythentity Initiative! This community-driven approach to recognizing and rewarding long-term, meaningful engagement within the Pyth ecosystem strikes a perfect balance between sustainability and inclusivity. The use of Discord roles combined with $PYTH and partner token staking to build a robust, anti-sybil scoring system shows strong strategic thinking to encourage genuine participation over speculative farming.

The idea of integrating Pythenians NFT ownership as an anti-Sybil measure while keeping it flexible for broader community access is smart, as it maintains security without alienating non-NFT holders. Also, the proposed technical stack and project management plan reflect a pragmatic and well-structured approach that should enable smooth MVP delivery and scalability.

I especially appreciate the focus on partnering with protocols to multiply network effects and channel rewards to engaged, high-conviction users. This aligns with Pyth’s broader vision of building a trusted, community-first oracle network that empowers real-world utility beyond short-term speculation.

Looking forward to seeing the active developer and community collaboration that will bring this initiative to life. The thoroughness of the proposal coupled with exciting prospective add-ons to Pythentity make this a cornerstone for sustainable growth in the Pyth ecosystem.

Kudos to everyone involved for driving this forward — a fantastic example of community innovation and decentralized governance in action!

[andy.quan366]

My thoughts on this proposal:

1. Discord chatter should not be a primary metric — too much noise, it doesn’t reflect real contribution.

2. Core contribution should come from governance ideas — submitting meaningful proposals and participating in votes are where real value lies.

3. Submitting a proposal should require staking — this prevents spam and ensures proposers have real skin in the game.

4. Beyond “pass or fail,” the community should also vote on proposal quality — not just whether it passes, but how valuable it is.

5. Rewards should scale with quality ratio — e.g. if you stake 1K and your idea gets >10 upvotes/downvotes ratio, you receive 2K (profit 1K); if ratio <5, you only get 0.5K back (loss 0.5K).

6. Pythenians NFT can be bought on the market, so it has limited anti-Sybil value — it works more like a ticket than an identity.

7. A genuine identity system should be contribution-based and non-transferable — built from long-term staking, voting history, and proposal quality, which cannot simply be purchased.

Key challenge: how to prevent Sybil accounts from mass upvoting?

• Require cost to vote (small fee or partial stake not fully refundable).

• Weight votes by staking or contribution history, not one-account-one-vote.

• Add time constraints (new accounts only gain voting power after holding/staking for some period).

• Introduce a reputation system: votes aligned with final outcomes increase reputation; repeated poor judgments decrease it.

• Hide interim results until voting ends, so people can’t just follow the majority.

• Evaluate by ratio of credible votes, not raw totals, reducing the effect of Sybil spam.

This ensures that long-term, genuine contributors gain more influence, while Sybil attempts become costly and ineffective.

[grizzlyland]

Thats fair. Looking forward to it . Are we gonna have a vote soon ?

[grizzlyland]

If i could add one detail, it would be to include active governance participation (meaning if they voted on proposals or not ) Something similar to what Jupiter does.

[lowkeigh]

Agreed, including governance will both incentivise governance activity and also help identify those who are truly active in the eco

[eukodal]

hey derrp do we have vote or people who are willing to start working on this ?

[Derrp]

Hey mate.

Lots of people have already expressed their willingness to begin, and their skillsets in the posts above. Several Pythian chads have also expressed interest via DMs as they feel more comfortable doing so.

We discuss these things informally in daily chats, and also formally in weekly meetings. Things are moving in a positive direction, and hopefully we will have some news to share soon. Super bullish on our community: willing to build application that literally reward our community. Pythian community is stronger than ever.

[Amensch]

Will this go to a Vote? Is this just the discussion? Is there going to be a final iteration of the proposal for us to vote on?

[Derrp]

This will likely be an internal decision for the Community Council as the PYTH allocations will be supplied from the Community Council budget, and the proposal was from the Community Council. Though no definitive decisions regarding your specific question have been made at this time .

[Amensch]

Thank you for the quick response. I look forward to seeing this project materialize and the success of Pyth. May we go from a Network to an Empire in the days to come

[Kirito.sol]

Yeah fam, hiding everyone’s scores except your own sounds like the way to go to avoid the free riding issue

[pstar]

Pythentity Initiative : Development Complete, Ready for Production Handoff

Hey everyone!

I’m pleased to report that the Pythentity Initiative MVP is feature-complete and ready for production deployment. The full codebase is built, functional end-to-end, and sitting in a finalized repo.

Try it out live: https://pythentity.netlify.app

---

What Was Built

Over 40 commits across a 3-month development window (Nov 2025 – Feb 2026), the following was delivered:

Frontend (Vue 3 + Vite + Tailwind CSS + Pinia)

• Landing page with Solana wallet connection (Phantom, Solflare, Coinbase, Trust, Ledger)

• NFT-gated access — verifies Pythenians NFT ownership on-chain

• Profile page with NFT avatar, score breakdown, Discord/Twitter linking

• Admin dashboard with leaderboard view, snapshot generation, CSV export

• Guest mode for non-NFT holders (read-only browsing)

• Wallet disclaimer signature system (versioned, stored in DB)

Backend (14 Netlify Serverless Functions)

• Wallet signature verification and user management

• Discord OAuth + Twitter OAuth 2.0 (link/unlink/refresh roles)

• Score calculation engine with daily automated cron updates

• Admin tools: recalculate scores, generate snapshots, user lookup

Database — MongoDB (shared with Pyth IA Discord Bot)

• The app connects to the same MongoDB database used by the Pyth Impact Awards Discord Bot

• This shared database means Discord bot data and Pythentity web app data live side by side — no duplication, no sync issues

Scoring Engine

• Square-root-based formula to compress whale advantage

• Token price ratio normalization (PYTH with 2x emphasis, JUP, KMNO)

• Staking streak multipliers — up to 3.5x for PYTH (730 days), 2.0x for partner tokens

• Discord role multipliers: 1.2x (Low Priest) through 2.2x (Chiron)

• Twitter bonus: flat 1,000 points

• Streak floor system (drop below 20% of peak = streak reset)

On-Chain Solana Integrations (Direct Account Parsing — no wrapper APIs)

• PYTH governance staking (position slot parsing from staking program accounts)

• JUP locked-voter escrow accounts

• KMNO kfarms UserState accounts

• Retroactive first-stake-date detection via transaction history pagination

Codebase Stats

• ~7,800 lines of application code (48 files — frontend + backend)

• ~1,900 lines of test code (6 test suites)

• ~18,000 lines of documentation (20 doc files)

• 40 commits over 30 active development days

---

What Remains (Operational, Not Development)

The app is functionally complete. What’s left is deployment and configuration, not code:

1. Thorough QA testing : end-to-end testing with real NFT holders, edge cases, load testing with multiple users

2. Host on official Pyth domain : move from my dev environment to the official production domain

3. Transfer repo and Netlify project : move to official Pyth org/platforms

4. Update OAuth callback URLs : once the production domain is set, update Discord and Twitter OAuth redirect URIs to match

5. Update Helius subscription out of free tier for higher requests use : make the RPC scalable

These are all infrastructure/config steps that require access to official Pyth platforms.

---

Grant Allocation Request

The original grant was 80,000 $PYTH for 160 hours of full-stack development.

I’m requesting 85% of the grant for the development work completed — the full MVP is built, functional, and documented with extensive test coverage.

The remaining 15% should be allocated to testers/QA — or back to me depending on how much testing and bug fixing is ultimately needed once real users start using the platform. If testing surfaces significant issues that need code fixes, I’m happy to handle those as part of that 15%.

---

Special Thanks

Shoutout to @chop, @frozenmind, and @arguer for the help throughout this process; I really do appreciate the trust that was given to me.

Happy to answer any questions!

[totti]

@pstar

https://pythentity.netlify.app

This is brilliant work pstar! just tried it out- it works flawlessly, I would only recommend one addition that is to be able to connect multiple wallets.

Thanks for your work.