Is there any coinmarketcap indicator live at the moment or will this be active in a later stage of the project? 
https://api.coinmarketcap.com/v1/ticker/datacoin/
Topic: [ANN] Datacoin - Censorship-Free Data Storage - page 33. (Read 66794 times)
https://api.coinmarketcap.com/v1/ticker/datacoin/
Hello, i got the datacoin-qt wallet, but my wallet is not syncing..
and i have added the nodes. what is wrong?
download bootstrap from hereand i have added the nodes. what is wrong?
https://github.com/datacoinproject/datacoin/releases
it will speed up syncing
Hello, i got the datacoin-qt wallet, but my wallet is not syncing..
and i have added the nodes. what is wrong?
and i have added the nodes. what is wrong?
Is there any coinmarketcap indicator live at the moment or will this be active in a later stage of the project?
Reason is quite simple: on nearly every coin I do solo mining in config file is always been set to 6666.
So I guess that people are inert, so they just say: if it work on this it will work on second coin also.
May be we need to change default pool port to another?
I was active in mining before at last two years. Coin I mined in past are gone forever now. But , at least , by default,DTC wallet, your wallet is also set to 6666. Regardless fact I start it with C:\Users\Alpha-I7\Desktop\dtc_win_bin_0.15.99.08\datacoin-qt.exe datacoin-qt-frontport=8888 ( switch you recomended) miner start with port 6666 and if I was asked, no we need to change anything: it works perfectly. Few people ( from total number ) are mining solo: and even few of those small group have need to open two wallet in localhost: so in that case port will be problem: but they know how to fix it.
By the way: your wallet was working perfectly, in localhost was mining with 24 GPU, on three rigs, connected with WIFI . Great job!
Reason is quite simple: on nearly every coin I do solo mining in config file is always been set to 6666.
So I guess that people are inert, so they just say: if it work on this it will work on second coin also.
May be we need to change default pool port to another?
Because we forget that this wallet have embedded mining pool.
And config file have port 6666....you see confusion
It is very little probability to set exactly rpcport=6666, not 6665, not 6667, not 12345, not any other number. Why 6666?And config file have port 6666....you see confusion
Is there any reason why people set it exactly 6666? It is very interesting.
Why, mister Anderson?
Reason is quite simple: on nearly every coin I do solo mining in config file is always been set to 6666.
So I guess that people are inert, so they just say: if it work on this it will work on second coin also.
Because we forget that this wallet have embedded mining pool.
And config file have port 6666....you see confusion
It is very little probability to set exactly rpcport=6666, not 6665, not 6667, not 12345, not any other number. Why 6666?And config file have port 6666....you see confusion
Is there any reason why people set it exactly 6666? It is very interesting.
Why, mister Anderson?
Because we forget that this wallet have embedded mining pool.
And config file have port 6666....you see confusion
And config file have port 6666....you see confusion
Because they can.
I often spin up another instance of a coin, copying the datdadir and running the second client on a different port alongside the first.
Cheers
Graham
Coincidence?
Guys
Thanks for all the replies, and PM's.
Waiting for wallet to sync, then will try your siggestions, another 4-6 hours yet.
One mistake i did make was i thought i had launched new wallet, and did old one by mistake....that does force a full resync each time you do that....
Def resyncing to "dtc_win_bin_0.15.99.08" now thou.
J
Thanks for all the replies, and PM's.
Waiting for wallet to sync, then will try your siggestions, another 4-6 hours yet.
One mistake i did make was i thought i had launched new wallet, and did old one by mistake....that does force a full resync each time you do that....
Def resyncing to "dtc_win_bin_0.15.99.08" now thou.
J
I need to know why such users have set up rpcport=6666
Because they can.
I often spin up another instance of a coin, copying the datdadir and running the second client on a different port alongside the first.
Cheers
Graham
Btw. if anyone interested syncing on newest version take 4-4.5H there about on fast PC. Nonetheless great improvrmrnt from 24-36H.
hmmm... i will watch this one. although i didnt get the primecoin fork i think it is worth invest
It seems the problem in rpcport=6666.Why do you set it?
There was another user with similar problem.
I need to know why such users have set up rpcport=6666
Hi Guys,
Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Do you have datacoin.conf file in your datacoin data dir?Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Yes
rpcuser=user
rpcpassword=password
server=1
daemon=1
listen=1
rpcallowip=127.0.0.1
rpcport=6666
You can remove all those lines from conf file and you just add nodes there.
Also , check does modem block port 6666
Miner start with this
Quote
# SOLO MINING
server = "127.0.0.1";
port= "6666";
address = "DQD7F............................";
name = "Intel I7- ALPHA-AMD";
server = "127.0.0.1";
port= "6666";
address = "DQD7F............................";
name = "Intel I7- ALPHA-AMD";
I'll check as soon as a i can.
Each time wallet crashes, it now re-indexes....It never used to have to do that, takes about 1-2 hours each tme
Might be best to go back to the old wallet
J
Hi Guys,
Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Do you have datacoin.conf file in your datacoin data dir?Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Yes
rpcuser=user
rpcpassword=password
server=1
daemon=1
listen=1
rpcallowip=127.0.0.1
rpcport=6666
You can remove all those lines from conf file and you just add nodes there.
Also , check does modem block port 6666
Miner start with this
Quote
# SOLO MINING
server = "127.0.0.1";
port= "6666";
address = "DQD7F............................";
name = "Intel I7- ALPHA-AMD";
server = "127.0.0.1";
port= "6666";
address = "DQD7F............................";
name = "Intel I7- ALPHA-AMD";
Yes
rpcuser=user
rpcpassword=password
server=1
daemon=1
listen=1
rpcallowip=127.0.0.1
rpcport=6666
Why do you set rpcport=6666 ?
Hi Guys,
Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Do you have datacoin.conf file in your datacoin data dir?Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Yes
rpcuser=user
rpcpassword=password
server=1
daemon=1
listen=1
rpcallowip=127.0.0.1
rpcport=6666
Hi Guys,
Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Do you have datacoin.conf file in your datacoin data dir? Just tried solo mining to new wallet "dtc_win_bin_0.15.99.08"
but as soon as i open console and tpe "setgenerate true" i get this crash
https://ibb.co/eGZjty
J
Jump to: