Sunny,
Would the Nonce value equal to 0, be the best flag to detect a Proof of stake block?
That's one way or you can check the hex block hash doesn't begin with 8 zeroes. Internally ppcoind doesn't use the above methods to decide. The most safe way is to verify that transaction #1 exists and it's output #0 is empty (amount is 0). |
|
|
|
Nice chart! Gratz  |
|
|
|
I didn't redownload or anything and the block count is accurate. {
"version" : "v0.2.0ppc-beta",
"protocolversion" : 60002,
"walletversion" : 60000,
"balance" : -,
"newmint" : -,
"stake" : 0.00000000,
"blocks" : 6404,
"moneysupply" : 82954.04147400,
"connections" : -,
"difficulty" : 13048.66171444,
"testnet" : false,
"errors" : ""
}
This is a bug. There is a tiny window where if ppcoind is stopped after a block is accepted but moneysupply figure is not yet written for that block. So when you restart ppcoind moneysupply starts from 0 again. I will look into how to avoid this situation. Meanwhile the workaround is to redownload block chain. That is, first backup wallet ppcoind backupwallet <destination-backup-wallet-name>ppcoind stopthen remove all directories/files under the wallet directory except for leaving wallet.dat and ppcoin.conf in place. then start up ppcoind again. Thanks for reporting the issue! (If you know how to search logs you can send me the relevant logs where this problem occurred. You can search for 'moneysupply=' and look for where it started from 0 again. You should see ppcoind stop/start around the time) |
|
|
|
|
Mint per block is calculated as
9999 / (difficulty ** (1/4))
Then you can derive your expected daily earnings from there.
|
|
|
|
I noticed 'moneysupply' started a couple of days ago at zero again, why is this ?
moneysupply is tied to the block you are at. If you are redownloading block chain, then it is normal to see it increasing from 0 as block chain is downloaded. Other than that it shouldn't be shown as 0. |
|
|
|
The thing with 51% atack protection is that if you can have it, everyone can have it. So could be hundreds of altcoins like PPC out there in a few months and very little money going to the "new protected altcoins" population of altcoins".
You probably miss the point about ppcoin project. We are not trying to solve 51% attack, as that is the nature of decentralization. We are trying to solve energy consumption as we believe decentralization does not require massive use of energy. If by 51% protection you refer to the central checkpointing it now only serves as a bootstrapping safety measure and will be gradually weakened/eventually removed to achieve similar decentralization level of Bitcoin and Litecoin. |
|
|
|
Ya nothing works until you put the hard work in. Thanks for doing the hard work to make the explorer available to community |
|
|
|
|
FYI the first proof-of-stake block showed up on block chain:
sunny> ppcoind getblockhash 6325
514e141ef5778299506b779145c9c94d78b0603281246741cb31f112c6635365
sunny> ppcoind getblock 514e141ef5778299506b779145c9c94d78b0603281246741cb31f112c6635365
{
"hash" : "514e141ef5778299506b779145c9c94d78b0603281246741cb31f112c6635365",
"size" : 2415,
"height" : 6325,
"version" : 1,
"merkleroot" : "6b4da40f28a8eaa49f75dfee7093f0f8bbe2e78be5f739bf258917fe9694629b",
"time" : "2012-09-18 22:01:24 UTC",
"nonce" : 0,
"bits" : "1c00ffff",
"difficulty" : 256.00000000,
"mint" : 2.03000000,
"previousblockhash" : "00000000000419baabec9789419e757103ec9af618d65321c8f167247cf8bd10",
"nextblockhash" : "000000000000712540f7f2752cbfcea2314c9ee2a3bb7111fdc3822e781efd59",
"tx" : [
"3e30aa6c1e748784d69e35a0e29ae35442db97cba51312e597d54e984e91fa6e",
"6476ede8707a8090c6b861c92efedbea4d72763d4e9b01039b2f5de913a85305",
"01de3e5d12e5a573b7bef8572c03c64e1f589926c7cd75eea74e1384372bd145",
"a87dff197b0a90ee7486156c9c1753cc7b51bfa2e856529f948b28fc7cdcdc56",
"da979b24457f8cf9ba0386b3033c9d72647e69509fa3254a071e609e8a286c42"
]
}
|
|
|
|
|
Inflation model cannot be changed or market will lose confidence in the currency. It doesn't matter that a majority agree with the change or not. Market often disagrees with majority opinion.
Even just smoothing the sudden drop would be a dangerous exercise as that opens a precedence that inflation model is changeable.
|
|
|
|
|
Generally speaking any provable quantity can be a candidate, hashrate, coins, coin-age etc. But not addresses, keys as those are not provable entity thus subject to sybil attack.
Yes the 'voting power' needs to be proportional to the provable quantity and this is what gives protection to the network.
|
|
|
|
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. |
|
|
|
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. |
|
|
|
|
If anyone finds an easy setup to reproduce the memory leak issue please let me know. Thanks,
|
|
|
|
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. |
|
|
|
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!
|
|
|
|
|
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.
|
|
|
|
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? |
|
|
|
|
Hi coinotron,
I have sent you a pm.
|
|
|
|
|
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.
|
|
|
|
|
Pegging currency value to energy cost sounds nice on the surface, but if you are losing value against Bitcoin capital would like to flow to Bitcoin. Assuming the benefit would be that merchants don't need to reprice products daily but market has been developing solutions to this by having computers automatically adjust price based on exchange rate, so the advantage there would be rather limited.
Not to mention properly pegging value is a daunting task without some form of centralization, demonstrated by the attempt of solidcoin. It's likely going to end up still with fairly volatile exchange rate.
|
|
|
|
|
Show Posts
