Topic: [ANN][Datacoin] Datacoin blockchain start announcement (Minor code upd + logo) - page 7. (Read 171808 times)

Hello Gentlemen,

    The latest upstream tagged release is from 2013 at v0.8.6 for the Primecoin repository.
    That's obviously not the state of the art.

    The last commit upstream was on July 21st, 2014.

    What is the lineage of the primecoin-hp branch?
    Has there not been an official Sunny King update to the Primecoin sources since Bitcoin v0.8.6?
    If not, then why?  Aren't there big issues with non DER encoded signatures which cause forks across architectures?

    Current Datacoin is minting version 2 blocks.
    BIP66 which enforces strict DER signatures isn't inherited in our code from upstream since activation/enforcement came long after Bitcoin v0.8.6.

    It almost feels like the right thing to do is make a Datacoin network upgrade on the Bitcoin v0.10 sources which introduce BIP66 and then BIP65.
    By the time we get there we will know what commits "make Primecoin" so that we can "make Datacoin" again on top of more recent Bitcoin.

    It is more work but I have to wonder why there haven't been updates to Primecoin's repository in so long.

Best Regards,
-Chicago
   

thanks, Chicago

btw, confirmations stop performing for more that 2 days, any thoughts?

Hello Mightinside,

    The difficulty isn't included in the original code either.
    Easiest way to see the current difficulty would be to:


    Simply replace /var/lib/datacoin/debug.log with the location where your datadir/debug.log exist.

Best Regards,
-Chicago

Thanks for the positive response. It's not a wallet, it's a web app talking to the wallet. The visual aspects are courtesy of the Semantic-UI CSS framework which I omitted to credit. You can toggle between viewing metadata for mainnet and testnet by clicking on the coinlogo+name in the navbar (an easter egg).

Cheers

Graham

(edit: added URL, clarified)

Yes, it can be easily removed or, as the author notes, disabled. I also note that the community has been seeking technical contributors for some time and I'm sort of sensitive to the apparent message that stripping out/disabling the donation code would send.


Sure, each to his own and all that. My own attempts to create an non-donation HP-14 version reflect my understanding that Datacoin differs from most other PoW-based alts in that the economic benefit of the work done isn't constrained to merely supporting the altcoin's internal token value system but also contributes to overall mathematical endeavour and it's that aspect that is enhanced by speeding up the calculation of primes.


I can't say for sure right now, it all depends on how big a footprint, i.e. how much of the original code was changed. I'm guessing that an upgrade to Core 0.10 could be reasonably straightforward, depends on how much work is required to bring the getwork side of things up to date. The change to using block headers is (AIUI) currently presenting an upgrade barrier to most PoS alts. I've been advised that PIVX is Core 0.12 and uses PoS but I've also noted that where overlay node alts are concerned, the “0.12“ is actually 0.10 under the hood (the version numbers of the “release notes” files on docs are often instructive).


The former, which is not available directly from the JSON API. The latter is expressed directly in the results from getblock and is mapped to RDF.

If this is the verbatim straight JSON:

~/bin/datacoin getblock 9c4a0c53dc5c2da031cc9515daa29c91f151f033b9d78eca648b6acbc46157b0
{
    "hash" : "9c4a0c53dc5c2da031cc9515daa29c91f151f033b9d78eca648b6acbc46157b0",
    "confirmations" : 1,
    "size" : 198,
    "height" : 1979931,
    "version" : 2,
    "headerhash" : "c05f00c01f9c759833fa5b104b08d2270bf6e0e7e0d006c456dba27f002e5edc",
    "merkleroot" : "3f95b66ed63a722f2bc7ba558953157c0ca97e097b1ec68677703f45f51fdf98",
    "tx" : [
        "3f95b66ed63a722f2bc7ba558953157c0ca97e097b1ec68677703f45f51fdf98"
    ],
    "time" : 1503653771,
    "nonce" : 465138,
    "bits" : "07c80f68",
    "difficulty" : 7.78148508,
    "transition" : 7.96567649,
    "primechain" : "2CC07.fcb7d4",
    "primeorigin" : "5049200510910873383815124963229437742780997306869231794732113951576948673432067 51904218000",
    "previousblockhash" : "eeab89f0199fe1dc74cf6821afeb338aaa3091875203106b94f017a2e034c67a"
}

It is readily expressible in JSON-LD, of which the below is an arbitrary and roughly sketched-out example because I skipped this intermediate stage of mapping:


{
  "@context": "https://purl.org/net/bel-epa/ccy#",
  "@id": "C9c4a0c53dc5c2da031cc9515daa29c91f151f033b9d78eca648b6acbc46157b0",
  "type": "https://purl.org/net/bel-epa/ccy#Block",
  "confirmations" : 1,
  "size" : 198,
  "height" : 1979931,
  "version" : 2,
  "previousblockhash" : "https://purl.org/net/bel-epa/ccy#Ceeab89f0199fe1dc74cf6821afeb338aaa3091875203106b94f017a2e034c67a"
}


The above will fail a validator, it's merely an attempt to demonstrate that it's a mapping  (for a more thorough understanding, see the JsoN-LD docs).

SPARQL queries return transaction metadata by address (or date, or block, or with/without data, or ...).

Cheers

Graham

uh the wallet teaser looks beautiful, seems like an interesting project. are you guys going to do something serious with this coin, I understand it's just a fork for testing?

Thank you for helping me. I have 3 active connections.

New coin named DATAcoin coming soon.

The original version of primecoin-hp14 has a built-in donation code. I think it can be easily removed from the source code. But it is not very important.

I am more interested in functional improvements. Such improvements can raise up the popularity of DTC.


I think it is meaningless. The latest version of primecoin is very old also. It seems Primecoin-HP14 is already latest version. There is no any other recent version of primecoin .

Which recent codebase do you mean?

If you mean the recent bitcoin code there will be another problems.

I can try to define the difference between datacoin (primecoin) and the original bitcoin code. I can analyze this difference then apply it to the latest bitcoin code.


But latest bitcoin code is very changed. For example it has SegWit support.


I did not look into SegWit. I don't sure the above mentioned difference can be successfully applied
 to bitcoin code without taking SegWit into account.


But I can try to do it. Can you advice me something?



Do you need transaction metadata by address?

Do you mean payment addresses or transaction addresses (hash)?

Indeed it is. But importantly, it is a full clone of Primecoin and retains the prior commit history.


Yes, it is. The Primecoin codebase has been improved since the Datacoin fork. It is now at hp-14 (improvements to the speed). One route to upgrading Datacoin is by integrating those subsequent improvements. That's the approach taken by g1go in https://github.com/g1g0/datacoin-hp/commits/master

I'm looking to create a donation-free version by merging direct from the Primecoin commits. Not quite there yet. The work-in-progress is in https://github.com/gjhiggins/datacoin.


Fixing up the test suite would be a useful start. That, in conjunction with enabling Travis CI (Continuous Integration) would bring a beneficial hike in the standard of software engineering employed in the curation and would help increase confidence in the reliability of the engine. Getting the speed up to HP-14 will be a significant achievement.


Well, extro24 is also having a go at compiling the source, so it looks like we might have a small group of curators.


I am looking into an alternative possibility, trying to develop a working understanding of the precise outline of Datacoin's footprint on the Primecoin codebase and how well (or otherwise) that might transfer to a more recent codebase. I've not made much progress, it's a labour-intensive process - as you observed.

And I'm in the process of completing an adaptation of ACME for Datacoin. ACME stands for A Cryptocurrency Metadata Explorer, a block and transaction explorer like Abe/Iquidus, etc, the difference being that ACME (transparently) maps the blockchain to RDF, with all the power that brings.

It's a rapid prototype built from hooking up a Pyramid web app, a Datacoin node, and Fuseki, the Apache Jena SPARQL server.

To get an idea of what this delivers, the first phase of ACME for Slimcoin is nearly complete, it's accessible on http://tessier.bel-epa.com, port 6054 (be gentle, it's not yet optimised for delivery).

The Datacoin adaptation is in its early stages. The presentation uses calls on the JSON-RPC API of the node to get its block and tx data. Address data has to be collated off-chain because basically, a wallet is a transaction explorer, scoped to a set of addresses. The index maintained by the wallet is transaction -> address but to browse addresses, the index needs to be address <- transaction, hence the RDF+SPARQL with the added advantage that the RDF graph is replicable, i.e. publishable and amenable to ad hoc interrogation by means of SPARQL query.

I working my way through the blockchain in 20k chunks, mapping the block and tx hashes and data to RDF, then loading that up to the SPARQL server.

More by way of a teaser than anything useful at the moment, an instance of ACME for Datacoin is running : http://tessier.bel-epa.com, port 5059. Again, be gentle, this is work-in-progress, for example, on the Publications->Chains page, the addresses listed against blocks with height > 400000 won't resolve because that's as far as I've got with the mapping to RDF.



The Pyramid app is maintained as branch of ACME: https://github.com/gjhiggins/acme/tree/datacoin

The aim is to end up with a deployable package of a running instance of ACME with a synced node and RDF graph.

Cheers

Graham

Thanks!  That compiled beautifully.  I am now running Datacoin version v0.1.2.0dtc-hp14-unk-beta.  I mirrored the changes on Github under extro24/datacoin-hp.

The most up to date version of the client is that of Graham Higgins, https://github.com/gjhiggins/datacoin, and that is the one that I will be compiling in the future.

The current DTC code is very old.

I can try to upgrade the code. Is it meaningful?

May be I will try to support it. I need a list of necessary improvements.


But I am a newbie in cryptocurrencies. I need the time for deep exploration of the original code and proposed improvements (if there will be any). It can take a month or more. Please write here if you are interested in.


Please write the list of necessary improvements.


Is it possible to integrate some new cryptocurrency technologies into DTC?
If source code of such technologies is open I can try to integrate it.

How do you think?

Hello everyone,

just made a debian build for those who are lazy.
https://github.com/Mightinside/datacoin-hp

I found interesting attempt to develop new datacoin2107  "in shadow".
Why getinfo doesn't print difficulty?

{
    "version" : "v0.1.2.0dtc-hp11-g791125b9-beta",
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" :
    "blocks" : 1978127,
    "moneysupply" : 26187045.02783475,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "testnet" : false,
    "keypoololdest" : 1503367205,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

Lookin forward to partaking in this project

Try these nodes:

80.74.157.31
144.76.64.49
104.236.250.232
82.36.172.103

Change line #242 of src/rpcrawtransaction.cpp from ...

const CScriptID& hash = boost::get(address);

to ...

const CScriptID& hash = boost::get(address);

Cheers

Graham

Mining = running a node. You can do both

Download: http://datacoin.info/

Mining control built in to client but you can put "gen=1" into datacoin.conf for automatic mining.

Look back up through thread for recent addnodes - add to datacoin.conf like "addnode=159.203.81.200"

Good luck

I would like to join and mine this coin or should I run a node.
Can somebody help me here?
Thank you.

When I tried to compile g1g0's version of Datacoin I got the following error:  

../datacoin-hp/src/rpcrawtransaction.cpp:242:77:   required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE'
     BOOST_STATIC_ASSERT_MSG(
     ^
Makefile:2018: recipe for target 'build/rpcrawtransaction.o' failed
make: *** [build/rpcrawtransaction.o] Error 1
22:58:14: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project datacoin-qt (kit: Qt4)
When executing step "Make"

I followed exactly the instructions for compiling bitcoin under Ubuntu found here:  https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

I am using Qt Creator 3.5.1 with kit Qt4.

I have tried it again.

It is strange. In my case the "getdata" works perfectly for any external transaction.

For example:

getdata 9a78fa1022ab40c8abce9b86279236ccffd25fc2448f8197d5592839ebdea7ba
=> I0ZSQTIwMTcsTEVQRU4sVTVDTjhGQ1IsZGMwMjNkNzc4MzkxNzIzYWY4MWMzMGU5OWI4ZGM3ZGI=
after DecodeBase64 => #FRA2017,LEPEN,U5CN8FCR,dc023d778391723af81c30e99b8dc7db

It coincides with Bytestamps info. http://www.bytestamp.net/blocks/qtx/en/9a78fa1022ab40c8abce9b86279236ccffd25fc2448f8197d5592839ebdea7ba


Does Apertus.io team use the latest version of DTC code?

May be I don't understand the problem.

Can you repeat the issue description in detail?

Datacoin went down because the developer disappeared.  It was very active before that happened.  With new developers the coin should revive fairly quickly.  The name has good brand recognition and immediately indicates the function.