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

And also full of bullsh*t, I've spent most of my life trying to figure out which is which. Let's see if I can actually deliver this.

Cheers

Graham

www.Apertus.io.
www.bytestamp.net
DTC Browser

Metadisk used to work with Datacoin as well.  But I think it was changed to Florincoin.  Maybe someone should bring it back 
https://github.com/StorjOld/MetaDisk

I wasn't planning to take that route. The Datacoin approach is reasonably straightforward, uses an extra field in the CTransaction object, no impact on the opcode/scripting at all (afaict). Or have I missed something critical?


Even better, gatra's Riecoin is a primes-as-proof-of-work clone of straight Bitcoin 0.8.3, not a hint of “ppcoin” anywhere in the sources and a very useful set of version branches.


  remotes/origin/0.10.2
  remotes/origin/0.6.2
  remotes/origin/0.6.3
  remotes/origin/0.7.2
  remotes/origin/0.8.1
  remotes/origin/0.8.3
  remotes/origin/0.8.4
  remotes/origin/0.8.5
  remotes/origin/0.8.6
  remotes/origin/0.8.6-ric
  remotes/origin/0.9.1
  remotes/origin/0.9.2
  remotes/origin/HEAD -> origin/0.10.2
  remotes/origin/blockheaders
  remotes/origin/freenode-verf
  remotes/origin/master
  remotes/origin/master-ric


So, I was able to upgrade foo1inge (via Primecoin) to 0.8.4 and 0.8.5 and then pull up to 0.8.6, at which point I was able to shimmy over to 0.8.6-ric, pick up the (albeit Riecoin-specific) primes-as-PoW architecture, then take a long running jump and grab to Datacoin 0.9.1. Which is where I am atm, cross-referencing against a Minkiz Foundry 0.9 Bitcoin Core template (to identify common change points). At this point, the refactoring of foo1inge Datacoin-specific code is still significantly incoherent with respect to the 0.9.1 base, so the next step is a cross-comparison of Datacoin vs its original cloneparent at the point of cloning - to more precisely delineate the original footprint of the Datacoin-specific changes and use that as reference for the final refactoring of the Datacoin code so that it is coherent w.r.t to an 0.9.1 codebase. It should only be a standing jump to 0.10 from there, iirc. And the only remaining Prime/PPcoin code will be limited to that which is required by the Datacoin-specific PoW routines, i.e. not a lot.

Cheers

Graham

Exchanges need a solid network before they will consider datacoin. They can't risk chain being attacked. Difficulty is rising fast now but we still need more nodes mining to secure network. 51% attack still quite possible even for individual at current level. We need high enough difficulty that someone with garage full of GPU rigs can't touch. Then exchanges will be able to consider other factors.

Hello,

    Yes, there are several.  Have a read through the last few pages of this thread to find a few links.

Best Regards,
-Chicago

Hi!
Anybdy knows apps using dtc?

Hi Graham, Extro,

    I agree the move to an immediate v0.14.2 Core clone is premature.

    If porting Datacoin's unique storage feature as a new script opcode into a plain Core clone becomes an understood process - - then perhaps we're left with just two more pieces.
    The first would be bringing in the proof-of-work method employed by Primecoin/Datacoin and the second would be the implications the additional Datacoin script has on transaction/block creation/verification.

    Somehow I don't think we can achieve the latter without having first mastered the former.

    Advance the Datacoin code with the primary goal being the preservation and re-usability of upstream Core's battle-tested implementation of the various branches.

    I'd imagine the experiments would start by taking 0.8 Bitcoin/Litecoin and doing a big-bang with the additional script.
    So long as that tests well for doing everything Datacoin does today -- then experiment #2 would probably be another iteration of experiment #1 which employs the Datacoin/Primecoin proof-of-work algorithm.

    After that tests satisfactorily; then a next experiment should be attempting to verify the current entire blockchain using the work from the previous experiments.
    After that tests satisfactorily; then probably coding in the same Network Magic and other parameters to try and not be DoS banned by existing Datacoin clients would reveal where we are succeeding or have further work to perform as we connect it to the peer swarm for the first time.

    These are just some initial thoughts on how to move forward in the absence of Primecoin upstream development.

Best Regards,
-Chicago

To get Datacoin listed on exchanges people need to register on those exchanges and ask for the listing.  The more the merrier.
I have submitted the details of Datacoin to Poloniex, Bter and Bittrex as support tickets.  These are large exchanges, but they don't charge so maybe we get lucky.

When you register open a support ticket to "List Datacoin (DTC)" and paste the following info:


Code= DTC
Name= datacoin
Github= https://github.com/foo1inge/datacoin-hp
Debian build= https://github.com/Mightinside/datacoin-hp
Windows wallet= https://sourceforge.net/projects/datacoin/files/
Bitcointalk= https://bitcointalksearch.org/topic/anndatacoin-datacoin-blockchain-start-announcement-minor-code-upd-logo-325735
Webpage= datacoin.info
Explorer= www.bytestamp.net/blocks/index
Example address=any of these: www.bytestamp.net/blocks/lunsp
Already listed on CMC - www.coinmarketcap.com/currencies/datacoin
Reddit= www.reddit.com/r/Datacoin

Most up-to-date client is Graham Higgins at https://github.com/gjhiggins/datacoin

Any further advice on how to get Datacoin onto exchanges would be very welcome.

Thank you.

That entails a long running jump and grab to an 0.14.2 Core clone. And a hard fork. That's quite a big “ask”.

Right now, I'm trying to get a sense of the role that Datacoin's unique strorage feature plays in the overall functioning of the coin. It's PoW, so people can readily acquire coins by mining, to pay the fees to store data. It's all nicely self-contained and unchanged from the day it was launched. There's nothing to stop people from making full use of the feature.

There have been a total of 4,327 data tx made since Nov 2013 during which time (/me checks) 1985959 blocks have been chained. A significant number of tx can only be classified as “noise” (dozens and dozens of entries 'W10=' and 'Broughs=').  Even if this “noise” is included, I make that around 0.2% (of blocks).

I'm sorting out some public filesharing space so I can publish the raw lists should anyone wish to conduct their own analysis.

Cheers

Graham

The other issue with upgrading is Segwit.  I understand it will make easy cross chain exchange with other Segwit coins like Bitcoin and Litecoin.

1. Noted.
2. Good questions. As Chicago has pointed out, there is a twisty-turny path to upgrading Datacoin to a clone of 0.10 Core. Dash is a clone of 0.10, as are its klonekinder. Monero uses the Cryptonote protocol and would be an unsuitable target. I've not investigated Zcash in any detail, so I don't have much sense of the degree of complexity of the migration. So right now, any “anonymity” feature is restricted to coin-mixing-via-overlay-network, a la Dash, i.e. not actually anonymous.

On other matters, the entire(*) Datacoin blockchain has now been mapped to RDF, so addresses now resolve. It's a single-threaded server, straight Python (waitress) and I'm also not at all sure that I've configured Fuseki with sufficiently generous resources and because I'm still working on it, nothing is being cached, so response alacrity is “best effort” atm.

(*) I accidentally-on-purpose omitted to copy the contents of the tx data field over to the RDF graph as the stored data isn't strictly metadata. Instead, in the next workspace over, as I write this, a small Python script is working its way methodically through the blockchain, recording the hash of each block that has one or more data txs, the hashes of those txs and the size of the stored data for the tx.

Sample output, copynpasta'd:

790000 <- height achieved thus far
["2be1fffdb16c1163ece07029862f58fcc90f55e91dba42bd1f17a8f5a7187366", "1ec6a6370f603be614cc29338aeb2a9abaf55bb9a41012fb80e38bffd3c4b9de", 136],
["2be1fffdb16c1163ece07029862f58fcc90f55e91dba42bd1f17a8f5a7187366", "3b500c4bf2841c80bd3ff3ebe7090865e521bbc55ab753d0ba1cf16466595a5f", 140],
["2be1fffdb16c1163ece07029862f58fcc90f55e91dba42bd1f17a8f5a7187366", "1a3966eb8ac879c5de7d19675f46b7ffbe1074e57ab0b6c35c3287991b3b438b", 136],
["9da914b8e0236dda7e87c55e3079a0825c3be173119384ac636d732f9d77d536", "4ca286534961fc8ff10dd7e4ef3d42ccba9a9c3efac2b5aa23476f09cc6b6b2e", 136],

you can try them out:

http:// tessier.bel-epa.com port 5059  /main/tx/1ec6a6370f603be614cc29338aeb2a9abaf55bb9a41012fb80e38bffd3c4b9de

I'll then add those facts to a separate RDF graph (to keep the blockchain mapping untainted) and re-do the exercise, this time using a routine that attempts to determine the MIME type of the stored data, which when confirmed, can be added to the graph.

(If the way that ACME presents the metadata makes little sense to you, check out the accordion drop-down “Unprocessed JSON response”, that's what we have to work with - if anyone has suggestions for making a clearer presentation, please feel free to pitch in.)

And before anyone jumps in to  point out the obvious, a Python web app that marshals and presents data retrieved over the wire can be rewritten using a Javascript framework, browserified and embedded in the client, courtesy of Qt5's webengine implementation of v8. Windows binaries would have to be compiled natively because (aiui) there is no MXE cross-compiler implementation of qtwebengine because of, well v8 and Microsoft but I have proof-of-concept browserified js apps running out of a Linux build of a 0.14 Core clone.

The possibilities are entertaining: https://doc.qt.io/qt-5/qtwebengine-features.html -- and, because it's Qt and restricted to the GUI part of the wallet, adding user-appealing functionality doesn't entail any fiddling with the blockchain engine and is basically just a bolt-on.

Cheers

Graham

1.  Windows wallet needs to be updated.
2.  Are you familiar with the anonymity features of Dash, Monero and Zcash?  Maybe these could be added to Datacoin?

Hi Graham,

    This is brilliant.  Last time I remember seeing Jinja2 used to get down and dirty is with Ansible.
    With this template; one could basically write a series of tasks and a playbook to essentially eliminate a whole lot of non-valued added work as it pertains to maintaining coin code.

    I will be looking to abstract a vanilla Litecoin v0.10.2.2 repository with the template methodology.


    There is just a little bit more to do for changing the proof-of-work algorithm because all of the makefile.foo files in the 0.8 branch derivatives would need to have lines stricken and replaced.

    However, passing the tests -- which also involve updating the data used in the tests is going to be much easier when using a template with Ansible tasks.
    For example, updating the BitcoinMiner tests which have some precomputed solutions to a run of blocks -- or the Alert system tests which need to have some pre-signed messages with the new alert key, or the address tests where changing the Base58 prefix needs to happen or else they fail on new *foo*coin.

    So much more can be done than diff and patch or sed when you abstract the vanilla repository into a Jinja2 template.

    Your idea very much aligns with code re-usability and will promote sustainability of multiple coin networks.

Best Regards,
-Chicago

Ah, thanks for that clarification, I've not had the time to pin down the crossover details precisely. Thinking back, the coin I was upgrading was a straight clone, just param changes, so when they introduced 0.9, I just re-rebranded Bitcoin and migrated the coin's params to chainparams.

Co-incidentally, the refactoring has given me an opportunity to lend a bit more depth to an existing piece of work ...

More than one person has failed to detect the tongue-in-cheek nature of Minki’s Foundry: https://minkiz.co/foundry.

Originally the advertised “latest Bitcoin Core release” was 0.9 because that's when I published the work. Riffing off've the re-rebranding and the distillation of the parameter differences into a single location, I created for myself a “template branch” of Bitcoin Core with all the re-rebranding and parameter distillation abstracted out and replaced by Jinja2 template statements. I had been playing around with the notion of distilling a coin's profile (hence the DOACC metadata collection http://github.com/DOACC/individuals) and for a while I toyed with the idea of trawling Github-hosted chainparams.cpp files and extracting the specific technical metadata for adding to DOACC. In the end, I brought DOACC to a close, it had served its purpose, and I decided to go in the opposite direction - use the metadata + templates to implement the Foundry offers. Now that the pow functionality has been handily abstracted out to pow.[cpp|h] it's just too tempting to resist. I'm too involved atm but I have a compiled version of FerrariBoat to return to at some point in the future. (The naming convention is homage to a classic Snickers ad: https://www.youtube.com/watch?v=anm2SWU_BHo)

This is the YAML description of Chaincoin from a while ago, with Bitcoin values as end-of-line comments:


CHC:
  checkpointestimatedtransactions: 572007 # 60000.0
  checkpointtimestamp: 1434866355 # 1397080064
  checkpointtotaltransactions: 960 # 36544669
  checkpoints: [
    [0, "0x00000f639db5734b2b861ef8dbccc33aebd7de44d13de000a12d093bcc866c64"],
    [6143, "0x0000000026fb51f5bc9943ed69d9ff7697ecf7fed419d88b417655f93a487ce1"],
    [12797, "0x000000002c29644e179baa188fa6b9b9454721f1f21f2b9f31eebe9acc1a31db"],
    [30092, "0x0000000098a23e1c503f71a6d61c333c5abaabb4c5fa1b474012e004db4bfbbe"],
    [80998, "0x000000010ebcfe9a00a99f2b61104f4a141555a707f1c007aba8a978f6030cfb"],
    [144759, "0x000000047e7b7bfd63b4f019a0a24c8d65b10afa6eb80721e10fa7c49ce6fb6e"],
    [189046, "0x00000000bd507c435b46ee8a13b25b85ec38fdb0eb5b00faeaa0611cd6a483d3"],
    [277316, "0x00000016a20503fe496e79d34fb85c33f633059315c046ffa1b4826d08a1e856"],
    [483849, "0x000001eb7f8124282ab62296e63d3145ff6c84cf18afae4d4b8e02cd3182b6a8"]
  ] # [['   0', "0x0"]]
  clientname: "Satoshi" # "Satoshi"
  coinbasematurity: 100 # 100
  coinlcname: "chaincoin" # "bitcoin"
  coinbsname: "chaincoin" # "bitcoin"
  coinname: "Chaincoin" # "Bitcoin"
  coindisplayname: ""Chaincoin" " # "Bitcoin"
  coinucname: "CHAINCOIN" # "BITCOIN"
  coinsymbol: "CHC" # "BTC"
  coinunit: "Chaincoin" # "Bitcoin"
  coinlcsymbol: "chc" # "btc"
  cointype: "0x80000005" # "0x80000005"
  proofofworklimit: "CBigNum(~uint256(0) >> 20)" # CBigNum(~uint256(0) >> 20)
  psztimestamp: "18-01-14 - Anti-fracking campaigners chain themselves to petrol pumps" # "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
  defaultminrelaytxfee: 1000 # 1000
  genesisblockhash: "0x00000f639db5734b2b861ef8dbccc33aebd7de44d13de000a12d093bcc866c64" # "0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f"
  genesisoutputscript: "04becedf6ebadd4596964d890f677f8d2e74fdcc313c6416434384a66d6d8758d1c92de272dc671 3e4a81d98841dfdfdc95e204ba915447d2fe9313435c78af3e8" # ""
  hashmerkleroot: "0xfa6ef9872494fa9662cf0fecf8c0135a6932e76d7a8764e1155207f3205c7c88" # "0x4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b"
  npowhumantargetspacing: "90 seconds" # "10 minutes"
  npowhumantargettimespan: "90 seconds" # "2 weeks"
  maxmoney: 30000000 # 21000000
  mintxfee: 10000 # 10000
  msgstrts: ["0xa3", "0xd2", "0x7a", "0x03"] # ["0xf9", "0xbe", "0xb4", "0xd9"]
  nbits: "0x1e0fffff" # "0x1d00ffff"
  nnonce: 2099366979 # 2083236893
  nsubsidy: 16 # 50
  npowtargetspacing: 90 # "10 * 60"
  npowtargettimespan: 90 # "14 * 24 * 60 * 60"
  ntime: 1390078220 # 1231006505
  nvalue: 16 # 50
  nversion: 1 # 1
  port: 11994 # 8333
  rpcport: 11995 # 8332
  prefixnum: 28 # 0
  scriptaddress: 4 # 5
  scriptpubkeyhex: "0x" # "0x"
  secretkey: 156 # 128
  subsidyhalvinginterval: 700800 # 210000
  vseeds: [
    ["seed1.chaincoin.org", "seed1.chaincoin.org"],
    ["seed2.chaincoin.org", "seed2.chaincoin.org"],
    ["seed3.chaincoin.org", "seed3.chaincoin.org"],
    ["seed4.chaincoin.org", "seed4.chaincoin.org"]
  ] # []
  xpub: "(0x02)(0xFE)(0x52)(0xF8)" # "(0x04)(0x88)(0xB2)(0x1E)"
  xprv: "(0x02)(0xFE)(0x52)(0xCC)" # "(0x04)(0x88)(0xAD)(0xE4)"
  regtestcheckpointestimatedtransactions: 0 # 0
  regtestcheckpoints: [] # [['   0', "0x0"]]
  regtestcheckpointtimestamp: 0 # 0
  regtestcheckpointtotaltransactions: 0 # 0
  regtestnpowhumantargetspacing: "90 seconds" # "10 minutes"
  regtestnpowhumantargettimespan: "90 seconds" # "two weeks"
  regtestmsgstrts: ["0xfc", "0x1f", "0xc3", "0x56"] # ["0xfa", "0xbf", "0xb5", "0xda"]
  regtestproofofworklimit: "CBigNum(~uint256(0) >> 1)"
  regtestngenesisblockhash: "0x" # "0x0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206"
  regtestmerkelroothash: "0x" # "0x4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b"
  regtestnbits: "0x207fffff" # "0x207fffff"
  regtestnnonce: 3 # 2
  regtestntime: 1296688602 # 1296688602
  regtestnvalue: 16 # 50
  regtestnversion: 1 # 1
  regtestpubkeyaddress: 80 # 111
  regtestscriptaddress: 44 # 196
  regtestsecretkey: 208 # 239
  regtestsubsidyhalvinginterval: 150 # 150
  regtestnpowtargetspacing: 90 # "10 * 60"
  regtestnpowtargettimespan: 90 # "14 * 24 * 60 * 60"
  regtestport: 18444 # 18444
  regtestrpcport: 18445 # 18332
  regtestpub: "(0x04)(0x35)(0x87)(0xCF)" # "(0x04)(0x35)(0x87)(0xCF)"
  regtestprv: "(0x04)(0x35)(0x83)(0x94)" # "(0x04)(0x35)(0x83)(0x94)"
  testnetcheckpointestimatedtransactions: 960 # 300
  testnetcheckpoints: [
    [0, "0x0000082f5939c2154dbcba35f784530d12e9d72472fcfaf29674ea312cdf4c83"]
  ] # [['   0', "0x0"]]
  testnetcheckpointtimestamp: 1388868139 # 1337966069
  testnetcheckpointtotaltransactions: 0 # 1488
  testnetgenesisblockhash: "0x0000082f5939c2154dbcba35f784530d12e9d72472fcfaf29674ea312cdf4c83" # "0x000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943"
  testnetmerkleroothash: "0x" # "0x4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b"
  testnetnpowhumantargetspacing: "90 seconds" # "10 minutes"
  testnetnpowhumantargettimespan: "90 seconds" # "two weeks"
  testnetmsgstrts: ["0xfb", "0xc2", "0x11", "0x02"] # ["0x0b", "0x11", "0x09", "0x07"]
  testnetnbits: "0x1e0fffff" # "0x207fffff"
  testnetnnonce: 423087994 # 1211565
  testnetnpowtargetspacing: 90 # "10 * 60"
  testnetnpowtargettimespan: 90 # "14 * 24 * 60 * 60"
  testnetntime: 1388868139 # 1374901773
  testnetnvalue: 16 # 50
  testnetnversion: 1 # 1
  testnetport: 21994 # 18333
  testnetrpcport: 21995 # 18332
  testnetpubkeyaddress: 80 # 111
  testnetscriptaddress: 44 # 196
  testnetsecretkey: 216 # 239
  testnetsubsidyhalvinginterval: 150 # 210000
  testnetvseeds: [] # []
  testnetpub: "(0x3a)(0x80)(0x61)(0xa0)" # "(0x04)(0x35)(0x87)(0xCF)"
  testnetprv: "(0x3a)(0x80)(0x58)(0x37)" # "(0x04)(0x35)(0x83)(0x94)"
  testnetcointype: "0x80000001"


That pretty much does the main job. Not sure whether I can get enough abstraction to do the hash algo swapping by template, perhaps just a dynamically-computed patch for now.

I s'pose I could ultimately publish FerrariBoat on the Datacoin blockchain in the form of a patch against a clone of a given Bitcoin Core version.

Cheers

Graham
 

Hi Graham,

    The v0.9 branch the way I've found it to be was a forklift move to the Autotools based build system.
    Then in v0.10 they started refactoring things.

    Pieces of code you can find in v0.8 branches of altcoins live in the same files in v0.9 Bitcoin ---  but not anymore in v0.10, when they introduced chainparams style declaration of the coin specification.

Best Regards,
-Chicago

Maybe Sunny has relaxed his grip, maybe he's suffering from acute NIH. Someone did contribute a strict-DER fix:
https://github.com/coinkeeper/2015-06-22_18-45_primecoin

Perhaps it was just inadequately advertised. It does seem odd that it wasn't integrated into the “main” development effort, perhaps it fell short of Sunny King's standards.


ISTM that there were some quite important changes, especially between the 0.9 and 0.10 versions, which basically render the latter as the minimum acceptable version according to contemporary perceptions of robustness and vulnerability. AIUI, there was general developer relief at getting 0.10 safely out of the door as it addressed various previously-unmentionable issues, some of which might not unreasonably be perceived as vulnerabilities to exploitation.

Cheers

Graham

Hello,

    I lied.  Here is the easiest method to find difficulty, using the RPC.


Best Regards,
-Chicago

Looks more like someone at U of Georgia is finding their way around git.


Dunno, it's in the code.

Added to issues list: https://github.com/gjhiggins/datacoin/issues

Cheers

Graham

Hello Mightinside,

    Here's why!

    The coinbase maturity is 3000 blocks.
    The target spacing is one minute.

    Expect to wait 2.083 days for a mature coinbase reward.


    This feature enshrines well-secured data into the blockchain which resists reorganization quite heavily.

Best Regards,
-Chicago