A Twitter & Telegram bot announcing Big $BIND stakes and daily stake reports - Created By Compendia Validator Bindie
Do you like Bindie's stake reports or thought this public repository was useful?
Consider giving validator Bindie a vote on the Compendia Network.
Don't have a vote? We're always open for $BIND donations to cU3kVS8sgH4E4hcyaUEQ6DtxwJo2Y4L8iP
module.exports = {
// Any other plugin(s) ..
"@robovalidators/power-poster": {
telegram: {
token: "", // Telegram token (obtained from @BotFather)
channelId: "" // ID of the telegram channel you want to announce in
},
twitter: {
consumerKey: "", // Twitter API key
consumerSecret: "", // Twitter API secret
accessKey: "", // Twitter User Access Key
accessSecret: "" // Twitter User Access Secret
},
minimumAmount: 0, // Minimum amount of USD to announce as a "whale"-post
startHeight: 0, // Heigh to start the announcements from
txUrl: "https://bindscan.io/transaction", // API endpoint for transaction
token: "BIND", // Token you want to use (used in price API call)
currency: "USD", // Token value currency you want to query and post
cron: "0 18 * * *" // The cron expression used for the accumulative stake reports
},
// Any other plugin(s) ..
};As a tip, check your expressions here to verify they are correct: cron expression generator
# Install Redis
sudo apt update
sudo apt install redis-server
# Enable redis on system reboots
sudo systemctl enable redis-server
# Navigate to plugins folder
cd ~/compendia-core/plugins/
# Clone repo
git clone https://github.com/RoboValidators/power-poster
# Install deps
cd power-poster && yarn
# Create serviceAccountKey file
touch serviceAccountKey.json
# Copy FireBase secrets to the serviceAccountKey file
# Secrets can be found in Project Settings -> Service Accounts
nano serviceAccountKey.json
# Build the project
yarn build
# Start the validator/relay
ccontrol start relay | forger | core
# If you see ============== POWER-POSTER ==============
# in your logs during startup, everything is set and done!
If you discover a security vulnerability within this package, please send an e-mail to [email protected]. All security vulnerabilities will be promptly addressed.