we were talking about this earlier...on a PoW block with a PoT, the flags on the block look like this on explorer for "raw block"
chaintrust": "404626a868f",
"previousblockhash": "000000030099fbdb29c48c46e177bcfc718589865ac9612efd01f56e6173e5a0",
"flags": "proof-of-work",
"extraflags": "proof-of-transaction",
"proofhash": "00000001db51107d9a9c712eb6dade73ba2f6b2cb7d36ebf717918d2507b12f5",
I expect that a PoS block with a PoT would have proof-of-stake, and extra proof-of-transaction
5000 FLT bounty to someone who can find me a PoS with Pot so I can check something.
Note: tablet is still dead battery but I think I figured out why my checkpoints were not working, compiling a build to checkpoint block 95000. Hoping this will let us sync up a bit easier.
Has anyone compiled QT and fluttercoind for windows, or a howto guide I can review on what I need on my windows box to do it.
ah hell yeah, i had synced up to 95010 or so, and was still 40 off of main...i used my new code and started it up, checkpoint failed!
Loading block index...
Opening LevelDB in /home/ubuntu/.fluttercoin/txleveldb
Transaction index version is 70507
Opened LevelDB successfully
ERROR: CTxDB::LoadBlockIndex() : Failed stake modifier checkpoint height=95000, modifier=0x37210c9bc00450c0
FlutterCoin: Error loading blkindex.dat
Flush(false)
DBFlush(false) ended 0ms
StopNode()
Flushed 0 addresses to peers.dat 10ms
Flush(true)
DBFlush(true) ended 0ms
FlutterCoin exited
Now it just does this over and over again though, was sure hoping it would be smart enough to know....ok, let me go back to last checkpoint and resync, nope! Time to resync from block0
other notes...we will try to get this resolved again, stupid forks
some of you are still on wrong chain
receive version message: version 70009, blocks=95185, us=54.84.46.196:47234, them=192.99.159.64:7408, peer=192.99.159.64:7408
receive version message: version 70009, blocks=95185, us=54.84.46.196:34183, them=61.230.45.35:7408, peer=61.230.45.35:7408
receive version message: version 70009, blocks=95146, us=54.84.46.196:49011, them=98.220.203.77:7408, peer=98.220.203.77:7408
receive version message: version 70009, blocks=95146, us=54.84.46.196:33630, them=76.177.91.53:7408, peer=76.177.91.53:7408receive version message: version 70009, blocks=92050, us=54.84.46.196:33114, them=36.84.148.43:7408, peer=36.84.148.43:7408
you know who you are, get synced! AND YOUR MINING ON IT TOO which just makes the problem worse, ugh!
I'm testing my code, to see what happens when I end up on the 95146 chain, and it hits block 95k and checkpoint fails...see if it is smart enough to know, I am on bad chain, and try another...
oh, found this on the PoT on PoS debate...so it doesn't look like it's implemented, and all the POTv2 code is all around PoW
// I thought he finished the PoS part of PoT
if (!blockindex->IsProofOfStake() && block.vtx[0].vout.size() > 1)
result.push_back(Pair("extraflags", "proof-of-transaction"));
else
result.push_back(Pair("extraflags", "none"));
here is where it calcs the PoW PoT transaction lines in miner.cpp lines 686, 687
pblock->vtx[0].vout[0].nValue = (GetProofOfWorkReward(pindexPrev->nHeight+1, pindexPrev->GetBlockHash())*0.95);
pblock->vtx[0].vout[1].nValue = (GetProofOfWorkReward(pindexPrev->nHeight+1, pindexPrev->GetBlockHash())*0.05);