# Self hosted Bot to easy vote in cosmos ecosystem

**URL:** <https://community.lavanet.xyz/t/self-hosted-bot-to-easy-vote-in-cosmos-ecosystem/48>\
**Category:** 👾 dApps & Projects\
**Created:** [February 7, 2024, 10:42am UTC](https://community.lavanet.xyz/t/self-hosted-bot-to-easy-vote-in-cosmos-ecosystem/48 "2024-02-07T10:42:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ruslan](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.lavanet.xyz/ruslan/32/51_2.png) [@ruslan](https://community.lavanet.xyz/u/ruslan)\
**Post date:** [February 7, 2024, 10:42am UTC](https://community.lavanet.xyz/t/self-hosted-bot-to-easy-vote-in-cosmos-ecosystem/48/1 "2024-02-07T10:42:04Z")

</div>

There is no need to vote via CLI or web UI, just setup a bot with your validator or wherever you want to get notifications with vote options, and vote _ **directly in telegram!** _

Supports [LavaSdk](https://github.com/mellifera-labs/janusbot?tab=readme-ov-file#lava-integration) out of the box.

You can find the source code and instructions for setup on GitHub

> **[GitHub - MELLIFERA-Labs/janusbot: Self hosted Bot to easy vote in cosmos...](https://github.com/mellifera-labs/janusbot)**
>
> Self hosted Bot to easy vote in cosmos ecosystem. Contribute to MELLIFERA-Labs/janusbot development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![kagemnikarimu](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.lavanet.xyz/kagemnikarimu/32/23_2.png) [@kagemnikarimu](https://community.lavanet.xyz/u/kagemnikarimu)\
**Post date:** [February 8, 2024, 11:27pm UTC](https://community.lavanet.xyz/t/self-hosted-bot-to-easy-vote-in-cosmos-ecosystem/48/2 "2024-02-08T23:27:43Z")

</div>

Very exciting contribution, @ruslan !

> Supports [LavaSdk](https://github.com/mellifera-labs/janusbot?tab=readme-ov-file#lava-integration) out of the box.

I love the integration - and I’m curious if it can be set to also use [Badges](https://docs.lavanet.xyz/sdk-frontend) in the environmental variable setup for Lava.

This could be accomplished by adding two environmental variables

1. **LAVA\_BADGE\_ID** - whereby a user inputs their [badge projectID](https://docs.lavanet.xyz/sdk-frontend#-badges)
2. **LAVA\_BADGE\_SERVER** - whereby a user inputs their badge server address, or it is auto-populated by [Lava’s default badge server](https://docs.lavanet.xyz/badge-server#lava-badge-server-).

Obviously, the application would have to check if **LAVA\_PRIV\_KEY** or **LAVA\_BADGE\_ID** were set and decide which one to use. Alternatively, you could have them set it in the _config.toml_ (probably a better approach if you go this route!)