Waiting for a revised timeline for Anon - Navajo Coin
New wallet Released! Links updated on page 1
New Blockchain
New Website coming
X13 only 50,000,000
Fully POS
new wallet? this wallet is 2-3 weeks old -.- we are still waiting for the new wallet I can't even sync my wallet, I did everything exactly as instructed for the last wallet. me too . stop on 11491. Thank You for information. We will check this problem. Kind Regards - Navajo Coin Development Team please update the last wallet . let it like other coin's wallet : just download and no delete \create \copy\paste.............. copy your %appdata% file...(make a backup)1. Download the new wallet. 2. Download the block chain that soopy provided. 3 put that block chain in %appdata% conf. file and start wallet. If coins are not what you had before run repairwallet in console. still does not work I've done this so many times, I don't even keep count any more and just gave up. Hopefully a new wallet will be made to address this issue asap. Is this a new wallet? are you on PC, MAC, or Linux? PC. I'm using my wallet.dat and the conf file that is suggested. |
|
|
|
Waiting for a revised timeline for Anon - Navajo Coin
New wallet Released! Links updated on page 1
New Blockchain
New Website coming
X13 only 50,000,000
Fully POS
new wallet? this wallet is 2-3 weeks old -.- we are still waiting for the new wallet I can't even sync my wallet, I did everything exactly as instructed for the last wallet. me too . stop on 11491. Thank You for information. We will check this problem. Kind Regards - Navajo Coin Development Team please update the last wallet . let it like other coin's wallet : just download and no delete \create \copy\paste.............. copy your %appdata% file...(make a backup)1. Download the new wallet. 2. Download the block chain that soopy provided. 3 put that block chain in %appdata% conf. file and start wallet. If coins are not what you had before run repairwallet in console. still does not work I've done this so many times, I don't even keep count any more and just gave up. Hopefully a new wallet will be made to address this issue asap. |
|
|
|
|
Is this a Revo coin clone via try to limited hash per user? That didn't work too well with Revo, people just made more users to get around that restriction. Plus the dev on Revo isn't active after end of POW and wallet release.
|
|
|
|
Waiting for a revised timeline for Anon - Navajo Coin
New wallet Released! Links updated on page 1
New Blockchain
New Website coming
X13 only 50,000,000
Fully POS
new wallet? this wallet is 2-3 weeks old -.- we are still waiting for the new wallet I can't even sync my wallet, I did everything exactly as instructed for the last wallet. |
|
|
|
|
A review panel here and/or minimum requirements to post a new coin launch are some of the options to minimize all this stupid scam coins.
|
|
|
|
I am constantly geting this an my miner not mining. Can somebody help?
10:04:08:752 8cc got 75 bytes
10:04:08:752 8cc buf: { "error": "Block expired", "id": 1, "jsonrpc": "2.0", "result": null}
10:04:08:752 8cc parse packet: 62
10:04:08:752 8cc cannot find block data:
10:04:08:752 8cc {"error":"Blockexpired","id":1,"jsonrpc":"2.0","result":null}
10:04:08:752 8cc cannot convert blob data
10:04:08:757 8cc new buf size: 0
10:04:08:847 8cc got 76 bytes
10:04:08:847 8cc buf: { "error": "Invalid job id", "id": 1, "jsonrpc": "2.0", "result": null}
10:04:08:847 8cc parse packet: 62
10:04:08:847 8cc cannot find block data:
10:04:08:852 8cc {"error":"Invalidjobid","id":1,"jsonrpc":"2.0","result":null}
10:04:08:852 8cc cannot convert blob data
10:04:08:857 8cc new buf size: 0
10:04:09:112 8cc got 304 bytes
10:04:09:112 8cc buf: { "error": "Invalid job id", "id": 1, "jsonrpc": "2.0", "result": null}
{ "error": "Invalid job id", "id": 1, "jsonrpc": "2.0", "result": null}
{ "error": "Invalid job id", "id": 1, "jsonrpc": "2.0", "result": null}
{ "error": "Invalid job id", "id": 1, "jsonrpc": "2.0", "result": null}
10:04:09:112 8cc parse packet: 62
10:04:09:112 8cc cannot find block data:
10:04:09:112 8cc {"error":"Invalidjobid","id":1,"jsonrpc":"2.0","result":null}
10:04:09:117 8cc cannot convert blob data
10:04:09:117 8cc remove first packet 186
10:04:09:117 8cc new buf size: 186
10:04:09:117 8cc parse packet: 62
10:04:09:117 8cc cannot find block data:
10:04:09:117 8cc {"error":"Invalidjobid","id":1,"jsonrpc":"2.0","result":null}
10:04:09:122 8cc cannot convert blob data
10:04:09:122 8cc remove first packet 124
10:04:09:122 8cc new buf size: 124
10:04:09:122 8cc parse packet: 62
10:04:09:122 8cc cannot find block data:
10:04:09:122 8cc {"error":"Invalidjobid","id":1,"jsonrpc":"2.0","result":null}
10:04:09:127 8cc cannot convert blob data
10:04:09:127 8cc remove first packet 62
10:04:09:127 8cc new buf size: 62
10:04:09:127 8cc parse packet: 62
10:04:09:127 8cc cannot find block data:
10:04:09:132 8cc {"error":"Invalidjobid","id":1,"jsonrpc":"2.0","result":null}
10:04:09:132 8cc cannot convert blob data
10:04:09:132 8cc new buf size: 0
I'm getting a lot of those similar errors while mining of minergate. Make me want to go back to 5.1, even with the memory leak. |
|
|
|
|
So far working well on AMD cpu's, but not on my Intel cpu machines. The error pops up just like the other have experience. Is there an issue with Intel cpu? I running a couple core i5's....
|
|
|
|
How about updating the OP and putting the wallet link under the wallet info? Little thing like that are a plus. |
|
|
|
Use the debug console. Use the command "Setgenerate True X", with X being how many cpu thread you want to mine with. Best to keep one or two free for OS and Gpu mining. Mining from wallet crashes like Alex showed. I'm mining fine with the debug console. |
|
|
|
I'm glad there is some discussion going on here already.  The coin might end up dying in the end but people who bought the coin at least deserve a place to chat. A coin will only die if no one puts the effort to put real development into it, originality in features and good PR. Also, have a strong will to take FUD/criticism. |
|
|
|
Use the debug console. Use the command "Setgenerate True X", with X being how many cpu thread you want to mine with. Best to keep one or two free for OS and Gpu mining. |
|
|
|
This coin is worth to takeover.It's already on bittrex and even on bter.com.Saved a lot efforts to put on exchanges.
It's also on Poloniex also. A takeover and forking it is a must now to keep some form of momentum going for it. |
|
|
|
|
The original dev of DarkCash in my opinion is weak. Promise something and didn't deliver, then he locks his thread because he can't handle criticism/FUD which is a part of the crypto world. That just doesn't sound like someone that should lead a project period, let alone start another one.
|
|
|
|
|
Why do we have to compile the wallet and miner? That should have been done before launching the coin. -1 already for that.
How energy efficient is this compared to out algos? Hope this isn't like Aiden's Scrypt-OG which isn't really energy efficient compared to regular Scrypt.
Why does the qt wallet have a SC logo? Wouldn't it be Neo, NeoC or NC?
|
|
|
|
Stick with Darkcoin if you can deliver. Take your time and do it right. we just need regular updates.
Ya stick with Darkcoin. I think he meant DarkCash...lol |
|
|
|
does anyone know if dedicated pool has the latest wallet?
i still cant transfer out from dedicated. i hope they rectify it soon I withdrew from suprnova 24 hours ago and still no coins in my wallet. I made sure the transfer address is correct on the pool and wallet. Is there an issue with some of the pools? |
|
|
|
Here is the thing. Cloning stealthcoin with tor functionality and a new algorithm is the easy way out. But then it looks like I am abandoning this coin. So that is what I am saying for the investors who lost money because was asleep I can launch a stealthcoin clone with the tor functionality, build a mobile wallet, and go from there. However, the harder way is to build the tor functionality to the ConcealCoin clone which DarkCash really is.
I am asking the comunity's response in regard to this.
Eww, this was a clone to CNL, that just doesn't sound right. My honest opinion, stick with DRKC and fix/improve it. Trust me, you'll gain a lot of respect and credibility doing that than making another clone coin. |
|
|
|
The tor implementation is as follows:
I was going to first setup a tor relay node that you can enter in your wallet's socks5 network entry. Then I was going to look at stealthcoin's source and use it's implementation to add it to the coin. I was in the process of doing it until all this drama happened. It just takes some time as there are alot of files do edit.
Now here is the other option. Since you guys are sticking with me I was thinking of releasing another coin which will be a clone of stealthcoin (because it already has tor implemented) however, I will tailor the X13 algorithm back to X11. That way the tor implementation for DarkCash would be the relay nodes that could be used in conjunction to the new coin.
This coin will still get the anon transactions developed as that is also a real idea which is not far in reach. It is a lot to work on but I am trying to work with you guys. I will also open a moderated thread in the next few minutes.
So in short, your abandoning this coin? True, deadlines in the crypto world are tentative, but you should try to stick to them as close as possible. Making another clone coin just to get a feature that you can fork into this coin would be more respectable. Doing this might hurt your credibility. |
|
|
|
Isn't luffa part of the x* algos?
I might be wrong, but isn't the X series coins use Luffa-256 and not Luffa-512. Haha maybe. If its the same algorithm base though - the creation of miners and such for it shouldn't be that complicated. 256 jump to 512 is many folds more encryption. Not impossible, but more work. |
|
|
|
|
If power cost is an issue, then the Nvidia GTX 750ti is the way to go. But if power cost isn't an issue, then the AMD 280X/7970, 290 and 290X are the way to go.
|
|
|
|
|
Show Posts
