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

[doublec]

I see it on my pool as well. Running 64bit Linux it's at 4.6g. The exchange doesn't though, it's at 185m so I assume it's something mining related.

[1685478967]

1685478967

[1685478967]

1685478967

[1685478967]

1685478967

[1685478967]

1685478967

[Sunny King]

Ah that's probably why I don't see it on any of my nodes. Which RPC calls does the pool software call other than getwork? I don't see any change to getwork so I assume it's some other call causing this problem.

[doublec]

Ah that's probably why I don't see it on any of my nodes. Which RPC calls does the pool software call other than getwork? I don't see any change to getwork so I assume it's some other call causing this problem.

getwork calls CreateNewBlock, has that changed? The pool also called getdifficulty.

[coinotron]

getwork calls CreateNewBlock, has that changed? The pool also called getdifficulty.

My pool also calls:
-getblockcount
-gettransaction

and from time to time :
-sendtoaddress
-validateaddress
-getbalance

[AndyRossy]

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?

Linux engine.redb.us 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


drwx------  3 andrew andrew 4.0K Sep 16 12:01 .
drwx------ 25 andrew andrew 4.0K Sep 14 14:08 ..
-rw-------  1 andrew andrew 848K Sep 16 12:03 addr.dat
-rw-------  1 andrew andrew 2.6M Sep 16 11:57 blk0001.dat
-rw-------  1 andrew andrew 2.7M Sep 16 11:57 blkindex.dat
drwx------  2 andrew andrew 4.0K Sep 16 11:57 database
-rw-------  1 andrew andrew  24K Sep 16 12:01 __db.001
-rw-------  1 andrew andrew 1.8M Sep 16 12:04 __db.002
-rw-------  1 andrew andrew  32M Sep 16 12:04 __db.003
-rw-------  1 andrew andrew 1.2M Sep 16 12:04 __db.004
-rw-------  1 andrew andrew 6.1M Sep 16 12:04 __db.005
-rw-------  1 andrew andrew  48K Sep 16 12:03 __db.006
-rw-------  1 andrew andrew    0 Sep  5 10:16 db.log
-rw-------  1 andrew andrew 1.3M Sep 16 12:04 debug.log
-rw-------  1 andrew andrew    0 Sep  5 10:16 .lock
-rw-rw-r--  1 andrew andrew   90 Sep  5 10:17 ppcoin.conf
-rw-------  1 andrew andrew 360K Sep 16 11:57 wallet.dat



pypool; custom modified.

I think it is linked to getwork/mining also.

[Sunny King]

Weekly Update #4

• With Chris' debut of Bitparking PPC Exchange the week before, this week we have witnessed a mini episode of gold-rush, where difficulty is ramped from below 4000 to over 22000. At some point, I estimated that the network surpassed 1% of Bitcoin's hashing power. The peak was reached at block 6031, difficulty 22334. Currently we are back at around 16000. I would like to caution traders and investors to be aware of the risk involved especially during periods of high volatility in market. Remember ppcoin is still an experimental chain and lots of different risks are possible.
• There are a few reports of high memory consumption of ppcoind in certain environment. I will search for a reproducible setup to help investigate this problem.
• It seems that our continuous target adjustment handles difficulty drop quite well. It's been only 2 days since peak difficulty and we are already at 72% of peak difficulty so the drop rate is reasonably fast.
• Bug fix release v0.2.1 is under testing and expected to be ready some time next week.

Have fun and next week!

[xisalty]

• Bug fix release v0.2.1 is under testing and expected to be ready some time next week.

One question, how long until the github repo will be updated. I'd like to start work on building the new client as soon as possible.

[Sunny King]

One question, how long until the github repo will be updated. I'd like to start work on building the new client as soon as possible.

Repo is updated right before release builds are ready for pickup. This release is not mandatory so there is no rush.

[Sunny King]

If anyone finds an easy setup to reproduce the memory leak issue please let me know. Thanks,

[xisalty]

One question, how long until the github repo will be updated. I'd like to start work on building the new client as soon as possible.

Repo is updated right before release builds are ready for pickup. This release is not mandatory so there is no rush.

Alright thanks, just wanted to clear that up.

[doublec]

If anyone finds an easy setup to reproduce the memory leak issue please let me know. Thanks,

Was PPCoin based on a stable bitcoin release? If so, what commit id, so I can get a diff of just the PPCoin change.

[AndyRossy]

Gut feeling it's in the CreateNewBlock section, the version it was forked from would also help.

[AndyRossy]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

[Sunny King]

Was PPCoin based on a stable bitcoin release? If so, what commit id, so I can get a diff of just the PPCoin change.

It's based on Bitcoin v0.6.3 (6e0c5e3). Not sure it's CreateNewBlock, I just sent a loop of getwork to ppcoind and no visible effect to memory usage.

[Sunny King]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

[AndyRossy]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

OK.

Also, getting ABE instance working, it looks like the tx blocks have also been altered (as with the block themselves). How have the tx's been altered? I'll look at the diffs from the above.

[dreamwatcher]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

OK.

Also, getting ABE instance working, it looks like the tx blocks have also been altered (as with the block themselves). How have the tx's been altered? I'll look at the diffs from the above.

I have already adapted Abe, and am in the process of hosting it. Hopefully sometime this week.
...
The answer to your question in 2 fold:

There is an extra time stamp after the version field in each transaction.

You need to use the most recent version of Abe (few days old) as it auto cuts some bytes at the end of the block that really wreck chaos with Abe's ability to keep track of its position when translating the blk0001 to its database.

[AndyRossy]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

OK.

Also, getting ABE instance working, it looks like the tx blocks have also been altered (as with the block themselves). How have the tx's been altered? I'll look at the diffs from the above.

I have already adapted Abe, and am in the process of hosting it. Hopefully sometime this week.
...
The answer to your question in 2 fold:

There is an extra time stamp after the version field in each transaction.

You need to use the most recent version of Abe (few days old) as it auto cuts some bytes at the end of the block that really wreck chaos with Abe's ability to keep track of its position when translating the blk0001 to its database.

That's great, im not too far from where you are.  Will you be releasing the changes / committing to abe tree?

[dreamwatcher]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

OK.

Also, getting ABE instance working, it looks like the tx blocks have also been altered (as with the block themselves). How have the tx's been altered? I'll look at the diffs from the above.

I have already adapted Abe, and am in the process of hosting it. Hopefully sometime this week.
...
The answer to your question in 2 fold:

There is an extra time stamp after the version field in each transaction.

You need to use the most recent version of Abe (few days old) as it auto cuts some bytes at the end of the block that really wreck chaos with Abe's ability to keep track of its position when translating the blk0001 to its database.

That's great, im not too far from where you are.  Will you be releasing the changes / committing to abe tree?

I have run into some strange new issues with the latest commit, so either I have to fix it in this commit, or just continue to use the earlier version.

There are some other issues, while not show stoppers, need to be addressed.

After I polish it a bit more, I will see if John Tobey would like me to release a commit. I feel it is his baby, his choice.

For now I would like to gauge the interest in a hosted version. I would have to buy at least a VPS (simple web hosting will not work) to host it one, which of course incurs a monthly fee.

I would probably use advertising on the site to cover costs, so before I go out on this venture I kind of want to see how much interest the PPC community has in it.

[AndyRossy]

Could we have, a way to find out coinage for each address a person holds? So can see how far from a PoS we are? A command like

./ppcoin getcoinage (address) or getcoinage account "" (and it'll do all addresses in that account) etc?

That would be sort of misleading as luck do play quite a bit role as well.

OK.

Also, getting ABE instance working, it looks like the tx blocks have also been altered (as with the block themselves). How have the tx's been altered? I'll look at the diffs from the above.

I have already adapted Abe, and am in the process of hosting it. Hopefully sometime this week.
...
The answer to your question in 2 fold:

There is an extra time stamp after the version field in each transaction.

You need to use the most recent version of Abe (few days old) as it auto cuts some bytes at the end of the block that really wreck chaos with Abe's ability to keep track of its position when translating the blk0001 to its database.

That's great, im not too far from where you are.  Will you be releasing the changes / committing to abe tree?

I have run into some strange new issues with the latest commit, so either I have to fix it in this commit, or just continue to use the earlier version.

There are some other issues, while not show stoppers, need to be addressed.

After I polish it a bit more, I will see if John Tobey would like me to release a commit. I feel it is his baby, his choice.

For now I would like to gauge the interest in a hosted version. I would have to buy at least a VPS (simple web hosting will not work) to host it one, which of course incurs a monthly fee.

I would probably use advertising on the site to cover costs, so before I go out on this venture I kind of want to see how much interest the PPC community has in it.

I think it's a good idea