1) all tokens/balances/NFT watch goes to "harvester3", which will become just "harvester"
2) form current "harvester" we keep watching for the stakes, and mapping, as this is custom functionality bound to custom smart-contracts. Make new name for it.
Few extra things:
1) Ideally, there should be single code with RPC client for the particular BC.
2) Ideally, we need to have generic way of dealing with those "custom" extensions which depends on details of particular smart-contract (there are more coming very likely very soon). Shall they be just extensions for the harvester (aka harvester3)? (assuming RPC client is part of harvester)
1) all tokens/balances/NFT watch goes to "harvester3", which will become just "harvester" 2) form current "harvester" we keep watching for the stakes, and mapping, as this is custom functionality bound to custom smart-contracts. Make new name for it.
Few extra things: 1) Ideally, there should be single code with RPC client for the particular BC. 2) Ideally, we need to have generic way of dealing with those "custom" extensions which depends on details of particular smart-contract (there are more coming very likely very soon). Shall they be just extensions for the harvester (aka harvester3)? (assuming RPC client is part of harvester)