Developer: API Requests, bugs, etc

If the oAuthed user is the coin's creator, let them provide either the rnbUserId or an email/social media ID to view the amount of coin held by that user. Return 0 if "not found"; that should cover most security concerns, I think.

Having a KYCFinished flag on a user record that we can use in API gives us an important attribute. This would allow Developer and Creators to understand the relative risk level of a user, and also, very importantly, use the KYC flag as a trigger for releasing some kind of user reward based on attribution.

There have been use cases which have come up which call for the conversion CC to another CC or to RLY. For example, an app may need to convert CC to RLY in order to bridge out and purchase real world good that the user ordered with their CC. We currently lack the ability to convert coins at all via API right now. This means a business or organization would need to maintain a human process in order to manage hundreds (and soon, thousands) of Creator Coin in order to do business.