This project is modeled on Marc Jansen’s WavesLPoSDistributer and follows the same conventions as much as possible. The objective is being a drop in replacement. Following the same architecture has the added bonus of being able to verify the correctness of each script’s output.
The code was written from scratch, with the intent of improving several areas:
providing easier, centralized configuration that is isolated in a separate file;
lowering memory and disk requirements;
lowering execution time;
allowing data analysis and statistics on top of the blockchain information
As in WavesLPoSDistributer you can use the payment utilities to execute payments for any file that conforms to the payout.json format. So if you have any home brew utilities that write their output in this format you can keep on using them as usual.
Any ideas on how to improve, pull requests, or any kind of constructive feedback is accepted. A couple of ideas for future versions are:
database support for more transaction types
a REST interface to extract information from the database
I’ve linked to your github profile and I mention localwavesnode.
In the next few days I’ll add some more updates to the code. I’m making changes to enable our node’s new policy (distributing 100% of the fees but subtracting the cost of transferring the payout to leasers).
Is there any way not to pay Leasint’s rewards from a specific address? Example, XXY address allocated 1000 Waves but is a wallet my stay that is always offline, and I want the reward to be sent directly to another YYX wallet. Would you have to put this function in the program?