[ANN] [PPC] PPCoin Released! - First Long-Term Energy-Efficient Crypto-Currency

[Vorksholk]

Well balance only shows blocks that are 520 blocks old or older, do ppcoind getinfo and see if there is anything newmint?

# ppcoind getinfo
{
    "version" : "v0.2.0.0-g09051bd-beta",
    "protocolversion" : 60002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 3647,
    "moneysupply" : 5569889.13000000,
    "connections" : 8,
    "proxy" : "",
    "ip" : "1.1.1.1",
    "difficulty" : 3357.31983600,
    "testnet" : false,
    "keypoololdest" : 1346744327,
    "keypoolsize" : 102,
    "paytxfee" : 0.01000000,
    "errors" : ""
}

Appreciate the assist!  Any other ideas?  I'm wondering if maybe I should try an older version of ppcoind?

I'm no expert, but the ip of 1.1.1.1 looks a bit odd....? Any experts here...

[1714806413]

1714806413

[inbox]

.

[burnside]

Does cpuminer support ppcoins? I use cgminer.

It's all sha256, should be fine, but I did do a little research before I started:

yes ,
i got it working, had to restart ppcoind.exe 

only mining locally, want to try on your pool tomorrow, i'm going to sleep now

edit:
fyi im using poolers cpu miner for best performance, it looks like it is ~10Mhash faster

minerd -a sha256d -o http://127.0.0.1:9902 -u user -p pass

(and on the other machine i use cgminer for the gpu)

I'm no expert, but the ip of 1.1.1.1 looks a bit odd....? Any experts here...

Yeah, removed it.   

[doublec]

Mining LTC (scrypt):

Aug 26 06:26:39 xxx cpuminer[20774]: accepted: 821191/824212 (99.63%), 72.10 khash/s (yay!!!)
Aug 26 06:26:39 xxx cpuminer[20774]: accepted: 821192/824213 (99.63%), 72.12 khash/s (yay!!!)

Mining PPC (sha256):

Sep  4 08:00:45 xxx cpuminer[28799]: 14 miner threads started, using 'sha256d' algorithm.
Sep  4 08:00:46 xxx cpuminer[28799]: thread 0: 2097152 hashes, 4694 khash/s
Sep  4 08:00:46 xxx cpuminer[28799]: thread 1: 2097152 hashes, 4693 khash/s

Are you mining on a pool with LTC but not with PPC? If so the 'yay' is from difficulty 1 shares and you'll get more of them.

[burnside]

Mining LTC (scrypt):

Aug 26 06:26:39 xxx cpuminer[20774]: accepted: 821191/824212 (99.63%), 72.10 khash/s (yay!!!)
Aug 26 06:26:39 xxx cpuminer[20774]: accepted: 821192/824213 (99.63%), 72.12 khash/s (yay!!!)

Mining PPC (sha256):

Sep  4 08:00:45 xxx cpuminer[28799]: 14 miner threads started, using 'sha256d' algorithm.
Sep  4 08:00:46 xxx cpuminer[28799]: thread 0: 2097152 hashes, 4694 khash/s
Sep  4 08:00:46 xxx cpuminer[28799]: thread 1: 2097152 hashes, 4693 khash/s

Are you mining on a pool with LTC but not with PPC? If so the 'yay' is from difficulty 1 shares and you'll get more of them.

Yeah, that probably is why I'm not seeing the yay! ...

I also noticed that the official linux distribution compiles a different version string than it is shipped with in the bin directory!

    "version" : "v0.2.0.0-g09051bd-beta",

vs.

    "version" : "v0.2.0.0-beta",

I always compile from source.  Somethings wrong there.

I'm gonna try on ppcoin 0.1.0 for a bit too, see how that goes.

[Sunny King]

Yeah, that probably is why I'm not seeing the yay! ...

I also noticed that the official linux distribution compiles a different version string than it is shipped with in the bin directory!

    "version" : "v0.2.0.0-g09051bd-beta",

vs.

    "version" : "v0.2.0.0-beta",

I always compile from source.  Somethings wrong there.

I'm gonna try on ppcoin 0.1.0 for a bit too, see how that goes.

If you build with make yourself, the version would look like that so it's normal. Here g09051bd refers to the git commit id which is the correct commit id for v0.2.0. The official build version string is v0.2.0ppc-beta.

As to your cpuminer issues I don't know if it's just pure bad luck or something else. One suggestion is to look through debug.log and search for 'ERROR'. If you see messages about rejection of blocks you can post it here for analysis (although I suppose cpuminer should report block rejection in some fashion as well?).

[burnside]

Yeah, that probably is why I'm not seeing the yay! ...

I also noticed that the official linux distribution compiles a different version string than it is shipped with in the bin directory!

    "version" : "v0.2.0.0-g09051bd-beta",

vs.

    "version" : "v0.2.0.0-beta",

I always compile from source.  Somethings wrong there.

I'm gonna try on ppcoin 0.1.0 for a bit too, see how that goes.

If you build with make yourself, the version would look like that so it's normal. Here g09051bd refers to the git commit id which is the correct commit id for v0.2.0. The official build version string is v0.2.0ppc-beta.

As to your cpuminer issues I don't know if it's just pure bad luck or something else. One suggestion is to look through debug.log and search for 'ERROR'. If you see messages about rejection of blocks you can post it here for analysis (although I suppose cpuminer should report block rejection in some fashion as well?).

Awesome, glad there's no issues with the version strings.

Been running on v0.1.0 for the last several hours, see lots of the exceptions (as expected?) but I also see:

Code:

ERROR: CAlert::CheckSignature() : verify signature failed
ERROR: BitcoinMiner : proof-of-work not meeting target
ERROR: CTransaction::CheckTransaction() : vout empty
ERROR: CTxMemPool::accept() : CheckTransaction failed
ERROR: CTransaction::CheckTransaction() : vout empty
ERROR: CTxMemPool::accept() : CheckTransaction failed
ERROR: CTransaction::CheckTransaction() : txout.nValue below minimum
ERROR: CTxMemPool::accept() : CheckTransaction failed

Any of that mean anything?

I'll switch back to v0.2.0, see if I get any other errors.  Thanks!

[Sunny King]

Code:

ERROR: BitcoinMiner : proof-of-work not meeting target

This means a block was rejected. Could you post log output around this particular error?

[TheSeven]

My logic with the command line option was that I know java far better than web development, so I'd be able to secure it a lot easier, but on second thought I really don't want to make an exchange, as I'd be the one in the end holding the bag when someone finds some security hole in my program. I'm not confident enough in my programming skills at this point in time to put money on the line like that... it just takes one oversight Thanks for the input though, and yeah, the only reason the java client was more secure is because I could code it alot better.

You still didn't get it. The security of the server is what's crucial, the code quality of the client does not impact overall security at all. The client can't protect against any attacks at all, as an attacker could always just build his own client. So whether it's a web client or not doesn't make any difference, as long as the server side backend is the same.

[burnside]

Code:

ERROR: BitcoinMiner : proof-of-work not meeting target

This means a block was rejected. Could you post log output around this particular error?

Yesterday on v0.1.0:

Code:

askfor tx 23645e1ed55eecbbbefe   1346818855000000
askfor tx 3f5f16ab087c4254e877   0
sending getdata: tx 3f5f16ab087c4254e877


******* exception encountered *******
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z13LogStackTracev+0x45)[0x55c235]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_ZN11CDataStream4readEPci+0xcd)[0x466f3d]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z16Unserialize_implI11CDataStream5CTxInSaIS1_EEvRT_RSt6vectorIT0_T1_EiiRKN5boost17integral_constantIbLb0EEE+0x270)[0x4e4270]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z11UnserializeI11CDataStream12CTransactionEvRT_RT0_li+0x66)[0x4e46a6]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind[0x4c6883]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z15ProcessMessagesP5CNode+0x5b9)[0x4c84e9]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z21ThreadMessageHandler2Pv+0x139)[0x4e8099]
/usr/src/ppcoin-0.1.0ppc-linux/src/src/ppcoind(_Z20ThreadMessageHandlerPv+0x42)[0x4e8272]
/lib/libpthread.so.0(+0x69ca)[0x7fe350c799ca]
/lib/libc.so.6(clone+0x6d)[0x7fe350228cdd]
ProcessMessages(tx, 227 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
ProcessMessage(tx, 227 bytes) FAILED
askfor tx 3f5f16ab087c4254e877   1346818857000000
ERROR: BitcoinMiner : proof-of-work not meeting target
askfor tx f70a1ea1f3056c76c20f   0
sending getdata: tx f70a1ea1f3056c76c20f

two more last night on v0.2.0:

Code:

ProcessSyncCheckpoint: sync-checkpoint at 00000000000a36a734e199b2b87850e7c272aa89ea43d8faf049e74a8f3a1ab2
getblocks -1 to 00000000000000000000 limit 500
Added 1 addresses from 188.165.73.215: 9 tried, 9122 new
Added 1 addresses from 72.14.191.28: 9 tried, 9122 new
Added 1 addresses from 99.119.197.208: 9 tried, 9122 new
Added 1 addresses from 89.29.69.214: 9 tried, 9122 new
Added 1 addresses from 72.14.191.28: 9 tried, 9123 new
Added 1 addresses from 89.29.69.214: 9 tried, 9123 new
Added 1 addresses from 99.119.197.208: 9 tried, 9123 new
Added 1 addresses from 188.165.73.215: 9 tried, 9123 new
Added 1 addresses from 89.29.69.214: 9 tried, 9123 new
Added 1 addresses from 72.14.191.28: 9 tried, 9123 new
Added 1 addresses from 46.19.139.68: 9 tried, 9124 new
Added 1 addresses from 150.140.159.226: 9 tried, 9124 new
Added 1 addresses from 202.9.106.22: 9 tried, 9123 new
Added 1 addresses from 188.165.73.215: 9 tried, 9123 new
Added 1 addresses from 72.14.191.28: 9 tried, 9123 new
Added 1 addresses from 46.19.139.68: 9 tried, 9124 new
ERROR: BitcoinMiner : proof-of-work not meeting target
Added 1 addresses from 150.140.159.226: 9 tried, 9125 new
Added 1 addresses from 188.165.73.215: 9 tried, 9126 new
Added 1 addresses from 89.29.69.214: 9 tried, 9125 new
Added 1 addresses from 89.29.69.214: 9 tried, 9125 new
Added 1 addresses from 72.14.191.28: 9 tried, 9125 new
Added 1 addresses from 188.165.73.215: 9 tried, 9125 new
Added 1 addresses from 99.119.197.208: 9 tried, 9125 new
ResendWalletTransactions()
Added 1 addresses from 188.165.73.215: 9 tried, 9126 new

Code:

Flushed wallet.dat 241ms
ProcessSyncCheckpoint: sync-checkpoint at 00000000000dacb0f51d53fec053520a9df71b34e205e0595210b51a7c3c4578
Added 1 addresses from 89.29.69.214: 9 tried, 9165 new
askfor block 000000000005ecf19db4   0
sending getdata: block 000000000005ecf19db4
received block 000000000005ecf19db4
SetBestChain: new best=000000000005ecf19db4  height=3695  trust=3696  moneysupply=5633071.87
ProcessBlock: ACCEPTED
Added 1 addresses from 99.119.197.208: 9 tried, 9163 new
2012-09-05 12:53:53 UTC Flushing wallet.dat
Flushed wallet.dat 179ms
Added 1 addresses from 188.165.73.215: 9 tried, 9163 new
ProcessSyncCheckpoint: sync-checkpoint at 000000000005ecf19db4c351a69b3f3484b1b0d1c5749115653e818b0bd21637
Added 1 addresses from 150.140.159.226: 9 tried, 9163 new
Added 1 addresses from 188.165.73.215: 9 tried, 9163 new
Added 1 addresses from 89.29.69.214: 9 tried, 9163 new
Added 1 addresses from 72.14.191.28: 9 tried, 9164 new
Added 1 addresses from 119.110.100.241: 9 tried, 9165 new
Added 1 addresses from 72.14.191.28: 9 tried, 9163 new
ERROR: BitcoinMiner : proof-of-work not meeting target
Added 1 addresses from 119.110.100.241: 9 tried, 9162 new
Added 1 addresses from 46.19.139.68: 9 tried, 9163 new
Added 1 addresses from 150.140.159.226: 9 tried, 9163 new
Added 1 addresses from 72.14.191.28: 9 tried, 9163 new
askfor block 0000000000007f53d326   0
sending getdata: block 0000000000007f53d326
askfor block 0000000000007f53d326   1346849933000000
askfor block 0000000000007f53d326   1346850053000000
received block 0000000000007f53d326
SetBestChain: new best=0000000000007f53d326  height=3696  trust=3697  moneysupply=5634394.30
ProcessBlock: ACCEPTED
2012-09-05 12:58:57 UTC Flushing wallet.dat
Flushed wallet.dat 137ms
ProcessSyncCheckpoint: sync-checkpoint at 0000000000007f53d3260233ba17606cfac219af6752ccd108e53825ed5526c5
Added 1 addresses from 202.9.106.22: 9 tried, 9163 new
Added 1 addresses from 150.140.159.226: 9 tried, 9164 new
Added 1 addresses from 202.9.106.22: 9 tried, 9164 new
Added 1 addresses from 119.110.100.241: 9 tried, 9164 new
Added 1 addresses from 46.19.139.68: 9 tried, 9164 new
Added 1 addresses from 99.119.197.208: 9 tried, 9164 new
Added 1 addresses from 99.119.197.208: 9 tried, 9165 new

I shifted my miners back to LTC this morning when I saw I was still at "newmint" : 0.00000000.

Would love to get this going though.

Thanks!

[burnside]

Any thoughts?  Why are all my proof-of-work's bad?

[Vorksholk]

Any thoughts?  Why are all my proof-of-work's bad?

That's really weird, have you tried pointing it at NothinG's pool just as a control variable?

[MXRider]

Any thoughts?  Why are all my proof-of-work's bad?

I don't know the answer on the proof-or-work questions BUT: You are mining with CPU and with some quick math your hashpower is about 12MH/s max. You will not find a block with a CPU, at least not in two weeks.

[Sunny King]

Any thoughts?  Why are all my proof-of-work's bad?

I don't know the answer on the proof-or-work questions BUT: You are mining with CPU and with some quick math your hashpower is about 12MH/s max. You will not find a block with a CPU, at least not in two weeks.

Ah I didn't read that cpuminer says 4Mh/s each thread. I thought burnside said he was mining with gpu at 2Gh/s. Though I still don't know why there was this rejection for not enough proof-of-work in debug log.

[eja]

Could be that cpuminer submits all shares above a certain difficulty. I see the same from shares passed from pushpool, it appears to pass all shares above 256 difficulty to the coiner daemon and so cause these same messages in the log.
Bit still with 2GH/s it should generate a share with sufficient difficulty regularly, even if if also submit too low shares.

[burnside]

Any thoughts?  Why are all my proof-of-work's bad?

I don't know the answer on the proof-or-work questions BUT: You are mining with CPU and with some quick math your hashpower is about 12MH/s max. You will not find a block with a CPU, at least not in two weeks.

Ah I didn't read that cpuminer says 4Mh/s each thread. I thought burnside said he was mining with gpu at 2Gh/s. Though I still don't know why there was this rejection for not enough proof-of-work in debug log.

I'm correct in my math.  60 servers x 16 cores x 2.5Mh = ....  

I was being conservative at 2,000Mh.  It's actually a bit higher.

I run the ltc.kattare.com pool, I have a semi-decent idea how it all works.  

[burnside]

Any thoughts?  Why are all my proof-of-work's bad?

That's really weird, have you tried pointing it at NothinG's pool just as a control variable?

Yeah, I could try that.

Is there anything special about the pushpoold NothingG is using?  I'd rather just start up my own PPC pool.

ppc.kattare.com?  heh.

[jjshabadoo]

So is the only way to mine this coin is to run the client on the mining rig and the use something like cgminer ?

I can't get this to run at all and I know part of it is I suck at command line stuff.

I'm trying to use the gui client for my wallet, but I guess you can only solo mine this which likely means you have to run the ppc client on your mining machine. Is this correct ?

[Sunny King]

So is the only way to mine this coin is to run the client on the mining rig and the use something like cgminer ?

I can't get this to run at all and I know part of it is I suck at command line stuff.

I'm trying to use the gui client for my wallet, but I guess you can only solo mine this which likely means you have to run the ppc client on your mining machine. Is this correct ?

Doesn't have to be on the same machine. You can run ppcoind on a separate machine or vm, and allow your mining machines to connect via RPC by setting rpcallowip according to the examples in ppcoin.conf:
# if miners all on LAN 192.168.1.*
rpcallowip=192.168.1.*

[jjshabadoo]

okay thanks, I think I get it now.