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
Since there's one bitcoin wallet for the Payment Zone, users all send their BTC to the same address (otherwise doing the settlement transactions would become costly).
Also, the CosmicBridge wallet doesn't integrate with Bitcoin directly - the user performs the payment via some other, standard bitcoin wallet.
This means the CosmicBridge wallet needs to know a user is actually the owner of a specific Bitcoin address like the user claims (otherwise the user could feed in any address and claim they're the owners of it). One easy way to do this is have the user sign a message one time via the private key. We can think of other ways too.
The text was updated successfully, but these errors were encountered:
Changing the name because the method of using CosmicBridge/wallet (chrome extension) to sign a microtransaction is the best way.
To initiate a PZ Microtransaction, we must have the signature of the payer's bitcoin wallet. The functionality to sign something should be available in some form in the bcoin API.
lidarwin
changed the title
Create a way for the CosmicBridge wallet to prove ownership of a Bitcoin address
Signing for Payment Zone microtransactions
May 9, 2018
Since there's one bitcoin wallet for the Payment Zone, users all send their BTC to the same address (otherwise doing the settlement transactions would become costly).
Also, the CosmicBridge wallet doesn't integrate with Bitcoin directly - the user performs the payment via some other, standard bitcoin wallet.
This means the CosmicBridge wallet needs to know a user is actually the owner of a specific Bitcoin address like the user claims (otherwise the user could feed in any address and claim they're the owners of it). One easy way to do this is have the user sign a message one time via the private key. We can think of other ways too.
The text was updated successfully, but these errors were encountered: