I hear buying this coin is a good way of throwing away money
Right in the bulls eye  Still listed on polo though eh? |
|
|
|
Am I the only one so far that has noticed an inconsistency with the clock on zpool's website at the upper right corner?
For instance; It says next payout 15:52 EST; But I am presently at 5:09 PM Pacific time (17:09PST) which is -3 hours from EST. And a payout was just processed:
1m ago 0.00155413 3e1707c0ea8272eb1b12502130286d55e54f...
Payouts are every hour, `around` the same time. The time listed right now is 21:08 EST. It's approximate as there could be other background tasks running. It's looks ok from where I am... |
|
|
|
Have you tried with nodes listed on this page? What blockheight it is stucked at anyway?
Yup, tried with all them. It doesn't even load 1 block... I can not help you more, my Win7 node is working just fine and I am out of troubleshoting solutions. Check https://cryptocointalk.com/forum/186-phoenixcoin-pxc/ developer seems to be there more often than here. Thanks, I posted there and hope they see it. |
|
|
|
|
Just wondering if the dev can tell me why when my pool submits the block to my wallet, that it crashes:
ThreadRPCServer method=submitblock
******* exception encountered *******
./diamondd[0x550fbc]
./diamondd[0x425519]
./diamondd[0x42ae58]
./diamondd[0x48c090]
./diamondd[0x4bb2d8]
./diamondd[0x506e49]
./diamondd[0x4d5c4e]
./diamondd[0x4d96db]
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0(+0x10bc5)[0x7f9394d18bc5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76aa)[0x7f9393e916aa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9393325eed]
Any idea how to fix this? I'm using Ubuntu 15.10
|
|
|
|
Hello pool admin!
I was messing around with Groest since there were no blocks found yet, it looks like the port changed from 5033 to 5333. 5033 is still up but it shows 5333 in the pool section. Are you switching over to 5333? thanks
hrmm! Sorry yes, it should be on 5333. Can you try it now on the proper port? Thanks! |
|
|
|
|
Crypty's prices are inflated because people are buying the alts as it's the only way to get their money (BTC) out of Cryptsy. They've had ongoing withdraw issues for BTC/LTC/BTCD and a few others. I would never suggest Cryptsy and in fact, over the past 2 weeks, I've stripped Cryptsy out of my pool's trading scripts due to so many problems.
|
|
|
|
|
HI have submitted MBL to any other exchanges? Would love to see it on bitt/polo/bleu or yobit!
Thanks!
|
|
|
|
I have not got a clue, must wait for Ghost
i use this
thread-pool-size=4
steady-thread-pool-size=4
rpcthreads=4
waiting-thread-count=4
Ok, I'll see if that makes a difference. How it is a solution for paying out in ORB? If I could get this submitblock issue fixed my pool would payout in ORB. The way it works, is if you are mining using an ORB address... blocks found on ORB will get applied to your mining efforts but it required that we can actually find blocks! hopfully the dev can see something and point me to a solution. The other neo coins I have work as I expect... |
|
|
|
I have not got a clue, must wait for Ghost
i use this
thread-pool-size=4
steady-thread-pool-size=4
rpcthreads=4
waiting-thread-count=4
Ok, I'll see if that makes a difference. |
|
|
|
Okay, seems like the problems are now sorted out?
So what is going on with the dividends?
Without paying dividends this Coin is going nowhere, because there are already 1500000000 Coins which have the same use as Amber now. Absolutely NO use!
Only problems now are the exchanges are not on the right chains and are in maintenance. |
|
|
|
HI, Thanks for the update and coind email. We've updated our wallet and are back mining successfully on www.zpool.caCheers! |
|
|
|
Hi, We've added ORB to the miners multipool: www.zpool.caCheers! works good! Thanks I'm interested in this function "You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk" The problem is when I use a ORBitcoin address like these oWop3vTAU8V6dwgcJppqggoakJHiSLJiKE, I get Omnicoin but I want ORB. You will receive 250 ORB if after six months if you solves probelm  ! because I want to have it permanently! Still working though some issue with ORB. It seems that it won't generate block. Does anyone know what the problem might be: ThreadRPCServer method=submitblock ******* exception encountered ******* ./coind/orbitcoind[0x54073b] ./coind/orbitcoind[0x41fb9e] ./coind/orbitcoind[0x42492a] ./coind/orbitcoind[0x4f4bd0] ./coind/orbitcoind[0x4fb4c0] ./coind/orbitcoind[0x4c69ce] ./coind/orbitcoind[0x4ca286] /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0(+0x10bc5)[0x7fbb98366bc5] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76aa)[0x7fbb974df6aa] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbb96973eed] Thanks! |
|
|
|
|
Can someone post up their node if there are different from the ones posted above? Would like to get more than 2 nodes connect just for stability.
Cheers!
|
|
|
|
At least the 3 of us are on the same chain At least 53 wallets are on the same chain  Please check yours. 616127 "proofhash" : "00002458b29e384c08c1ed4876a682d5f378ecbba4b3b12484ec0679ac2aead3" I 'm on the same boat, "proofhash" : "00002458b29e384c08c1ed4876a682d5f378ecbba4b3b12484ec0679ac2aead3", 20:51:34  getblockbynumber 616127 20:51:34  { "hash" : "4bed68fcb27565f4b1339942e4b6a41e051251c386796c96049c1a02f48a9956", "confirmations" : 1716, "size" : 410, "height" : 616127, "version" : 6, "merkleroot" : "87d98d220a99a5d7b7b748de1777c84fee0fab814f7ed5edc5095e6d76834b14", "mint" : 0.77997260, "time" : 1449430052, "nonce" : 0, "bits" : "1d0542f9", "difficulty" : 0.19005293, "blocktrust" : "30a77fa2", "chaintrust" : "543c94f153bee3", "previousblockhash" : "0a6e7d877a35b04d9f1745aff9785782d654275cf5ead9dca5ec1c5cca13f1b3", "nextblockhash" : "7bd13577b234e4889c66c5465633543c42096a1c8cf8a3b3390ee20c0f96d1ae", "flags" : "proof-of-stake", "proofhash" : "00002458b29e384c08c1ed4876a682d5f378ecbba4b3b12484ec0679ac2aead3", "entropybit" : 0, "modifier" : "7bb24f2b872edd1c", "modifierchecksum" : "8e716432", "tx" : [ "49df935763520bc6ce52a138200a947f7d924c0ac973fb06a574e522370fb1bc", "4cf1214a41581f849bba79320115daea2c8ebe2c64247d5edb2d5e2e409660df" ], "signature" : "30440220455eeb7bc169b13612bf4b5fd808f62425f9c73313c389ede3cb5303c56360ef0220596 8ccc326f6b1956e5e03079b0d3ca2406329983246156fb0d34b05cfb6f12f" } Still on this one as well. |
|
|
|
It looks like your profit estimates are way off. They are approximately one half of the other guy.
This problem started around midnight last night on all algos and is plainly visible in the pool estimate graphs.
Thanks we'll look into it! Seems some algos are and some arn't... Estimates are still off. I compared some coins with the other clone and you're both reporting the same block size and difficulty but your profit estimates are 60% to 75% of the competition on most algos. I'm convinced the problem is with zpool because the profit estimate for all algos took a sudden drop at the same time while the other pool's estimates continued the same trend. Looks like they should be sorted out. Part of the problem was with c-cex integration so I've disabled that for the time being. |
|
|
|
Have you tried with nodes listed on this page? What blockheight it is stucked at anyway?
Yup, tried with all them. It doesn't even load 1 block... |
|
|
|
Cryptsy.com via freshdesk.com
4:21 AM (7 hours ago)
to me
Hello Makis,
MZC is now back online.
You can now process transactions.
Have a great weekend!
Sincerely,
Phoebe
Cryptsy.com Yay *edit: that also made price moving! yayay! I'm still missing thousands from deposits. It may be back online... but they didn't give anyone their MZC that was sent before they dropped the wallet offline. |
|
|
|
My pool's wallet had 8 peers now and stable for more than 24h now! No fork, few orphans... seems good for the moment. Keep crossing my fingers! Join now ! Seems like the network is now more stable now since it is more peer to peer and not a lot of people using 'connect' to centralize the network on one or two peers. I've been on the correct chain for days and have 17 connections Can you post your peers? I can never get more then 3 or 4... |
|
|
|
I can't seem to sync the chain...
ProcessSyncCheckpoint: pending for sync-checkpoint 8556823b9fe456185feeb6456941361dcafb334623f8bba9e0ebfd12b1d2a996
ProcessSyncCheckpoint: pending for sync-checkpoint 8556823b9fe456185feeb6456941361dcafb334623f8bba9e0ebfd12b1d2a996
ProcessSyncCheckpoint: pending for sync-checkpoint 8556823b9fe456185feeb6456941361dcafb334623f8bba9e0ebfd12b1d2a996
ProcessSyncCheckpoint: pending for sync-checkpoint 8556823b9fe456185feeb6456941361dcafb334623f8bba9e0ebfd12b1d2a996
Keeps saying lots of that...
First of all, make sure you are using the latest wallet. If problem is still present then just run wallet once with -reindex option. Once reindexing is over you can also run it once with -rescan option. I just pulled from git last night so assuming it has to be the latest "version" : 60600, I'll try... but it's got no blocks already so nothing to re-index... seems to be doing just the same thing... |
|
|
|
|
Still on the right chain?
$ ambercoin-cli getblockbynumber 615387
"hash" : "0000000004cd0f7ab0374ac660eda8b98be2582bb7ebb260aa4c7541456900c0",
"proofhash" : "0000000004cd0f7ab0374ac660eda8b98be2582bb7ebb260aa4c7541456900c0",
"tx" : [
"04ad6129e5eecd0284b5e59d96e62ce400c522cdd01c3f4bd7dfe376285c87c2"
|
|
|
|
|
Show Posts
