Is it possible to make the address shorter wallet?
You could make it shorter by compressing it.
I don't believe it will function the same as the original uncompressed address though, at least from my understanding of how the code is written.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 481. (Read 4671924 times)
October 19, 2016, 03:49:06 AM
You could make it shorter by compressing it.
I don't believe it will function the same as the original uncompressed address though, at least from my understanding of how the code is written.
October 19, 2016, 02:34:01 AM
Is it possible to make the address shorter wallet?
October 18, 2016, 10:42:48 PM
wtf. I tried to delete my bitmonero folder again under program data/bitmonero and I still get this shit on resync. Wth? Anyone?
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
I think it's a joke.
October 18, 2016, 09:49:14 PM
wtf. I tried to delete my bitmonero folder again under program data/bitmonero and I still get this shit on resync. Wth? Anyone?
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
This is ok to ignore. This happens when you restart the blockchain download from scratch.
October 18, 2016, 08:56:24 PM
wtf. I tried to delete my bitmonero folder again under program data/bitmonero and I still get this shit on resync. Wth? Anyone?
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
SYNCHRONIZATION started
2016-Oct-18 21:50:32.379171 [P2P6]ERROR C:/msys64/DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:1835 Ours and foreign blockchain have only genesis block in common... o.O
October 18, 2016, 05:56:04 PM
No problem, needing some help myself.
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
The wallet bin has a new name now, that I don't recall off the top of my head...
Perhaps you are just running the old wallet version as you didn't notice the new bin?
Nope, monerod.exe and monero-wallet-cli.exe - All have worked fine until my db got corrupted (a few pages back), so now it's rebuilt but all weird... Here is a snip of the cli-log.
Code:
2016-Oct-18 08:23:12.450689 Monero 'Wolfram Warptangent' (v0.10.0.0-release)
2016-Oct-18 08:23:12.451689 Setting log level = 0
2016-Oct-18 08:23:12.451689 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 08:23:12.451689 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 08:23:23.916830 Loaded wallet keys file, with public address: xxxxx
2016-Oct-18 08:24:05.419731 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:24:05.420227 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 08:24:05.420227 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:24:16.546972 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 08:24:21.548851 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:26.550738 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:31.552727 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:36.554348 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:41.555177 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2699 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:24:41.555177 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2699:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = transfer_selected
2016-Oct-18 08:24:41.555177 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:43:23.510222 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:43:23.510222 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 08:43:23.510222 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:43:33.360222 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 12:28:49.526292 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 12:28:49.526292 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 12:28:49.526292 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 12:29:18.970371 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:34:35.771140 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:34:35.771140 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:34:35.771140 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:36:02.371021 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:48:51.728197 Monero 'Wolfram Warptangent' (v0.10.0.0-release)
2016-Oct-18 17:48:51.729200 Setting log level = 0
2016-Oct-18 17:48:51.729200 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:48:51.729200 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:48:55.633296 Loaded wallet keys file, with public address: xxxx
2016-Oct-18 17:52:58.268476 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:52:58.268476 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:52:58.268476 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:52:58.269477 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:53:38.827222 Error: No unmixable outputs found
2016-Oct-18 17:54:18.836410 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:54:18.836410 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:54:18.836410 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:54:32.131238 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:56:26.548052 Error: failed to get blockchain height: possibly lost connection to daemon
2016-Oct-18 17:56:47.297902 Got control signal 2. Exiting without saving...
2016-Oct-18 17:58:56.701768 Monero 'Wolfram Warptangent' (v0.10.0.0-release)
2016-Oct-18 17:58:56.701768 Setting log level = 0
2016-Oct-18 17:58:56.701768 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:58:56.701768 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:59:00.350745 Loaded wallet keys file, with public address: xxxxxxx
2016-Oct-18 17:59:38.398032 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:59:38.398032 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:59:38.398032 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 18:00:35.278940 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 18:07:30.445775 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 18:07:30.445775 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 18:07:30.445775 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 18:07:38.333668 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 18:07:38.333668 Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
2016-Oct-18 08:23:12.451689 Setting log level = 0
2016-Oct-18 08:23:12.451689 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 08:23:12.451689 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 08:23:23.916830 Loaded wallet keys file, with public address: xxxxx
2016-Oct-18 08:24:05.419731 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:24:05.420227 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 08:24:05.420227 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:24:16.546972 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 08:24:21.548851 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:26.550738 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:31.552727 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:36.554348 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:3787 Failed to connect to daemon
2016-Oct-18 08:24:41.555177 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2699 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:24:41.555177 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2699:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = transfer_selected
2016-Oct-18 08:24:41.555177 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:43:23.510222 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 08:43:23.510222 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 08:43:23.510222 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 08:43:33.360222 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 12:28:49.526292 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 12:28:49.526292 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 12:28:49.526292 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 12:29:18.970371 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:34:35.771140 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:34:35.771140 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:34:35.771140 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:36:02.371021 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:48:51.728197 Monero 'Wolfram Warptangent' (v0.10.0.0-release)
2016-Oct-18 17:48:51.729200 Setting log level = 0
2016-Oct-18 17:48:51.729200 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:48:51.729200 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:48:55.633296 Loaded wallet keys file, with public address: xxxx
2016-Oct-18 17:52:58.268476 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:52:58.268476 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:52:58.268476 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:52:58.269477 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:53:38.827222 Error: No unmixable outputs found
2016-Oct-18 17:54:18.836410 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:54:18.836410 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:54:18.836410 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 17:54:32.131238 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 17:56:26.548052 Error: failed to get blockchain height: possibly lost connection to daemon
2016-Oct-18 17:56:47.297902 Got control signal 2. Exiting without saving...
2016-Oct-18 17:58:56.701768 Monero 'Wolfram Warptangent' (v0.10.0.0-release)
2016-Oct-18 17:58:56.701768 Setting log level = 0
2016-Oct-18 17:58:56.701768 default_log: C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:58:56.701768 Logging at log level 0 to C:\Users\me\Desktop\monero.win.x64.v0-10-0-0\monero-wallet-cli.log
2016-Oct-18 17:59:00.350745 Loaded wallet keys file, with public address: xxxxxxx
2016-Oct-18 17:59:38.398032 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 17:59:38.398032 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 17:59:38.398032 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 18:00:35.278940 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 18:07:30.445775 ERROR C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791 !r. THROW EXCEPTION: error::no_connection_to_daemon
2016-Oct-18 18:07:30.445775 C:/msys64/DISTRIBUTION-BUILD/src/wallet/wallet2.cpp:2791:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_outs.bin
2016-Oct-18 18:07:30.445775 Error: no connection to daemon. Please make sure daemon is running.
2016-Oct-18 18:07:38.333668 ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/http_client.h:321 HTTP_CLIENT: Failed to SEND
2016-Oct-18 18:07:38.333668 Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
so weird.... all I did was resync the blockchain. is my wallet corrupted maybe?
Edit - Ok, this is messed up. No wallets work anymore, so how do I completely wipe my blockchain data out everywhere on windows, something is just not right here at all, and I don't want to lose my wallets even if I only have a few xmr in them.
Thanks again
October 18, 2016, 05:27:50 PM
https://medium.com/@dcorbacho/zcash-vs-monero-zec-in-bitmex-fe1cd4f5f81c#.xqc4khr1i
Quote
Zcash vs Monero. ZEC in BITMEX
Note: BITMEX is a trading platform that offers ZEC
It’s like Betamax vs VHS, Coke vs Pepsi, Ring Signatures vs zk-SNARKs; the choice for a winner in the battle for online cryptocurrency privacy is not so clear cut. We see two main contenders: Zcash and Monero.
Note: BITMEX is a trading platform that offers ZEC
It’s like Betamax vs VHS, Coke vs Pepsi, Ring Signatures vs zk-SNARKs; the choice for a winner in the battle for online cryptocurrency privacy is not so clear cut. We see two main contenders: Zcash and Monero.
October 18, 2016, 05:23:32 PM
No problem, needing some help myself.
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
The wallet bin has a new name now, that I don't recall off the top of my head...
Perhaps you are just running the old wallet version as you didn't notice the new bin?
October 18, 2016, 05:13:34 PM
No problem, needing some help myself.
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
I recently deleted my blockchain data in \users\me\programdata\bitmonero and resynced from scratch.
In addition to the problem I noted above, when I run status in the wallet CLI with the daemon listening on 18080/18081 like normal, it says:
Error: Daemon uses a different RPC version that the wallet: http://localhost:18081. Either update one of them, or use --allow-mismatched-daemon-version.
Refreshed 1157700/?, no daemon connected
Any ideas? Tried that option but didn't seem to fix transfer anyhow, Will try and run status and see what it changed.
Netstat -an output:
TCP 0.0.0.0:18080 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 0.0.0.0:0 LISTENING
TCP 127.0.0.1:18081 127.0.0.1:61186 ESTABLISHED
Thanks!
October 18, 2016, 02:26:08 PM
How do I send my coins from cli wallet to exchange? Do I need to send it with this command:
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
To transfer with mixin of 5:
transfer 5 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
No -p is required and you can also leave mixin count off to use default, ie. transfer
Thanks
October 18, 2016, 11:31:24 AM
How do I send my coins from cli wallet to exchange? Do I need to send it with this command:
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
To transfer with mixin of 5:
transfer 5 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
No -p is required and you can also leave mixin count off to use default, ie. transfer
Thanks
October 18, 2016, 11:17:08 AM
How do I send my coins from cli wallet to exchange? Do I need to send it with this command:
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
transfer 2 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB 10.8 -p 8f343aeb16003be08ac1e35e727f47284343b9aaf721642788067cbc07ab52e6
October 18, 2016, 07:27:24 AM
Well, now I have this problem when I try and make a transfer in wallet-cli:
Error: no connection to daemon. Please make sure daemon is running.
then in the daemon window, this error comes up:
2016-Oct-18 08:24:05.419224 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/abstract_tcp_server2.inl:355 Exception at [connection::handle_read], what=Attempting to get output pubkey by index, but key does not exist
Any ideas? I mine to this address, do I have to sweep_dust or whatever it is? Thanks again
Error: no connection to daemon. Please make sure daemon is running.
then in the daemon window, this error comes up:
2016-Oct-18 08:24:05.419224 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/contrib/epee/include/net/abstract_tcp_server2.inl:355 Exception at [connection
Any ideas? I mine to this address, do I have to sweep_dust or whatever it is? Thanks again
October 17, 2016, 06:19:23 PM
Can someone post me a link to the windows GUI build instructions again? I know someone posted it in the past few days, but Ilya's github Readme.md is still missing the Windows instructions/dependencies.
Thanks, I tried trawling back pages, but between this and the speculation thread, I can't find it!
Thanks, I tried trawling back pages, but between this and the speculation thread, I can't find it!
Also posting in this thread for visibility:
https://github.com/mbg033/monero-core/tree/build-docs-win#on-windows
TYVM!
October 17, 2016, 05:28:42 PM
Can someone post me a link to the windows GUI build instructions again? I know someone posted it in the past few days, but Ilya's github Readme.md is still missing the Windows instructions/dependencies.
Thanks, I tried trawling back pages, but between this and the speculation thread, I can't find it!
Thanks, I tried trawling back pages, but between this and the speculation thread, I can't find it!
Also posting in this thread for visibility:
https://github.com/mbg033/monero-core/tree/build-docs-win#on-windows
October 17, 2016, 07:54:29 AM
Judging from what has been said at the Shanghai conference, it should be assumed that ZCash and Ethereum plan to join forces in some way, so that the two technologies can be used as part of an integrated super-system.
Would it be a good idea if Monero forged alliances with Ethereum Classic to do the same thing? It's obvious to me that ETC is the superior blockchain due to it's political base, as opposed to the rather scammy corporate hype-machine base of ETH/ZCASH.
Another suggestion would be LISK partnering with AEON.
It seems to me that this is the direction we are headed, and it might be a good idea to think of things in this way as a form of expansionist strategy.
Would it be a good idea if Monero forged alliances with Ethereum Classic to do the same thing? It's obvious to me that ETC is the superior blockchain due to it's political base, as opposed to the rather scammy corporate hype-machine base of ETH/ZCASH.
Another suggestion would be LISK partnering with AEON.
It seems to me that this is the direction we are headed, and it might be a good idea to think of things in this way as a form of expansionist strategy.
I like the idea of Monero and Ripple joining forces. Monero brings the much needed privacy and security that Ripple needs for their financial/business transactions .
October 17, 2016, 04:53:45 AM
Monero has been added to crypto-games.net!
Crypto-Games.net is a gambling site offering Dice, Slot, BlackJack and Roulette
with low house edges, a faucet, a friendly community and more.
For further information visit their official thread
or head over to the site now and explore it yourself.
Crypto-Games.net is a gambling site offering Dice, Slot, BlackJack and Roulette
with low house edges, a faucet, a friendly community and more.
For further information visit their official thread
or head over to the site now and explore it yourself.
October 16, 2016, 06:02:55 PM
Help wanted. I'm going to sync my daemon today and it just crashes/fails with this error. Any ideas or am I looking at a full resync?
Thanks
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
Thanks
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
This partiicular error is spurious and current git master has been patched to ignore it. No idea if anything else is wrong with your DB.
Thanks. Couldn't get rid of it, so I just deleted my db and am re syncing from scratch. Thanks for the help, not a big deal, also super thanks for making this part SOOO much faster and halving the db size, it is VERY MUCH appreciated.
October 16, 2016, 05:56:40 PM
Help wanted. I'm going to sync my daemon today and it just crashes/fails with this error. Any ideas or am I looking at a full resync?
Thanks
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
Thanks
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
This partiicular error is spurious and current git master has been patched to ignore it. No idea if anything else is wrong with your DB.
October 16, 2016, 05:16:44 PM
Help wanted. I'm going to sync my daemon today and it just crashes/fails with this error. Any ideas or am I looking at a full resync?
Thanks
2016-Oct-16 18:14:31.797585 Net service bound to 0.0.0.0:18080
2016-Oct-16 18:14:31.798585 Attempting to add IGD port mapping.
2016-Oct-16 18:14:32.883117 Added IGD port mapping.
2016-Oct-16 18:14:32.885119 P2p server initialized OK
2016-Oct-16 18:14:32.888122 Initializing core rpc server...
2016-Oct-16 18:14:32.890125 Binding on 127.0.0.1:18081
2016-Oct-16 18:14:32.892797 Core rpc server initialized OK on port: 18081
2016-Oct-16 18:14:32.894828 Initializing core...
2016-Oct-16 18:14:32.901347 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...
2016-Oct-16 18:14:32.905352 option: fast
2016-Oct-16 18:14:32.907353 option: async
2016-Oct-16 18:14:32.909355 option: 1000
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.932286 Deinitializing rpc server...
2016-Oct-16 18:14:32.936960 Deinitializing p2p...
2016-Oct-16 18:14:32.971537 Deinitializing core...
2016-Oct-16 18:14:32.977048 Closing IO Service.
2016-Oct-16 18:14:32.978049 Failed to deinitialize core...
2016-Oct-16 18:14:32.980051 Deinitializing cryptonote_protocol...
C:\Users\me\Desktop\monero>
Edit. I have had my system lock up a few times the past day or so since updating Nvidia drivers. Perhaps it's corrupted?
Should post a new post about this, but can I use an existing wallet to generate Payment Id's from? Or must it be a new one? This is why I was syncing my daemon, to try and figure this out.
Thanks
2016-Oct-16 18:14:31.797585 Net service bound to 0.0.0.0:18080
2016-Oct-16 18:14:31.798585 Attempting to add IGD port mapping.
2016-Oct-16 18:14:32.883117 Added IGD port mapping.
2016-Oct-16 18:14:32.885119 P2p server initialized OK
2016-Oct-16 18:14:32.888122 Initializing core rpc server...
2016-Oct-16 18:14:32.890125 Binding on 127.0.0.1:18081
2016-Oct-16 18:14:32.892797 Core rpc server initialized OK on port: 18081
2016-Oct-16 18:14:32.894828 Initializing core...
2016-Oct-16 18:14:32.901347 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...
2016-Oct-16 18:14:32.905352 option: fast
2016-Oct-16 18:14:32.907353 option: async
2016-Oct-16 18:14:32.909355 option: 1000
2016-Oct-16 18:14:32.923777 Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.927780 Error opening database: Failed to drop m_hf_starting_heights: MDB_NOTFOUND: No matching key/data pair found
2016-Oct-16 18:14:32.932286 Deinitializing rpc server...
2016-Oct-16 18:14:32.936960 Deinitializing p2p...
2016-Oct-16 18:14:32.971537 Deinitializing core...
2016-Oct-16 18:14:32.977048 Closing IO Service.
2016-Oct-16 18:14:32.978049 Failed to deinitialize core...
2016-Oct-16 18:14:32.980051 Deinitializing cryptonote_protocol...
C:\Users\me\Desktop\monero>
Edit. I have had my system lock up a few times the past day or so since updating Nvidia drivers. Perhaps it's corrupted?
Should post a new post about this, but can I use an existing wallet to generate Payment Id's from? Or must it be a new one? This is why I was syncing my daemon, to try and figure this out.
Jump to: