kenscho
|
|
August 03, 2016, 07:49:15 PM |
|
is this mine worth to mine?
|
|
|
|
|
|
|
|
|
"This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
ghostlander (OP)
Legendary
Offline
Activity: 1239
Merit: 1020
No surrender, no retreat, no regret.
|
|
August 12, 2016, 11:04:24 PM |
|
is this mine worth to mine?
Seems so. If there are people out there mining it, don't you think they do it for pure fun?
|
|
|
|
BitcoinNational
Legendary
Offline
Activity: 1470
Merit: 1010
Join The Blockchain Revolution In Logistics
|
|
August 21, 2016, 12:15:00 PM |
|
|
|
|
|
antp1114
Newbie
Offline
Activity: 26
Merit: 0
|
|
December 07, 2016, 05:17:40 AM |
|
So because the coin is neoscrypt now does this mean that no scrypt asics will work on it at all, including those usb scrypt asics?
|
|
|
|
ghostlander (OP)
Legendary
Offline
Activity: 1239
Merit: 1020
No surrender, no retreat, no regret.
|
|
December 09, 2016, 03:23:16 PM |
|
So because the coin is neoscrypt now does this mean that no scrypt asics will work on it at all, including those usb scrypt asics?
Indeed. I'm now aware of any FPGA implementations either. It's for GPU and CPU miners only.
|
|
|
|
SISAR
|
|
December 14, 2016, 08:17:57 AM |
|
Any development plans, a roadmap? If nothing else, one cool feature would bring more people back to this coin and there is already much to copy and paste from other projects, go for it.
|
|
|
|
cryptohunter
Legendary
Offline
Activity: 2100
Merit: 1167
MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG
|
|
January 20, 2017, 03:15:35 PM |
|
any word on this or hal? I think ghostlander is quite a good developer. Any word on these projects? I know for hal he is probably waiting for eth to go casper or get their POS rolling but what about this one?
|
|
|
|
ph4nt0m
|
|
February 01, 2017, 01:20:52 PM |
|
0.5 million buy yesterday on Cryptopia
|
|
|
|
hashrefinery
|
|
February 15, 2017, 10:00:25 PM |
|
0.5 million buy yesterday on Cryptopia
Cryptopia's PXC wallet has been disconnected from the network for about a month and despite me opening several tickets I don't think they have any intention of fixing it. The current status says they are delisting: https://www.cryptopia.co.nz/CoinInfo/?coin=PXC
|
Hash Refinery Pool http://pool.hashrefinery.com/ - Over 50 coins active on 15+ algos - Receive payouts in any listed coin or auto-conversion to BTC
|
|
|
allknowingeye
|
|
February 16, 2017, 07:07:59 AM |
|
I too filed several tickets with them, and provided them with nodes several times including my own full node which I was keeping open just so they could sync but never have seem to be able to connect any nodes which is bizarre to say the least. I am currently connected to 8 working nodes. This is very negative for the outlook on this coin. Who else is listing it currently?
|
|
|
|
|
ghostlander (OP)
Legendary
Offline
Activity: 1239
Merit: 1020
No surrender, no retreat, no regret.
|
|
February 17, 2017, 03:14:31 AM |
|
It's interesting why they have zero connections while I always have quite many. My seed nodes are online, too.
|
|
|
|
Newton90
|
|
February 17, 2017, 07:43:13 AM |
|
any exchange?
|
|
|
|
remistevens
|
|
February 21, 2017, 10:24:47 PM |
|
Sent Cryptopia a support request as I do have some PXC now stranded on their exchange. Seems odd. I downloaded and started a new wallet, it had no problem finding active connections and started syncing.
|
|
|
|
remistevens
|
|
February 21, 2017, 11:59:29 PM |
|
Here is what I heard from support:
"Unfortunately there is a significant difference between trying to sync a fresh wallet and an exchange wallet with hundreds if not thousands of addresses and thousands if not 10s of thousands of transactions. We have been trying to sync PXC for months and have determined it to be too unstable for an exchange as we can't even get it to sync to process withdraws for users. If the Windows wallet works we will be happy to sync one up and manually process you withdraws, but we will be proceeding with delisting PXC as planned."
Comments? I've never heard that before that a coin can be stable enough to support simple wallets, but not to support ones that have many addresses and transactions. . .
|
|
|
|
6436346346
|
|
February 22, 2017, 12:23:31 AM |
|
It's interesting why they have zero connections while I always have quite many. My seed nodes are online, too.
We have connections, that's not the issue, it does not sync, we have tried multiple Linux distrbutions, honestly we have tried every trick in the book, but we have no ide WTF is going on ./PXC getinfo { "version" : 60600, "protocolversion" : 60004, "walletversion" : 60000, "balance" : 0.00000000, "allpowmint" : 0.00000000, "newpowmint" : 0.00000000, "blocks" : 0, "connections" : 4, "timeoffset" : 0, "proxy" : "", "testnet" : false, "keypoololdest" : 1483344770, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00010000, "errors" : "" } 4 connections, but never syncs a block Debug Log: ThreadDNSAddressSeed started ThreadSocketHandler started ThreadIRCSeed exited ThreadMessageHandler started ThreadOpenAddedConnections started ThreadOpenConnections started trying connection 107.161.164.223:9555 last seen=-385478.5hrs last try=-413256.3hrs connected 107.161.164.223:9555 peer 107.161.164.223:9555 unknown, sending version using dual magic sent version message to 107.161.164.223:9555, version 60004, blocks=0, us=0.0.0.0:0, them=107.161.164.223:9555 137ms Flushed 7 addresses to peers.dat Added time data, samples 2, offset +0 (+0 minutes) received version message from 107.161.164.223:9555, version 60004, blocks=1296419, us=162.255.117.105:63309, them=107.161.164.223:9556 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 ResendWalletTransactions() received block a4c7dab99e2d71bcb2f5 height 1296419 ProcessBlock: ORPHAN BLOCK, prev=d0069601d37282bc2b71 received block 006e800301bbd850d7ba height -1 ERROR: CheckProofOfWork() : hash doesn't match nBits ERROR: CheckBlock() : proof-of-work verification failed ERROR: ProcessBlock() : CheckBlock FAILED received block bde2e3c86d87e869a4d7 height -1 ERROR: CheckProofOfWork() : hash doesn't match nBits ERROR: CheckBlock() : proof-of-work verification failed ERROR: ProcessBlock() : CheckBlock FAILED disconnecting node 107.161.164.223:9555 DNS seeds: 7 addresses loaded ThreadDNSAddressSeed exited trying connection 185.53.128.119:9555 last seen=-20.4hrs last try=-413256.3hrs trying connection 108.61.10.90:9555 last seen=-385478.5hrs last try=-413256.3hrs connected 108.61.10.90:9555 peer 108.61.10.90:9555 unknown, sending version using dual magic sent version message to 108.61.10.90:9555, version 60004, blocks=0, us=0.0.0.0:0, them=108.61.10.90:9555 connected 185.53.128.119:9555 peer 185.53.128.119:9555 unknown, sending version using dual magic sent version message to 185.53.128.119:9555, version 60004, blocks=0, us=0.0.0.0:0, them=185.53.128.119:9555 trying connection 162.217.250.114:9555 last seen=-385478.5hrs last try=-413256.3hrs trying connection [2a00:1768:1004::3ace:c493]:9555 last seen=-82.5hrs last try=-413256.3hrs connect() failed: 101 connected 162.217.250.114:9555 peer 162.217.250.114:9555 unknown, sending version using dual magic sent version message to 162.217.250.114:9555, version 60004, blocks=0, us=162.255.117.105:9555, them=162.217.250.114:9555 Disconnected 107.161.164.223:9555 for misbehavior (score=100) Added time data, samples 3, offset +0 (+0 minutes) received version message from 108.61.10.90:9555, version 60004, blocks=1296419, us=162.255.117.105:63351, them=108.61.10.90:9556 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 Added time data, samples 4, offset -1 (+0 minutes) received version message from 185.53.128.119:9555, version 60004, blocks=1296419, us=162.255.117.105:63349, them=185.53.128.119:9555 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 Added time data, samples 5, offset +0 (+0 minutes) nTimeOffset = +0 (+0 minutes) received version message from 162.217.250.114:9555, version 60004, blocks=1296419, us=162.255.117.105:63391, them=162.217.250.114:9556 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 trying connection 194.135.88.196:9555 last seen=-20.5hrs last try=-413256.3hrs trying connection 176.31.126.191:9555 last seen=-385478.5hrs last try=-413256.3hrs connected 176.31.126.191:9555 peer 176.31.126.191:9555 unknown, sending version using dual magic sent version message to 176.31.126.191:9555, version 60004, blocks=0, us=162.255.117.105:9555, them=176.31.126.191:9555 received block d0069601d37282bc2b71 height 1296418 ProcessBlock: ORPHAN BLOCK, prev=69f2a771c7989f8f43bf Added 383 addresses from 108.61.10.90: 4 tried, 386 new connected 194.135.88.196:9555 peer 194.135.88.196:9555 unknown, sending version using dual magic sent version message to 194.135.88.196:9555, version 60004, blocks=0, us=162.255.117.105:9555, them=194.135.88.196:9555 Added time data, samples 6, offset +0 (+0 minutes) received version message from 176.31.126.191:9555, version 60004, blocks=1296419, us=162.255.117.105:63436, them=176.31.126.191:9556 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 Added time data, samples 7, offset +0 (+0 minutes) nTimeOffset = +0 (+0 minutes) received version message from 194.135.88.196:9555, version 60004, blocks=1296419, us=162.255.117.105:63435, them=194.135.88.196:9556 ProcessSyncCheckpoint: pending for sync-checkpoint a4c7dab99e2d71bcb2f5cc29a1f89cb3530ec07b18bde2180e9a75aacf71ab61 received block 69f2a771c7989f8f43bf height 1296417 ProcessBlock: ORPHAN BLOCK, prev=894686eaac5cc27add3d trying connection 105.100.178.15:9555 last seen=-122.0hrs last try=-413256.3hrs Added 615 addresses from 176.31.126.191: 4 tried, 1001 new received block d68b9b5037ae7fe46c9a height -1 ERROR: CheckProofOfWork() : hash doesn't match nBits ERROR: CheckBlock() : proof-of-work verification failed ERROR: ProcessBlock() : CheckBlock FAILED received block 2b8311b65a5cbd1a7bea height -1 ERROR: CheckProofOfWork() : hash doesn't match nBits ERROR: CheckBlock() : proof-of-work verification failed ERROR: ProcessBlock() : CheckBlock FAILED disconnecting node 185.53.128.119:9555 Disconnected 185.53.128.119:9555 for misbehavior (score=100) connection timeout
If you have any ideas we will be happy to give it one more shot But we have a windows wallet syncing so we can process withdrawals once its fully synced so no one will lose and PXC as we are happy to manually process PXC withdrawals for our users.
|
|
|
|
SISAR
|
|
February 22, 2017, 08:11:53 AM |
|
If you have any ideas we will be happy to give it one more shot
It seems that you are on the wrong fork, there are few "PoW verification failed" errors at debug.log so you should shutdown and restart wallet with -reindex option. Or simply sync from scratch with a fresh, new, never used wallet.dat and when syncing is over shutdown wallet. Replace wallet.dat with the one you have been using at exchange then start wallet with -rescan option. There is also -upgradewallet option with Bitcoin, not sure if it exists for Phoenixcoin. And there are -checkwallet and -repairwallet options if I can recall correctly, check if those help.
|
|
|
|
remistevens
|
|
February 22, 2017, 02:04:29 PM |
|
If you have any ideas we will be happy to give it one more shot
I appreciate this. I love that Cryptopia offers some coin selections that can't be found elsewhere. PXC is the #1 reason i have an account there.
|
|
|
|
ghostlander (OP)
Legendary
Offline
Activity: 1239
Merit: 1020
No surrender, no retreat, no regret.
|
|
February 27, 2017, 03:45:56 PM |
|
received block a4c7dab99e2d71bcb2f5 height 1296419 ProcessBlock: ORPHAN BLOCK, prev=d0069601d37282bc2b71 received block 006e800301bbd850d7ba height -1 ERROR: CheckProofOfWork() : hash doesn't match nBits ERROR: CheckBlock() : proof-of-work verification failed ERROR: ProcessBlock() : CheckBlock FAILED Block a4c7dab99e2d71bcb2f5 height 1296419 is orphan because it's too far in the future. This is expected behaviour. However block 006e800301bbd850d7ba height -1 is a misreported height 1 actually because it's v1 with no height data in its coin base. This is a legacy Scrypt block. The reason why you get this error is because you've built your daemon from the master branch rather than the v0.6.6.0 release tag. There was an upgrade to NeoScrypt code in September of 2015, after the v0.6.6.0 release, which switched hash calculations to assembly code rather than reference C code by default. It seems the Scrypt part of 64-bit assembly code hasn't been tested good enough and may produce incorrect results. I suggest to turn it off and use the reference C code until I fix this bug. Just remove -DASM from your makefile, then delete obj/neoscrypt.o and obj/neoscrypt_asm.o, and recompile. obj/neoscrypt.o: neoscrypt.c gcc -O2 -fomit-frame-pointer -DSHA256 -DASM -DOPT -c -o $@ $^
obj/neoscrypt_asm.o: neoscrypt_asm.S gcc -DASM -DOPT -c -o $@ $^
|
|
|
|
allknowingeye
|
|
March 13, 2017, 11:22:55 AM |
|
So I guess this is dead then. Is there any exchange left, nor aware of one myself.
|
|
|
|
|