DL'ed EXE, doesn't do anything just opens a command line window then closes. What gives?
You probably downloaded cryptonited. Download cryptonite-qt. |
|
|
|
Looks like an issue with the Windows Qt, I haven't seen it happen on Linux. I would say that 80% of development time was spent on cryptonited before we even moved onto making Qt work, so yes it may be a little buggy compared to cryptonited, especially on Windows, because there wasn't a whole lot of testing done on Windows. The issue should be solved in the next release.
No, it's common problem for both Windows and Linux, just checked it on Ubuntu 14.04 and exact same thing is happening. Until the ~/.cryptonite directory is deleted the Bitcoin-QT is messed up. Fix it for Linux and you'll fix it for Windows also. Yeah it was mentioned in this thread earlier actually, some how bitcoin-qt is trying to use the cryptonite data folder. Must be some sort of memory issue, catia will take a look at it when he's available. For now I guess the easiest fix is to just start Bitcoin with the datadir flag pointing to the right directory. |
|
|
|
|
Looks like an issue with the Windows Qt, I haven't seen it happen on Linux. I would say that 80% of development time was spent on cryptonited before we even moved onto making Qt work, so yes it may be a little buggy compared to cryptonited, especially on Windows, because there wasn't a whole lot of testing done on Windows. The issue should be solved in the next release.
|
|
|
|
We now have a basic block explorer available: http://minichain.infoStill seems a little bit buggy so go easy on it. |
|
|
|
|
@sbgyuff520: yes that looks correct.
|
|
|
|
The design looks very vulnerable to 51% type attacks, much more so than Bitcoin even. Wouldn't trust it with my money.
At least you have taken the time to come up with a reasonably valid criticism that is worth talking about. I believe what you are referring to is the Secret Chain Attack. Following quote taken from the weaknesses and attack vectors wiki page. The Secret Chain Attack
If an attacker had enough hashing power he could generate a fake chain in secret using the real proof chain but a fake account tree. He would need to out-pace the real mini-blockchain for a full cycle until there's no evidence left to indicate his account tree is fake and then start broadcasting the fake chain.
This wont affect older nodes who have been validating blocks for longer than the cycle of the mini-blockchain because they can detect the fake chain or simply ignore super long forks. In Cryptonite existing nodes will just stick with the chain they have if the origin point of the fork appears to be older than the cycle time.
So there's no way the attacker could trick existing nodes to accept his fake chain, but new nodes are still at risk. New nodes have no way of determining which is the valid chain because they have no history of what happened before the oldest block in the mini-blockchain. Using some sort of consensus mechanism is not perfect either.
Minimizing risk of attack success
If a new node detects multiple chains which originate from the same proof chain it can try to query other nodes for older blocks all the way to the block in which the competing chains diverged and if no one around has this long history (no one is required to have it) the user can either take a chance on the chain the nodes recieves first, or refuse to participate in the network until one of the chains has won the race.
The user will be warned when any type of fork longer than 24 hours is detected. The user could also manually point the node to the correct chain with the use of a community checkpoint. The community will release a new checkpoint as quickly as possible if this situation does arise. When the checkpoint is released new nodes will be able to safely join the network and help the other nodes work against the attacker.
Since this attack will only put new nodes at risk and since it will most likely never happen, let alone succeed, this strategy is an acceptable contingency plan for dealing with the attack. Worse case scenario is that new nodes have to wait until the situation has been resolved or wait until a new checkpoint is released which points to the real chain. Anyone already running a node would not be affected in any way.
In summary, this attack is unconcerning and unlikely for several reason:
* requires an incredible amount of hashing power
* requires that no one has historic blockchain data
* only nodes which haven't synced for more than a week are susceptible
* when all else fails new nodes can resolve the problem with a checkpoint
* attack will never succeed due to checkpoints and probably could never be profitable
|
|
|
|
Total coins 1.84 billion?
yes Isnt that alot? You think it will hold its value? It's amazing how people around here are all so used to the scam coins that when a fair coin comes out they can't compute it. The economics of pump and dumps is so common around here that people actually think 1.8 billion coins is some astronomical number. It will be 10 years before even half of all the coins are mined, so yes I think XCN will hold its value perfectly fine as long as nothing else goes wrong. |
|
|
|
Cannot for the love of me get the wallet to sync.
Try adding this to your conf file: addnode=125.114.199.168:8253 addnode=83.212.123.220:8253 addnode=49.83.144.209:8253 addnode=117.93.65.238:8253 addnode=27.192.114.47:8253 addnode=220.189.23.67:8253 |
|
|
|
Yes indeed we now have a 3rd XCN exchange. Just got the news from guys over at C-CEX.com: |
|
|
|
I just hope ocminer will soon add a pool on suprnova...
As for GPU miners, I'm pretty sure there is at least one, maybe even 2 private ones available
There is no reason that Dev doesn't develop one for himself since all algorithms are open source. He just doesn't release it. Shame on him. What is with all these accusations based on no evidence? It's like this place has become a bad drama. Shame on you. Agreed. This post from the dev also is indicative of not having one: https://bitcointalk.org/index.php?topic=167229.msg8113615#msg8113615Dev said he had opencl experience! and the testnet ran for months! and he didn't write a gpu miner just for fair ? wowowowow~~~~ Even more, opencl skill is not required since all the algorithms used are open source. He only need to write several lines of codes to enable GPU mining. Actually it was some what intentional to start off without a GPU miner, I wanted Cryptonite to be easy for the average desktop computer to mine in the beginning, so that everyone had a chance to get in on the action during the early phase of mining. But we should have a public GPU miner available any day now, and mining will become dominated by the people who have good GPU's. And to answer illodin's question in the post above this, we created a new PoW algorithm so that a GPU miner wasn't easy to create and because I felt that there needed to be a good multi-hash PoW algorithm that didn't use a bunch of obscure hashing functions. We had overhauled most other aspects of Cryptonite, so why stop at the PoW algorithm. |
|
|
|
I put 1,000,000 cryptonite coins that I mined, not 2million...quit changing my text.
Oh so ReRunRod also changed the text to 2 million did he? lol just look at his trust rating guys... nothing more need to be said. |
|
|
|
Im looking to sell 2,000,000 Cryptonite's for 20(400% below market price) satoshi each. Yes I mined it with a GPU.
There have only been 1.5 million XCN mined so far, do not trade with this scammer. |
|
|
|
|
Sorry about the website being down earlier folks, it should be working fine now.
|
|
|
|
It's not a DLL problem, I have all DLL's in the folder with cryptonite-qt.exe. Compatibility mode (Vista, Vista SP1/SP2, Server 2008 SP, 7 without SP) doesn't work too.
Well like I said I'm not sure what else you can try, it's weird that the error only appears for some people using Windows 8 but not others. We'll do our best to find a solution but let us know if you end up working it out yourself. |
|
|
|
Files may have modified my bitcoin %appdata% folder. Can anybody verify?
I know for sure that on Linux it wont mess with the bitcoin data folder. It's highly unlikely that Windows is any different, but I'm not 100% sure. |
|
|
|
I have some errors on Win7 x64 and the latest release of qt-binaries:
First error:
Assertion failed!
Program: F:\kryptowaluty\cryptonite\win64_cryptonite-qt_14073005.exe
File: trieview.cpp, Line 26
Yeah several people have reported that problem but we're not sure what the issue is since many people seem to be running it fine on Windows 8.0 and 8.1. What I would suggest is that you ensure you have all the Win64 DLL's in the same folder as the cryptonite-qt exe, and maybe try running it in compatibility mode if you still have problems. Other than that I'm not really sure what else you could try. |
|
|
|
|
Show Posts
