How we built an Abstract upvote bot

Understand the target flow

The bot should not vote blindly. It should watch the Abstract Portal window, notify you in Telegram, then broadcast only after you tap confirm.

Prepare the server workspace

Use a small VPS or always-on machine. Install Node.js 20+, create a project folder, and keep secrets outside git.

mkdir -p ~/abstract-upvote-bot
cd ~/abstract-upvote-bot
npm init -y
npm install viem @abstract-foundation/agw-client

• Use a dedicated folder for the bot.
• Commit code, but never commit private keys or bot tokens.
• Create an out/ folder for logs and daily run output.

Create a dedicated Telegram bot

In Telegram, talk to @BotFather, create a new bot, copy the token, then send your bot one message so it can identify your chat.

# Example env shape — token values stay private
TELEGRAM_BOT_TOKEN=123456:bot_token_here
TELEGRAM_CHAT_ID=your_numeric_chat_id

• Use a separate bot for upvotes so alerts are not mixed with normal chat.
• Allow only your Telegram user/chat ID.
• Send a test message before adding any wallet logic.

Read Abstract Portal vote status

The daily sender should ask Portal whether the wallet already voted today. If votedToday=true, it exits quietly. If not, it sends a Telegram card.

// pseudo-flow
const status = await getPortalVoteStatus(wallet)
if (status.votedToday) return
await sendTelegramCard({ appId, currentStreak, nextVoteBy })

Create a limited AGW session key

The session key is a separate signer. It must be registered with the Abstract Global Wallet and scoped to exactly the upvote action.

• Target contract: Abstract Portal vote contract.
• Allowed selector: voteForApp(uint256).
• ETH value: 0.
• Fee cap: small, explicit limit.
• Expiration: set a real end date.

Write the preflight script

Before a vote can broadcast, preflight checks that the action is still valid and safe. This prevents duplicate votes, wrong app IDs, expired sessions, or policy mismatches.

node tools/abstract-wallet/prepare-session-vote-tx.mjs --app 207

• Check votedToday=false.
• Check selected app is allowlisted and not already voted this epoch.
• Check session has not expired.
• Check target contract, selector, value, and fee cap match policy.
• Estimate gas / simulate before broadcast.

Write the Telegram confirmation flow

The daily card has two choices: confirm or skip. Confirm calls the broadcast script with an exact confirmation string. Skip does nothing.

✅ Confirm upvote → broadcast-session-vote-tx.mjs
⏭ Skip today     → no transaction

Write the broadcast script

Broadcast should be boring and narrow. It receives the confirmed app ID, re-runs preflight, then uses the session signer to submit the vote.

node tools/abstract-wallet/broadcast-session-vote-tx.mjs \
  --app 207 \
  --confirm "CONFIRM_ABSTRACT_UPVOTE"

• Reject if confirmation string is missing or wrong.
• Reject if preflight fails.
• Return concise Telegram success/failure text.
• Include tx hash on success.

Schedule the daily reminder

Use cron to run the daily card sender after the Portal window opens. Log every run so you can inspect failures.

5 15 * * * cd ~/abstract-upvote-bot && \
  node tools/abstract-upvotes/send-daily-card.mjs \
  >> tools/abstract-upvotes/out/daily-card.log 2>&1

Test in this order

Do not jump straight to production cron. Test each layer separately so any failure is easy to isolate.

• Telegram test message arrives.
• Portal status checker returns the wallet vote state.
• Daily card sends only when votedToday=false.
• Preflight passes for the chosen app.
• Manual confirm broadcasts one successful vote.
• After success, Portal shows votedToday=true.
• Next daily cron sends the card at the expected time.