search

urbit / urbit-key-generation

Key derivation and HD wallet generation functions for Urbit
MIT License
15 stars 8 forks source link

Update to Azimuth nomenclature #57

Closed jtobin closed 5 years ago

jtobin commented 5 years ago

Ship -> point, etc.

Fang- commented 5 years ago

Probably not? This is about Urbit key generation, and Urbit deals with ships. Points are an Azimuth thing, and while they lie at the foundation of Urbit ships, they are not the surface.

Fang- commented 5 years ago

There is, of course, an argument to be made about turning this and our spec into being about Azimuth wallets, but I'd counter that by saying that different applications of Azimuth have different requirements as far as wallets are concerned.

jtobin commented 5 years ago

Hard to say. I'd argue that in the general case one is generating a wallet for an Azimuth point, not specifically a ship (which, as you state correctly, is an Arvo-level concept).

But perhaps you're right. My main concern is that the switching of nomenclature from 'point' to 'ship' in Bridge for keygen arguments alone feels weird. 😄

Fang- commented 5 years ago

Bridge is an Urbit tool for dealing with Urbit assets, and so should already be talking about ships rather than points. Exception there is, of course, the azimuth-js interfacing.

jtobin commented 5 years ago

eyes cutlass

jtobin commented 5 years ago

This one doesn't seem necessary, and hasn't gone anywhere, so let's shut 'er down.