# Pyth Price Feed Twitter/TG Bot Proposal

**URL:** <https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298>\
**Category:** Ideas Bank\
**Created:** [December 8, 2025, 5:45am UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298 "2025-12-08T05:45:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chop](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/chop/32/49_2.png) [@Chop](https://forum.pyth.network/u/Chop)\
**Post date:** [December 8, 2025, 5:45am UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298/1 "2025-12-08T05:45:03Z")

</div>

**🐍 Pyth Price Feed Twitter/TG Bot Proposal**

**Abstract**  
The proposed Pyth Price Feed Bot initiative aims to create a publicly accessible tool on social media platforms (starting with Twitter/X and Telegram) that can be called upon by users to instantly reply with a series of statistics about a specified asset’s price and other Pyth Price Feed-based information (e.g., 24-hour performance, confidence interval). The rationale is to create a highly visible utility that showcases the superiority of Pyth’s real-time pricing data and broadens Pyths’ brand awareness across key social channels. This project will be developed through live, community “vibe-coding” sessions to encourage engagement and demonstrate what motivated community members can achieve, including securing community grants for quality work.

**Rationale**  
Web3 and DeFi are characterized by a focus on verifiable, quality data, and Pyth Network is the leading provider of first-party financial data. This proposal is necessary to address the need for a highly visible, social-native utility that:

- Showcases the _accuracy, speed, and broad breadth_ of Price Feeds available through Pyth Network.

- Creates a presence in social contexts (Twitter/X and Telegram) where real-time asset price discussion occurs, demonstrating Pyth’s data superiority.

- Incentivizes and educates the community by conducting the development through open, “vibe-coding” sessions, thereby inspiring other motivated individuals to seek community grants for their own good work.

**Proposed Plan and Feasibility**  
The Minimum Viable Product (MVP) will focus on creating a functional bot on Twitter/X and/or Telegram with the following features and use cases:

- **Core Functionality:** The bot will reply with a series of price feed statistics (e.g., current price, 24-hour performance) whenever a specific phrase is used to call it within a social post/message.

- **Development Method:** The initial development will be conducted through live, public _“vibe-coding” sessions_ with the community. This open process is an exercise in community building, allowing people to collaborate over the creation of something of tangible benefit to the Pyth brand and the Pyth community.

- **Usage and Utility:** Usage of the bot will be open to anyone who knows how to call on it. The bot is managed by the community council and may in future require _$PYTH tokens_ in order to call on the bot. This functionality will be designed with PYth tokenomics in mind, so that usage is directly tied to Pyth token utility and value accrual.

**Projected Impact on the Pyth Community and Ecosystem**

- **For the Community:** The live vibe-coding of a community proposal should showcase what is possible for those who are motivated within the Pyth community. Someone watching can achieve or build stuff and get a community grant if it’s good. The live vibe coding is also an exercise in community building.

- **For the Ecosystem:**

**Implementation and Next Steps**  
Once the bot has reached a workable MVP stage and is live on twitter, there could be a second phase of development where we apply the bot to other social platforms such as Reddit, Discord and others.

**Grant Request for MVP Development**  
Since the development will be driven by weekly vibe-coding sessions with community input, the cost estimate has been revised by halving the estimated development time.

- Time to complete for an experienced full-stack developer: approx 80 hours
- Hourly dev cost (USD): $60
- Total dev cost (USD): $80hrs X $60 = $4,800
- Assumed $PYTH price: 0.08c per $PYTH
- Total $PYTH equivalent (USD terms): $4,800 / $0.08 = 60,000 $PYTH
- Desired $PYTH grant (Requesting): 60,000 $PYTH
- Projected timeframe to completion: approx 2 months

---

<div class="post-metadata">

**Author:** ![MAYOR](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@MAYOR](https://forum.pyth.network/u/MAYOR)\
**Post date:** [December 11, 2025, 4:42am UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298/2 "2025-12-11T04:42:09Z")

</div>

Best works on discord as well.

Bots are fun when it comes to summoning for stats and data on discord, I think theass adoption is on X will also help push the narrative if implemented with the right summoning phrase.

There can always be a public. free version with limited features and also a pro version where all needed datas irl, irt e.t.c are well revealed meaning pro users will be needing $PYTH to be held.

Thanks for this proposal.

---

<div class="post-metadata">

**Author:** ![Mersault](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/mersault/32/651_2.png) [@Mersault](https://forum.pyth.network/u/Mersault)\
**Post date:** [December 11, 2025, 2:10pm UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298/3 "2025-12-11T14:10:55Z")

</div>

This is a wonderful initiative, and I fully support it.

Creating a public bot based on Pyth Price Feeds is truly a necessary step for the ecosystem. Such a tool not only showcases Pyth’s real-time advantages but also strengthens the brand’s presence in spaces where active discussions about prices and markets take place.

The approach with open vibe-coding sessions is especially valuable, as it organically engages the community

---

<div class="post-metadata">

**Author:** ![arguer](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/arguer/32/39_2.png) [@arguer](https://forum.pyth.network/u/arguer)\
**Post date:** [December 14, 2025, 2:43pm UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298/4 "2025-12-14T14:43:27Z")

</div>

Overall, I really like the idea.

One concern I have is **branding risk**. Since this would be a very visible, public-facing touchpoint, an underwhelming or unreliable bot could have a net negative impact on the Pyth brand.

To mitigate this, it may be better to run it as a **friendly**  **community competition, which involves two phases** :

- Phase 1 could be framed as experimental and non-official, focused on facilitating innovation, educating community members on the basics of vibe coding and setting the foundations for building such a price feed bot. Yet at the same time, leaving enough room for individual creativity and ideas.

- In Phase 2, the winner is selected (assumed to be a decently high-performing bot). This will then be further optimized and improved (maybe with help and inputs from Pyth Devs and integrating more powerful APIs?), before being released as the a more “official” **Pyth Price Feed Bot**.

Community vibe-coding sessions (e.g. Discord streams) can still play a role, but more as an **educational on-ramp** : introducing people to vibe coding at a base level and guiding them toward building a price feed bot. This encourages more hands-on participation rather than just passive demonstration by a few.

Finally, the grant request could be structured as a **prize pool for competition winners** , rather than just paying a small number of developers, which better aligns incentives around quality and performance.

---

<div class="post-metadata">

**Author:** ![offmylawn](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@offmylawn](https://forum.pyth.network/u/offmylawn)\
**Post date:** [December 17, 2025, 6:23pm UTC](https://forum.pyth.network/t/pyth-price-feed-twitter-tg-bot-proposal/2298/5 "2025-12-17T18:23:04Z")

</div>

great idea! i can help put this together, and to arguer’s point above would be happy to build this alongside the community if required
