Why NOMP pool imposible mining to wallet address?

[Master-01]

Hellow! I runned you PICS wallet and connected my NOMP pool, but as soon as I find a new block, the reward for this unit falls to the address of another wallet. That is, I specify config the address of my wallet "7Ls7SJSXDZs3sZDzkGXge5fZGrJ1Gi45PJ" in NOMP, but the award goes into a completely different wallet "PSPEpeN3cnQ6atoTj3rS36Z2T2bjdvMnV6", for example transaction "0f27c3341e2747ab2716b4fd1e69db41190e56270e57d630997b42477e497cc5". Please tell me what changes need to be made in the NOMP code so that the reward gets to the exact address of the wallet specified in the settings?

[minblock]

Version 17 automatically defaults to SEGWIT or 7 based addressing. The NOMP server mines with legacy addresses (P) but can relay those funds to 7 or P2SH Segwit addresses. This is meant to mine SEGWIT efficiently. To mine properly, use version Picscoin version 16 which has a default P based new wallet address. P2SH or 7 Addresses cannot be used as a client for your NOMP server. The mining client can be downloaded here: https://downloads.picscoins.org/picscoin-0.16.3-x86_64-linux-gnu.tar.gz. . Picscoin v17 is meant for Segwit transactions. Block discovery times for P2SH are lagged due to the fact that it offloads transactions. Currently we are adding more v17 Segregated witness nodes that can authenticate those mined transactions.

[minblock]

If you had a version 16 wallet to start, used that wallet address that was generated for example (PSPEpeN3cnQ6atoTj3rS36Z2T2bjdvMnV6), then shut down your Picscoin Client, upgraded it to version 17, and then you would get default Segregated witness addressing (Beginning with 7) however you will still receive mining income to your P address since those public wallet addresses are based off the same seed. The process of upgrading to load default wallet addressing in Picscoin version 17 would be to type getnewaddress ( "label" "address_type" ) and specify legacy as address_type and you will be issued a P address.

[sevecat]

When you use segwit it detaches the wallet from the mining and will fabricate a legacy wallet address the one that begins with "P" to illustrate where the transaction for mining is going to and coming from initially if paying itself with segwit(offthechainandprivatetransactionwheretheclientsCPUdoesmostofthework) and it the public mining server cannot send money to a wallet address that is concealing its origin(beginningwith7address), only if you are using the mining pool wallet, then it could be lucky because it knows that it fabricated it. However there are errors when people are mining with 7 addressing when the blockchain wasn't propagated to segwit so any transactinos sent during the launch of segwit wallet to wallet irregardless of mining would of been lost if there was no segwit mining going down at that time. All servers were using the legacy wallet addressing as well as numerous relaunch attempts for segwit leaves certain times of the blockchain completely down and not syncing.