Open m21 opened 9 years ago
Sounds like fun, mind to go into detail?
There are the RPC calls:
signmessage "bitcoinaddress" "message"
verifymessage "bitcoinaddress" "signature" "message"
If the project leader is looking forward to implement @TierNolan's cross chain protocol or similar, there is actually a cross-chain transaction Bitcoin Core integration:
https://github.com/XertroV/ZEDD/tree/chaintrade https://github.com/XertroV/ZEDD/wiki/Chaintrade-Specification
That aside, what's the plan to overcome the balance, insteaf of output, based constraints of Mastercoin?
Edit: just realized this is the Omniwallet and not Master Core repo. I guess it's about providing an interface to the above mentioned calls.
For token (SP) value transfer from Omni Protocol to another chain the sender must prove they own respective tokens on the Omni Protocol. They easiest way to do so is to sign some text message with a private key from the wallet. Most node-wallets & web-wallets already do that. OmniWallet needs to allow that as well -- Adam thought the implementation is a matter of days. There are at least 2 use cases that may require this.