We are working...
I am having trouble connecting to the network. Do you have any stable (seed) nodes? |
|
|
|
I was asked to help a human problem:
does not open the wallet file, I reset the wallet, rename wallet file - does not help. With backup restored, it did not help.
What can help, what is the problem?
Sometimes the .wallet file corrupts, if you exit the not property (or some other reason). In such case there is .tmp.23513 or some sort of tmp file created. Use the .tmp file Since corrupted .wallet is pretty common issue I get on democats, I advice everyone to use the 'export_keys' command from simplewallet in the latest Forknote release for backup. You will have your keys and you will not rely on a .wallet file |
|
|
|
|
xci.cryptonotepool.com is on a fork
|
|
|
|
|
Hi guys,
Please don't put more than 50% on one pool (Democats in this case). Spread the hashrate, keep the network healthy.
|
|
|
|
hi something not right with democats pool i did not get payment between 2017-01-31 11:33:51 (7 hours ago) 2017-01-31 03:18:44 (15 hours ago) i only get 91 xci i m supposed to get more than 500  Sorry, the daemon got stuck for still unknown reason |
|
|
|
Probably MINER need a --config-file parameter, but didn't take it  Sorry if I offended you. It's kind of impossible to understand user's level from 1-2 posts. You don't need --config-file for 'miner'. A possible explanation for the 'Levin signature mismatch' WARNING is you are trying to mine on the P2P port, instead of the RPC port Here is the actual setup I use to mine a few test blocks on BitCoal (I use it as testnet usually, because it has small blockchain, stable hashrate and the hashrate is low). It's on macOS, FN v2.0.1: Terminal 1: ./forknoted --config-file configs/bitcoal.conf Terminal 2: ./miner --daemon-address localhost:7701 --address CiSgoXqH8s1MbgW5uH84hNNmkBNnu2ZaPRSvjE1o4yBcedrv7LPmgg2HL3vvjAQKoPCNiL4MCAFnKc3rvxnGzfYpRc8A3AK If you share your actual setup + commands it will be easier to replicate and debug |
|
|
|
 I tried. Miner stopped immediately with log - 2017-Jan-30 15:54:17.442694 DEBUG [MinerManager] starting 2017-Jan-30 15:54:17.442694 INFO [MinerManager] requesting mining parameters 2017-Jan-30 15:54:17.473894 WARNING [MinerManager] Couldn't get block template:The stream is ended Fatal: The stream is ended And got errors in daemon - 2017-Jan-30 15:53:41.983532 WARNING [10.10.77.77:62587 INC] Exception in connectionHandler: Levin signature mismatch 2017-Jan-30 15:54:17.458293 WARNING [10.10.77.77:62595 INC] Exception in connectionHandler: Levin signature mismatch Hey 'miner' has some required parameters - 'address' and 'daemon-address' Here is an example how to use it for Dashcoin at if you run daemon at localhost: ./miner --daemon-address localhost:29081 --address D8yFneNkLn617zawXhdruwVQf8GWVdtgz4K3UnjqVXWH34hB4VMFU4U7QYzqvXbQUNDpSc4NmdHmT1Rc78wmPwV7VU2VNyF For more details you can see the help: On the daemon question - "Levin signature mismatch" just means someone with wrong network_id is connected to the network. Nothing to worry about |
|
|
|
Hello slb! Could you tell me please, is it possible to solo mine in last Forknote release? I tried both forknote and bcn and failed Any suggestions? Yes. The miner is not in the daemon anymore. You need to use 'miner' included in the binaries. |
|
|
|
Update. Forknote syncs to the current height. From scratch it took less than 20 minutes. BTW, after the fork height it synchronizes slower. \
On this - the v2 daemon does not perform any validation for blocks below the last checkpoint. This makes syncing very, very fast. To speed it up more you can add more recent checkpoints |
|
|
|
Looks like Democats stuck at 72903. Due to Bytecoin v2.0.1 code vs v1.0.11?
Daemon got stuck for some reason. So far I got Bytecoin v2.0.1 code running on 2 networks and none of it forked. |
|
|
|
|
Just in case people do not realize what is going on - there was a 48 hour window, in which people could double-spend their coins.
|
|
|
|
Looks like Democats should reduce max difficulty for users, this could help to find block more often.
Point taken, the max difficulty is now 50000. Is it ok, or it needs to be lower? |
|
|
|
From where I can get blockchain so I can sync my wallet faster? My wallet is open almost a week and only 500000 blocks downloaded  Use bytecoin 2.0.1 or forknote v2.0.1 (it contains some bug fixes over bytecoin 2.0.1). It syncs in less than 1-2 hours from 0. I am not sure how the things are with the GUI |
|
|
|
...
"amount" is in atomic units |
|
|
|
|
Just to add, you can import your paper wallets into Forknote v2, if you saved your spend and view keys. Importing the mnemonic seed is not supported yet
|
|
|
|
I do use that one. I had it running before. I've tried on 2 computers with the all the revisions that are in the thread here and I get the no seeds no peers message and in the sync process it gives that error that I pasted above about the failed check and it won't get past that. Ok, you need to add those lines if you want to use this client (not tested but it should work): CHECKPOINT=55000:84190dfb00457f90be17eb9d9f35ae509423d10c9efaa3e9fdc3c12062cb2c2a
CHECKPOINT=80000:07fe04d5857ff710b12bb192b58375bab08b713dce995e9bee8d450738cf053c Alternatively, you can update to the latest version of forknote: https://github.com/forknote/forknote/releases/tag/2.0.1I am using the v2.0.1 version and it is all workinf fine there |
|
|
|
This is a required update?
And if I use daemon forknote and simplewallet from the original, so it is possible, reset should be done?
The update is not required, but it's comparable to the LMDB update of Monero (if you are familiar with it). You will get much mess ram usage and a lot faster network sync. It can sync to the Bytecoin network from 0 for less than 3 hours, and most of the smaller networks take just a few minutes to sync |
|
|
|
|
Show Posts
