After looking at some stake code, I wonder if the Hobonickels dev, or original poster, realize that everything in this thread, including the coin itself, is the exact dictionary definition of Ponzi scam. Early entrants are rewarded with huge, unsustainable minting rewards, just like in a regular Ponzi scam, then as more people join in the system, the unsustainable stake rewards slow to a crawl due to stake amount being linked to a difficulty variable, eventually going exponentially lower. There's really no rationalizing around it. It is for all intents an purposes, identical to a Ponzi scam.
Ponzi scheme - a fraudulent investment operation that pays returns to its investors from existing capital or new capital paid by new investors, rather than from profit earned by the individual or organization running the operation. Operators of Ponzi schemes usually entice new investors by offering higher returns than other investments, in the form of short-term returns that are either abnormally high or unusually consistent. The perpetuation of the high returns requires an ever-increasing flow of money from new investors to sustain the scheme
The only way for a proof of stake coin to not be a Ponzi scam, is if interest rate was static, and not linked to any difficulty variable. I suggest the Hobonickel dev work on implementing a method to create static interest rates before governments come in for crypto regulation, otherwise they will either outright ban the Hobonickel in most countries, or possibly try to throw you in some kind of gulag.
Why are you putting so much energy into finding problems where there is none ? What's wrong with variable interest? It's purpose is to have a sustainable inflation rate. on the long term. doubling the supply every year is not very wise at some point in the growth of this coin. And what's wrong with the fact that the people making it possible for this coin to grow right now be rewarded with a higher yield while difficulty is low? You not liking the name fine, I don't judge your opinion. But bringing this up has a Ponzi scheme... I mean come on! don't you have better things to do? "a fraudulent investment operation that pays returns to its investors from existing capital or new capital paid by new investors"new capital is NOT paid by investors or from existing capital, but MADE by the network based on some rules... like any other crypto right now. Plus, if Investors would pay anything for this currency it would be the actual value determined by the market. I think I'll stop here... and maybe you should too since your comments are getting less and less constructive. He's just trolling. There is no reason to listen to him anymore. Best we click that ignore button. Yeah I guess you're right. If I get his reasoning correct. Basically anyone who starts anything and his first to innovate or adopt it... is a crook anyone who makes money... is a crook. anyone who invest a lot of time and energy to achieve a certain goal... is a crook Since being successful is only for crooks! I think I got that about right! What about if I didn't buy the HBN but made a lot of them with PoW... is that still a Ponzi scheme? oh yeah my bad, it surely is! I guess R0ach is a crook too... why would he be interested in crypto or this thread for that matter? |
|
|
|
After looking at some stake code, I wonder if the Hobonickels dev, or original poster, realize that everything in this thread, including the coin itself, is the exact dictionary definition of Ponzi scam. Early entrants are rewarded with huge, unsustainable minting rewards, just like in a regular Ponzi scam, then as more people join in the system, the unsustainable stake rewards slow to a crawl due to stake amount being linked to a difficulty variable, eventually going exponentially lower. There's really no rationalizing around it. It is for all intents an purposes, identical to a Ponzi scam.
Ponzi scheme - a fraudulent investment operation that pays returns to its investors from existing capital or new capital paid by new investors, rather than from profit earned by the individual or organization running the operation. Operators of Ponzi schemes usually entice new investors by offering higher returns than other investments, in the form of short-term returns that are either abnormally high or unusually consistent. The perpetuation of the high returns requires an ever-increasing flow of money from new investors to sustain the scheme
The only way for a proof of stake coin to not be a Ponzi scam, is if interest rate was static, and not linked to any difficulty variable. I suggest the Hobonickel dev work on implementing a method to create static interest rates before governments come in for crypto regulation, otherwise they will either outright ban the Hobonickel in most countries, or possibly try to throw you in some kind of gulag.
Why are you putting so much energy into finding problems where there is none ? What's wrong with variable interest? It's purpose is to have a sustainable inflation rate. on the long term. doubling the supply every year is not very wise at some point in the growth of this coin. And what's wrong with the fact that the people making it possible for this coin to grow right now be rewarded with a higher yield while difficulty is low? You not liking the name fine, I don't judge your opinion. But bringing this up has a Ponzi scheme... I mean come on! don't you have better things to do? "a fraudulent investment operation that pays returns to its investors from existing capital or new capital paid by new investors"new capital is NOT paid by investors or from existing capital, but MADE by the network based on some rules... like any other crypto right now. Plus, if Investors would pay anything for this currency it would be the actual value determined by the market. I think I'll stop here... and maybe you should too since your comments are getting less and less constructive. |
|
|
|
You want to save this coin...
Force POS to only happen/accept on "Even" block numbers. That allows for POW between every POS, and that WILL give you some actual security. Until the last coin is mined, then, and only then, should POS be allowed to run on every block.
Even better, only allow POS on "every other", "Even block". (1/4)
That will limit the distribution to be more evenly also, as one CPU can't just build upon its own blocks which have not even had time to distribute through the network. (That alone, decreases security, because one POS puke could all come from one fast CPU and fork the whole chain.)
I have no anger of how this works right now either... But I find your suggestions interesting. I would love coin devs and knowledgable people to comment on this. There's always space for improvment and if it can contribute to secure the coin value and network, why not debate it? And as presstab said, it might not be 100% efficient the way it works now but for sure, people checking in on their mining will switch to other coins that rack in more profits. Who likes to pay the electricity bill just for the fun of it  |
|
|
|
I hear you r0ach. From a marketing standpoint the name does not reflect a "good" image. But that just about it... A name. Now everything else is pretty solid about this coin.
Maybe its just me, but I really like the name HoboNickels, it is unique, has a cool ring to it, actually is something that has existed historically, and best of all it isn't the typical <insertnamehere>coin. I personnaly don't dislike the name, like others have said and I have to say that I agree, it's a goofy name. I admit that that's what caught my attention in the first place. But like I said, from a "marketing" stand point, this name conveys a lot of baggage that people don't always associate with the "good standings" of society. It is a "renagade" kind of name. Maybe what I try to say is that it's not a politically correct name for a mass market usage. But that being said... I truly couldn't care less about that. And maybe that's why I am here and I enjoy this coins and it's community. I believe R0ach is right from where he comes from. But on the other hand, this coins is NOT for every one and NOT made to be used as a mass market currency... It's value lies in it's rarity, it's uniqueness and the return it yields... Much like the actual physical coins appeals to collectors. The longer you keep the coin, the more value you'll get out of it. |
|
|
|
You a miscer brah?
I see that you're mining some HBNs and was wondering what sort of investment I'd have to put into a rig in order to make somewhat of a profit/return on the machine, and in what sort of time period. I ask because I only have a small amount of funds to invest into the market, and was hoping to get the best return (obviously). Would you recommend just purchasing HBNs or look into a mining rig? Or wait until the price comes down?
Appreciate the advice
Investing in mining equipment is a costly enterprise. You return on investment depends greatly on how the network evolves. Meaning if difficulty sky rockets, you return on investment could be = to none. I think that if you have a small budget, don't feel like getting your hands dirty with hardware and constantly monitoring your rigs... Than buying them off of the market is the way to go. If your somewhat geeky and feel like it's a fun project to mine and don't worry to much about the financial outcome of your mining adventure, but rather focus on the project of mining and contributing to the evolution of crypto currencies in that matter... then have fun and equip yourself with some mining rigs hardware. Either way, do your research and make sure you know what you are getting into both ways... this is still all new and exciting adventures, with ton of potential, but risky to say the least. |
|
|
|
short answer, no
you need to have your coins in an open unlocked wallet to stake
Do stakes build up over time? Like let's say I hold my HBN for a year. Could I then take them out and get the accumulated interest? I'm guessing that since the wallet addresses would be different in that case, I'm just giving the interest to Cryptsy aren't I :  Well the best time to take your coins out is just after they generated a successful stake block. Knowing that it should take around 10 days for your coins to stake. Once they did, the coin age is destroyed. Meaning that your initial deposit date is irrelevant for the next stake (no additional benefits). A new cycle is starting right after that stake. So if you leave them one year, you would accumulate about 36, 10 days cycles @ 2% return. I am not sure if this answers your question, and I hope it clarifies things for you. Check out the link presstab provided, you might find more useful information there. I don't know if Cryptsy makes interest on the amount of HBN in their wallet... But one thing is sure is that you don't :p |
|
|
|
Yea, I didn't mean to be derogatory to the hobo dev, it's just that having your currency associated with hobos is going to be quite an obstacle to overcome. The name does pull a slight lead over Junkcoin and Leadcoin though.
I hear you r0ach. From a marketing standpoint the name does not reflect a "good" image. But that just about it... A name. Now everything else is pretty solid about this coin. I am curious to see what will happen to Mint in over a year. There client is way inferior compare to the HBN one. Well for a PoS coin at least. What Tranz as brought to the community is a major features. Let's give time to both of these coins, but for now, I feel like MINT devs rush out the launch of their coin, and I think they should of incorporated some of the features HBN clients has. So IMO, for now, Mint has a cool name, and an interesting launch strategy. But that's about it. |
|
|
|
Thanks man!!  Hope your holding a bunch yourself. I think we could see a 1mil market cap veerrryyy soon. Come on! We want this coin to fly under the radar for a few more months so that we can pick up more cheap coins! Hmm... maybe your right... I should even buy some more... Have a few spare BTC flying around... Hehe exactly, I really liked the 10000 satoshis mark. Cheap coins to build my account... I like the current price (and I am amazed of the 29800 satoshis test line at the time of writing this) but if this coin could stay under the radar longer I won't mind  I feel this is the kind of situation where I am happy to see people trusting the coin and sad that the price moves up so fast that I can't keep up to buy at a good price! And I'm not going to talk about the mining difficulty that sky rockets... damn bots Oh well. it's been a good day for my account anyways  |
|
|
|
i have no idea but it sent the amount that i wanted to send it wasnt short any fees
So hopefully what happened is that you sent the block, and it took the .001 transaction fee out of the block being sent. To make sure your other blocks are still aging, you can get into the "inputs" area. Expand the arrow and you will see all of your blocks and their number of confirmations. Hopefully none of your blocks were reset from a fee being taken out of it, and you would know if it was reset because the confirmations would be low. To avoid these types of scenarios, I keep a wallet for transactions and a wallet for staking coins. now it is showing my entire balance as one block now for next time do i need to go to input and check the blocks or leave it unchecked and it will do it automatically? i also have around 40k hbn do i need to split them in small amount to stake or will it stake at 40k? You should get used to using coin control. Or the wallet will choose the coins for you. Sometimes it will be ok, other times it may not. Having 1 huge block defeats the purpose of coin control. Better to have a few medium blocks some some can be sent, and others kept for stake. Your coins will stake fine at 40K. What will happen is that when the stake occurs. you will see a balance of ~40800 HBN. But if you look at your coins in coin control you will see 2 new blocks of ~20400 HBN. You shouldn't need to move those coins because these are still big chunks of coins. But over time, you will get smaller and smaller blocks. That's when your coin control will come handy. What I do, since I've had multiple transactions of of 100-200 HBN that have staked over time, is I combine the results and send them to a new address into a bigger block. after 2 months, a 100 HBN initial transaction will look like 64 transactions of about 1.5 HBN (plus the 2%). I like to regroup them in larger blocks so the stake yields bigger chunks of the 2% return. I also use the change address in that process. Since I want blocks of 1000 HBN I use the change address for the overage of transactions. I select the coins with coin control that have lowest confirmations that will bring me just over 1000 HBN. let's say I have 1003.764 HBN by selecting about 50 smaller blocks. The 3.764 HBN that I have there, I don't want it in my new block. So I use the change address to regroup all those overage and contain the smaller amounts. The transaction fee will be taken from that overage also, witch is fine, plus if I ever need to fill a gap in a subsequent transaction, I can alway go fishing in that change address since there is only small amounts in there, so I don't really care about destroying the age of the coins and losing 2% on those, even if they are mature for stake. I keep my more "important" block safe and good for stake. I don't really think it's a must to have round number blocks. I think that if you regroup your 1003.764 HBN into 1 block it's just as fine. But I like it when I see round amounts in my wallets. that's just me But the important thing here is that it's good practice to keep your wallet "clean" and organized. Check your coins with coin control maybe every 2-3 months and send all the small dust coins into a bigger chunk into a new wallet. If I remember reading in an earlier thread, with thousands of transactions in 1 wallet, the client starts to be longer to load. So keeping it clean helps in that matter also. |
|
|
|
That is going to be a great addition! But does this mean -salvagewallet doesn't get rid of orphans? I know it didn't for me but maybe I use it wrong.
-salvagewallet will for the wallet.dat file on start up. It doesn't hit every wallet in your %appdata% but it should remove orphans from the default wallet. ok that's why! I had 2 custom wallets  Thanks for the pro tip |
|
|
|
Correct.
They stake but take more time. That being said, I have virtualized a windows installation on my Mac with Virualbox because I just don't like having to many orphans. They clutter my wallet. But nothing to worry about other than that.
I know there is a way to "clean" those orphans with -salvagewallet. But I must be using it wrong since it doesn't work for me!
It seems to me that if you were to unload your wallet and then reload your wallet it would probably lose the orphans... right? I think that each time you load your wallet it grabs the wallet transactions from the blockchain not from the memory of the wallet client. I am not positive on this, but it is worth a try I think. Negative. Unloading/Reloading doesn't get rid of the orphans... It will if you unload from one client and reload on a different one where you never loaded the wallet before. In version 1.4 I will update the repairwallet rpc command to remove the orphans.
That is going to be a great addition! But does this mean -salvagewallet doesn't get rid of orphans? I know it didn't for me but maybe I use it wrong. Thnkas guys, yeah what you said was correct, It did stake but I got slightly more coins . The previous 2 transactions didn't go through but the 3rd did. I also think potentially it could do with the mac client becoming unresponsive. This happens a lot if I have the client open(this may have to do with mac laptops sleeping). If I close and reopen, wait for it to load the block chain its fine though and thats when it restacke'ed. Very happy with hobo nickels and must say stacking every 10 days feels quite good You're right stacking every 10 days is sweet. I don't think I ever had a "responsiveness" issue. I didn't try the close/open sequence i just let it open and eventually I'd have a successful stake. Talking with Tranz it might be a timing issue with the network. Tranz is looking into a possible solution, but maybe the Mac client is slower to talk to the network and if there is another client staking at the same time, you get the orphan. On my setup, I use the same physical machine with a virtualization of windows 7 and on windows I barely get orphans where as on the mac it's the opposite... I barely get valid blocks! they go thru, but at a much slower rate! |
|
|
|
Presstab is correct, these are orphans. The Mac client does work and will stake, however the staking algorithm is not very efficient on it. So you end up with more orphans then accepted. Not to worry though. If they are orphaned they retain their coin age and try again. Plus you will get the increased interest once they are finally accepted. I suggest using larger coin blocks with the Mac client.
Unick and I did some test on test net with the mac clients. They are producing the correct solution to solve a PoS block ,but they just do it a bit slower.
Correct. They stake but take more time. That being said, I have virtualized a windows installation on my Mac with Virualbox because I just don't like having to many orphans. They clutter my wallet. But nothing to worry about other than that. I know there is a way to "clean" those orphans with -salvagewallet. But I must be using it wrong since it doesn't work for me! |
|
|
|
Thanks. This is what my debug console looks like now 14:29:54  Welcome to the HoboNickels RPC console. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Type help for an overview of available commands. 14:30:47  addnode 50.125.160.28:7372 14:30:47  addnode <node> <add|remove|onetry> Attempts add or remove <node> from the addnode list or try a connection to <node> once. (code -1) 14:31:21  addnode 5.249.152.30:7372 14:31:21  addnode <node> <add|remove|onetry> Attempts add or remove <node> from the addnode list or try a connection to <node> once. (code -1) 14:32:37  addnode 5.39.90.17:7372 14:32:37  addnode <node> <add|remove|onetry> Attempts add or remove <node> from the addnode list or try a connection to <node> once. (code -1) 14:33:02  addnode 162.243.251.173:7372 14:33:02  addnode <node> <add|remove|onetry> Attempts add or remove <node> from the addnode list or try a connection to <node> once. (code -1) 14:33:26  addnode 94.23.31.223:7372 14:33:26  addnode <node> <add|remove|onetry> Attempts add or remove <node> from the addnode list or try a connection to <node> once. (code -1) Does this look right? No connections yet but I'll keep the wallet open. Also, If there's a HBN noob forum, kindly point me there. I don't want to become an irritation but I do want to figure things out and become a hobonickel miner. yeah pepto, that looks about right... give it time to pick up a connection. If it doesn't work. Try opening up your firewall |
|
|
|
4) PoS can be used as a financial weapon. If you look at HBN from another angle, its pretty much a High-Yield Investment Program.
If Goldman Sachs came out today and announced a Scrypt-based "digital bond" paying out 100% annually, they would create a billion dollar market overnight. You would get every heavy hitter dumping money into that bond just for a chance to double up.
Exactly. What happens when all tech stocks and real world companies are replaced by nothing but Goldman Sachs, financial vehicle, proof of stake coins? The world collapses. This is obviously not a sustainable model. When government gets involved making Bitcoin laws, they're either going to come down on proof of stake coins hard, or they will have the same relationship how Wall Street currently exists, to enrich insiders and screw over everyone else. "Interest" is not really something I want to see survive in the Bitcoin protocol's future. The idea of trying to replicate the current, broken financial system is outrageous. I obviously don't see how this could be used as a "financial weapon" or even know what a financial weapon looks like. But I think PoS is a more efficient way to mine new coins than GPUs electricity addict and heat producing mechanism. Plus why is "interest" or yield so bad? I think it has it's use in some markets. How is deflation any better? today you buy some bread for 1$, and down the road, your bread cost you 50 cents because of deflation. Wouldn't you want to wait to buy your bread so you could buy 2 instead of 1? How can you have a sustainable business model based on deflation? Can the "ideal" world, if it exist, be a a mix of both inflationist and deflationist currencies? I can see an HBN type of currency witch would be used as some sort of "savings" account or whatever the financial term is for that and another more "day to day" currency to buy other types of goods. Life is complexe and I don't think there is any ONE good solution. And what is really broken about our financial system is that it is closed and reserved to insiders... but with this new cryptocurrency wave... everything opens up and is accessible to you, me and everyone out there. And the more we put effort in sharing and building better systems TOGETHER, I REALLY don't see how only "insiders" would benefit from this. Since the merely concept of insiders can't exist if everything is "open source" and public. |
|
|
|
unick, if you are available some night, I wouldn't mind doing a testnet run, just our 2 nodes, and see how that flushes out.
If not no worries. We can discuss over PM. Thanks
I PM you |
|
|
|
So as I write this I am restarting the Mac client but with the zip version of the compile (witch is on github now) and I'll see if the orphan block will try to restake later this night or tomorrow and see if the PoS block gets accepted or rejected with that client and I'll keep you posted with that.
Thanks so much. This will be helpful. ok, as soon as the client synced the block chain, it did succesfully mine a PoS block. So it looks like the dmg compile had some kind of a bug in it. I'll still keep an eye on it tomorrow for any kind of unwanted behaviors. and I'll report if any issues are found. Prefect thanks for trouble shooting this for us. Let me know if Coin Control seems good, and if you see any different between the win version (if you use it) and the Mac version. Feel free to post an address for your help. okay, here's a quick update. I had to redownload the blockchain because I had issues with the wallet (I think it's the corrupted issue that was mentioned earlier in this thread). That took over 24 hours but now my wallets load fine. So it's been 9 hours that I let the wallet sit for it to stake and while it does stake, I find that the orphan rate is way higher than on the windows client. It could be just a coincidence, I don't know for sure. On 13 inputs, I had 6 orphan (all one after the other) the last input just got in ~30 minutes ago and was accepted. I'll continue to monitor and report. If you need more details, I would be glad to share them with you. Just let me know and what you need exactly I noticed the orphan rate was higher on the mac in version 1.2 as well. A friend took a snapshot of his transactions. The coins did eventually get accepted but seemed to take 2-1 orphan to accept. Were as windows I get 90% accepted. So this might be an issue with the mac client, I got 2 more orphans since I posted this morning. Do you have an idea as why this happens? As of right now, no I do not know. 2 potential reasons come to mind. 1 the stake takes too long in the kernel and once it gets out, the difficulty or time for next PoS has changed and it is no longer valid. The other reason may the calculation done are not 100% correct on the mac client. More information can be retrieved by starting the client with the following switches: -printcoinstake -printcreation Perhaps the debug.log will give a clue as to why the mac is not quite right, at least for stakes. okay, there is a lot of orphan but some get accepted. I think I found the lines where in the debug.log file concerning the PoS. This one is Accepted 05/02/2014 22:01:32 CPUMiner : proof-of-stake block found 2882126ee15f236c4b34c2bfe118ccfe3e763db96608ed635838613cd73f8eb4
05/02/2014 22:01:32 CPUMiner:
05/02/2014 22:01:32 new block found
hash: 2882126ee15f236c4b34c2bfe118ccfe3e763db96608ed635838613cd73f8eb4
target: 000000ffc6000000000000000000000000000000000000000000000000000000
05/02/2014 22:01:32 CBlock(hash=2882126ee15f236c4b34c2bfe118ccfe3e763db96608ed635838613cd73f8eb4, ver=4, hashPrevBlock=000000004c44c2ef8acac86dad647f773ce51311507633305f6ad6c3845d04fe, hashMerkleRoot=f49049fe1af4959fc61f1ba99ddd0810ce18f05362ed71bc1c15c2dda74b91c0, nTime=1391637683, nBits=1e00ffc6, nNonce=0, vtx=5, vchBlockSig=3046022100cf172b3044c3a098c0128e88d7987933d30bcf36b9aab946b046ad39ecc05c61022100a655bda02b222b7e75227852921fa2e529ca9e175406a7de77771c380810aae4)
05/02/2014 22:01:32 Coinbase(hash=44bd190b6f, nTime=1391637683, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 03349c08016b062f503253482f)
CTxOut(empty)
Coinstake(hash=0c324d32c1, nTime=1391637683, ver=1, vin.size=1, vout.size=3, nLockTime=0)
CTxIn(COutPoint(8f65762ae5, 1), scriptSig=3045022061da17cc55406b31)
CTxOut(empty)
CTxOut(nValue=194.472054, scriptPubKey=03883741c91ad164857563a203d4d433dd5759487882eab73b677fc09ac1d9095c OP_CHECKSIG)
CTxOut(nValue=194.472055, scriptPubKey=03883741c91ad164857563a203d4d433dd5759487882eab73b677fc09ac1d9095c OP_CHECKSIG)
CTransaction(hash=31a0da62dd, nTime=1391637682, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(e55a0b8d97, 1), scriptSig=304402204ece151e01129092)
CTxOut(nValue=0.999, scriptPubKey=OP_DUP OP_HASH160 dd8a04cef8a5f94e410a14397923e0f8f1abcfd8 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=424.706267, scriptPubKey=OP_DUP OP_HASH160 3409d5a47a3638af381c46dc2785b10c8bba6641 OP_EQUALVERIFY OP_CHECKSIG)
CTransaction(hash=b77d08076f, nTime=1391637659, ver=1, vin.size=3, vout.size=2, nLockTime=0)
CTxIn(COutPoint(e24183be68, 0), scriptSig=30450221009ea2a8162391df)
CTxIn(COutPoint(8b6d8d9cfe, 0), scriptSig=30440220160989eba9d92efe)
CTxIn(COutPoint(201b4b8a70, 0), scriptSig=3046022100a75ef852e5178d)
CTxOut(nValue=0.01474, scriptPubKey=OP_DUP OP_HASH160 d162ff2f6f0f0427fe028786048d8eb4c2baf87d OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5.098999, scriptPubKey=OP_DUP OP_HASH160 562fe2aff8ce538136df8671e901fddb713a5b67 OP_EQUALVERIFY OP_CHECKSIG)
CTransaction(hash=7889cfab76, nTime=1391637615, ver=1, vin.size=6, vout.size=2, nLockTime=0)
CTxIn(COutPoint(5de0c4dc39, 0), scriptSig=304602210084cea31a5e839b)
CTxIn(COutPoint(dc6ddad90b, 0), scriptSig=304502205fcff33a97f6ba85)
CTxIn(COutPoint(99e749d26e, 0), scriptSig=3046022100b16f14c2216efd)
CTxIn(COutPoint(148a761c24, 0), scriptSig=3046022100802ad4aa14bec9)
CTxIn(COutPoint(8c92847078, 0), scriptSig=304402203f7122cfb81f9216)
CTxIn(COutPoint(72a3aa9c11, 0), scriptSig=30460221009ddc83c01681b1)
CTxOut(nValue=1.229028, scriptPubKey=OP_DUP OP_HASH160 046dce0d4e442878623cad3ab00afc23b599d98c OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=25.511499, scriptPubKey=OP_DUP OP_HASH160 e0a8197ae0212f1241155d3e9be906419266dded OP_EQUALVERIFY OP_CHECKSIG)
vMerkleTree: 44bd190b6f 0c324d32c1 31a0da62dd b77d08076f 7889cfab76 e4c689aaa8 76788048ca e22cb901a7 d91281d634 6effce0ab9 f49049fe1a
05/02/2014 22:01:32 generated 0.00
05/02/2014 22:01:32 AddToWallet 0c324d32c1 new
05/02/2014 22:01:33 WalletUpdateSpent found spent coin 375.1916hbn 8f65762ae56f66df738c05266c2ac6118ee5086cfdcfd7631bb12c02caa98ee2
05/02/2014 22:01:33 NotifyTransactionChanged 8f65762ae56f66df738c05266c2ac6118ee5086cfdcfd7631bb12c02caa98ee2 status=1
05/02/2014 22:01:33 NotifyTransactionChanged 0c324d32c145b82a4cb55758ba92c02d46848beabeaf28aa80fb39cf033b2725 status=0
05/02/2014 22:01:33 updateWallet 8f65762ae56f66df738c05266c2ac6118ee5086cfdcfd7631bb12c02caa98ee2 1
05/02/2014 22:01:33 inWallet=1 inModel=1 Index=615-616 showTransaction=1 derivedStatus=1
05/02/2014 22:01:33 updateWallet 0c324d32c145b82a4cb55758ba92c02d46848beabeaf28aa80fb39cf033b2725 0
05/02/2014 22:01:33 inWallet=1 inModel=0 Index=46-46 showTransaction=1 derivedStatus=0
05/02/2014 22:01:34 SetBestChain: new best=2882126ee15f236c4b34 height=564276 trust=828671574817 date=05/02/2014 22:01:23
05/02/2014 22:01:34 ProcessBlock: ACCEPTED
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:34 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:35 received getdata for: block 2882126ee15f236c4b34
05/02/2014 22:01:35 ProcessSyncCheckpoint: sync-checkpoint at 2882126ee15f236c4b34c2bfe118ccfe3e763db96608ed635838613cd73f8eb4
05/02/2014 22:01:36 connection timeout
05/02/2014 22:01:36 Flushing wallet.dat
05/02/2014 22:01:36 Flushed wallet.dat 275ms
This one is orphaned 05/02/2014 22:37:06 trying connection 77.91.163.23:7372 lastseen=13.0hrs
05/02/2014 22:37:08 received block 0000000045fa8b0ec1de
05/02/2014 22:37:09 SetBestChain: new best=0000000045fa8b0ec1de height=564366 trust=829108533648 date=05/02/2014 22:36:04
05/02/2014 22:37:09 AcceptPendingSyncCheckpoint : sync-checkpoint at 0000000045fa8b0ec1de0a5da141c8bf49b616b9f667773dc023b2493f7f2dce
05/02/2014 22:37:09 ProcessBlock: ACCEPTED
05/02/2014 22:37:09 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:09 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:09 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:09 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:10 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:10 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:10 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:10 getblocks 321359 to 3a81de695dced54584cb limit 500
05/02/2014 22:37:10 getblocks stopping at 321541 3a81de695dced54584cb
05/02/2014 22:37:10 getblocks 318858 to 00000000000000000000 limit 500
05/02/2014 22:37:10 getblocks stopping at limit 319357 00000000a5426558b279
05/02/2014 22:37:10 getblocks 512005 to 00000000dc809cb48408 limit 500
05/02/2014 22:37:10 getblocks stopping at limit 512504 000000011e8eaa700927
05/02/2014 22:37:10 getblocks 512005 to 00000000d4f529bbae49 limit 500
05/02/2014 22:37:10 getblocks stopping at limit 512504 000000011e8eaa700927
05/02/2014 22:37:10 getblocks 511869 to 00000000000000000000 limit 500
05/02/2014 22:37:10 getblocks stopping at limit 512368 000000015f55c4a62e35
05/02/2014 22:37:10 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:10 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:11 CPUMiner : proof-of-stake block found 5ffe0d189a6b9c0e6021276070e698c1bb3844f651148d7a354866a54c5cedaf
05/02/2014 22:37:11 CPUMiner:
05/02/2014 22:37:11 new block found
hash: 5ffe0d189a6b9c0e6021276070e698c1bb3844f651148d7a354866a54c5cedaf
target: 000000ff41000000000000000000000000000000000000000000000000000000
05/02/2014 22:37:11 CBlock(hash=5ffe0d189a6b9c0e6021276070e698c1bb3844f651148d7a354866a54c5cedaf, ver=4, hashPrevBlock=0000000045fa8b0ec1de0a5da141c8bf49b616b9f667773dc023b2493f7f2dce, hashMerkleRoot=1ad02a8df13459dbb7d9eccc2d227187d82de43b5d04218bb590a9559bb22f5f, nTime=1391639821, nBits=1e00ff41, nNonce=0, vtx=2, vchBlockSig=304502206cffff8c9d79640d9d398c35410fee3896f4cfaf1d42ea63449ae3f7cd1c72f5022100eccc5605bf284cd1887a07eb588b68fbeb1fa3d065094b591390450bd5d20e6f)
05/02/2014 22:37:11 Coinbase(hash=3b889a27b7, nTime=1391639821, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 038f9c080106062f503253482f)
CTxOut(empty)
Coinstake(hash=4018255361, nTime=1391639821, ver=1, vin.size=1, vout.size=3, nLockTime=0)
CTxIn(COutPoint(498cd4bde8, 2), scriptSig=3045022100b2fa025a4a6872)
CTxOut(empty)
CTxOut(nValue=73.005008, scriptPubKey=03de18db67a372f7c1a8f086787d436a0a984a356c4289d18eb81690ad18198b9c OP_CHECKSIG)
CTxOut(nValue=73.005009, scriptPubKey=03de18db67a372f7c1a8f086787d436a0a984a356c4289d18eb81690ad18198b9c OP_CHECKSIG)
vMerkleTree: 3b889a27b7 4018255361 1ad02a8df1
05/02/2014 22:37:11 generated 0.00
05/02/2014 22:37:11 AddToWallet 4018255361 new
05/02/2014 22:37:12 WalletUpdateSpent found spent coin 280.104662hbn 498cd4bde82c9cb9834598ce1fbb766762b9818572cf69b2500aef53edef9ae6
05/02/2014 22:37:12 NotifyTransactionChanged 498cd4bde82c9cb9834598ce1fbb766762b9818572cf69b2500aef53edef9ae6 status=1
05/02/2014 22:37:12 NotifyTransactionChanged 40182553614f55d8de4469e450ba25a156231e3d1da85e0219c822e026a91084 status=0
05/02/2014 22:37:12 updateWallet 498cd4bde82c9cb9834598ce1fbb766762b9818572cf69b2500aef53edef9ae6 1
05/02/2014 22:37:12 inWallet=1 inModel=1 Index=320-321 showTransaction=1 derivedStatus=1
05/02/2014 22:37:12 updateWallet 40182553614f55d8de4469e450ba25a156231e3d1da85e0219c822e026a91084 0
05/02/2014 22:37:12 inWallet=1 inModel=0 Index=270-270 showTransaction=1 derivedStatus=0
05/02/2014 22:37:13 SetBestChain: new best=5ffe0d189a6b9c0e6021 height=564367 trust=829125359902 date=05/02/2014 22:37:01
05/02/2014 22:37:13 ProcessBlock: ACCEPTED
05/02/2014 22:37:20 ProcessSyncCheckpoint: pending for sync-checkpoint 76bc3c8d09e74a7395f67699d8d823137db1b36ca4cf3fc02eaa093e6fc9b7dd
05/02/2014 22:37:21 connection timeout
05/02/2014 22:37:30 Flushing wallet.dat
05/02/2014 22:37:30 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:30 received block 76bc3c8d09e74a7395f6
05/02/2014 22:37:30 ProcessBlock: ACCEPTED
05/02/2014 22:37:30 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:30 Flushed wallet.dat 366ms
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 getblocks 564367 to 00000000000000000000 limit 500
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 getblocks 321359 to 0000000045fa8b0ec1de limit 500
05/02/2014 22:37:31 getblocks stopping at limit 321858 00000008529103906eff
05/02/2014 22:37:31 getblocks 321359 to 00000000d4f529bbae49 limit 500
05/02/2014 22:37:31 getblocks stopping at limit 321858 00000008529103906eff
05/02/2014 22:37:31 getblocks 319358 to 00000000000000000000 limit 500
05/02/2014 22:37:31 getblocks stopping at limit 319857 00000001fa7819446b3b
05/02/2014 22:37:31 getblocks 512045 to 0000000045fa8b0ec1de limit 500
05/02/2014 22:37:31 getblocks stopping at limit 512544 000000000fb98f3fa9a4
05/02/2014 22:37:31 getblocks 512045 to 00000000d4f529bbae49 limit 500
05/02/2014 22:37:31 getblocks stopping at limit 512544 000000000fb98f3fa9a4
05/02/2014 22:37:31 getblocks 512045 to 000000013c49b924050e limit 500
05/02/2014 22:37:31 getblocks stopping at 512047 000000013c49b924050e
05/02/2014 22:37:31 getblocks 512045 to 000000015eb8bfc28895 limit 500
05/02/2014 22:37:31 getblocks stopping at 512064 000000015eb8bfc28895
05/02/2014 22:37:31 getblocks 512045 to 00000000953d7302f8d3 limit 500
05/02/2014 22:37:31 getblocks stopping at 512067 00000000953d7302f8d3
05/02/2014 22:37:31 getblocks 512045 to 0000000074858f094f7d limit 500
05/02/2014 22:37:31 getblocks stopping at 512080 0000000074858f094f7d
05/02/2014 22:37:31 getblocks 512045 to 1872f3ca1577f7d65a5d limit 500
05/02/2014 22:37:31 getblocks stopping at 512086 1872f3ca1577f7d65a5d
05/02/2014 22:37:31 getblocks 512045 to 0000000053f4c5e9a445 limit 500
05/02/2014 22:37:31 getblocks stopping at 512089 0000000053f4c5e9a445
05/02/2014 22:37:31 getblocks 512045 to 000000013853e46804d6 limit 500
05/02/2014 22:37:31 getblocks stopping at 512112 000000013853e46804d6
05/02/2014 22:37:31 getblocks 512045 to 000000014c1fab23c814 limit 500
05/02/2014 22:37:31 getblocks stopping at 512115 000000014c1fab23c814
05/02/2014 22:37:31 getblocks 512045 to 00000000fa3fd4069e17 limit 500
05/02/2014 22:37:31 getblocks stopping at 512118 00000000fa3fd4069e17
05/02/2014 22:37:31 getblocks 512045 to 000000001ced90943afa limit 500
05/02/2014 22:37:31 getblocks stopping at 512133 000000001ced90943afa
05/02/2014 22:37:31 getblocks 512045 to 3d33cba37e5b20784325 limit 500
05/02/2014 22:37:31 getblocks stopping at 512143 3d33cba37e5b20784325
05/02/2014 22:37:31 getblocks 512045 to 00000000e572d12e1645 limit 500
05/02/2014 22:37:31 getblocks stopping at 512153 00000000e572d12e1645
05/02/2014 22:37:31 getblocks 512045 to 0000000083d86ec90235 limit 500
05/02/2014 22:37:31 getblocks stopping at 512167 0000000083d86ec90235
05/02/2014 22:37:31 getblocks 512045 to 000000014484ae18fea3 limit 500
05/02/2014 22:37:31 getblocks stopping at 512171 000000014484ae18fea3
05/02/2014 22:37:31 getblocks 512045 to 000000004f9a2e404564 limit 500
05/02/2014 22:37:31 getblocks stopping at 512178 000000004f9a2e404564
05/02/2014 22:37:31 getblocks 512045 to 00000000e04590cd9d12 limit 500
05/02/2014 22:37:31 getblocks stopping at 512189 00000000e04590cd9d12
05/02/2014 22:37:31 getblocks 512045 to 0000000070b5a92ca80c limit 500
05/02/2014 22:37:31 getblocks stopping at 512203 0000000070b5a92ca80c
05/02/2014 22:37:31 getblocks 512045 to 0000000053d6fda4251f limit 500
05/02/2014 22:37:31 getblocks stopping at 512208 0000000053d6fda4251f
05/02/2014 22:37:31 getblocks 512045 to 00000001502a1d0e3398 limit 500
05/02/2014 22:37:31 getblocks stopping at 512214 00000001502a1d0e3398
05/02/2014 22:37:31 getblocks 512045 to 00000000b6aec463cc03 limit 500
05/02/2014 22:37:31 getblocks stopping at 512219 00000000b6aec463cc03
05/02/2014 22:37:31 getblocks 512045 to 0000000152651f2c5133 limit 500
05/02/2014 22:37:31 getblocks stopping at 512225 0000000152651f2c5133
05/02/2014 22:37:31 getblocks 512045 to 00000000c5b7db27d600 limit 500
05/02/2014 22:37:31 getblocks stopping at 512228 00000000c5b7db27d600
05/02/2014 22:37:31 getblocks 512045 to ec92f4757e97836cd0aa limit 500
05/02/2014 22:37:31 getblocks stopping at 512241 ec92f4757e97836cd0aa
05/02/2014 22:37:31 getblocks 512045 to 000000007e5a6eb909a5 limit 500
05/02/2014 22:37:31 getblocks stopping at 512248 000000007e5a6eb909a5
05/02/2014 22:37:31 getblocks 512045 to 0000000083df5fc8d658 limit 500
05/02/2014 22:37:31 getblocks stopping at 512253 0000000083df5fc8d658
05/02/2014 22:37:31 getblocks 512045 to 000000002e20467b0938 limit 500
05/02/2014 22:37:31 getblocks stopping at 512258 000000002e20467b0938
05/02/2014 22:37:31 getblocks 512045 to 000000006b8d129084ff limit 500
05/02/2014 22:37:31 getblocks stopping at 512269 000000006b8d129084ff
05/02/2014 22:37:31 getblocks 512045 to 00000000fae4b09162b8 limit 500
05/02/2014 22:37:31 getblocks stopping at 512284 00000000fae4b09162b8
05/02/2014 22:37:31 getblocks 512045 to 000000005b94a7f0f0e8 limit 500
05/02/2014 22:37:31 getblocks stopping at 512286 000000005b94a7f0f0e8
05/02/2014 22:37:31 getblocks 512045 to 0121a53e8ba28088c29e limit 500
05/02/2014 22:37:31 getblocks stopping at 512290 0121a53e8ba28088c29e
05/02/2014 22:37:31 getblocks 512045 to 000000001edad8da0c3a limit 500
05/02/2014 22:37:31 getblocks stopping at 512292 000000001edad8da0c3a
05/02/2014 22:37:31 getblocks 512045 to 0000000048a18729b9fe limit 500
05/02/2014 22:37:31 getblocks stopping at 512294 0000000048a18729b9fe
05/02/2014 22:37:31 getblocks 512045 to 000000012e57fa39356e limit 500
05/02/2014 22:37:31 getblocks stopping at 512296 000000012e57fa39356e
05/02/2014 22:37:31 getblocks 512045 to 00000000668f81444182 limit 500
05/02/2014 22:37:31 getblocks stopping at 512301 00000000668f81444182
05/02/2014 22:37:31 getblocks 512045 to 00000000fdfc27e50e62 limit 500
05/02/2014 22:37:31 getblocks stopping at 512313 00000000fdfc27e50e62
05/02/2014 22:37:31 getblocks 512045 to 000000015d0f7e9ba203 limit 500
05/02/2014 22:37:31 getblocks stopping at 512318 000000015d0f7e9ba203
05/02/2014 22:37:31 getblocks 512045 to 000000002fa7420d045e limit 500
05/02/2014 22:37:31 getblocks stopping at 512327 000000002fa7420d045e
05/02/2014 22:37:31 getblocks 512045 to 00000000d6014e6f8a7e limit 500
05/02/2014 22:37:31 getblocks stopping at 512329 00000000d6014e6f8a7e
05/02/2014 22:37:31 getblocks 512045 to 00000000c8de045b4e32 limit 500
05/02/2014 22:37:31 getblocks stopping at 512354 00000000c8de045b4e32
05/02/2014 22:37:31 getblocks 512045 to 00000000695287d6461c limit 500
05/02/2014 22:37:31 getblocks stopping at 512365 00000000695287d6461c
05/02/2014 22:37:31 getblocks 512045 to bc7b59d600cf873ada0f limit 500
05/02/2014 22:37:31 getblocks stopping at 512374 bc7b59d600cf873ada0f
05/02/2014 22:37:31 getblocks 512045 to 22ecb4392d15b6cee236 limit 500
05/02/2014 22:37:31 getblocks stopping at 512376 22ecb4392d15b6cee236
05/02/2014 22:37:31 getblocks 512045 to 000000007e3037e450ef limit 500
05/02/2014 22:37:31 getblocks stopping at 512389 000000007e3037e450ef
05/02/2014 22:37:31 getblocks 512045 to 00000000657c4ee12312 limit 500
05/02/2014 22:37:31 getblocks stopping at 512395 00000000657c4ee12312
05/02/2014 22:37:31 getblocks 512045 to 000000010c906d740993 limit 500
05/02/2014 22:37:31 getblocks stopping at 512397 000000010c906d740993
05/02/2014 22:37:31 getblocks 512045 to 000000004d910e6bc259 limit 500
05/02/2014 22:37:31 getblocks stopping at 512418 000000004d910e6bc259
05/02/2014 22:37:31 getblocks 512045 to 00000000873a7fd2d2b6 limit 500
05/02/2014 22:37:31 getblocks stopping at 512431 00000000873a7fd2d2b6
05/02/2014 22:37:31 getblocks 512045 to 0000000136439ccfcd46 limit 500
05/02/2014 22:37:31 getblocks stopping at 512452 0000000136439ccfcd46
05/02/2014 22:37:31 getblocks 512045 to 00000000ce426bf229ae limit 500
05/02/2014 22:37:31 getblocks stopping at 512503 00000000ce426bf229ae
05/02/2014 22:37:31 getblocks 512005 to 00000000000000000000 limit 500
05/02/2014 22:37:31 getblocks stopping at limit 512504 000000011e8eaa700927
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:31 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:32 trying connection 71.215.79.182:7372 lastseen=2.2hrs
05/02/2014 22:37:38 socket no message in first 60 seconds, 0 1
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 received block 00000000a2058b9e660d
05/02/2014 22:37:41 REORGANIZE
05/02/2014 22:37:41 REORGANIZE: Disconnect 1 blocks; 0000000045fa8b0ec1de..5ffe0d189a6b9c0e6021
05/02/2014 22:37:41 REORGANIZE: Connect 2 blocks; 0000000045fa8b0ec1de..00000000a2058b9e660d
05/02/2014 22:37:42 REORGANIZE: done
05/02/2014 22:37:42 SetBestChain: new best=00000000a2058b9e660d height=564368 trust=829125364155 date=05/02/2014 22:37:06
05/02/2014 22:37:42 AcceptPendingSyncCheckpoint : sync-checkpoint at 00000000a2058b9e660dabdc32ee31a6fc2977a201e9571500f518c7a8566aee
05/02/2014 22:37:42 ProcessBlock: ACCEPTED
05/02/2014 22:37:42 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:42 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:42 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:42 received getdata for: block 5ffe0d189a6b9c0e6021
05/02/2014 22:37:47 connection timeout
05/02/2014 22:37:48 disconnecting node 107.170.27.230:8469
05/02/2014 22:37:52 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:52 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:52 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 getblocks 321359 to 3a81de695dced54584cb limit 500
05/02/2014 22:37:53 getblocks stopping at 321541 3a81de695dced54584cb
05/02/2014 22:37:53 getblocks 319858 to 00000000000000000000 limit 500
05/02/2014 22:37:53 getblocks stopping at limit 320357 00000003aee919352311
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:53 ProcessSyncCheckpoint: pending for sync-checkpoint cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:37:57 trying connection 109.200.101.213:7372 lastseen=6.8hrs
05/02/2014 22:37:58 Flushing wallet.dat
05/02/2014 22:37:58 received block cadc4401e3eac601ea15
05/02/2014 22:37:59 Flushed wallet.dat 544ms
05/02/2014 22:38:00 SetBestChain: new best=cadc4401e3eac601ea15 height=564369 trust=829142141627 date=05/02/2014 22:37:37
05/02/2014 22:38:00 AcceptPendingSyncCheckpoint : sync-checkpoint at cadc4401e3eac601ea15979d6c9661c8fda39d9681bcb5c55eb72bd018b5890c
05/02/2014 22:38:00 ProcessBlock: ACCEPTED
05/02/2014 22:38:00 ProcessSyncCheckpoint: pending for sync-checkpoint 000000003fbfc7efafdf1e1eff3d5188496adcea762242a025aace83414423ee
Does this help you out ? I did started the wallet with -printcoinstake -printcreation |
|
|
|
Indeed, it's going to get very interesting Good luck to all you HoboNickelers |
|
|
|
So as I write this I am restarting the Mac client but with the zip version of the compile (witch is on github now) and I'll see if the orphan block will try to restake later this night or tomorrow and see if the PoS block gets accepted or rejected with that client and I'll keep you posted with that.
Thanks so much. This will be helpful. ok, as soon as the client synced the block chain, it did succesfully mine a PoS block. So it looks like the dmg compile had some kind of a bug in it. I'll still keep an eye on it tomorrow for any kind of unwanted behaviors. and I'll report if any issues are found. Prefect thanks for trouble shooting this for us. Let me know if Coin Control seems good, and if you see any different between the win version (if you use it) and the Mac version. Feel free to post an address for your help. okay, here's a quick update. I had to redownload the blockchain because I had issues with the wallet (I think it's the corrupted issue that was mentioned earlier in this thread). That took over 24 hours but now my wallets load fine. So it's been 9 hours that I let the wallet sit for it to stake and while it does stake, I find that the orphan rate is way higher than on the windows client. It could be just a coincidence, I don't know for sure. On 13 inputs, I had 6 orphan (all one after the other) the last input just got in ~30 minutes ago and was accepted. I'll continue to monitor and report. If you need more details, I would be glad to share them with you. Just let me know and what you need exactly I noticed the orphan rate was higher on the mac in version 1.2 as well. A friend took a snapshot of his transactions. The coins did eventually get accepted but seemed to take 2-1 orphan to accept. Were as windows I get 90% accepted. So this might be an issue with the mac client, I got 2 more orphans since I posted this morning. Do you have an idea as why this happens? |
|
|
|
So as I write this I am restarting the Mac client but with the zip version of the compile (witch is on github now) and I'll see if the orphan block will try to restake later this night or tomorrow and see if the PoS block gets accepted or rejected with that client and I'll keep you posted with that.
Thanks so much. This will be helpful. ok, as soon as the client synced the block chain, it did succesfully mine a PoS block. So it looks like the dmg compile had some kind of a bug in it. I'll still keep an eye on it tomorrow for any kind of unwanted behaviors. and I'll report if any issues are found. Prefect thanks for trouble shooting this for us. Let me know if Coin Control seems good, and if you see any different between the win version (if you use it) and the Mac version. Feel free to post an address for your help. okay, here's a quick update. I had to redownload the blockchain because I had issues with the wallet (I think it's the corrupted issue that was mentioned earlier in this thread). That took over 24 hours but now my wallets load fine. So it's been 9 hours that I let the wallet sit for it to stake and while it does stake, I find that the orphan rate is way higher than on the windows client. It could be just a coincidence, I don't know for sure. On 13 inputs, I had 6 orphan (all one after the other) the last input just got in ~30 minutes ago and was accepted. I'll continue to monitor and report. If you need more details, I would be glad to share them with you. Just let me know and what you need exactly |
|
|
|
So as I write this I am restarting the Mac client but with the zip version of the compile (witch is on github now) and I'll see if the orphan block will try to restake later this night or tomorrow and see if the PoS block gets accepted or rejected with that client and I'll keep you posted with that.
Thanks so much. This will be helpful. ok, as soon as the client synced the block chain, it did succesfully mine a PoS block. So it looks like the dmg compile had some kind of a bug in it. I'll still keep an eye on it tomorrow for any kind of unwanted behaviors. and I'll report if any issues are found. |
|
|
|
|
Show Posts
