AGENTS.md watermarks refreshed to HEAD (358f719). Content updates:
- scripts/harb-evaluator/AGENTS.md: documented wallet.ts auto-reconnect
fix (wagmi EIP-6963 auto-connect handling, 10s disconnect timeout)
- All other AGENTS.md files: watermark bump only
Pending actions (3): promote #1155 pitch-deck to backlog.
Escalate: #1158 (Phase 1 completion accuracy) — needs planner/human decision.
2 KiB
2 KiB
Transaction Bot - Agent Guide
Automation service that maintains liquidity alignment and tax enforcement for the KRAIKEN protocol.
Responsibilities
- Monitor Ponder GraphQL metrics to detect when
recenter()should be triggered. - Track staking positions for overdue taxes and call
payTax()when profitable. - Expose a status endpoint (
GET /status) for operational visibility.
Architecture
service.js- Main loop that polls the GraphQL endpoint, evaluates triggers, and submits transactions.generateKey.js- Utility for provisioning dedicated bot wallets.package.jsonscripts -npm install,npm start, and debug runs viaDEBUG=* npm start.- ES Module: This service uses
"type": "module"and imports kraiken-lib as an ES module. All imports use ES module syntax (importinstead ofrequire()). - Node.js Compatibility: Requires Node.js ≥14 with ES module support. The
__dirnameand__filenameglobals are not available; useimport.meta.urlwithfileURLToPath()instead.
Configuration
Set the following environment variables (automatically generated when the stack script is used):
ENVIRONMENT=BASE_SEPOLIA_LOCAL_FORK|BASE_MAINNET_LOCAL_FORK|BASE_SEPOLIA|BASE
PROVIDER_URL=<rpc-url>
PRIVATE_KEY=<hex-private-key>
LM_CONTRACT_ADDRESS=<liquidity-manager-address>
STAKE_CONTRACT_ADDRESS=<stake-contract-address>
GRAPHQL_ENDPOINT=<ponder-graphql-url>
# Optional: PORT=43069
Operations
- Launch via
nohup ./scripts/dev.sh start &; the script handles env injection and process supervision. - For focused debugging, run
npm installthennpm startwithinservices/txnBot/after the stack is already up. - Monitor logs for transaction receipts and ensure gas pricing stays within acceptable bounds.
Safety Checklist
- Use dedicated wallets and keep balances minimal.
- Rotate keys if compromise is suspected; update secrets before restarting the stack.
- Observe exponential backoff behaviour and avoid hammering RPC endpoints on failure.