[ANN] Datacoin - Censorship-Free Data Storage

[dzkrb]

Honestly, at the beginning I did not quite believe in this project. But, having watched, I saw activity both here and in social networks, which means that investors' interest is growing.

[DataSea]

I'd like to do a etching stress test, however, the last time I did one on mainnet, I quite possibly took out many peoples wallets in the process...
Thus, has anyone looked at getting the Datacoin Testnet operational for this build? I get "Unable to start HTTP server. See debug log for details." and it crashes.

Please give detailed instructions to reproduce error. I have started testnet (datacoin-qt -debug -testnet) successfuly.

Ope!
User error.
Testnet loaded, then synced with common swarm -- running additional tests now.

[DataSea]

Updated binaries and sources.

Source code DTC 0.15.99-05: https://yadi.sk/d/ghrCHoxA3Un8Cm
Windows binaries 0.15.99-05: https://yadi.sk/d/auGBz2cO3Un8CD

Added code for convenient synchronization with other 0.15-0.16 clients.
Some other internal improvements.

IMPORTANT: Backup your wallet before using it.

I'd like to test these -- is anyone else having trouble downloading them?

[muf18]

Updated binaries and sources.

Source code DTC 0.15.99-05: https://yadi.sk/d/ghrCHoxA3Un8Cm
Windows binaries 0.15.99-05: https://yadi.sk/d/auGBz2cO3Un8CD

Added code for convenient synchronization with other 0.15-0.16 clients.
Some other internal improvements.

IMPORTANT: Backup your wallet before using it.

This wallet don't work with old blockchain.
New synchronization is required.
Blocks have to be rebuilded.

[Verionum]

This wallet don't work with old blockchain.
New synchronization is required.
Blocks have to be rebuilded.

Sorry for inconvenience (and for my English :) ).

Of course blockchain the same. But index needs to be rebuilt. In this case it provokes resyncing. It happens once and no need additional resyncing in future.

0.15-0.16 versions of BitcoinCore (and Datacoin) client have another synchronization logic then old (0.8) clients.

For effective using this logic we need to send more data with HEADERS network messages (bnPrimeChainMultiplier fields).
Unfortunately old datacoin clients omit such data (fill it with zero).

In new version of my client I have updated this datacoin client logic. Now, instead of sending zero as bnPrimeChainMultiplier, it sends real bnPrimeChainMultiplier fields. But it requires to rebuilt index.

This change is backwards compatible.

Old clients without problem must receive this updated HEADERS messages. They just ignore  bnPrimeChainMultiplier fields.

[ZenoDiac]

"setgenerate true" for solo mining was removed in 0.13  - but it might still be useful for Datacoin.  Is there a way to bring it back?

-extro

Yes, this is possible. But a little later.

Which version of miner do your prefer.
There are options:
- embedded CPU miner.
- embedded server for external GPU miner (xpmclient).

Oh please include the embedded server for external GPU miner. This is going to be very useful to keep the network healthy and attract more miners.
I'm burning to make a GPU mining video.
I'm just waiting for this functionality to be implemented in a future version, because this currently only works (as far as I know) on v0.1.2 gunk beta, which about 11% people are using.
(Kind of redundant having a new wallet plus an old wallet just for mining)

[ZenoDiac]

"setgenerate true" for solo mining was removed in 0.13  - but it might still be useful for Datacoin.  Is there a way to bring it back?

The internal miner was removed in this commit.
Reverting the change will almost certainly lead to false virus detection.
We do not want to see Datacoin-Qt or the installer being quarantined nor do we want to pay protection money to the security suite vendors on a continual basis to whitelist us.

At least qt-i386 doesn't conflict with Windows Def. Can't speak for the others though.

[Chicago]

"setgenerate true" for solo mining was removed in 0.13  - but it might still be useful for Datacoin.  Is there a way to bring it back?

The internal miner was removed in this commit.
Reverting the change will almost certainly lead to false virus detection.
We do not want to see Datacoin-Qt or the installer being quarantined nor do we want to pay protection money to the security suite vendors on a continual basis to whitelist us.

At least qt-i386 doesn't conflict with Windows Def. Can't speak for the others though.

What I found with regard to Microsoft specifically is limited to Microsoft Security Essentials -- and that is the outlier in the bunch. Microsoft Security Essentials tends to quarantine whether or not the internal miner has been removed.

Other suites like Norton, AVG or Avast will happily allow an install after the internal miner code has been removed.

What we found during a test over the past week - is that a 0.8 branch clone with the built-in miner triggers 22 warnings from virustotal whereas a 0.10 clone with the internal miner commit backported sees just 3 warnings.

More work is needed to have a comprehensive data set for how the various other anti-virus software reacts, but the pattern is already clear, speaking to me through the data; when a miner is builtin the masses get told to beware and the software gets removed.


Things like leaving the reference client alone w/ just a getblocktemplate and adapted miner for regtest should be fine.
It will be more maintenance to build in libraries from other projects which see updates more quickly than our own.

However -- everybody loves choices!
So we could maintain two flavors -- one with an expected trigger for experts where the A/V expectations are managed through trust --
and the other where the A/V expectations are managed by neutering the code to hold back a miner.

If we go that route then our website where the general public finds us - should deliver them an executable with great assurances it will be trusted by their security software.

[MarcusDe]

Hi,

IMHO best way is to make main wallet software without non-general features, like GPU or CPU miner or server.
Miner or server software will change, optimalizations will come, maybe we don't want rebuilding - we want clean and elegant wallet, with as low AV software triggers as possible :-)
Nothing holds us from making another version with miners included, name it "dev wallet" for more "pro" crypto users.

M.

[hamburger]

Downloaded 0.15.99.05 from https://yadi.sk/d/ghrCHoxA3Un8Cm

Installed 0.15.99.03 and 0.15.99.04 with no issues and on 0.15.99.05 this appear, any solution? I saw many references about this error, however, no solutions where mentioned.

Makefile:5765: recipe for target 'rpc/libdatacoin_server_a-blockchain.o' failed
make[2]: *** [rpc/libdatacoin_server_a-blockchain.o] Error 1
make[2]: Leaving directory '/root/datacoin/src'

Ubuntu 16.04 x64


Tnx,

H

[DataSea]

Primecoin is the target of some kind of Bitcoin--Primecoin activity...
Very peculiar:
https://twitter.com/BitcoinPrime_
Primecoin price has mooned -- but buyer beware.
(Note this is not an endorsement, just an observation --- as Primecoin is a relative of ours)

[Verionum]

CPU miner is revived. But it's so slow ....

[Verionum]

Downloaded 0.15.99.05 from https://yadi.sk/d/ghrCHoxA3Un8Cm

Installed 0.15.99.03 and 0.15.99.04 with no issues and on 0.15.99.05 this appear, any solution? I saw many references about this error, however, no solutions where mentioned.

Makefile:5765: recipe for target 'rpc/libdatacoin_server_a-blockchain.o' failed
make[2]: *** [rpc/libdatacoin_server_a-blockchain.o] Error 1
make[2]: Leaving directory '/root/datacoin/src'

Ubuntu 16.04 x64


Tnx,

H

Sorry. I don't understand what the matter. Are you sure you have done $ ./autogen.sh and $ ./configure --with-gui=yes LDFLAGS="-L/home/veter/dbbin/lib/" CPPFLAGS="-fPIC -I/home/veter/dbbin/include/" LIBS="-lgmp -lboost_timer -levent_pthreads" ?

[Verionum]

Updated binaries and sources.

Source code DTC 0.15.99-06: https://yadi.sk/d/Vnkrnl1q3V2rnw
Windows binaries 0.15.99-06: https://yadi.sk/d/Zrb-2B7u3V2rrM

CPU miner from XPM-hp14 added. Some other fixes.
Commands:
Mine on all CPU: setgenerate true
Mine on 4 CPU: setgenerate true 4
Turn off miner: setgenerate false

IMPORTANT: Backup your wallet before using it.

[hamburger]

Downloaded 0.15.99.05 from https://yadi.sk/d/ghrCHoxA3Un8Cm

Installed 0.15.99.03 and 0.15.99.04 with no issues and on 0.15.99.05 this appear, any solution? I saw many references about this error, however, no solutions where mentioned.

Makefile:5765: recipe for target 'rpc/libdatacoin_server_a-blockchain.o' failed
make[2]: *** [rpc/libdatacoin_server_a-blockchain.o] Error 1
make[2]: Leaving directory '/root/datacoin/src'

Ubuntu 16.04 x64


Tnx,

H

Sorry. I don't understand what the matter. Are you sure you have done $ ./autogen.sh and $ ./configure --with-gui=yes LDFLAGS="-L/home/veter/dbbin/lib/" CPPFLAGS="-fPIC -I/home/veter/dbbin/include/" LIBS="-lgmp -lboost_timer -levent_pthreads" ?

Verionum,

I have sorted the problem - I forgot to install autoconf on the server,

All versions - 0.15.99-03 / 0.15.99-04 / 0.15.99-05 and 0.15.99-06 compiled on Ubuntu 16.04 x64

Tnx,

H

[Verionum]

Good day!
At 2018-05-01 22:42:21 GMT the next block was generated by test client.

block hash = e75e39b1338a4bd81439ee1002e87d0a8665236809b88cf0ede3ae961361d5d3
  Target: 09.d081f3
  Chain: 1CC09.d2b52b

height=2395102
   
getblock e75e39b1338a4bd81439ee1002e87d0a8665236809b88cf0ede3ae961361d5d3 0

Raw block:
000000203ca528e815eda16e030f3971e7246205d73def78b1e0cb9794ded25bb1b65ba7b72ed2c d2b33531c6fe73a07806559830228bbea2aa41aa55226812f965887cb4bede85af381d009944d00 000a62aa4276d7e61d1180000101000000010000000000000000000000000000000000000000000 000000000000000000000ffffffff0903de8b2403cde45500ffffffff01405dcf3d000000002321 036f6310727abc53f003d98e398a6f0a007db33394411270a9fe33ef1a68acb6c6ac0000000000

The block was rejected by old clients of main network and client temporarily banned for misbehaving. Previously generated few blocks was accepted successfully.
Can someone give me the reason of rejection and misbehaving from your logs?

Before embedding gpu miner I need to resolve this issue.

[liaoguipan]

great job，a new version

[gjhiggins]

getblock e75e39b1338a4bd81439ee1002e87d0a8665236809b88cf0ede3ae961361d5d3 0

Can someone give me the reason of rejection and misbehaving from your logs?

Code:

received block e75e39b1338a4bd81439ee1002e87d0a8665236809b88cf0ede3ae961361d5d3
ERROR: CheckPrimeProofOfWork() : block header hash under limit
ERROR: CheckProofOfWork() : check failed for prime proof-of-work
ERROR: ProcessBlock() : proof of work failed

HTH

Cheers

Graham

[Verionum]

Code:

received block e75e39b1338a4bd81439ee1002e87d0a8665236809b88cf0ede3ae961361d5d3
ERROR: CheckPrimeProofOfWork() : block header hash under limit
ERROR: CheckProofOfWork() : check failed for prime proof-of-work
ERROR: ProcessBlock() : proof of work failed

Thank you very much, Graham!

It is unbelievable, but uint256("55") > uint256("46") in old bitcoin client and uint256("55") < uint256("46") in modern bitcoin client. They changed comparison in reverse byte order.

There is only one place when that important in dtc client, but it happend.
Fixed.

[minerja]

Good day,

I see someone has suddenly become aware of Datacoin, and has doubled the nethash. 4 rigs (20 cards).
Well thanks for screwing the small guy. No point trying to compete with that hash. Price dropped by 2/3rds and for every £5 of power i spend i get approx £0.25 of Datacoin. (That was pre hash increase.)
I wish there was a way to implement say something like for every gpu you needed 8 or 16GB of system ram, that way at least it might keep the 1080ti rigs away a little longer.

I'll stick a 1030Gt on it, just to help keep the chain ticking over.
Be interesting to see where the mining goes next.

Will keep a casual eye on developments, cos i love the concept, and think the individuals behind this are some of the very best i have come across.
J