You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not relevant to this specification because this specification does not define how a service maintains it's own accounts. You could use an arbitrary string or a numeric identifier.
I think the only reason that an accountid would be defined would be if there were a standard way to open accounts programmatically via API with peer channel servers, so for instance for an application that would let the user choose to use "johnpitts" peer channel hosting business or "electrumsv" peer channel hosting business.
ElectrumSV's server model has it's own programmatic account creation via an API, but some businesses would have web form-based sign up.
Documentation mentions "accountID" many times in the API endpoints, but where does an account get it's ID? Self-generated? A BitCoin public key?
Maybe a dumb question, but nonetheless asking it anyway.
The text was updated successfully, but these errors were encountered: