[ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3 - page 30.

bholzer

hero member

Activity: 490

Merit: 510

The Murraycoin Project ▪ Lead Developer

Quote from: r3wt on August 09, 2013, 04:31:38 AM

well i bought 930 PHS yesterday from Moray, and now they are all showing up as "unconfirmed" could this mean they are being orphaned? if they get orphaned i will be opening a scam accusation against Moray unless he either a) reimburses my 6 ltc i paid or b) sends me 930 PHS to replace the orphaned transaction. this whole thing is pissing me off. what the fuck!!!

I wouldn't jump to conclusions just yet -- obviously there are some issues going on here but until they're all sorted out we can't assume anything. It's possible once everything syncs up your transaction will be confirmed and you'll be good to go.

In other news...after closing and opening the wallet a few more times over the course of an hour...I'm now up to block 6155. Right now it says 6155 of 8119 but moments ago the total was different (it's bouncing back-and-forth there as well.) It's been sitting at 6155 now for about 25 minutes...although the "blocks remaining" are continuing to increase.

r3wt

hero member

Activity: 686

Merit: 504

always the student, never the master.

johntawaki

member

Activity: 65

Merit: 10

I passed 6084 without problem:

Quote

updateWallet 2007cfcf27483e905fea451e2dfc76d4f2c506c76c293fa955561d422f0686bd 1
inWallet=1 inModel=1 Index=28-29 showTransaction=1 derivedStatus=1
SetBestChain: new best=acecf0d67c9c6d7b384fe49c1fe6348d3ea226e2a563d44d1d77665cb8f2dfbb height=6140 trust=262361452 date=08/09/13 09:05:20
updateWallet 6f40e1448b358ce68358c1ec389290512abe90d152c6030715147dab62291b57 0
inWallet=1 inModel=0 Index=84-84 showTransaction=1 derivedStatus=0
ProcessBlock: ACCEPTED
received getdata for: block acecf0d67c9c6d7b384f
received getdata for: block acecf0d67c9c6d7b384f

could it be just slow?

This is what I observed on block 6084: this apparently the separate point of new and old client. After this point, all the blocks generated by the old client will be rejected, there's apparently a chain of 200 blocks or so that have been rejected, so it will stuck at this point for a while, until it find the new chain, where the old chain will become orphans.

Once this is done, it will process normally for the new chain

Quote

ProcessBlock: ORPHAN BLOCK, prev=00000000126837e34347
received block 00000000108bb4c975db
ProcessBlock: ORPHAN BLOCK, prev=0000000053bbe2178c7b
connection timeout
trying connection 182.239.230.164:16281 lastseen=138.9hrs
connection timeout
trying connection 158.132.219.184:16281 lastseen=285.8hrs
connection timeout
trying connection 203.57.147.2:16281 lastseen=152.6hrs
received block 000000016d8926ec64f7
ProcessBlock: ORPHAN BLOCK, prev=0000000035b50c124496
received block 1dab565bfe7338a7cd5f
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake c68e79417006495ae4ba51f2675444373ce2a3a916f973f79ea3202c568f984b, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 1dab565bfe7338a7cd5f7f220e971ad15e28586fc4f2b2ca32dcbd92d4d141a1
connection timeout
trying connection 68.81.64.95:16281 lastseen=147.2hrs
connection timeout
IRC connect failed
IRC waiting 138 seconds to reconnect
>> Wallet: abnCredit = 130112328
CPUMiner : proof-of-stake block found 583424f9ed03839faf51ed8a12e89f96b4deaad536b4b5264f06270edb949561
BitcoinMiner:
new block found
  hash: 583424f9ed03839faf51ed8a12e89f96b4deaad536b4b5264f06270edb949561
target: 00000fffff000000000000000000000000000000000000000000000000000000
CBlock(hash=583424f9ed03839faf51ed8a12e89f96b4deaad536b4b5264f06270edb949561, ver=4, hashPrevBlock=e9d82503dabb0634437a090efbe810c25f903ddfe38ba0d6b1e2684a4eef57c2, hashMerkleRoot=15cc17c035abda2f22de982cf7d1d0b931119d0864a03122fd38f30bbdec7f5d, nTime=1376036592, nBits=1e0fffff, nNonce=0, vtx=2, vchBlockSig=30450220163dc02d986a6b1d62e93ff77156110a9d67d0a0674480015ef21f6d66b8ee41022100b81eb83834184caaf9b7d66744f8c97a47ea470fdfd527d8ecb687cd02806b6d)
  Coinbase(hash=ca1839f753, nTime=1376036592, ver=2, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, 4294967295), coinbase 02c617012b062f503253482f)
   CTxOut(empty)
  Coinstake(hash=bba82f4672, nTime=1376036592, ver=2, vin.size=1, vout.size=3, nLockTime=0)
   CTxIn(COutPoint(965430ab9f, 0), scriptSig=3046022100fa494300f3bfac)
   CTxOut(empty)
   CTxOut(nValue=65.05, scriptPubKey=03e302fe2a9b8121c4f082b70d74646321be4204f89070fa83e2c83ccdec5d03d3 OP_CHECKSIG)
   CTxOut(nValue=65.062328, scriptPubKey=03e302fe2a9b8121c4f082b70d74646321be4204f89070fa83e2c83ccdec5d03d3 OP_CHECKSIG)
  vMerkleTree: ca1839f753 bba82f4672 15cc17c035
generated 0.00
connection timeout
AddToWallet bba82f4672 new
WalletUpdateSpent found spent coin 128.00PHS 965430ab9fc2abcb89c7aac0a924fb7a2f7dfefe7fd539f4311de60323700524
NotifyTransactionChanged 965430ab9fc2abcb89c7aac0a924fb7a2f7dfefe7fd539f4311de60323700524 status=1
NotifyTransactionChanged bba82f4672502976b85e209b987477359c2b8213a0c7948d0a71b3b7ba516bb4 status=0
updateWallet 965430ab9fc2abcb89c7aac0a924fb7a2f7dfefe7fd539f4311de60323700524 1
   inWallet=1 inModel=1 Index=85-86 showTransaction=1 derivedStatus=1
updateWallet bba82f4672502976b85e209b987477359c2b8213a0c7948d0a71b3b7ba516bb4 0
SetBestChain: new best=583424f9ed03839faf51ed8a12e89f96b4deaad536b4b5264f06270edb949561 height=6086 trust=2103239 date=08/09/13 08:23:12
   inWallet=1 inModel=0 Index=122-122 showTransaction=1 derivedStatus=0
ProcessBlock: ACCEPTED
trying connection 111.161.70.15:16281 lastseen=150.2hrs
received getdata for: block 583424f9ed03839faf51
>> Wallet: abnCredit = 130139726
CPUMiner : proof-of-stake block found 170c2bbc594261a38d3785381f62ebf4003d62d1a5e90a0af62dfcb52620a48d
BitcoinMiner:

r3wt

hero member

Activity: 686

Merit: 504

always the student, never the master.

johntawaki, could you possibly just upload a copy of the blockchain to get us past this problem? if you are not sure what to do to fix the client, might i suggest contacting muddafudda. he's really good at working out these kinds of problems.

r3wt

hero member

Activity: 686

Merit: 504

always the student, never the master.

Quote from: bholzer on August 09, 2013, 03:56:37 AM

Quote from: sheinsha on August 09, 2013, 01:50:23 AM

And it wont go past "blocks" : 6084, !!!

After following the above steps, I'm hanging on block 6084 as well.

ok, i got stuck at block 5500. closing and reopening the wallet got it to 6084 and now i'm stranded here as well. could it be that i need to have the addnodes in the conf file? i'm not mining FWIW, but i did buy 930 phs yesterday for 6 LTC, and i will be pissed if this doesn't get resolved.

r3wt

hero member

Activity: 686

Merit: 504

always the student, never the master.

Quote from: johntawaki on August 09, 2013, 03:30:23 AM

sorry some people have issues. I don't have any problems to sync my wallets. It seems that some people still use the old client thus may created a forked chain.

If you have sync problems, please do this:
1. Make sure you use the Version 1.2 client, or compile from the latest source code in the github.
2. In the config dir, delete all file except wallet and philosopherstone config file, you can leave the peers.dat if you want, then restart the client, it will sync from the scratch, and it should work.
** Please make sure you do not delete wallet.dat file **

No need to patch wallet files etc, it should not have problems. The worst you can see are some orphaned blocks which should be OK.

Also please note that the sync can be slow sometimes, because of the generations and sync of the PoS blocks. A lot PoS blocks are generated as we are entering the PoS generation period...

i'm hanging on block 5500 of 6084

bholzer

hero member

Activity: 490

Merit: 510

The Murraycoin Project ▪ Lead Developer

Quote from: sheinsha on August 09, 2013, 01:50:23 AM

And it wont go past "blocks" : 6084, !!!

After following the above steps, I'm hanging on block 6084 as well.

bholzer

hero member

Activity: 490

Merit: 510

The Murraycoin Project ▪ Lead Developer

Quote from: johntawaki on August 09, 2013, 03:30:23 AM

sorry some people have issues. I don't have any problems to sync my wallets. It seems that some people still use the old client thus may created a forked chain.

If you have sync problems, please do this:
1. Make sure you use the Version 1.2 client, or compile from the latest source code in the github.
2. In the config dir, delete all file except wallet and philosopherstone config file, you can leave the peers.dat if you want, then restart the client, it will sync from the scratch, and it should work.
** Please make sure you do not delete wallet.dat file **

No need to patch wallet files etc, it should not have problems. The worst you can see are some orphaned blocks which should be OK.

Also please note that the sync can be slow sometimes, because of the generations and sync of the PoS blocks. A lot PoS blocks are generated as we are entering the PoS generation period...

Mine syncs fine up until about 75% (currently 2007 blocks remaining...but that number just slowly bumps up as more blocks are found.) It's been sitting here making no progress for about 10 minutes at block 6084 (right now it's 6084 of 8091.)

johntawaki

member

Activity: 65

Merit: 10

sorry some people have issues. I don't have any problems to sync my wallets. It seems that some people still use the old client thus may created a forked chain.

If you have sync problems, please do this:
1. Make sure you use the Version 1.2 client, or compile from the latest source code in the github.
2. In the config dir, delete all file except wallet and philosopherstone config file, you can leave the peers.dat if you want, then restart the client, it will sync from the scratch, and it should work.
** Please make sure you do not delete wallet.dat file **

No need to patch wallet files etc, it should not have problems. The worst you can see are some orphaned blocks which should be OK.

Also please note that the sync can be slow sometimes, because of the generations and sync of the PoS blocks. A lot PoS blocks are generated as we are entering the PoS generation period...

sheinsha

sr. member

Activity: 434

Merit: 250

lets wait for the dev to check my issue so i can restart the pool...
But this is soo weird, it has never happened to me before

bholzer

hero member

Activity: 490

Merit: 510

The Murraycoin Project ▪ Lead Developer

Quote from: digeros on August 09, 2013, 02:44:02 AM

Quote from: bholzer on August 09, 2013, 02:38:24 AM

Something is definitely screwed up -- I'm shutting down the mining until it's straightened out. I added the original nodes back in...lost some coins...some coins moved from balance to stake...difficulty continues to just jump around like crazy (like I mentioned yesterday, sometimes dipping down as low as 0.0002xxx) -- I'll wait until it blows over. In the meantime, the people that are rocking and rolling should get hooked up with a low difficulty.

I've been on 1.2 since it was posted -- a bit concerned.

wow hate to say it but you may have mined on an aborted Fork... I did that on Bit bar.. and when I reloaded the blockchain my mined blocks... were gone without a trace... spooky I know. But coins that move from balance to stake are now minting stakes that will pay dividends... Much better than coins that evaporate--- read up on POS coins and commands like walletpassphrase and reservebalance - peace digeros

I read up on PoS just yesterday, actually, to make sure I got it all down. What is strange is that there are a handful of coins that just juggle back-and-forth between stake and balance each time I load up the wallet. I've been using 1.2 the entire time and I've been using the 4 nodes provided in the thread. I have also been solo-mining exclusively for the past several days.

It will appear up-to-date...then at random it will show as being 15 - 20 blocks behind...but it never catches up. After a few minutes...it just jumps back to being "up-to-date" (but it never did catch up.) This happens over-and-over. I've tried the extra nodes...tried a brand new wallet on a new machine. It's more trouble than it's worth right now, I suppose. We'll see how it plays out.

Hopefully I don't lose out on everything I've mined since I switched to 1.2 -- that's the only change I've made since I started mining PHS and I immediately started getting some strange issues (although this is definitely the worst it's been.)

sheinsha

sr. member

Activity: 434

Merit: 250

The weird thing is i have wiped every trace of Philosophestone from the server, re cloned from github, compiled, and started with fresh wallet, and it crashes at block 6084/6085

Is there any cache or something im missing?

digeros

sr. member

Activity: 280

Merit: 250

Quote from: bholzer on August 09, 2013, 02:38:24 AM

Something is definitely screwed up -- I'm shutting down the mining until it's straightened out. I added the original nodes back in...lost some coins...some coins moved from balance to stake...difficulty continues to just jump around like crazy (like I mentioned yesterday, sometimes dipping down as low as 0.0002xxx) -- I'll wait until it blows over. In the meantime, the people that are rocking and rolling should get hooked up with a low difficulty.

I've been on 1.2 since it was posted -- a bit concerned.

wow hate to say it but you may have mined on an aborted Fork... I did that on Bit bar.. and when I reloaded the blockchain my mined blocks... were gone without a trace... spooky I know. But coins that move from balance to stake are now minting stakes that will pay dividends... Much better than coins that evaporate--- read up on POS coins and commands like walletpassphrase and reservebalance - peace digeros

bholzer

hero member

Activity: 490

Merit: 510

The Murraycoin Project ▪ Lead Developer

Something is definitely screwed up -- I'm shutting down the mining until it's straightened out. I added the original nodes back in...lost some coins...some coins moved from balance to stake...difficulty continues to just jump around like crazy (like I mentioned yesterday, sometimes dipping down as low as 0.0002xxx) -- I'll wait until it blows over. In the meantime, the people that are rocking and rolling should get hooked up with a low difficulty.

I've been on 1.2 since it was posted -- a bit concerned.

sheinsha

sr. member

Activity: 434

Merit: 250

Palmdetroit

legendary

Activity: 910

Merit: 1000

PHS 50% PoS - Stop mining start minting

sheinsha

sr. member

Activity: 434

Merit: 250

My client wont sync, i have set up the .conf to connect to a know server that has correct fork, and i still get to 6084 and break.

log:

Code:

received block 000000004154363da3cf
SetBestChain: new best=000000004154363da3cf1c635c5f81acaa83da7d900e4c9fcab4205d16d6f613  height=6082  trust=6083  date=08/06/13 05:58:06
ProcessBlock: ACCEPTED
received block 000000007bc6de25dec6
SetBestChain: new best=000000007bc6de25dec6c099540dae685c6566fce520fd5fe9d92dcd72f4f093  height=6083  trust=6084  date=08/06/13 06:01:01
ProcessBlock: ACCEPTED
received block 000000006fc3794409f7
SetBestChain: new best=000000006fc3794409f7eb5ebfeff9e786a55e69f1faf5943a3a4e6b6f3a546e  height=6084  trust=6085  date=08/06/13 06:02:36
ProcessBlock: ACCEPTED
received block 66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
InvalidChainFound: invalid block=66dc6974844b5567accb  height=6085  trust=1054662  date=08/06/13 06:03:28
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 36c535509370fabf4fb8
Postponing 1 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 000000006fc3794409f7..000000006fc3794409f7
REORGANIZE: Connect 1 blocks; 000000006fc3794409f7..66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 66dc6974844b5567accb failed
InvalidChainFound: invalid block=36c535509370fabf4fb8  height=6086  trust=2103239  date=08/06/13 06:03:54
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block f420ff38aa6e27e40b5a
Postponing 2 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 000000006fc3794409f7..000000006fc3794409f7
REORGANIZE: Connect 1 blocks; 000000006fc3794409f7..66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 66dc6974844b5567accb failed
InvalidChainFound: invalid block=f420ff38aa6e27e40b5a  height=6087  trust=3207629  date=08/06/13 06:04:13
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 0000000013a6b15b1d4b
Postponing 3 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 000000006fc3794409f7..000000006fc3794409f7
REORGANIZE: Connect 1 blocks; 000000006fc3794409f7..66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 66dc6974844b5567accb failed
InvalidChainFound: invalid block=0000000013a6b15b1d4b  height=6088  trust=3207630  date=08/06/13 06:05:40
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000514fc83edd9b
Postponing 4 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 000000006fc3794409f7..000000006fc3794409f7
REORGANIZE: Connect 1 blocks; 000000006fc3794409f7..66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 66dc6974844b5567accb failed
InvalidChainFound: invalid block=00000000514fc83edd9b  height=6089  trust=3207631  date=08/06/13 06:10:40
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000724f21a0ed3e
Postponing 5 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 000000006fc3794409f7..000000006fc3794409f7
REORGANIZE: Connect 1 blocks; 000000006fc3794409f7..66dc6974844b5567accb
ERROR: ConnectInputs() : 72b470d844 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 66dc6974844b5567accb failed
InvalidChainFound: invalid block=00000000724f21a0ed3e  height=6090  trust=3207632  date=08/06/13 06:11:50
InvalidChainFound:  current best=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

I would love to get some help here, i have cleaned the chain many times and always the same block is wrong.

sheinsha

sr. member

Activity: 434

Merit: 250

Quote from: flyingcat on August 09, 2013, 01:55:37 AM

with version 1.2 i have no problem..

"repairwallet" corrupted my wallet, as i posted above, it said it was fixed, but the wallet is now 64kb and 0 balance...

flyingcat

sr. member

Activity: 588

Merit: 250

with version 1.2 i have no problem..

digeros

sr. member

Activity: 280

Merit: 250

Quote from: A L I E N on August 09, 2013, 01:39:19 AM

Quote from: sheinsha on August 09, 2013, 01:35:30 AM

give me the dev node so i can try that. I hope this fork has not corrupted the wallet.

Did you run "repairwallet" ?

Here are the ones he listed on the first page:
addnode=50.30.139.158
addnode=76.91.4.69
addnode=173.230.121.83
addnode=42.115.18.232

my info

{
"version" : "v1.2.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : xxxxx
"newmint" : xxxxxx
"stake" : 0.00000000,

"blocks" : 8033,

"moneysupply" : 788308.85147900,
"connections" : 52,
"proxy" : "",
"ip" : xxxxxxxxxx
"difficulty" : 1.10118798,
"testnet" : false,
"keypoololdest" : 1375254488,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
}

Topic: [ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3 - page 30. (Read 81158 times)