[bisq-network/bisq] Sign-Verify, Encrypt-Decrypt and onion addresses (#5174)

[huey735]

Sign-Verify, Encrypt-Decrypt are great functions provided by the cryptography used by bitcoin that allow users to prove custody of private keys associated with a certain public key/address.

Recently the [Mutisig Payout tool](https://github.com/bisq-network/bisq/pull/4899) was greatly improved by @jmacxx  to allow for the trust-less build, verification and broadcast of transactions. This brought Sign-Verify closer to the traders. Imagine how great it could be if traders could build-verify-sign-broadcast more type of transactions, with different payout schemes. This could greatly reduce the job of Mediators.

What if traders could Sign-Verify messages? They could prove the custody of the keys to others very easily without having to resort to other software like Electrum and risk copy pasting private keys from one application to another. The same for Encrypt-Decrypt.

At present Bisq has Trader, Mediation and Arbitration chats. Despite the huge work done on it by the developers it's very bare bones. With the tools above, the traders could still open a Mediation Ticket which would notify the Mediator but the conversation could be had on encrypted-chat apps like Keybase.

There the user would have an account named after their onion address and the Mediator could simply open a three-way chat with both traders. Still leaving the possibility for each of the three to break out into two-chats if they so intended.

This would allow the institution of practices like Support Agents introducing themselves to traders with a verifiable signed message. With Schnorr it could allow for any trader to post messages with the anonymity set of of all known public keys of Bisq trades.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5174
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210208/bf6d04e7/attachment.htm>