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
{{ message }}
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.
The current Kaleidoscope implementation uses a sendtoaddress payment method, which is basically the standard also in Bitcoin wallets. However, since we are building a new protocol, it could be a good opportunity to encourage the usage of invoices, that have the advantage of mitigating human errors with the amount or asset_id, and facilitate the transmission of other relevant information from the payee to the payer (such as the commitment scheme preference, see #82).
For this scope, it would be useful to formalise an invoicing standard in the protocol specifications.
The text was updated successfully, but these errors were encountered:
The current Kaleidoscope implementation uses a
sendtoaddress
payment method, which is basically the standard also in Bitcoin wallets. However, since we are building a new protocol, it could be a good opportunity to encourage the usage of invoices, that have the advantage of mitigating human errors with the amount or asset_id, and facilitate the transmission of other relevant information from the payee to the payer (such as the commitment scheme preference, see #82).For this scope, it would be useful to formalise an invoicing standard in the protocol specifications.
The text was updated successfully, but these errors were encountered: