Create a standardised URI schema

[owenvoke]

Description

We currently have a format for QR metadata content, it would be good to standardise a URI schema that can be used in future. Both for links, QR codes, and NFC tags.

Wallet QRs currently use the format:

{address}|{publicKey}|{privateKey}

Transaction QRs currently use the format:

arosend|{address}|{value}|{message}

Possible implementation

URI Scheme

All Arionum URLs should start with the arionum prefix. For example, arionum://send.

URI Endpoints

Send

The send endpoint is used for sending transactions to a specific address, alias, or public key.

# Sending to an address, alias, or public key
GET arionum://send?address=[address]
GET arionum://send?alias=[alias]
GET arionum://send?public-key=[publicKey]

# Sending a specific value
GET arionum://send?value=[value]

# Sending with a specific message
GET arionum://send?message=[message]

# Sending to an address with a pre-filled value and message
GET arionum://send?address=[address]&value=[value]&message=[message]

Account

The account endpoint is used for registering account details. The values can be combined to register a full keypair, or used individually.

# Register one or more values for an account
GET arionum://account?address=[address]
GET arionum://account?public-key=[publicKey]
GET arionum://account?private-key=[privateKey]

# Register a full keypair
GET arionum://account?public-key=[publicKey]&private-key=[privateKey]

Verify

The verify endpoint is used for verifying a signature matches the specified input data.

GET arionum://verify?data=[data]&signature=[signature]&public-key=[publicKey]