<p>The problem was that I was creating the transaction proposal and publishing it, after that I used the result from createTxProposal and passed it to signTxProposal.</p>

<p>turns out that the txProposal returned from createTxProposal doesn't have the property proposalSignature (which is filled when the transaction is published).</p>

<p>so, to solve this I had to get the transaction proposals (after publishing) and send the transaction fetched as argument to signTxProposal.</p>

CC BY-SA 4.0
2018-07-13T16:38:23.460Z
2018-07-13T17:21:07.850Z
2018-07-13T17:21:07.850Z
pmcoelho
<p>I'm getting an error trying to sign a transaction with bitcore-wallet-client. </p>

<p>I create the transaction, publish it and when I try to sign it, I'm getting the error: "SERVER_COMPROMISED - Server response could not be verified"</p>

<p>bws server: <a href="https://bws.bitpay.com/bws/api" rel="nofollow noreferrer">https://bws.bitpay.com/bws/api</a></p>

<p>can anyone point me in the right direction?</p>

<p>ps: using wallet-client (CLI) I can sign the same transaction (created and published from bitcore-wallet-client)</p>

<p>edit: I'm using a testnet account</p>

CC BY-SA 4.0
2018-07-13T15:43:24.637Z
Is it the bitcoin core wallet (as in headline) where you have problem, or the API of Bitpay? Maybe adopt the headline?
pebwindkraft
CC BY-SA 4.0
2018-07-13T15:52:20.417Z
so far could track the problem to the bitcore-wallet-client/lib/verifier.js (line 159) where my transaction doesn't have a proposalSignature. To fully answer your question, I'm pretty sure the problem as nothing to do with the API of Bitpay.
pmcoelho
<client><bitcore><bitpay>
Bitcore-wallet-client "Server response could not be verified"
pmcoelho
# Bitcore-wallet-client "Server response could not be verified"

(Asked by: username_0 on 2018-07-13)

I'm getting an error trying to sign a transaction with bitcore-wallet-client.

I create the transaction, publish it and when I try to sign it, I'm getting the error: "SERVER\_COMPROMISED - Server response could not be verified"

bws server: <https://bws.bitpay.com/bws/api>

can anyone point me in the right direction?

ps: using wallet-client (CLI) I can sign the same transaction (created and published from bitcore-wallet-client)

edit: I'm using a testnet account

**Tags:** client, bitcore, bitpay

> **Comments:**
> **username_1**: Is it the bitcoin core wallet (as in headline) where you have problem, or the API of Bitpay? Maybe adopt the headline?  
> **username_0**: so far could track the problem to the bitcore-wallet-client/lib/verifier.js (line 159) where my transaction doesn't have a proposalSignature. To fully answer your question, I'm pretty sure the problem as nothing to do with the API of Bitpay.  

---

## 1 answers

### Answer by username_0 on 2018-07-13. Score: 1

The problem was that I was creating the transaction proposal and publishing it, after that I used the result from createTxProposal and passed it to signTxProposal.

turns out that the txProposal returned from createTxProposal doesn't have the property proposalSignature (which is filled when the transaction is published).

so, to solve this I had to get the transaction proposals (after publishing) and send the transaction fetched as argument to signTxProposal.


---

