Bittrex is delisting. Blockchain dead. Sorry day, but might as well sell, not like the trader even works anymore.
Well, Quatloo is still listed on Bittrex, and the Blockchain is still limping along. We just need a glimmer of hope from the Coin promoters / Dev if the trading software on the coin will live on... Any glimmers? |
|
|
|
Thanks Vegas, all is well with my wallet! Nice work.
HORT! U still kickin'? :-) |
|
|
|
It looks like Kees wallet for the Official block explorer is offline.
My nodes were connecting to this for the proper blockchain. Since this wallet is offline, my nodes are adding to the blockchain only from those wallets that are connected to my nodes ams1.midnightminer.net and ams2.midnightminer.net. There is a very good chance that the blockchain will fork again if miners and pools are not connected to my nodes while the Blockexplorer wallet is offline.
I need miners and pool operators to send me there IPs so we can keep the blockchain from forking again.
I am only showing 11 connections on my wallet, there must be more wallets out there to improve the health of the AMS network!
Official Block Explorer wallet is back online! We are still going strong! |
|
|
|
|
It looks like Kees wallet for the Official block explorer is offline.
My nodes were connecting to this for the proper blockchain. Since this wallet is offline, my nodes are adding to the blockchain only from those wallets that are connected to my nodes ams1.midnightminer.net and ams2.midnightminer.net. There is a very good chance that the blockchain will fork again if miners and pools are not connected to my nodes while the Blockexplorer wallet is offline.
I need miners and pool operators to send me there IPs so we can keep the blockchain from forking again.
I am only showing 11 connections on my wallet, there must be more wallets out there to improve the health of the AMS network!
|
|
|
|
How do I get myself on the correct chain? I'm asking because my getpeerinfo has both of your nodes and my debug.log file has aforementioned incorrect IP's?
That is a very good question! Here are some hints on how to find out it you are on the proper blockchain: Look in your debug.log file for an entry similar to this: SetBestChain: new best=5866b9dae8f1c2202e207a6368262cd90d24a1ddd0f84ce763d4796f356af74c height=354931 trust=75362873945850746141 blocktrust=6825786956 date=03/21/16 19:42:27
ProcessBlock: ACCEPTED
Then on http://www.amsterdamblockchain.info/ copy & paste the tx hash from the debug.log into the search box. If the result is a GREEN box such as this:  You are on the correct Blockchain. |
|
|
|
Update: I have both my nodes confirmed on the proper chain. ams1.midnightminer.net ams2.midnightminer.net We need the pool operators to please contact Keesdewit or myself ( I am volunteering to help) to confirm you are on the right chain and set up your wallets to limit the spread of orphan blocks on the p2p channel. If you have the following IP*, you are on the fork: Obsolete wallet: 54.88.159.85
176.31.53.252
81.47.172.176
*Note: I will update this post over the next few days with new IPs as they show up in the log file. Last Update: 2016-05-21 |
|
|
|
Kees,
Anything that I need to worry about?
large disconnects and reconnects are signs of forking. however there is no way to determine if you are on the fork or if you are just connected to a poisoned wallet. you should resync from scratch to see if that fixes the issue. if it doesnt fix the issue and you resync and see these messages still, there are larger problems and a wallet fix is needed from the dev That is what I suspected, just wondering if others are getting this as I seem to be a spur node over here in North America. My nodes where using the Bootstrap Kees supplied with the wallet update, but the wallets are sucking up CPU and I/O resources on my machines sorting through Orphan Blocks. So my temp solution will be, to have my nodes only connect to 1 or 2 nodes that I am certain are on the proper blockchain. Other wallets will be able to connect to my nodes, but I will only be updating from trusted nodes. This should help clean up some of the noise on the p2p network. I will post an update when my nodes are clean again. was that error message pulled out of the log file? Yes, in debug mode. debug=1 In amsterdamcoin.conf file. |
|
|
|
Kees,
Anything that I need to worry about?
large disconnects and reconnects are signs of forking. however there is no way to determine if you are on the fork or if you are just connected to a poisoned wallet. you should resync from scratch to see if that fixes the issue. if it doesnt fix the issue and you resync and see these messages still, there are larger problems and a wallet fix is needed from the dev That is what I suspected, just wondering if others are getting this as I seem to be a spur node over here in North America. My nodes where using the Bootstrap Kees supplied with the wallet update, but the wallets are sucking up CPU and I/O resources on my machines sorting through Orphan Blocks. So my temp solution will be, to have my nodes only connect to 1 or 2 nodes that I am certain are on the proper blockchain. Other wallets will be able to connect to my nodes, but I will only be updating from trusted nodes. This should help clean up some of the noise on the p2p network. I will post an update when my nodes are clean again. |
|
|
|
Kees, I am getting these messages in my Windoze and linux wallets: ************************
EXCEPTION: St9bad_alloc
std::bad_alloc
amsterdamcoin in ProcessMessages()
ProcessMessage(block, 177 bytes) FAILED
Postponing 154 reconnects
REORGANIZE
REORGANIZE: Disconnect 585 blocks; babc622bd7a19f025c2012518d1c1b8623711905c376e83b2b33148ae0f8a684..a59aee4dbdd5c54bcc216f22cff5a2e2e919fba07f10974bf5af18dfe035565d
REORGANIZE: Connect 320 blocks; babc622bd7a19f025c2012518d1c1b8623711905c376e83b2b33148ae0f8a684..e36fe0c3cf2c5dc70ad15a62a7a34074d8a6c00f6faabe7797e9317fc844782a
connect() to 87.79.96.5:61510 failed after select(): No route to host
connect() to 81.169.137.12:61510 failed after select(): Connection refused
ping timeout: 1200.006816s
connect() to 87.79.96.5:61510 failed after select(): No route to host
connect() to 81.169.137.12:61510 failed after select(): Connection refused
connect() to 87.79.96.5:61510 failed after select(): No route to host
connect() to 81.169.137.12:61510 failed after select(): Connection refused
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
C:\Coins\amsterdamcoin-qt\amsterdamcoin-qt.exe in ProcessMessages()
ProcessMessage(block, 435 bytes) FAILED
CheckBlock() : Skipping masternode payment check - nHeight 439044 Hash 8a07b1b5a87d0aa47805dc81653fee2a56359677c33f2f764420283a107a5be4
ProcessBlock: ORPHAN BLOCK 675, prev=6df60da7d1d5b30064eb248f9106393239f1ac36cfc4a9546855f6a2c9c27d69
SecureMsgScanBlock().
Found 3 transactions, 1 elements, 0 new public keys, 1 duplicates.
force request: block b425f0b81405bd2e20cc74bfbe7172c472232aabdd8d09e0dfe07bf6dda79c20
CheckBlock() : pindex is null, skipping masternode payment check
ProcessBlock: ORPHAN BLOCK 676, prev=b8b9e4d56d21f1b353b94ad1b0d3daa56d97622de4a152f982f536f29a60f026
SecureMsgScanBlock().
Found 1 transactions, 0 elements, 0 new public keys, 0 duplicates.
CheckBlock() : Skipping masternode payment check - nHeight 439044 Hash d88c8f7ed16badcbaf7c80a09c7d380b07f6a81130ec70e7a521b227ac8bd265
CheckStakeKernelHash() : using modifier 0xb4ff67d34e36a3d0 at height=440445 timestamp=2016-05-04 22:33:04 UTC for block from timestamp=2016-05-03 21:14:40 UTC
CheckStakeKernelHash() : check modifier=0xb4ff67d34e36a3d0 nTimeBlockFrom=1462310080 nTimeTxPrev=1462310080 nPrevout=1 nTimeTx=1462401200 hashProof=0026a1e50e79bd73d819ffc5b8ae067d633d82150a07177b3f7c5c81df0b1ec3
Postponing 1493 reconnects
REORGANIZE
REORGANIZE: Disconnect 338 blocks; d6540a4be04be825d09e53ba338cb48a95b3213ad78d8dba7d5990fa5fa21651..cd064d7800ab17b0193e00e0f705820f7932ca0be6e2c17887e460b5b99fc9fe
REORGANIZE: Connect 248 blocks; d6540a4be04be825d09e53ba338cb48a95b3213ad78d8dba7d5990fa5fa21651..ecc1a99e2b51684ac3d218f4c39d4f12692b13ff1ad3a7c3d83325d5c5121a13
CheckBlock() : pindex is null, skipping masternode payment check
FindStealthTransactions() tx: a7b84ee6e16008a3123039514afe48f2427bf84983ede7860fb4c89b86a80e45
CheckBlock() : pindex is null, skipping masternode payment check
FindStealthTransactions() tx: 57a11d8aa614d7c8c07c9dd8a7d4be29cdf4df3e05407229294ccbfde2830165
CheckBlock() : pindex is null, skipping masternode payment check
FindStealthTransactions() tx: 55884b7b8e7823c903ede7f04f09215b3d14e7f4d8f270575c2572aed82ec0da
CheckBlock() : pindex is null, skipping masternode payment check Anything that I need to worry about? |
|
|
|
|
Interestingly, today my Bitdefender (Antivirus/Anti-malware) software removed the Quatloo EXE.
Suddenly out of the blue, Quatloo is a thread to my computer... Hmmm.
Oh well, if I had the time to fiddle with it I would look into the issue, but I have other things to do.
Anyone else have Bitdefender block the EXE?
|
|
|
|
|
Wow! SKR is on an exchange!
I was mining this back in Sept. '15 and then just parked for a while.
Who was involved in getting this coin listed on an exchange? I am curious to know who else is interested in this coin.
This is a great step in the right direction to have this coin alive again.
|
|
|
|
Ok got my x11 asic. Now what? Well I guess for now if someone wants to make me an offer in fly for renting for 24 hours, and it seems fair, Ill do it. Its 384 MHs
Vegas
In this cases, 'fair' is very subjective  What would you consider fair? Thats the problem Goldtiger. Just got it brand new yesterday, and have no idea how much it can generate. Ill say generally I would expect "a few hundred fly". I dont have an exact number in mind. Vegas if u wana use it to support FLY then just mine for example at nicehash and buy with earned BTC Fly the FLY u bought u place 100% higher at market again this way u move marketprice upwards and u reduce POS inflation because the coins on market dont compete for POS after few weeks/months when u managed increase market price by 100% u can start consider restart your old model of sell some of them private like 25% below marketprice and use that income too to buy upwards this is a self sustaining circle Damn good advice. |
|
|
|
Dev last online on the 9th. Is it so difficult to comment on here ?
Maybe Dev is still recovering from the 'almost scammed on the Bittrex listing'. It would be enough to take the wind out of my sails. I say hold tight, things in our Real Life happen, so there may be a reason for the silence. If nothing happens in 3 months, maybe as a community we can do something with the coin. |
|
|
|
When turn on wallets - yobit, bittrex ?
I am having trouble with my Linux wallet, so I would assume exchanges may have issues with the new wallet. It is just a guess, as soon as I have time I will dig into my wallet compile issues. Just too busy these last few weeks. Well I guess there is finally a plus for being on windows then. Funnie! Linux wallet has succesfully compiled and updating on 2 different platforms (Amd64 & Arm). Midnightminer.net nodes will be back up once blockchain is sync'd |
|
|
|
When turn on wallets - yobit, bittrex ?
I am having trouble with my Linux wallet, so I would assume exchanges may have issues with the new wallet. It is just a guess, as soon as I have time I will dig into my wallet compile issues. Just too busy these last few weeks. |
|
|
|
|
'Dev' or 'Promoter' is staking their pre-mine coins, so unless someone buys in a minimum 10 000 EDRC you will most likely not receive any staking rewards as your weight is so low you will not have the opportunity to win the staking lottery on the blockchain.
Not sure how long this coin will maintain it's value if only the promoter is gaining on the staking.
|
|
|
|
Dead?
Define what you call 'Dead?' The coin has an active blockchain, has miners, and on an exchange. Other work in progress but nothing official yet. |
|
|
|
the last 3 digits of litecoin Why LTC, when we can use FLY? In my opinion, using LTC is not right. We are building our crypto, but relying on the other one somehow. LTC has a more 'random' volatile price fluctuation with less influence from FLY traders with a direct interest in the outcome of the draw. But the last 3 digits of the Hash of the last trade price would make the outcome more interesting and random-ish. |
|
|
|
Guys I have always looked out for the people that have trusted me. I dont like rumors, but Ill tell you facts, yobit I think is on its way out. Most of the small wallets are all in maintenance mode. They have not answered any tickets in weeks. I sent 3 tickets about xde2 that was fully working , and unchanged and they put it in maintenance mode. Dont say I didnt warn you. This is another Cryptsy. I give it about 7-10 days, maybe less.
Vegas
YObit may be suffering the same effect of maintaining many wallets similar to the outages at SafeCEX - https://safecex.com/ There site is in limp mode because of provider issues causing wallet problems. |
|
|
|
I have submitted 2 tickets to YObit, and notified Blacksmith on YObit Trollbox 2 days ago that the YObit wallet is on a forked or isolated blockchain.
My advice is to hold your AMS on the exchange until the issue is resolved.
OK. But what will happen with my "in the middle of nowhere" coins? In ticket I asked to cancel my withdrawal, but have no answer... What do you think, can it be cancelled? I am no expert on how exchange wallets are handled, but they should be able to get their wallet back onto the right chain assuming all other withdrawals have failed since the fork. If anyone else has a wallet on the same fork, those coins are gone once YObit re-aligns to the proper blockchain. If your coin failed to transfer, when YObit is back on the blockchain you should be able to xfer the coins. Theoretically. |
|
|
|
|
Show Posts
