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

[The Koolio]

stupid question really but can you mine with mutiple gpus on multiple rigs to one ppcoin address?

also how do i point two gpus to mine ppcoin when using pheonix... currently when trying to get second gpu mining the phoenix client crashes.

CGminer works fine

I cant seem to install it... the instructions packaged with it i followed to a T but then as soon as it came to compiling cgminer within the mingw shell it throws errors about certain files not being present etc. Are there no setup installers for it?

[1715209786]

1715209786

[1715209786]

1715209786

[1715209786]

1715209786

[1715209786]

1715209786

[OneMINER]

stupid question really but can you mine with mutiple gpus on multiple rigs to one ppcoin address?

also how do i point two gpus to mine ppcoin when using pheonix... currently when trying to get second gpu mining the phoenix client crashes.

Forget about trying to build cgminer. Just download the latest from the link I sent. It should auto detect your cards. The program will be in a zipped folder that you will unzip in whatever location you prefer. No building required.
You'll be able to use both cards on one worker account at your pool.
You should use the same settings that you do when mining bitcoins. Ppcoin mining is the same as bitcoin.
One pool may be different from another but you'll probably get your coins after 520 blocks. At that time the coins will be "mature".

Good luck.

[Rubberduckie]

stupid question really but can you mine with mutiple gpus on multiple rigs to one ppcoin address?

also how do i point two gpus to mine ppcoin when using pheonix... currently when trying to get second gpu mining the phoenix client crashes.

Forget about trying to build cgminer. Just download the latest from the link I sent. It should auto detect your cards. The program will be in a zipped folder that you will unzip in whatever location you prefer. No building required.
You'll be able to use both cards on one worker account at your pool.
You should use the same settings that you do when mining bitcoins. Ppcoin mining is the same as bitcoin.
One pool may be different from another but you'll probably get your coins after 520 blocks. At that time the coins will be "mature".

Good luck.

If you mine @ http://ppcpool.bitparking.com/pool you can withdraw your coins as soon as they're mined without waiting for confirmation

[AndyRossy]

If you hold the coins for long enough to qualify for a PoS, but, you're constantly sending/receiving will it automatically select addresses with lowest coin age? Or, do we need to somehow do this ourselves?

[Sunny King]

If you hold the coins for long enough to qualify for a PoS, but, you're constantly sending/receiving will it automatically select addresses with lowest coin age? Or, do we need to somehow do this ourselves?

I am not aware that you can select which coins to send, unless you modify the code yourself. We haven't changed the coin selection logic so it's still the same as Bitcoin. The minter will gradually split your large coins to reasonable sizes so you don't end up consuming all your coinage in one small spend. But if you do lots of spends I am not yet sure. This is an action item that will be followed up likely for v0.3.

Thanks,

[Jutarul]

If you hold the coins for long enough to qualify for a PoS, but, you're constantly sending/receiving will it automatically select addresses with lowest coin age? Or, do we need to somehow do this ourselves?

But if you do lots of spends I am not yet sure. This is an action item that will be followed up likely for v0.3.

Thanks,

I guess for now you should use TWO wallets. One for mining, the other one for managing your PPC cash flow. Only leave those coins in the STAKE wallet which you intend to use as stake?

[Sunny King]

I guess for now you should use TWO wallets. One for mining, the other one for managing your PPC cash flow. Only leave those coins in the STAKE wallet which you intend to use as stake?

That would probably be too much trouble for users. I will look into this matter if it's a trivial change I would provide it sooner.

[FuzzyBear]

Hey all,

Just wanted to say gratz to sunny king and PPCoin as it seems to be happily being adopted by people especially in the last few days with a sudden rush of new pools, wallet gui's, exchanges and even video tutorials ty doublec, Darktongue and all those involved.

Did just want to highlight the sudden jump in difficulty .... been around 3600ish for a while... now up to 8800 ... and by looking at http://ppcpool.bitparking.com/blockstats i see that there are some hefty hashers out there in the pool already!!

i'm updating a few posts for pool mining and websites for PPCoins on http://www.ppcointalk.org and feel free to add ur own sites etc

enjoy ur PPCoins!!

[coinotron]

We have started a PPCoin pool! at Coinotron.com  

1. You can use any BTC miner
2. On our website choose worker type PPC. Point worker to coinotron.com, port 8322 or 9322.
3. Depending on worker type you can have Proportional (2% fee) or PPS (3% fee) rewards

[dreamwatcher]

Just a quick question Sunny, as my eyes are getting kinda blurry looking at hash.

For PPC what officially is the:


Chain Name

Code 3

Address_version

I have been experimenting with a block explorer for PPC.

Thank you

[Sunny King]

Just a quick question Sunny, as my eyes are getting kinda blurry looking at hash.

For PPC what officially is the:


Chain Name

Code 3

Address_version

I have been experimenting with a block explorer for PPC.

Thank you

Chain Name: ppcoin
Code 3: PPC (if this is what I guess what it is)
Address_version: 55 (address starts with 'P')

[Jutarul]

I guess for now you should use TWO wallets. One for mining, the other one for managing your PPC cash flow. Only leave those coins in the STAKE wallet which you intend to use as stake?

That would probably be too much trouble for users. I will look into this matter if it's a trivial change I would provide it sooner.

Having two different wallets is an easy concept for the user to grasp and you can be sure to have no interference. It would be great if you had that functionality within one wallet. But it may take a while to get this right. Till then, I think it's safest to employ a dedicated STAKE wallet.

[AndyRossy]

if a wallet is offline when it's PoS life is reached, as soon as it goes back online it signs accordingly and generates the block right; kinda backdated?

[Jutarul]

if a wallet is offline when it's PoS life is reached, as soon as it goes back online it signs accordingly and generates the block right; kinda backdated?

yes. coinage is accumulated regardless of the wallet being online or not. What matters is the time the corresponding input transaction was incorporated into the blockchain.
However, right now I think the maximum time you can accumulate per transaction is 90 days:

Code:

#define STAKE_MAX_AGE (60 * 60 * 24 * 90) // stake age for full weight
CBigNum bnCoinDay = CBigNum(nValueIn) * min(nTime-txPrev.nTime, (unsigned int)STAKE_MAX_AGE) / COIN / (24 * 60 * 60);

the second line takes the minimum number of seconds when it computes the coinage (CTransaction::CheckProofOfStake), which is either (nTime-txPrev.nTime) or STAKE_MAX_AGE, whatever is lower.

Thus if you stash away your stake wallet, put it online every 3 months to redeem your stake.

[dreamwatcher]

Sunny,

More questions is regard to a block explorer.

Has the structure of the block changed?

The trouble I am having adapting ABE to PPC:

When the deserializer tries to parse incoming transactions as shown here: (the highlighted print statement was added by me for debugging)

def parse_TxIn(vds):
 
  d = {}
  d['prevout_hash'] = vds.read_bytes(32)
  d['prevout_n'] = vds.read_uint32()
  d['scriptSig'] = vds.read_bytes(vds.read_compact_size())
  print len(d['scriptSig'])
  d['sequence'] = vds.read_uint32()
  return d

Output is such:

vm@vm-VirtualBox:~/abe$ python -m Abe.abe --config abe-my.conf --commit-bytes 100000 --no-serve
2235787
Failed to catch up {'blkfile_number': 1, 'dirname': u'/home/vm/.PPcoin', 'chain_id': Decimal('1'), 'id': 17L, 'blkfile_offset': 0}
Traceback (most recent call last):
  File "Abe/DataStore.py", line 2267, in catch_up
    store.catch_up_dir(dircfg)
  File "Abe/DataStore.py", line 2301, in catch_up_dir
    store.import_blkdat(dircfg, ds)
  File "Abe/DataStore.py", line 2423, in import_blkdat
    b = store.parse_block(ds, chain_id, magic, length)
  File "Abe/DataStore.py", line 2455, in parse_block
    d['transactions'].append(deserialize.parse_Transaction(ds))
  File "Abe/deserialize.py", line 94, in parse_Transaction
    d['txIn'].append(parse_TxIn(vds))
  File "Abe/deserialize.py", line 50, in parse_TxIn
    d['sequence'] = vds.read_uint32()
  File "Abe/BCDataStream.py", line 71, in read_uint32
    def read_uint32(self): return self._read_num('<I')
  File "Abe/BCDataStream.py", line 111, in _read_num
    (i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes



The red highlighted number is the length of the output it is receiving for ScriptSig (from the print statement I added), basically the rest of the  blk0001.dat file.

The error comes up (buffer need to be at least four bytes) because the read_cursor has already hit the end of the file. (At least that is what I believe).

My eyes are getting buggy from looking at PPC source code, maybe you can make this simple.

What structure changes has there been in the block, at least in the way TxIn is stored?


FYI, I removed all the other chain identifiers in abe, and that is why it identified the chain as "1" as it is the only chain ID in abe.

CHAIN_CONFIG = [
    {"chain":"PPcoin",
     "code3":"PPC", "address_version":"\x37", "magic":"\xe6\xe8\xe9\xe5"},
    ]

[Sunny King]

Hi dreamwatcher,
  This is most likely because abe needs to be aware that there is an additional timestamp field for ppcoin transactions. In ppcoin each transaction begins with a 32 bit unsigned timestamp.

[coinotron]

Hi Sunny
I've observed strange behavior of ppcoind running in Coinotron pool. After 3 days it uses 1.1 GB of RAM - much more than for example bitcoind (130MB).

I compiled the newest windows version: ppcoin-ppcoin-v0.2.0ppc-0-g09051bd.

There seems to be a memory leak somewhere.

There is a lot of "ERROR: BitcoinMiner : proof-of-work not meeting target" messages in debug.log.


Could you please look into it?

[Sunny King]

Hi coinotron,
  I have sent you a pm.

[AndyRossy]

Hi Sunny
I've observed strange behavior of ppcoind running in Coinotron pool. After 3 days it uses 1.1 GB of RAM - much more than for example bitcoind (130MB).

I compiled the newest windows version: ppcoin-ppcoin-v0.2.0ppc-0-g09051bd.

There seems to be a memory leak somewhere.

There is a lot of "ERROR: BitcoinMiner : proof-of-work not meeting target" messages in debug.log.


Could you please look into it?

I have same problem, after a few days im at 7.2G virt/5.4G Res

Andy

[Sunny King]

I have same problem, after a few days im at 7.2G virt/5.4G Res

Andy

Andy, are you on linux or windows? Which miner/external software you use? And the size of your wallet.dat file?