I had a couple requests from delegates who wanted to share their forged Lisks with the voters in a easy way, without becoming a pool.
For that i added this command to
LiskAK:
-U, --shareWithVoters <ARG1> Here is the complete list of commands so far:
-c, --configuration <ARG1> Path to the configuration json file (defaults to ./liskak.json)
-i, --info Displays your account info
-N, --newAccount Creates a new account
-b, --balance <ARG1> Displays an account's balance
-d, --getHeight Get block height
-L, --logLevel <ARG1> Logging level, one of: error, warn, info verbose, debug, silly ("info" by default)
-l, --listVotes <ARG1> Lists your votes
-V, --listVoters <ARG1> Lists your voters
-U, --shareWithVoters <ARG1> Share ARG1 percent / value of your account funds with your voters. -I, --upvote <ARG1> Vote for delegates in file specified
-O, --downvote <ARG1> Remove vote from delegates in file specified
-C, --checkVotes Checks current votes, compares with upvote/downvote data in files (flags -I and -O)
-r, --replaceVotes Set the upvotes exactly as provided by the upvote list from -I flag
-A, --commitVotes Executes your voting orders with upvote/downvote data in files (flags -I and -O); check first with -C flag for action list
-v, --voteForIrondizzy Allow a spare voting slot to go to "hmachado"
-y, --isForging Test if forging
-Y, --enableForging Enable forging
-W, --disableForging Disable forging
-z, --status Reports on sync status of node
-s, --donate <ARG1> Donate LSK to this great cause, default: 5
-t, --transfer <ARG1> <ARG2> Transfer LSK to an address from your configured account: -t LSK ADDRESS
-T, --lsktransfer <ARG1> <ARG2> Transfer LSK^-8 to an address from your configured account: -T LSK ADDRESS
-m, --multitransfer <ARG1>...<ARGN> Transfer LSK to a list of addresses from your configured account: -t LSK ADDRESS [ADDRESS] ...
-M, --multilsktransfer <ARG1>...<ARGN> Transfer LSK^-8 to a list of addresses from your configured account: -t LSK ADDRESS [ADDRESS] ...
-f, --failoverMonkey <ARG1>...<ARGN> Provide a list of available nodes for forging failover; stays awake and acts on blockchain and connection failures
-Z, --measureOnSyncOnly Takes measures of consensus only while syncing
-E, --switchConfirmation <ARG1> Wait for N cycles before switching ("3" by default)
-S, --supervise <ARG1> Provide lisk path to manage lisk process locally (handles fork3, etc.)
-K, --liskscript <ARG1> Provide absolute path for lisk script: lisk.sh for operations (supervise implied)
-J, --logfile <ARG1> Provide absolute path for lisk logfile (supervise implied)
-B, --minutesWithoutBlock <ARG1> Minutes without blocks before issuing a rebuild, default is disabled (0)
-Q, --consensus <ARG1> <ARG2> Broadhash consensus threshold (%), reload if under value for N consecutive samples ("0,10" by default)
-q, --inadequateBroadhash Restart on "Inadequate broadhash consensus" message
-R, --reloadSchedule <ARG1> Restart after N minutes if not forging, supervise only, 0 means disabled
-P, --pollingInterval <ARG1> Interval between node polling in milliseconds ("10000" by default)
-w, --apiRequestTimeout <ARG1> API request timeout, 0 means disabled
-F, --maxFailures <ARG1> Maximum failures tolerated when chatting with lisk nodes ("10" by default)
-D, --maxBlocksDelayed <ARG1> Maximum number of block difference between nodes before change forging node
-X, --testMode Test mode
Get LiskAK here ->
https://github.com/filipealmeida/liskakKeep sending me suggestions for new features and i will continue to implement them when i can.
If you use LiskAK or just wanna show your support,
send your vote here:
Delegate hmachado - 8858064098621060602L
