HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive

[dogechode]

Okay so after about 15 days I got my first POS / stake / whatever you call them? coins from keeping the wallet open nearly 24x7.

A couple days later I got another one, but it never confirmed - still shows as gray, 0 confirmations. Then a couple days after that, it happened again - another POS reward but... no confirms. What is going on?

Also, NONE of these POS rewards - even the first one that did confirm - went under "stake" in the wallet. Is that normal?

[1714258848]

1714258848

[1714258848]

1714258848

[1714258848]

1714258848

[1714258848]

1714258848

[otila]

using IRC to get the node list is a ridiculous idea. why not DNS?
or is this thing dead already? found today

...has been matched to a known bot pattern r#393 (Bitcoin Clients - http://s.rizon.net/peercoin)

[sigesang]

seems something is missing currently on github:

Code:

g++ -c -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_QRCODE -DUSE_UPNP=1 -DSTATICLIB -DUSE_DBUS -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtDBus -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -I/usr/include/db4.8 -Ibuild -Ibuild -o build/transactionrecord.o src/qt/transactionrecord.cpp
src/qt/transactionrecord.cpp: In member function 'void TransactionRecord::updateStatus(const CWalletTx&)':
src/qt/transactionrecord.cpp:173:28: error: 'const class CWalletTx' has no member named 'IsConfirmed'

edit:
was on https://github.com/Tranz5/HoboNickels, so maybe not so important.. but someone might want to know

[presstab]

Okay so after about 15 days I got my first POS / stake / whatever you call them? coins from keeping the wallet open nearly 24x7.

A couple days later I got another one, but it never confirmed - still shows as gray, 0 confirmations. Then a couple days after that, it happened again - another POS reward but... no confirms. What is going on?

Also, NONE of these POS rewards - even the first one that did confirm - went under "stake" in the wallet. Is that normal?

You are getting orphans. Are using Mac OS? It tends to get more orphans. Don't worry though, your coin age remains so your block is still in the pool competing for stake.  To double check your block to make sure it is still aged, go to the coin control feature of the wallet and look at the confirmations on your blocks.

Check out these two wiki pages if you need more explanation.

http://wiki.hobonickels.info/index.php?title=Orphan

http://wiki.hobonickels.info/index.php?title=Coin_Control

[presstab]

using IRC to get the node list is a ridiculous idea. why not DNS?
or is this thing dead already? found today

Way ahead of you  

http://wiki.hobonickels.info/index.php?title=Node#Permanent_Seed_Nodes

And it is actually built into the newest release of the HoboNickels client (v1.3.1)

[otila]

using IRC to get the node list is a ridiculous idea. why not DNS?
or is this thing dead already? found today

Way ahead of you 

http://wiki.hobonickels.info/index.php?title=Node#Permanent_Seed_Nodes

But what's the reason that those nodes are not included in the executable? Have to hunt 'em from some wikis.. way too non-userfriendly.

[presstab]

But what's the reason that those nodes are not included in the executable? Have to hunt 'em from some wikis.. way too non-userfriendly.

Lol I made an edit right when you replied. It is in the newest exe.  Version 1.3.1 - Official support on IRC ended within the last month so we are still in a transition phase.

[otila]

Lol I made an edit right when you replied. It is in the newest exe.  Version 1.3.1 - Official support on IRC ended within the last month so we are still in a transition phase.

I had version v1.3.0.0-g76880ab-hobo from https://github.com/Crypto-Expert/HoboNickels.git
  and tranz5 edition does not compile

[presstab]

I had version v1.3.0.0-g76880ab-hobo from https://github.com/Crypto-Expert/HoboNickels.git
  and tranz5 edition does not compile

You should be pulling your gits from Tranz, not from crypto-expert (although I believe the essentials for each release is updated to crypto-expert as well).  Here is the working directory https://github.com/Tranz5/HoboNickels  This would of course include commits that are beyond 1.3.1, so some of it is still in testing.

Check working details from Tranz here https://cryptocointalk.com/topic/4390-preparing-hbn-v14/page-3

[dogechode]

Okay so after about 15 days I got my first POS / stake / whatever you call them? coins from keeping the wallet open nearly 24x7.

A couple days later I got another one, but it never confirmed - still shows as gray, 0 confirmations. Then a couple days after that, it happened again - another POS reward but... no confirms. What is going on?

Also, NONE of these POS rewards - even the first one that did confirm - went under "stake" in the wallet. Is that normal?

You are getting orphans. Are using Mac OS? It tends to get more orphans. Don't worry though, your coin age remains so your block is still in the pool competing for stake.  To double check your block to make sure it is still aged, go to the coin control feature of the wallet and look at the confirmations on your blocks.

Check out these two wiki pages if you need more explanation.

http://wiki.hobonickels.info/index.php?title=Orphan

http://wiki.hobonickels.info/index.php?title=Coin_Control

Okay thanks I just thought it was strange that I got one legit one then 2 that never confirmed. So if I get an orphan you are saying the age of the coin/s that were trying to stake and produced an orphan, will not reset the way they would have if a legitimate reward had been produced?

BTW I am not using MacOS.

[presstab]

Okay thanks I just thought it was strange that I got one legit one then 2 that never confirmed. So if I get an orphan you are saying the age of the coin/s that were trying to stake and produced an orphan, will not reset the way they would have if a legitimate reward had been produced?

BTW I am not using MacOS.

Yep you should be fine. I have seen a couple PoS orphans on my machine running Windows server 2012.  It happens to everyone occasionally. Essentially what happens is that your PoS block is not accepted by the official blockchain, and so the block that you have sitting in your wallet had absolutely no activity according to the official blockchain.  So if you would like to double check to see if the block is still mature (which it should be) simply head to the advanced coin control.

Since no PoS transaction has occurred on the blockchain it is the same thing as nothing ever happening and your block should still be up for stake.

[Tranz]

The Tranz5 repo is my Work in Progress. It maybe unstable from time to time.  I'll work on those compile issues tonight. It should be a small change.  (Fixed)

The crypto expert is the stable release environment, I only push there once all the kinks and updates are complete.  

[dogechode]

I have "display coin control features" checked under options, but how do I do... whatever you guys are talking about to check if my coins that generated orphaned proof of stake are still "aged" ?

[otila]

I have looked at the source code for a minute, so I can't suggest anything yet, but 90% of the CPU time spent while synchronizing the blocks is spent in
Checkpoints::CheckSync

Code:

            while (pindex->nHeight > pindexSync->nHeight)
                if (!(pindex = pindex->pprev))

now 80 minutes CPU time for 300k blocks. This is the bottleneck, not network speed.

[Tranz]

I have "display coin control features" checked under options, but how do I do... whatever you guys are talking about to check if my coins that generated orphaned proof of stake are still "aged" ?

Under send coins, you should see a new box.

[presstab]

I have "display coin control features" checked under options, but how do I do... whatever you guys are talking about to check if my coins that generated orphaned proof of stake are still "aged" ?

After selecting the wallet hit the send coins button.
There will be a box titled Coin Control Features inside of this box , hit the inputs button. A new window will appear called Coin Control. In this window you have the option to use the tree mode or the list mode, I prefer tree mode, but decide yourself which you like the best.
You will see the total amount of coins held in the wallet with the amount of blocks held in the wallet in parenthesis. If you are using tree mode, hit the arrow to expand the view and display your wallet's blocks.  You should see confirmations next to the block, and an aged coin should have around 30k or more confirmations.

[Tranz]

I have looked at the source code for a minute, so I can't suggest anything yet, but 90% of the CPU time spent while synchronizing the blocks is spent in
Checkpoints::CheckSync

Code:

            while (pindex->nHeight > pindexSync->nHeight)
                if (!(pindex = pindex->pprev))

now 80 minutes CPU time for 300k blocks. This is the bottleneck, not network speed.

Thanks. I'll look into this more..

[Tranz]

added new menu option

https://cryptocointalk.com/topic/4390-preparing-hbn-v14/?p=56985

[ryanb]

added new menu option

https://cryptocointalk.com/topic/4390-preparing-hbn-v14/?p=56985

i like the new wallet keep up the good work

[glendall]

I have question , wondering if anyone could help me out with.

I encrypted some of my wallets.  I have a few than I would like to unlock so they can generate pos blocks. I tried to do so with the 'walletpassphrase' command.  However, it says that I can't do this because my wallet is not encrypted (my first wallet is not encrypted). 

So is their a command I can use to switch to the 'active' wallet so I can use the walletpassphrase command to unlock it.  Like in the debug command options, how to unlock certain wallets , or how does it select which wallet I'm talking about when I use that command?  Thanks for any assistance!