Hello all,
I just encrypted my wallet with a passphrase.. but now it shows the following error in the getinfo result?? any ideas?? will this affect proof of stake minted blocks??
{
"difficulty" : 10670.85500473,
"testnet" : false,
"keypoololdest" : 1348302135,
"keypoolsize" : 100,
"paytxfee" : 0.01000000,
"unlocked_until" : 0,
"errors" : "Info: Minting suspended due to locked wallet."
}
Many thanks
Topic: [ANN] [PPC] PPCoin Released! - First Long-Term Energy-Efficient Crypto-Currency - page 122. (Read 685197 times)
September 22, 2012, 04:30:12 AM
September 21, 2012, 08:51:26 PM
Just a small update to the server uploaded.
The explorer will now recognize Proof of Stake blocks and label them as such. A Future update will place a flag in the database and will have a function just to list those blocks.
Unknown address continues to be a issue:
I have found there is a difference between PPC and BTC raw transaction output. Hopefully it is a simple fix that is just escaping me right now, or maybe it is nothing at all and the BTC or PPC script is just further along the decoding before being displayed.
Example:
BTC : "040ebf936eae88bf59f619d32dc1d7630b222d3374678ba7b4333f2954ac5b0341f55b282fd7c6c c7ff866a4ed66cf301c9db063ca8bfe924f6c728f05d1560f61"
PPC: "2102a9b038cd9042a50919055eaa9380fb2ef4c3f7516c21e3bd0e029e0218db0939ac"
Abe's decoding engine continues to throw what appears to be random characters into the Hex output during OP CODE and Key separation. The database has clean versions of the scripts and if I place a small three line hex formatter to parse a script, it comes out neat and clean, but without OP CODES or in the "\xx" format the rest of the routines want.
The explorer will now recognize Proof of Stake blocks and label them as such. A Future update will place a flag in the database and will have a function just to list those blocks.
Unknown address continues to be a issue:
I have found there is a difference between PPC and BTC raw transaction output. Hopefully it is a simple fix that is just escaping me right now, or maybe it is nothing at all and the BTC or PPC script is just further along the decoding before being displayed.
Example:
BTC : "040ebf936eae88bf59f619d32dc1d7630b222d3374678ba7b4333f2954ac5b0341f55b282fd7c6c c7ff866a4ed66cf301c9db063ca8bfe924f6c728f05d1560f61"
PPC: "2102a9b038cd9042a50919055eaa9380fb2ef4c3f7516c21e3bd0e029e0218db0939ac"
Abe's decoding engine continues to throw what appears to be random characters into the Hex output during OP CODE and Key separation. The database has clean versions of the scripts and if I place a small three line hex formatter to parse a script, it comes out neat and clean, but without OP CODES or in the "\xx" format the rest of the routines want.
September 21, 2012, 02:57:10 PM
Yeah, that was the path I have been working on.
I may have narrowed it down a bit,
It appears that ABE is not processing the OP CODES properly,though the routine that catches the OP CODES is working, the routine that extracts the data is picking up garbage.
For example:scriptpubkey with a CHECKSIG OP CODE "210381f673908e54a91e4324bf55f875ae53cbb1078336c88c15ec2ba75cf50cd74bac"
The routine extracts it as: \x03\x81\xf6s\x90\x8eT\xa9\x1eC$\xbfU\xf8u\xaeS\xcb\xb1\x07\x836\xc8\x8c\x15\xec+\xa7\\\xf5\x0c\xd7K
Has there been any change from the bitcoin daemon that would effect how a program would have to extract a key from the surrounding OP CODE? Are there added codes or removed codes?
If I can rule out a change in the daemon, it will allow me to center my attention on other possible causes.
There is no change to the script format and engine. The only thing I can think of is that the conversion from public key to address is slightly different as the version has been changed. Presumably abe handles the version change already so I am not sure why it doesn't work if it works for Bitcoin.
September 21, 2012, 02:44:45 PM
Track down that nasty 'unknown' bug, I have put some time into this bug, but it still eludes me.
I've browsed the explorer a bit, all the unknown that I noticed seem to be related to pay-to-public-key payment type.
Not sure how abe handles this but normally you can just extract the public key from script and convert it to address (hash160 + base58 conversion).
Yeah, that was the path I have been working on.
I may have narrowed it down a bit,
It appears that ABE is not processing the OP CODES properly,though the routine that catches the OP CODES is working, the routine that extracts the data is picking up garbage.
For example:scriptpubkey with a CHECKSIG OP CODE "210381f673908e54a91e4324bf55f875ae53cbb1078336c88c15ec2ba75cf50cd74bac"
The routine extracts it as: \x03\x81\xf6s\x90\x8eT\xa9\x1eC$\xbfU\xf8u\xaeS\xcb\xb1\x07\x836\xc8\x8c\x15\xec+\xa7\\\xf5\x0c\xd7K
Has there been any change from the bitcoin daemon that would effect how a program would have to extract a key from the surrounding OP CODE? Are there added codes or removed codes?
If I can rule out a change in the daemon, it will allow me to center my attention on other possible causes.
September 21, 2012, 11:10:14 AM
Track down that nasty 'unknown' bug, I have put some time into this bug, but it still eludes me.
I've browsed the explorer a bit, all the unknown that I noticed seem to be related to pay-to-public-key payment type.
Not sure how abe handles this but normally you can just extract the public key from script and convert it to address (hash160 + base58 conversion).
September 21, 2012, 10:47:08 AM
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).
September 21, 2012, 10:19:13 AM
Updated PPC search uploaded.
This version contains mostly cosmetic improvements.
Sunny,
Would the Nonce value equal to 0, be the best flag to detect a Proof of stake block?
I will start a PPC search thread, after the next version, just kinda of holding back to avoid getting slammed until a few more bugs are worked out.
I noticed a big slowdown in server response this mourning, I reset the server hoping it was a memory or CPU usage problem (although I did not notice anything strange under ps -aux).
The slowdown persisted, it seems to have cleared up for now, it must have been something on the hosting end.
Next Version Goals:
Start running PPC Search as daemon as of now it is running as a process.
Track down that nasty 'unknown' bug, I have put some time into this bug, but it still eludes me.
Program the ability to detect and correctly display amounts in Proof of Stake blocks.
Edit: I was looking at the API interface recently, the ABE engine sees the PPC chain as PPCoin. I will make corrections in the next version to clear up the instructions.
This version contains mostly cosmetic improvements.
Sunny,
Would the Nonce value equal to 0, be the best flag to detect a Proof of stake block?
I will start a PPC search thread, after the next version, just kinda of holding back to avoid getting slammed until a few more bugs are worked out.
I noticed a big slowdown in server response this mourning, I reset the server hoping it was a memory or CPU usage problem (although I did not notice anything strange under ps -aux).
The slowdown persisted, it seems to have cleared up for now, it must have been something on the hosting end.
Next Version Goals:
Start running PPC Search as daemon as of now it is running as a process.
Track down that nasty 'unknown' bug, I have put some time into this bug, but it still eludes me.
Program the ability to detect and correctly display amounts in Proof of Stake blocks.
Edit: I was looking at the API interface recently, the ABE engine sees the PPC chain as PPCoin. I will make corrections in the next version to clear up the instructions.
September 19, 2012, 10:05:41 AM
Thanks, no problem, log -> pm
September 19, 2012, 09:29:54 AM
I didn't redownload or anything and the block count is accurate.
Code:
{
"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" : ""
}
"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
ppcoind stop
then 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)
September 19, 2012, 08:59:27 AM
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.
I didn't redownload or anything and the block count is accurate.
Code:
{
"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" : ""
}
"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" : ""
}
September 19, 2012, 08:39:08 AM
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.
September 19, 2012, 08:27:49 AM
I noticed 'moneysupply' started a couple of days ago at zero again, why is this ?
September 19, 2012, 03:31:17 AM
http://ppcexplore.org
The website now auto directs to the correct port.No need to use a port number anymore.
Now to work on the bugs:
1. The unknown address issue. Mostly from coin generation transactions, however I have noticed it on other transactions.
2. Amounts wrong for blocks 6325 +, most likely due to proof of stake being turned on. Sunny, if you could tell me where and what type of data the proof of stake added to the block, it would be a huge time saver for me.
I have turned the ppcoin daemon off until I fix this issue as ABE would just fill its database with the wrong information. I will need to do a rollback or reconstruct of the database after this bug is fixed.
3. Replace Abe symbol with PPC symbol, along with various other cosmetic fixes.
4. For now I have Abe reading the extra transaction time stamp into a placeholder variable, If really wanted I can make a database addition and display the value. I am of the opinion that it is not really necessary, but if enough people want it I will put it in.
I am sure there are plenty more, but that is the short list for now.
EDIT: It appears the amount bug is only for block 6325 and the blocks after appear to be fine, so it moves to the bottom of the list. I will probably just manually fix the entry for block 6325.
The website now auto directs to the correct port.No need to use a port number anymore.
Now to work on the bugs:
1. The unknown address issue. Mostly from coin generation transactions, however I have noticed it on other transactions.
2.
I have turned the ppcoin daemon off until I fix this issue as ABE would just fill its database with the wrong information. I will need to do a rollback or reconstruct of the database after this bug is fixed.
3. Replace Abe symbol with PPC symbol, along with various other cosmetic fixes.
4. For now I have Abe reading the extra transaction time stamp into a placeholder variable, If really wanted I can make a database addition and display the value. I am of the opinion that it is not really necessary, but if enough people want it I will put it in.
I am sure there are plenty more, but that is the short list for now.
EDIT: It appears the amount bug is only for block 6325 and the blocks after appear to be fine, so it moves to the bottom of the list. I will probably just manually fix the entry for block 6325.
September 18, 2012, 05:35:34 PM
I have hosted and made available a PPC coin explorer.
PLEASE NOTE: This project is in a VERY early stage and nowhere near the final product.
I am sure there are bugs and security holes abound (but there is nothing on this server except ABE..
)
I thought I would make it available for use, but it will be up and down as I upload fixes.
http://www.ppcexplore.org:2750/
You need to use the port as I have not made the normal port 80 web page yet, as I said EARLY STAGE.
PLEASE NOTE: This project is in a VERY early stage and nowhere near the final product.
I am sure there are bugs and security holes abound (but there is nothing on this server except ABE..
)I thought I would make it available for use, but it will be up and down as I upload fixes.
http://www.ppcexplore.org:2750/
You need to use the port as I have not made the normal port 80 web page yet, as I said EARLY STAGE.
Awesome dude!
September 18, 2012, 05:34:54 PM
Ya nothing works until you put the hard work in. Thanks for doing the hard work to make the explorer available to community 
September 18, 2012, 05:28:31 PM
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"
]
}
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"
]
}
OMG...LOL
First block with proof of stake breaks ABE for that block and after .....
Well, until I fix Abe for proof of stake, you can still use the explorer for the blocks before 6325.
September 18, 2012, 05:17:19 PM
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"
]
}
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"
]
}
September 18, 2012, 05:14:48 PM
I have hosted and made available a PPC coin explorer.
PLEASE NOTE: This project is in a VERY early stage and nowhere near the final product.
I am sure there are bugs and security holes abound (but there is nothing on this server except ABE..)
I thought I would make it available for use, but it will be up and down as I upload fixes.
http://www.ppcexplore.org:2750/
You need to use the port as I have not made the normal port 80 web page yet, as I said EARLY STAGE.
PLEASE NOTE: This project is in a VERY early stage and nowhere near the final product.
I am sure there are bugs and security holes abound (but there is nothing on this server except ABE..
)I thought I would make it available for use, but it will be up and down as I upload fixes.
http://www.ppcexplore.org:2750/
You need to use the port as I have not made the normal port 80 web page yet, as I said EARLY STAGE.
September 18, 2012, 07:17:20 AM
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?
./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
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
September 17, 2012, 07:12:48 PM
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?
./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
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.
Jump to: