[ANN] Datacoin - Censorship-Free Data Storage

[Verionum]

Yes
rpcuser=user
rpcpassword=password
server=1
daemon=1
listen=1
rpcallowip=127.0.0.1
rpcport=6666

Why do you set rpcport=6666 ?

[pepi]

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?

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

# SOLO MINING
server = "127.0.0.1";
port= "6666";
address = "DQD7F............................";
name = "Intel I7- ALPHA-AMD";

[minerja]

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?

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

# SOLO MINING
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

[Verionum]

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

[muf18]

Btw. if anyone interested syncing on newest version take 4-4.5H there about on fast PC. Nonetheless great improvrmrnt from 24-36H.

[gjhiggins]

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

[minerja]

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

[Verionum]

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

But why do they all use exactly 6666 port for rpc service. Why do they try to use exactly the same port as embedded mining pool port?
Coincidence?

[benxy031]

Because we forget that this wallet have embedded mining pool.
And config file have port 6666....you see confusion 

[Verionum]

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?
Is there any reason why people set it exactly 6666? It is very interesting.

Why, mister Anderson?

[pepi]

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?
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.

[Verionum]

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.

Is there any instruction for other coin to set rpcport=6666, the instruction you have followed?

May be we need to change default pool port to another?

[pepi]

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.

Is there any instruction for other coin to set rpcport=6666, the instruction you have followed?

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!  

[asdkhz99988]

 Is there any coinmarketcap indicator live at the moment or will this be active in a later stage of the project? 

[kieuthikhanhlinh72]

Hello, i got the datacoin-qt wallet, but my wallet is not syncing..
and i have added the nodes. what is wrong?

[pepi]

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 here
https://github.com/datacoinproject/datacoin/releases
it will speed up syncing

[muf18]

Make sure to mail this guy

https://www.coinopsy.com/dead-coins/datacoin/

[hamburger]

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/

[abrgeza]

I made a transaction and it seems to be stuck at "Status: 0/unconfirmed, in memory pool".

Status: 0/unconfirmed, in memory pool
Date: 17.5.2018. 19:40
To: DQrj37vGkkRt8h1GcxZKvEFanCCUHm6R4p
Debit: -10 400.00000000 DTC
Transaction fee: -5.85000000 DTC
Net amount: -10 405.85000000 DTC
Transaction ID: cc79ed995d89378d5c0a5634e41cbb6d9aa9a046fd6445ee80867706f689dd00
Transaction total size: 115980 bytes
Output index: 1

How to get coins back?

[Verionum]

I made a transaction and it seems to be stuck at "Status: 0/unconfirmed, in memory pool".

Status: 0/unconfirmed, in memory pool
Date: 17.5.2018. 19:40
To: DQrj37vGkkRt8h1GcxZKvEFanCCUHm6R4p
Debit: -10 400.00000000 DTC
Transaction fee: -5.85000000 DTC
Net amount: -10 405.85000000 DTC
Transaction ID: cc79ed995d89378d5c0a5634e41cbb6d9aa9a046fd6445ee80867706f689dd00
Transaction total size: 115980 bytes
Output index: 1

How to get coins back?

It seems the problem in Transaction total size: 115980 bytes.
The old wallets can't receive such big transactions into memory pool (but can receive it in blockchain).

It is a big problem of old wallets because of it prevents to accept transactions with 100kb data.

I have resolved it in 0.15.99.8 wallet, but problem will remain until most of network migrate to new wallet.

To avoid such problems with current network make transactions about 70 kb. (it is about 3-4 dtc of fee per once)

Try the followings.
1. Right click on the transaction in the list of transactions, then abandon it. Restart app.

If it doesn't help .
2. Backup wallet.dat. Start dtc with rescan wallet flags. f.e: "datacoin-qt -rescan -zapwallettxes=1"

P.S. And don't worry. Your coins is still yours.