[Feat]: Add in-game subscription status on-chain #43
Description
Motivation
When thinking about services that could be built out by 3rd party developers for the game - there are a number of products that would rely upon an initial distribution of something like a token. This would be true for: governance, trade currencies, alpha/beta access, reputation credits, etc etc etc. Anything built like this would need some initial mechanism to distribute "fairly" and to also not be "game-able". Having a player's in-game subscription status be queryable on-chain allows for 3rd party devs to manage distributions that aren't necessarily Sybil-resistant, but it does allow us to shift the mechanism for blocking attacks from a technological barrier to a more economic barrier to attack (basically - this would effectively require attackers to pay CCP for more account subscription(s) to claim more 3rd party distributions).
There's the additional benefit for CCP in that it raises the marginal benefit to the player of a subscription when the player is deciding whether or not to buy subscription time since they might get additional in-game benefits via participation in 3rd party services.
Details
I want the subscription status and/or history of subscriptions of a player to be defined on-chain in a way that can be consumed (read-only) for other 3rd party dev purposes. The objects should either be non-transferrable or non-fungible in such a way that 3rd party devs can create an ID for a specific subscription to "disallow double spending" when reading subscription history/state for a player.