Make the "chainPath" optional in Token file?

[coder5876]

Right now the getProfileFromTokens() function requires there to be a chainPath in the token and it also requires the user to pass in a master public key to derive a child key using the chainPath. I feel like it should be possible for the user to use a simpler structure where you have only a single public key that doesn't need the existence of an HD tree.

A simple addition is to have the logic of getProfileFromTokens() check for the existence of chainPath and if it's not there it skips that verification step. If there is interest I can do a pull request.

[shea256]

Ah good point. I'd say this is needed.

Though, it would be great to chat with you sometime and work through the requirements for this.

I've been thinking through some design improvements and I'd love to run them by you and learn more about how you plan on using this and what your needs are.

[coder5876]

Sounds good re chat! You want to do a Slack-convo or Skype/Hangouts chat?

[shea256]

@christianlundkvist Can you ping me in chat.blockstack.org and we'll coordinate?

[coder5876]

Sure, I'll ping you in the Slack channel.