Currently, there are no protocol-level specifications to prevent self-staking by Property holders.

When a Property holder self-stakes his Property, the user gets a reward for his Property in addition to the staking reward, which raises the issue of double APY acquisition.

There will be a certain amount of pain in resolving this issue, because if the Property holder is switching multiple wallet addresses, then validation by address also loses its meaning.

This proposal effectively nullifies self-staking by including its staking share in Property's reward calculation.

Holders of Property obtain regular staking rewards by oneself staking. They also obtain additional rewards in accordance with the staking gathered in Property.

For example, Alice has 50% of the Property and stakes 100 DEV. In her Property, 1000 DEV in total has been staked. We postulate APY at 30%.

Alice_staking_share = 100 / 1000 = 0.1
Alice_pool_share = 0.5
Pool_total_reward = 1000 * 0.3 = 300

Alice_creator_reward = 300 * 0.1 * 0.5 = 15
Alice_staking_reward = 100 * 0.3 = 30

Alice_earn_reward = 30 + 15 = 45

If Alice uses another wallet to staking 600 DEV, the reward for Alice as a creator can calculate the following.

Alice_staking_share = 100 / 1600 = 0.0625
                             ^       ^^^^
Alice_pool_share = 0.5
Pool_total_reward = 1600 * 0.3 = 480
                     ^           ^^
Alice_creator_reward = 480 * 0.0625 * 0.5 = 15
                       ^^      ^^^^
Alice_staking_reward = 100 * 0.3 = 30

Alice_earn_reward = 30 + 15 = 45

The reward for Alice as a creator will not change. This spec disables double APY's from being earned.

Advantages

Since Property holders are also stakers and staking share of creators in the calculation of their reward are included, they cannot doubly obtain reward with multiple wallets.

Disadvantages

Creators as Property holders need to purchase DEV and have to stake themselves to earn rewards. If they don't stake themselves, the Property holders' reward is 0.