[00:47:19] <navcoin-bot> <A-B> https://cdn.discordapp.com/attachments/416000318149754881/513877902928904195/unknown.png
[00:47:46] <navcoin-bot> <A-B> Ok that makes sense
[03:55:04] <navcoin-bot> <Matt (Dev)> If we run: getcoldstakingaddress(coldstaking_address, coldstaking_address) Do we think the error should be: A - Staking address is not a valid NavCoin address (because a cold staking address isn't valid) Or B - The staking address should be different to the spending address (because they're the same address)
[03:55:19] <navcoin-bot> <Matt (Dev)> and does it actually matter 😛
[21:20:19] <navcoin-bot> <Matt (Dev)> @aguycalled when we create a cold staking address can we pass an OpenAlias address?
[21:20:38] <navcoin-bot> <aguycalled> not supported
[21:20:45] <navcoin-bot> <Matt (Dev)> Thought so
[21:20:46] <navcoin-bot> <aguycalled> but could be
[21:20:51] <navcoin-bot> <Matt (Dev)> We can add it later
[21:21:04] <navcoin-bot> <Matt (Dev)> I'm just writing the RPC docs for getcoldstakingaddress
[21:21:05] <navcoin-bot> <aguycalled> anyway i think its safer to directly add the addresses
[21:21:08] <navcoin-bot> <Matt (Dev)> Agreed
[21:21:16] <navcoin-bot> <aguycalled> as theres a more direct relation with the pubkey
[21:21:28] <navcoin-bot> <aguycalled> while the openalias can for whatever reason point somewhere else
[21:21:38] <navcoin-bot> <Matt (Dev)> Yeah
[21:21:49] <navcoin-bot> <aguycalled> we would need to offer a confirmation so user can double check the pubkeys are the right ones
[21:24:53] <navcoin-bot> <Matt (Dev)> Yeah