Thanks for the reply.
I definitely agree, you would not want a single account holding PHP. So, the intention I was speaking of was definitely in the sense of individual's holding it.
The incentive to sell accounts that hold PHP may be a bad thing. That was one of the things I had thought about, but I hadn't really explored the +/- and if there would be a way around that.
When thinking about PHP, there are a few different ways to implement it. One way is to create a burn address for each account, and the liquid Hive would be sent to that address with no spending output, hence burning it. This doesn't require sending to a central burn address like @null, but I'm unsure if current or new accounts could be set up to add a new burn address to a current private key. But, you would probably need this, because you wouldn't need an additional token to represent PHP, nor would you want that additional token sent to an address with spending outputs, or it would render PHP no different than HP because you may not be able to power it down, but you could sell/trade it. So, I believe the best option would be the actual Hive in he burned address per account.
So, if you decide you want to sell you Hive account and you have incentive because it has a large amount of PHP, that may not be a good thing. Now, technically today you could still sell an account full of HBD, Hive, and HP. It could be as valuable as a whale account, or a zero balance, or minnow account. Nothing stops you today, so would an account with PHP really be any different than selling a loaded account today, other than the fact that it is loaded with PHP that is permanent and cannot be liquidated? Not that I see.
But, you are correct, it could create incentive. It would be a safer sale than selling an account with liquid Hive and liquid HBD, in the sense that you could sell the account, take the payment, then immediately sending the Hive/HBD from that account, screwing over the buyer.
One possible way to do it though that could work is, if you change your master password/keys, it would destroy the PHP burn address and create a new one. The first thing someone does when receiving a purchased account is change the password so that the previous owner can no longer access that. I wonder if that would be a possible solution? That way if you were to sell the account to a new user, they would not receive he PHP address associated with the account? If you could not transfer the account to a new user, you wouldn't have any incentive to borrow against the account?
Just a thought. Thanks for your input.