yahoo-fiurejf9
Newbie
Offline
Activity: 2
Merit: 0
|
|
July 01, 2017, 05:13:12 PM |
|
|
|
|
|
Chicago
|
|
July 01, 2017, 06:36:07 PM |
|
Hi yahoo-fiurejf9, Here are the full nodes as of today, from my observation point. 45.77.30.227 [2001:19f0:7001:7fb:5400:ff:fe6e:a871] 144.76.64.49 139.162.210.78 [2a01:4f8:191:7330::2] 71.239.112.232 [2001:558:6033:87:956a:244e:c4ab:e7b] You may want to update your init.sh commit since many of the addnode entries you have included there are externally inaccessible. There is no need to add a port number for the above hosts since they all listen on the official peer port, 4777. Thanks for your work. I'm looking forward to hearing of a new user who benefits from your actions today and has a more simplified onboarding experience using Datacoin. Best Regards, -Chicago
|
|
|
|
yahoo-fiurejf9
Newbie
Offline
Activity: 2
Merit: 0
|
|
July 02, 2017, 04:56:26 AM |
|
Hi yahoo-fiurejf9, Here are the full nodes as of today, from my observation point. 45.77.30.227 [2001:19f0:7001:7fb:5400:ff:fe6e:a871] 144.76.64.49 139.162.210.78 [2a01:4f8:191:7330::2] 71.239.112.232 [2001:558:6033:87:956a:244e:c4ab:e7b] You may want to update your init.sh commit since many of the addnode entries you have included there are externally inaccessible. There is no need to add a port number for the above hosts since they all listen on the official peer port, 4777. Thanks for your work. I'm looking forward to hearing of a new user who benefits from your actions today and has a more simplified onboarding experience using Datacoin. Best Regards, -Chicago done
|
|
|
|
|
bugreporterr
Newbie
Offline
Activity: 30
Merit: 0
|
|
July 31, 2017, 09:58:49 PM |
|
Code=DTC Name=datacoin Webpage=datacoin.info Explorer=www.bytestamp.net/blocks/index Example address=any of these: www.bytestamp.net/blocks/lunspConflicts=already listed on CMC - coinmarketcap.com/currencies/datacoin Reddit=www.reddit.com/r/Datacoin but its dead
|
|
|
|
extro24
|
|
August 04, 2017, 07:45:42 AM Last edit: August 04, 2017, 07:59:14 AM by extro24 |
|
Submitted to Bitsquare. I understand another official website would be http://datacoininfo.org. I understand we need to do a pull request to the exchange to have the coin added.
|
|
|
|
|
Chicago
|
|
August 07, 2017, 07:32:12 AM Last edit: August 07, 2017, 07:47:39 AM by Chicago |
|
Empoex trading Datacoin. Anybody have any experience?
Hi extro24, Nice find, I'm curious how others rate Empoex. Today is the first I've heard of it. Looks like there is nearly 1 BTC worth of buy support there at present, for 144 Satoshi per Datacoin. The real neat thing is it looks like back around March of this year, someone traded less than 20K DTC for more than 0.5 BTC. EDIT: That's DayTraderCoin and not Datacoin!Best Regards, -Chicago
|
|
|
|
extro24
|
|
August 07, 2017, 09:08:48 AM |
|
Woops!
Sorry.
|
|
|
|
|
extro24
|
|
August 09, 2017, 07:44:19 AM |
|
Maybe somebody can help.
I was chatting to Embii on the Facebook page of Apertus.io. He mentioned that they are able to get Javascript programs to run on Datacoin but only with the 20byte payload, not the full 128kB payload. They can write the data, but no other client can read it. With the 20byte payload it is very expensive to write Javascript programs into the Datacoin blockchain (you need to pay 0.05DTC for every chunk of code that gets written and with 20bytes you need a lot of chunks).
From embii: "we implemented encoding and deciding base 64 for DataCoin...we did get this to work...except what is saved in this manner is only accessible via RPC to the wallet that saved it... this is the real problem and is the main reason we abandoned it. It does have personal applications but does not let you share anything saved with others."
I tried to see if I could find the problem in the Datacoin wallet. In rpcwallet.cpp I saw
senddata(const Array& params, bool fHelp) { if (fHelp || 1 != params.size()) throw runtime_error( "senddata [data]\n" "<data> is a base64 encoded data chunk" + HelpRequiringPassphrase());
CWalletTx wtx;
// Transaction data std::string txdata; if (params.size() > 0 && params[0].type() != null_type && !params[0].get_str().empty()) { txdata = params[0].get_str(); if (txdata.length() > MAX_TX_DATA_SIZE) throw JSONRPCError(RPC_INVALID_PARAMETER, "data chunk is too long. split it the payload to several transactions."); }
string strError = pwalletMain->SendData(wtx, false, txdata); if (strError != "") throw JSONRPCError(RPC_WALLET_ERROR, strError);
return wtx.GetHash().GetHex(); }
I suspect HelpRequiringPassphrase() is the suspect. Anybody else have an idea? We will have to remove this so that other wallets can see the 128kB data in the blockchain. If this can be done the Datacoin blockchain will contain Javascript programs that will be visible to other clients and executable in the Apertus.io browser. And maybe other browsers as well. Datacoin could then use Javascript as a programming language.
|
|
|
|
crypto4jan
Legendary
Offline
Activity: 2453
Merit: 1026
Energy coin master
|
|
August 09, 2017, 08:24:46 AM |
|
That is a good idea and together with javascript implementation. Then there can be future for datacoin!
|
e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu 00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
|
|
|
Chicago
|
|
August 09, 2017, 10:02:46 AM |
|
Hello, std::string HelpRequiringPassphrase() { return pwalletMain->IsCrypted() ? "\nrequires wallet passphrase to be set with walletpassphrase first" : ""; }
I see this in src/rpcwallet.cpp. Are you telling me the ~128KiB data blob is only accessible with the private key of the spender and that the wallet.dat must be encrypted too? If so... couldn't there be some work-arounds where an M-of-N Datacoin address could be employed to make the ~128KiB blobs available to anybody at the time of publication whereby the publisher says, "BTW, here's the WIF for those so you can decode them." Best Regards, -Chicago
|
|
|
|
Chicago
|
|
August 09, 2017, 10:23:40 AM |
|
There's an opportunity to acknowledge the conflict and generously switch Datacoin (DTC) to the unoccupied and definitely safer from future trading symbol clashes Datacoin (DATA).
Hi Graham, Thanks for suggesting this! I'm okay with embracing DATA as the new symbol and I think the community could easily review a simple PR which only changes the symbols in the repository code. At present, DTC only appears in src/qt/bitcoinunits.cpp. Although, it would be hard to make that one change without also taking the time to update the various locale translations which still use BTC. Going stepwise through a change from DTC to DATA, we may as well add an updated PnSeed array in src/net.cpp so new peers will easily be able to find the Main swarm as well as uncommenting the block for DNS Seeds and implementing it. https://github.com/foo1inge/datacoin-hp/blob/master/src/net.cpp#L1194 https://github.com/foo1inge/datacoin-hp/blob/master/src/net.cpp#L1251 Without too much scope creep; a symbol change can be had along with the homing beacon (DNS Seeds/PnSeed array) and a checkpoint. https://github.com/foo1inge/datacoin-hp/blob/master/src/checkpoints.cpp#L37 Our last checkpoint was 1869413 block ago and we're probably due. Anybody have time or looking for a new project? Best Regards, -Chicago
|
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1290
|
|
August 09, 2017, 12:53:15 PM |
|
They can write the data, but no other client can read it.
In rpcwallet.cpp I saw
senddata(const Array& params, bool fHelp)
I'm not sure why your correspondent would think that. Certainly senddata must allow the user to provide a password for unlocking an encrypted wallet but there isn't any such requirement for getdata: https://github.com/foo1inge/datacoin-hp/commit/791125b901767b9dec40e04f6865181a3276395b#diff-e75eff0ce0dde388eddbe3173db85bd4R320Value getdata(const Array& params, bool fHelp) { if (fHelp || params.size() != 1) throw runtime_error( "getdata <hash>\n" "Returns base64 data from a given tx-hash.");
std::string strHash = params[0].get_str(); uint256 hash(strHash);
CTransaction tx; uint256 hashBlock = 0; if (!GetTransaction(hash, tx, hashBlock, true)) throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "No information available about transaction");
string data = tx.GetBase64Data();
return data; }
Or am I missing something fundamental? Cheers Graham
|
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1290
|
|
August 09, 2017, 04:31:43 PM |
|
I'm okay with embracing DATA as the new symbol and I think the community could easily review a simple PR...
Making the proposed changes is straightforward, github offers through-the-web editing. It would be preferable to have the tests passing and a Travis CI .yaml file to run the tests automatically after every commit. There is also a fork of the foo1inge “high-performance” codebase - https://github.com/datacoin-project/datacoin which carries some later commits. Cheers Graham
|
|
|
|
Chicago
|
|
August 09, 2017, 05:48:57 PM |
|
Hi Graham, I wish there had been a change to the CLIENT_NAME in src/version.cpp or an incremental update to the CLIENT_VERSION_REVISION in src/clientversion.h because when I look at the peers today, I see 3x as many nodes running /Satoshi:0.8.3/ (datacoin-hp) as I see running /Satoshi:0.8.5/ (datacoin) and I can't tell which are running from the datacoin-project repository and which are running from foo1inge's repository. I will try the datacoin-project repository fork of datacoin-hp (named datacoin) once more and figure out why I had stopped using it. If I am remembering correctly, there was something I didn't find working quite as well as on the foo1inge datacoin-hp repo. Since there seems to be some more interest here in Datacoin overall, I share this information in goodwill. Running the DatacoinMiner with setsievepercentage 40 and setsieveextensions 4 has yielded me a significant improvement in chains per day with the level of difficulty we have been seeing over the past few months. Are those sieve values very different from your own optimizations? Best Regards, -Chicago
|
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1290
|
|
August 10, 2017, 03:56:42 PM |
|
I wish there had been a change to the CLIENT_NAME in src/version.cpp or an incremental update to the CLIENT_VERSION_REVISION in src/clientversion.h because when I look at the peers today, I see 3x as many nodes running /Satoshi:0.8.3/ (datacoin-hp) as I see running /Satoshi:0.8.5/ (datacoin) and I can't tell which are running from the datacoin-project repository and which are running from foo1inge's repository.
The additional seven commits to the datacoin-project are mostly updates to IP addresses. Once synced, there's no functional difference between apps compiled from either repos. I will try the datacoin-project repository fork of datacoin-hp (named datacoin) once more and figure out why I had stopped using it. If I am remembering correctly, there was something I didn't find working quite as well as on the foo1inge datacoin-hp repo.
Any difference is sharply limited to the post-fork changes to the datacoin-project repos. Was it the IP address settings perhaps? Since there seems to be some more interest here in Datacoin overall, I share this information in goodwill.
I find the data storage component to be an interesting variant. Running the DatacoinMiner with setsievepercentage 40 and setsieveextensions 4 has yielded me a significant improvement in chains per day with the level of difficulty we have been seeing over the past few months.
Are those sieve values very different from your own optimizations?
I work on a cheapo 5-year old Acer i3 laptop (got 8Gb tho') so not in a position to mine DTC. Have you tried g1g0's hp14 version? https://github.com/g1g0/datacoin-hpCheers Graham
|
|
|
|
extro24
|
|
August 10, 2017, 07:16:56 PM Last edit: September 12, 2017, 02:41:01 PM by extro24 |
|
Mr Higgins I work on old Celeron laptops and I have mined tens of thousands of Datacoin. The difficulty is currently 6.98, so you get about 500 DTC every day from an ordinary computer.
To be honest, I would respectfully differ on changing the Datacoin abbreviation. I like the idea of saying 100 DTC instead of 100 DATA.
The Apertus.io project tried very hard to get Datacoin to work with their project. The Storj founder super3 did the same thing with Metadisk, but he wanted to create his own coin. The Apertus.io people want to work with existing coins, and Datacoin and Apertus seem handmade for each other. Javascript programs on the Datacoin blockchain that execute when it is browsed is a mouth watering idea. It would finally unlock the unique promise of Datacoin, which lies in those 128kB. They did not change the client, and it seems as if they do not have a C++ programmer amongst them. I may be wrong, but it would have been easier if such a person had produced his own version of the client.
So we have to figure this out somehow and produce an updated client.
This is a problem in senddata, not getdata. The Apertus.io people insist they cannot read Javascript programs etched on the Datacoin blockchain with senddata. It could only be read by the client that etched it. So we have to drop the encryption in senddata.
|
|
|
|
extro24
|
|
August 12, 2017, 02:31:10 PM Last edit: August 12, 2017, 02:44:48 PM by extro24 |
|
They can write the data, but no other client can read it.
In rpcwallet.cpp I saw
senddata(const Array& params, bool fHelp)
I'm not sure why your correspondent would think that. Certainly senddata must allow the user to provide a password for unlocking an encrypted wallet but there isn't any such requirement for getdata: https://github.com/foo1inge/datacoin-hp/commit/791125b901767b9dec40e04f6865181a3276395b#diff-e75eff0ce0dde388eddbe3173db85bd4R320Value getdata(const Array& params, bool fHelp) { if (fHelp || params.size() != 1) throw runtime_error( "getdata <hash>\n" "Returns base64 data from a given tx-hash.");
std::string strHash = params[0].get_str(); uint256 hash(strHash);
CTransaction tx; uint256 hashBlock = 0; if (!GetTransaction(hash, tx, hashBlock, true)) throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "No information available about transaction");
string data = tx.GetBase64Data();
return data; }
Or am I missing something fundamental? Cheers Graham Yes, this does baffle me. I thought data was stored without encryption, and that any other client could read it. We will have to redo the steps that the Apertus.io team went through to understand what went on. This seems to imply that the block explorer or DTCbrowser (or Apertus.io) must do some sort of decryption. I also wonder of they were using a client that could not do RPC for getdata. If I remember correctly the earliest datacoin-hp client could not do RPC. It was mostly for mining.
|
|
|
|
|