Sure, but first some context …
I have created initially 4 payments key pairs, and 4 stake keys pairs that would match them.
For example :
And used the stake key to create an address with staking capability after proper registration. In the example, I would call it just
I repeated that process for
rew (reward) and
pop (pool op). All four registered on chain for staking rights etc …
When I finally hit my pool cert creation :
cardano-cli shelley stake-pool registration-certificate --cold-verification-key-file node.vkey --vrf-verification-key-file vrf.vkey --pool-pledge 1000000000000 --pool-cost 2000000000 --pool-margin 0.10 --pool-reward-account-verification-key-file rew_stake.vkey --pool-owner-stake-verification-key-file own1_stake.vkey --pool-owner-stake-verification-key-file own2_stake.vkey --out-file nodecert
As you can see, I made use of the owners 1 and 2, as well as of my rewards address. But somehow I was certain there was a
--pool-operator-stake-verification-key-file flag I could use together with my
pop_stake.vkey. But nope, the CLI does not provide that option.
This is a minor thing really, as
rew will receive all rewards, but I thought… would be pretty neat to be able to separate pool operation from owner rewards like that, at the certificate creation.
I might be asking too much
Edit/Second thougth : Ok, that was a pretty dumb question after all. If that would be the case, anyone would start bargaining to pledge instead of delegate, and the poor pool operator would accept that Faustian contract. That would undermine the trust assumption that must exist between owners and operator which is sealed by the uniqueness of the reward address. My bad.