Documentation - Microsoft Internet Explorer
×
FileEditViewFavoritesToolsHelp
BackHome
Address
http://dannydevito.fun/docs
Links

Joe Bondin Documentation

Back to Desktop

A clear overview of how the platform works, what exists today, and what $BONDIN holders receive.

Table of Contents

Overview

Joe Bondin is a token driven platform that runs a recurring launch schedule, captures community signal, and turns that signal into new token launches. The platform is intentionally simple to use: connect a wallet, stake $BONDIN if you want allocations, and participate in conversation.

The ticker is $BONDIN.

Joe Bondin as a self operating agent

Joe Bondin is a self operating agent powered by a personality profile and live community inputs. The personality is loaded from a local profile file, and the agent responds in character through chat.

The system improves through a feedback loop. Token holders can participate in conversation, those messages are stored, and verified holder messages can influence upcoming launch previews. The platform also supports generating and posting tweets, which keeps the agent active in public channels.

Implementation notes: the agent logic lives in src/lib/dannyAgent.js and the profile lives in docs/joe_bondin_personality.json.

Core platform pillars

1) Vault and launch history
The Vault displays launch history and scheduled launch timing. Launches are stored in the database and rendered in the Vault UI.
Relevant page: src/app/vault/page.js
2) Launch scheduling and previews
The scheduler maintains a persistent cadence, prepares a draft before launch time, and provides a preview window for admins to review or adjust draft fields.
Relevant modules: src/lib/launchScheduler.js, src/app/api/cron/launch/route.js, src/app/api/admin/schedule/route.js
3) Pump.fun launch execution
Launches are executed on Solana using the Pump.fun create transaction. The platform signs the transaction through the configured treasury wallet.
Relevant module: src/lib/pumpfun.js
4) Staking and allocations
Staking uses 1:1 escrow wallets per user (server custody via Privy). Allocations accrue per launch and are claimable when the user unstakes. The user pays gas for the claim transactions.
Relevant page and logic: src/app/staking/page.js, src/lib/staking.js
5) Conversation and holder influence
The agent chat stores conversations. If the sender is a verified holder, their messages can be used as input to launch preview generation.
Relevant endpoints: /api/chat, /chat-logs, and holder verification via src/lib/holderGate.js
6) Twitter and public presence
The platform can generate tweets in character and post them through the X API. This is currently exposed as an admin authenticated endpoint.
Relevant endpoint and module: /api/twitter/tweet, src/lib/twitter.js
7) Admin console
Admins can review schedule drafts, trigger launches, and inspect allocations.
Relevant page: src/app/admin/page.js

$BONDIN holder benefits

Holding and staking $BONDIN provides access and upside that non stakers do not receive.

  • Launch allocations: stakers receive allocations from new launches. Allocations are weighted by stake and time multiplier.
  • Claim on unstake: allocations accrue across launches and are claimed together when you unstake. You pay the network fee, and you receive the accumulated launch tokens.
  • Influence: verified holders can have their chat messages used as input to launch preview generation.

Tokenomics note: the platform grabs 5% of supply per launch, and 2% of that grab is reserved for stakers.

Documents shipped in this codebase

The repository includes the following documents and reference files:

PathPurpose
docs/STAKING_SETUP.mdSetup notes for staking, database, and environment variables.
docs/danny_devito_personality.jsonPrimary character profile used to build the agent system prompt.
docs/personality profileA compact written personality reference.
docs/ai_pumpfun_master_spec.pngReference image spec for launch behavior and Pump.fun integration.

Key routes and endpoints

AreaRoutePurpose
Vault/vaultLaunch history and schedule status.
Staking/stakingStake, request unstake, claim, and view allocations.
Schedule/api/launch-schedulePublic schedule countdown and preview timing.
Cron launch/api/cron/launchAutomated scheduled launch execution.
Agent chat/api/chatChat with the agent. Holder messages can influence launches.
Twitter/api/twitter/tweetGenerate and post tweets (admin authenticated).

Configuration and environment variables

Configuration is stored in .env.local. The reference template is .env.example.

  • Solana RPC: SOLANA_RPC_URL and NEXT_PUBLIC_SOLANA_RPC_URL
  • Treasury wallet: TREASURY_WALLET_ID
  • Staking token mint: DEVITO_TOKEN_MINT
  • Admin allowlist: ADMIN_WALLET_PUBKEYS
  • OpenAI: OPENAI_API_KEY
  • X credentials: variables in the Twitter section of .env.example
Documentation is a work in progress. If you want a section added, specify the title and the intended audience.
✓Done
Internet
Start
📄Documentation - Internet Explorer
01:39 AM