Delegate, secret are a bit confusing in the current description:

We should modify delegate to bakerAddress so it's very clear that it's the baker's address and not the payout's wallet. Also, the fact that there is no need to specify the Payout Wallet Public Key because of passing the PK should be made clear to the user by using secretPayoutWallet.
Naming proposal:
i). bakerAddress: Baker's address, the node that is running the Tezos Bakery.
ii). delegators: the different addresses that are delegating to the Baker's address.
iii). payoutWallet & secretPayoutWallet: the wallet that is sending payouts to delegator addresses. We can use secretPayoutWallet for "encrypted secret key of the wallet paying (e.g. --secret=)"
To look have something like that:
./payman payout \
--bakerAddress=tz3gN8NTLNLJg5KRsUU47NHNVHbdhcFXjjaB \
--secretPayoutWallet=edesk1Qx5JbctVnFVHL4A7BXgyExihHfcAHRYXoxkbSBmKqP2Sp92Gg1xcU8mqqu4Qi9TXkXwomMxAfy19sWAgCm \
--password=abcd1234 \
--cycle=160 \
--node=127.0.0.1 \
--port=8732 \
--fee=0.05
Delegate,secretare a bit confusing in the current description:We should modify
delegatetobakerAddressso it's very clear that it's the baker's address and not the payout's wallet. Also, the fact that there is no need to specify the Payout Wallet Public Key because of passing the PK should be made clear to the user by usingsecretPayoutWallet.Naming proposal:
i).
bakerAddress: Baker's address, the node that is running the Tezos Bakery.ii).
delegators: the different addresses that are delegating to the Baker's address.iii).
payoutWallet&secretPayoutWallet: the wallet that is sending payouts to delegator addresses. We can usesecretPayoutWalletfor "encrypted secret key of the wallet paying (e.g. --secret=)"To look have something like that: