Holy Cryptsy Now QUARK / PTS / NXT / ZEIT is offline. And Apex is still online. Some coins are in maintenance mode for over 6 months. That one takes a bad end.
|
|
|
I was using 2.01
Been long time havent sync
Now i try to sync it got stuck at some block.
I try to download new 2.015 and copy blockchain into my folder /user/roaming/zeitcoin All my coins are gone... balance is zero.
What can i do... luckily i still have the backup of the /user/roaming/zeitcoin How can i update and sync successfully
Thank!
https://bitcointalk.org/index.php?topic=487814.msg9909181#msg9909181
|
|
|
The alert system, the github account and the checkpoint system is centralized and controlled by a few people. Alert/Checkpointing was the idea of SN (Szabono Nickoshi) - that guy who was premining 1M of his coins. Please tell me, what makes Bitcoin/Altcoin decentralized under these circumstances? It's like democracy - a big lie.
Cheers
|
|
|
NXT is centralized. There is no need for centralized checkpoints.
|
|
|
This would mitigate the attack, but it's not a good thing as it benefits the "rich" over the "poor".
I hardly think that would deter anyone who has investment in the coin. Just the same as with centralized checkpointing. Philosophy drops when money talks. Checkpointing is always centralized. Owners of the private master key (like theymos) are able to set checkpoints on demand. Cheers, Ray
|
|
|
really? meh.... why whould they pay?
Because of the safety and the future of CryptoCurrencies. If you are able to attack LTC testnet I would spend some bucks. (If you tell us how to reconstructing the attack) Cheers, Ray
|
|
|
You have to update. URGENT. Don't send any coins. Delete your blkindex 0001 etc... You are not up to date. There is a bootstrap on http://www.zeit-coin.net. Download it and copy it to your /user/roaming/zeitcoin ... directory. Wait one day and your're up to date. Old chain is not compatible anymore. That's the reason.
|
|
|
The solution is to raise the diff for POS Coins? (different algo?) I am thinking about a rollback system with wallet voting.
|
|
|
It seems the only exchange still trading Zeitcoin is Cryptsy, all others displayed on the Zeitcoin website donīt have ZEIT listed anymore... Mintpal doesn't exist it seems , usecrypto and atomic don't have Zeit listed.. I wish to buy a few 100K Zeit, yet cryptsy will hold them for god knows how long, yet there seems to be no other. Not a good sign I must say I now have 100K, but I cancelled the rest of my order, cuz cryptsy's not going to mint Zeit with my Zeitcoins!!! Any advice will be appreciated. Any member willing to sell 400K @ 0.4 LTC? (0.00000100 LTC) Thanks! Website is: www.zeit-coin.net not .com We are listed on 4 exchanges. Cheers, Ray
|
|
|
And a warning: most POW coins are not safe! it's easy to cheaply rent enough hashrate to attack a lot of coins with low to medium hashrate. Only the biggest ones are good.
Start with Litecoin Testnet If you are right, many honest coins will pay you a tax for your work. Cheers
|
|
|
Let's create a Hackcoin.
Everyone who is interested in POS security can download the wallet. Everyone who is interested in hacking can play around with it. The results could be useful for every honest coin.
We should never forget one thing: We are fighting against the system (banks and governments) - we are not fighting against decentralized digital currencies, am I right?
Some of us believe in what we are doing. The destruction of a random coin isn't the solution.
Cheers, Ray
I disagree. Hackcoin is what you get on a testnet. Go after real coins. That's where you have the most to learn. There is more to learn here than whether the OP can achieve a double spend. There is also information in the responses from the devs and the code they produce to compensate. Also, what are the responses from the exchanges, etc. There are many questions that can only be addressed by attacking the live system. It's still early in crypto. It's better to do this now while it can be done. When regulators step in to protect the system, it will be too late to learn this much. Agreed, Testnet is a solution - destroying active coins not. Cheers, Ray
|
|
|
What's the idea behind? Why did they set it to +/- 24h ? inline int64_t PastDrift(int64_t nTime) { return nTime - 24 * 60 * 60; } // up to 1 day from the past inline int64_t FutureDrift(int64_t nTime) { return nTime + 24 * 60 * 60; } // up to 1 day from the future My question is why do they think this fill fix the problem? I think there is no specific problem with apex (besides the lack of checkpoints and the cheap price which made it possible for me to buy enough to attack), it's more like a design thing of POS: everything is working as designed! You did not explain your hack. My first thought was timejacking, but tell us more I am really interested in make POS safer. Btw. a 1 day drift is a security hole. Another idea: You mint at a time (with a huge amount of coins) where nobody mints. But that's only possible with dead coins. Cheers, Ray
|
|
|
Other stuff than security? Seems you are not behind your coin. Features are not necessary.
Safe your coin, then you'll have time for the toys. Your post looks to me like advertising.
Cheers, Ray
PS: Your sig... Paycoin. It says all.
|
|
|
Let's create a Hackcoin.
Everyone who is interested in POS security can download the wallet. Everyone who is interested in hacking can play around with it. The results could be useful for every honest coin.
We should never forget one thing: We are fighting against the system (banks and governments) - we are not fighting against decentralized digital currencies, am I right?
Some of us believe in what we are doing. The destruction of a random coin isn't the solution.
Cheers, Ray
I already have a POS only Coin running on a live network but not sure if I want to do this. I have local connection problems need resolving but network running smoothly. Explain? Why not? Do ya think you're the next?
|
|
|
First thing you should do: lower the nMaxClockDrift to 10 or 5 minutes. It's not the final solution, but it's a beginning. If anyone is in touch with roboguy: zeit@zeit-coin.netTogether we will find a solution - I'm sure. Cheers, Ray Edit: kiklo wants to help you. What's the problem?
|
|
|
Let's create a Hackcoin.
Everyone who is interested in POS security can download the wallet. Everyone who is interested in hacking can play around with it. The results could be useful for every honest coin.
We should never forget one thing: We are fighting against the system (banks and governments) - we are not fighting against decentralized digital currencies, am I right?
Some of us believe in what we are doing. The destruction of a random coin isn't the solution.
Cheers, Ray
|
|
|
What's the idea behind? Why did they set it to +/- 24h ? inline int64_t PastDrift(int64_t nTime) { return nTime - 24 * 60 * 60; } // up to 1 day from the past inline int64_t FutureDrift(int64_t nTime) { return nTime + 24 * 60 * 60; } // up to 1 day from the future
|
|
|
Zeitcoin has 2*60*60 = 2h Apexcoin has 24*60*60 = 24h inline int64_t PastDrift(int64_t nTime) { return nTime - 24 * 60 * 60; } // up to 1 day from the past inline int64_t FutureDrift(int64_t nTime) { return nTime + 24 * 60 * 60; } // up to 1 day from the future Zeitcoin static const int64 nMaxClockDrift = 2 * 60 * 60; // two hours Clients with a (wrong) system time +/-1 day are able to confirm blocks. That's an issue. An attacker has a big window for timejacking or whatever. Blackcoin (New rules) Past limit: time of last block Future limit: +15 seconds Granularity: 16 seconds Expected block time: 64 seconds Related: https://bitcointalk.org/index.php?topic=604716.msg7140466#msg7140466I think we should change it: static const int64 nMaxClockDrift = 5 * 60; // five minutes It's not the final solution, but it feels better, eh? ....
|
|
|
I am sure he's talking about the time drift (of clients). Has nothing to with POS. Your client is valid one if he meats the 24h time window. He wants to lower the time drift to 5 mins.
In simple words: If your system clock is wrong (<24h) you are a valid client to confirm blocks.
Thats why higher blocks sometimes have an earlier timestamp as the blocks before,.
|
|
|
Centralizing is no solution, it's the contrary. I did not post anything about this silly CPS idea. But let us play with the time drift scenario. I don't understand the advantage of it. Can anyone explain?
|
|
|
|