Add LeanPocket Capability #44
Description
Is your feature request related to a problem? Please describe.
Currently the price of one servicer node is quite cheap relatively in comparison to other nodes, and currently in our Dappnode package we only allow a single custodial node to be run, and without creating a copy package manually and edit a lot of params etc, so we can't run more than one instance on Dappnode right now.
While adding more Pokt to the staked amounts over the minimum staked limits + some room for fees can help keep you from being jailed right away, but it doesn't change anything until you break the validator levels, which starts producing Pokt Blocks and producer rewards in addition to servicer rewards, but producer rewards are not nearly as large/profitable as the servicer rewards are, and it takes a lot more Pokt for a node it to be a validator than a servicer.
Describe the solution you'd like
Add LeanPockt to the config and UI. It allows the use of one pocket instance to run multiple accounts/nodes and allows for multiple nodes on one server multiplying potential rewards using the same Pokt node using the same chains on all nodes/accounts only needing the single Pocket node, blockchain, RAM usage etc, doesn't double with each additional servicer. But allows for running multiple Pokt servicers on a single machine all running the same chains increases the .
This allows to multiply rewards by adding multiple validators which is just not possible right now with the current config and way the UI and app are written currently.
Describe alternatives you've considered
Potentially create a separate package for lean pocket Multiple validators and use the this package for single node validators who dont want to use lean pocket because of the cost of more servicers, or the downside of having multiple servicers on one pokt node and dappnode in general, is one goes down, all go down, all chains and all individual servicers. so theres a goo reason not to want to use lean pocket but its best to use the one package and just make it as configurable as possible from the UI, 1 node or lean pocket, custodial or non, and custom endpoint selection from the UI are top config priorities others to be considered with lean pocket is multiplying config options such as the open files limit, no file limit and max connections limits.
Other important configs to add to the DappManger config are, max peers inbound, outbound, seeds, persistent peers to add other dappnodes especially dev's long running nodes with well filled address books. and dappnode validators and seeds (I am working towards running my own seed node)
Additional context
https://docs.pokt.network/node/leanpocket/