0.000049
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 161. (Read 478852 times)
December 15, 2014, 02:31:06 PM
Buying like kerazzzzyyyy
0.000049
0.000049
December 15, 2014, 07:02:59 AM
Sorry for the OFF but tell me please, which of the following cards is better
SAPPHIRE VAPOR-X R7 250X 2GB/GDDR5 or
ASUS R7 250X-2GD5 2GB/GDDR5
Thanks.
SAPPHIRE VAPOR-X R7 250X 2GB/GDDR5 or
ASUS R7 250X-2GD5 2GB/GDDR5
Thanks.
Since they are pretty much the same, I'd go for the cheapest one.
December 14, 2014, 11:23:45 AM
Sorry for the OFF but tell me please, which of the following cards is better
SAPPHIRE VAPOR-X R7 250X 2GB/GDDR5 or
ASUS R7 250X-2GD5 2GB/GDDR5
Thanks.
SAPPHIRE VAPOR-X R7 250X 2GB/GDDR5 or
ASUS R7 250X-2GD5 2GB/GDDR5
Thanks.
December 10, 2014, 07:10:42 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Wish I could say the same... Been poking at the upgrade for close to a week now. I couldn't get any responses from any peers. The wallet is installed on a Windows 8 computer along with a Hyper wallet and an AsiaCoin Wallet. Hyper and AsiaCoin are working fine. My router is set up for uPnP and had shown a port forward for TCP Port 7372, but for some reason it disappeared. I manually added it back, but still no success. I also upgraded the version of DD-WRT on my router around the same time I upgraded the HoboNickels Wallet. I just figured out that DD-WRT has decided that HoboNickels on Port 7372 constitutes a P2P protocol and my rule blocking all P2P was blocking HoboNickels. I'm finally getting The wallet caught up, but I'm puzzled by what it took.
Sorry to hear this, but glad you got it sorted. There were some changes to the way this connected to and talked with peers. Although I can't imagine it was that it was so different then the other wallets, that it was flagged as P2P whereas the others were not.
I wonder if without the upgraded rule, would the older 1.4 wallet be able to connect?
December 10, 2014, 12:44:22 AM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Wish I could say the same... Been poking at the upgrade for close to a week now. I couldn't get any responses from any peers. The wallet is installed on a Windows 8 computer along with a Hyper wallet and an AsiaCoin Wallet. Hyper and AsiaCoin are working fine. My router is set up for uPnP and had shown a port forward for TCP Port 7372, but for some reason it disappeared. I manually added it back, but still no success. I also upgraded the version of DD-WRT on my router around the same time I upgraded the HoboNickels Wallet. I just figured out that DD-WRT has decided that HoboNickels on Port 7372 constitutes a P2P protocol and my rule blocking all P2P was blocking HoboNickels. I'm finally getting The wallet caught up, but I'm puzzled by what it took.
December 08, 2014, 08:03:58 PM
Understood... HBN has been rock solid forever now.
Heck, my first transaction was in 9/2013 -- and I've never had a problem!
Heck, my first transaction was in 9/2013 -- and I've never had a problem!
that's great
December 08, 2014, 07:54:14 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Suffering? because of the POS limit?
I think that's only a limit per POS transaction... not a total limit.
I think he meant he was prepared for the worst, but he had no problems at all.
December 08, 2014, 07:53:25 PM
Understood... HBN has been rock solid forever now.
Heck, my first transaction was in 9/2013 -- and I've never had a problem!
Heck, my first transaction was in 9/2013 -- and I've never had a problem!
December 08, 2014, 07:52:07 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Suffering? because of the POS limit?
I think that's only a limit per POS transaction... not a total limit.
no
I have three days before this updated TEK:
cut fashion qt growths ...
Search for missing coins ...
in short, an exciting experience
December 08, 2014, 07:48:12 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Suffering? because of the POS limit?
I think that's only a limit per POS transaction... not a total limit.
I think he meant he was prepared for the worst, but he had no problems at all.
December 08, 2014, 07:42:07 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
Suffering? because of the POS limit?
I think that's only a limit per POS transaction... not a total limit.
December 08, 2014, 07:32:02 PM
Sent out an alert for version below 1.5.
Yesterday I already updated wallet.
Preparing for suffering ...))
But everything went smoothly.
good job Tranz
December 08, 2014, 07:04:26 PM
Sent out an alert for version below 1.5.
December 08, 2014, 06:55:06 PM
guys who work with this coin? and in what pool mining?
Here are some mining pools
https://cryptocointalk.com/topic/21159-mining-pools/
December 08, 2014, 06:40:25 PM
Wounder if anyone can help me? I am trying to connect to the hobo wallet rpc with a python lib that I am currently using on other coins like bottlecaps, supercoin and a couple others. It wont connect to hobo for some reason though. I get a socket timeout error. Any help would be appreciated
I am sure someone here can help. Quick guess is, the capitalization maybe off? Otherwise I think we might need the script you are running and/or the error log.
capitalization? is in the conf file?
Check your conf file, then check it again, then one more time.
I can't tell you how many times I have wondered -- what the heck, and found I misspelled something.
Also check your firewall (if windows)... are you inadvertently blocking the port you want to listen on?
If your conf file in %appdata%\HoboNickels
Here is sample I used named hobonickels.conf
listen=1
daemon=1
server=1
rpcuser=someuserhere
rpcpassword=somecrazylongpassword
rpcallowip=127.0.0.1
rpcallowip=192.168.172.*
addnode=69.85.86.195
addnode=74.196.48.62
rpcport=10000
port=10001
Please pay attention to rpcallowip=
If you do not have the right value here, internal network access will result in a socket timeout.
NEVER USE rpcallowip=* -- I will steal all your coins
December 08, 2014, 06:18:23 PM
guys who work with this coin? and in what pool mining?
December 08, 2014, 02:20:49 PM
I have been away for a while... I am so glad to see this coin is still active and going strong!
December 07, 2014, 12:16:20 AM
Wounder if anyone can help me? I am trying to connect to the hobo wallet rpc with a python lib that I am currently using on other coins like bottlecaps, supercoin and a couple others. It wont connect to hobo for some reason though. I get a socket timeout error. Any help would be appreciated
I am sure someone here can help. Quick guess is, the capitalization maybe off? Otherwise I think we might need the script you are running and/or the error log.
capitalization? is in the conf file?
I am just saying are you calling the correct daemon, spelling and case wise?
December 07, 2014, 12:15:21 AM
Getting the wiki backup and running. It got spammed by a bunch of bots, so I updated the security and added WYSIWYG editing to it. I got 1/2 the pages up so far. I'll get the others here soon as well.
If anyone wants access to add/edit pages, let me know. I will have to manually add you.
If anyone wants access to add/edit pages, let me know. I will have to manually add you.
December 07, 2014, 12:15:13 AM
Wounder if anyone can help me? I am trying to connect to the hobo wallet rpc with a python lib that I am currently using on other coins like bottlecaps, supercoin and a couple others. It wont connect to hobo for some reason though. I get a socket timeout error. Any help would be appreciated
I am sure someone here can help. Quick guess is, the capitalization maybe off? Otherwise I think we might need the script you are running and/or the error log.
capitalization? is in the conf file?
Jump to: