search

dashpay / electrum-dash-old

Electrum-DASH - a Dash thin client
https://electrum-dash.org
MIT License
37 stars 113 forks source link

Activating the masternode with trezor: Error response: code 32601 #30

Closed splawik21 closed 7 years ago

splawik21 commented 8 years ago

On build e744161 while activating the masternode via trezor getting the error as below.

electrum5

schinzelh commented 8 years ago

Is there a message in the console too?

splawik21 commented 8 years ago

No, the console is fine, no messagges at all.

splawik21 commented 8 years ago

Is this issue be based on the trezor firmware which yet was not out?

thelazier commented 8 years ago

The issue would be solved if the electrum server connect to dashd v0.12.1.x running on mainnet.

Kefkius commented 8 years ago

As @thelazier said, the message means that the problem is with the server, not the client. Earlier versions of dashd don't have the masternodebroadcast RPC.

I think the best option is to increment electrum-dash-server's version and require servers of at least that version in Electrum-DASH.

schinzelh commented 8 years ago

@Kefkius good idea, the client needs to have a way to identify servers which are capable of doing masternodebroadcast.

Dash Core client is using "service bits" in the handshake to inform the network of its capabilities, would this be a solution for Electrum-Dash server as well? Or do we want to rely on good acting server admins to

a) increase version b) install dashd 0.12.1

Kefkius commented 8 years ago

Whatever we do, we'll have to rely on server admins to act honestly. The server's version is requested by the client and any response can be given.

I intend to take this version-based approach to interacting with a server from the client.

schinzelh commented 8 years ago

You are right, Electrum server admins are to be trusted anyway. So version string may be sufficient.

splawik21 commented 8 years ago

Connecting to electrum.dash.siampm.com and activating the node does now cause the issue anymore.