Looks like the network is forked and we're on the latest version:
"version" : 80701, "protocolversion" : 70002, "walletversion" : 60000, "blocks" : 922843, "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Thanks, richie@bittrex
Same here, looking at getpeerinfo it looks like the sync node is running 0.8.6.4 still?
|
|
|
Hey MrData
Thanks for the attempt however you do realise a checkpoint key change is a hard fork?
Please people do not update to this version as cryptsy and other places have not been notified.
I've prepared an update to ADTv2 which is a hard fork. fixes the forking issues, and fixes the POS to be frequent enough to allow the chain to actually move. I'll release it soon after more testing
Ahmed
Changing the checkpoint key isn't a hardfork as far as a coin functioning it just wouldn't accept checkpoints from the original key anymore but it would continue working otherwise; since the original owner hasn't been sending those checkpoints in 3+ months then it pretty much doesn't make a difference at all except giving people a coin that is checkpointed again and not giving people error messages. Both coins will follow the existing chain just fine and would only be an issue if one key checkpointed one fork of the blockchain and the other checkpointed another. If the people would rather you run the checkpointing server rather than me I will be glad to give you the checkpoint secret key or you can just change it again in your update (mine was just a quick update to get things working again for people, not necessarily a long term solution as I don't intend to be the ADT dev.)
|
|
|
I posted a quick updated version at https://github.com/Crypto2/AndroidsTokens_v2/releases/tag/v2.0.1.2The only changes from the last official version are: - Added new checkpoint
- Set new checkpoint and alert keys since the "official" checkpoint server has been down 3+ months.
- Bumped the version
- Added a DNS seed (if you are running a public node let me know and I'll add the IP.)
|
|
|
The warning about the checkpoint being too old is more likely referring to the hardened checkpoints contained in the source code (checkpoints.cpp) - it means the newest is more than 90 days old. It's a routine warning that many quiet/abandoned coins will see.
Nope, that message is specifically for the broadcasted checkpoints from the checkpointing node.
|
|
|
I will be happy to pay someone to get this thing going again. I own about 1bil and want to put another 5btc in.
It would be more than a shame to let it go. How much do we need to get cryptsy wallet up?
It sounds like whoever was running the checkpointing node just needs to start it back up, or give the key to someone else to run it. I already run a node so it wouldn't be a problem if you want that person to be me.
|
|
|
My connections died , could you give some nodes..
If you have an old peers.dat and have trouble, try deleting it before launching your client. It should pick up the master nodes within 30-60 seconds.
|
|
|
Whatever the connection is it came from BTCJam's email DB not Coinbase's; the email I got it at was only used there.
|
|
|
Some basic questions.
1) How much premine, or is there one? 2) There was a spots coin some time back by a fellow I think who worked in a cleaning industry or something. What is the relationship with this coin? 3) The idea of linking a coin to a commodity like silver is good, as long as it is done at a technical level, and not just marketing. Are there any plans to make a hard link between the coin and silver for example?
I'm curious too why the coin is so cheap. The market cap seems to be around 10 btc but it looks like a healthy coin. Can someone summarize any drama or news that a person looking at the coin might want to know about?
Thanks.
1) There was no premine in Spots. 2) Spots v2 is a continuation of Spots by a new team without the involvement of iGotSpots who made Spots v1 (who owns/owned a cleaning business.) It is the same blockchain but with a updated client. 3) It would be nice, but I don't think it would be possible to enforce with no silver holdings backing it or anything. It's a stable and established coin, it just doesn't have any "hype" making it more popular.
|
|
|
I designed PICISI a crowdfunding website that accepts fiat and cryptocurrency, do you think any of your tools would be fitting for my plan?
Yes, the CoinPayments buttons or API (depending on the level of integration you want) would work great. You can find more info, examples, and documentation at https://www.coinpayments.net/merchant-tools
|
|
|
Ours was accurate to within ~0.02 NOBL so all good here.
|
|
|
Thanks! Connecting and syncing now.
|
|
|
I already have those, in my debug.log every time it tries them the connection times out for both of them. Edit: Also I'm using the latest wallet from http://www.maxcoin.co.uk/, v0.9.3.1.
|
|
|
Anyone have any working nodes?
|
|
|
Hey everyone. I think I remember something about stake not working when the max stake age was infinite. We at FindCoin are having the same problem. Could you please tell us how you fixed the problem?
Maybe you didn't even have this problem. I can't really remember.
The fix for that is to set it to something besides infinite; or rewrite the code everywhere the max stake age is used to correct it to support infinite stage age/negative numbers.
|
|
|
0.2BTC Spots marketcap, what you talking about? )) 60$ demand for spots.
They are spamming that all over, it's not to Spots specifically.
|
|
|
Is Bittrex on the same fork as the Windows client in the OP? Withdrew from them hours ago but nothing has shown up.
|
|
|
|