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

[semajjames]

Hi
   I have 3 minning rigs all running on one LAN

Now if i want to Solo mine hbn straight to a wallet do i have to install the wallet on each of the minning pc's or can i install the wallet just once on a 4th pc and have the 3 minners use the one wallet on the 4th pc 

thanks

[unick]

Hi
   I have 3 minning rigs all running on one LAN

Now if i want to Solo mine hbn straight to a wallet do i have to install the wallet on each of the minning pc's or can i install the wallet just once on a 4th pc and have the 3 minners use the one wallet on the 4th pc  

thanks

You need to have one pc (not on the miners) running the client

in the HoboNickels.con file of that pc running the client, you should add the rpcallowip= for each ip of your rigs (if you are on the same subnet, I believe you can use wildcards like rpcallowip=192.168.1.*).  If you are behind a router, you only need to put your public IP there.

Then on your rigs, simply add a pool and put the IP as the url from the pc running the client and the rpcport= (like URL:PORT) the username password will be the rpcusername= and rpcpassword= from that same config file


Newly mined block rewards will be on the wallet from that pc, you can then transfer those coins back to your main wallet when they mature.

[dogechode]

Tranz I don't quite understand why you need to specify that you want 500 keys assigned when you create a wallet. I did not do this (I didn't specify anything I just created a second wallet using buttons/menus not by typing commands. Am I going to run into a problem?

[semajjames]

Hi
   I have 3 minning rigs all running on one LAN

Now if i want to Solo mine hbn straight to a wallet do i have to install the wallet on each of the minning pc's or can i install the wallet just once on a 4th pc and have the 3 minners use the one wallet on the 4th pc  

thanks

You need to have one pc (not on the miners) running the client

in the HoboNickels.con file of that pc running the client, you should add the rpcallowip= for each ip of your rigs (if you are on the same subnet, I believe you can use wildcards like rpcallowip=192.168.1.*).  If you are behind a router, you only need to put your public IP there.

Then on your rigs, simply add a pool and put the IP as the url from the pc running the client and the rpcport= (like URL:PORT) the username password will be the rpcusername= and rpcpassword= from that same config file


Newly mined block rewards will be on the wallet from that pc, you can then transfer those coins back to your main wallet when they mature.

thanks
in this .conf file why is there two different ports OR is it a mistake


listen=1
daemon=1
server=1
rpcuser=*your hobo name*
rpcpassword=*Your hobo  quote*
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

[brother3]

Hi
   I have 3 minning rigs all running on one LAN

Now if i want to Solo mine hbn straight to a wallet do i have to install the wallet on each of the minning pc's or can i install the wallet just once on a 4th pc and have the 3 minners use the one wallet on the 4th pc  

thanks

You need to have one pc (not on the miners) running the client

in the HoboNickels.con file of that pc running the client, you should add the rpcallowip= for each ip of your rigs (if you are on the same subnet, I believe you can use wildcards like rpcallowip=192.168.1.*).  If you are behind a router, you only need to put your public IP there.

Then on your rigs, simply add a pool and put the IP as the url from the pc running the client and the rpcport= (like URL:PORT) the username password will be the rpcusername= and rpcpassword= from that same config file


Newly mined block rewards will be on the wallet from that pc, you can then transfer those coins back to your main wallet when they mature.

thanks
in this .conf file why is there two different ports OR is it a mistake


listen=1
daemon=1
server=1
rpcuser=*your hobo name*
rpcpassword=*Your hobo  quote*
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

not a mistake
7373 is the port you solo with

[unick]

Hi
   I have 3 minning rigs all running on one LAN

Now if i want to Solo mine hbn straight to a wallet do i have to install the wallet on each of the minning pc's or can i install the wallet just once on a 4th pc and have the 3 minners use the one wallet on the 4th pc  

thanks

You need to have one pc (not on the miners) running the client

in the HoboNickels.con file of that pc running the client, you should add the rpcallowip= for each ip of your rigs (if you are on the same subnet, I believe you can use wildcards like rpcallowip=192.168.1.*).  If you are behind a router, you only need to put your public IP there.

Then on your rigs, simply add a pool and put the IP as the url from the pc running the client and the rpcport= (like URL:PORT) the username password will be the rpcusername= and rpcpassword= from that same config file


Newly mined block rewards will be on the wallet from that pc, you can then transfer those coins back to your main wallet when they mature.

thanks
in this .conf file why is there two different ports OR is it a mistake


listen=1
daemon=1
server=1
rpcuser=*your hobo name*
rpcpassword=*Your hobo  quote*
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

not a mistake
7373 is the port you solo with

that's correct, you need to point your miners to the IP:rpcport of the wallet described above. The other port setting is for the listening port connecting to other nodes on the network.

[brother3]

My first stake ever !  Feels like a proud papa 

[presstab]

My first stake ever !  Feels like a proud papa 

My first stake I remember thinking "it worked, it actually worked!"

[Tranz]

Tranz I don't quite understand why you need to specify that you want 500 keys assigned when you create a wallet. I did not do this (I didn't specify anything I just created a second wallet using buttons/menus not by typing commands. Am I going to run into a problem?

Most likely no.. Especially if are primarily staking and not much sending/receiving. You can always top up the keypool and then back it up. The larger the keypool the more keys are in you wallet, the more transactions it can do before it is necessary to back it up again.

This applies for every coin out there.

[dogechode]

Tranz I don't quite understand why you need to specify that you want 500 keys assigned when you create a wallet. I did not do this (I didn't specify anything I just created a second wallet using buttons/menus not by typing commands. Am I going to run into a problem?

Most likely no.. Especially if are primarily staking and not much sending/receiving. You can always top up the keypool and then back it up. The larger the keypool the more keys are in you wallet, the more transactions it can do before it is necessary to back it up again.

This applies for every coin out there.

When you say back it up, do you mean back up the wallet? I back up all my wallets obsessively. Does backing it up do something related to the keys? Sorry I really am not familiar with the inner workings of coin wallets...

[unick]

Tranz I don't quite understand why you need to specify that you want 500 keys assigned when you create a wallet. I did not do this (I didn't specify anything I just created a second wallet using buttons/menus not by typing commands. Am I going to run into a problem?

Most likely no.. Especially if are primarily staking and not much sending/receiving. You can always top up the keypool and then back it up. The larger the keypool the more keys are in you wallet, the more transactions it can do before it is necessary to back it up again.

This applies for every coin out there.

When you say back it up, do you mean back up the wallet? I back up all my wallets obsessively. Does backing it up do something related to the keys? Sorry I really am not familiar with the inner workings of coin wallets...

yes.

When you ask for a new address in the client, it does not create a new address on the fly, it takes it from the key pool most likely generated when you first created your wallet.  By default it creates 100 addresses (or 101, I'm not sure). 

If you always reuse the same address, you'll never use up all the keypool's addresses. But if you need let's say 200 addresses, you need to generate the missing addresses.

What happens is that the keypool will now contain 200 addresses but your backup will still have only 100 addresses.  Now if something goes wrong and you used addresses between 100 and 200. They won't be backed up and you might lose the coins sent to those address.

That's why Tranz said that when you generate a new set of addresses, it is good practice to back up the wallet right after they have been generated to make sure you have in a safe place all your private/public key pair.


Try to play with the RPC command dumpwallet. You will visually see in a text file, all your keys and this will make more sense.  It's also a nice way to print out your keypool and physically store it in a safe place.

[tricass]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

[dogechode]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

I wouldn't get too excited about it. They can't seem to provide any meaningful information in the "whitepapers" and when questioned about the basic functionality they explain like a politician.

They have been asked if their system would just encourage people to send coins back and forth between addresses they control, and the response was basically "oh no they won't need to do that, there wouldn't be a reason to" but then they say "the system rewards users who make transactions." So in other words this garbage will launch, and people will just send back and forth between their own addresses and abuse it, and the whole thing will be a clusterfuck.

[Tranz]

Try to play with the RPC command dumpwallet. You will visually see in a text file, all your keys and this will make more sense.  It's also a nice way to print out your keypool and physically store it in a safe place.

dumpwallet is a good way to see your keys. This is also in the GUI under File->Export Wallet

[Tranz]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

I wouldn't get too excited about it. They can't seem to provide any meaningful information in the "whitepapers" and when questioned about the basic functionality they explain like a politician.

They have been asked if their system would just encourage people to send coins back and forth between addresses they control, and the response was basically "oh no they won't need to do that, there wouldn't be a reason to" but then they say "the system rewards users who make transactions." So in other words this garbage will launch, and people will just send back and forth between their own addresses and abuse it, and the whole thing will be a clusterfuck.

Once the code is released, I'll have a look.  But if it is anything like rewarding people for sending coins, all you are going to get a bloated block chain.

[presstab]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

I wouldn't get too excited about it. They can't seem to provide any meaningful information in the "whitepapers" and when questioned about the basic functionality they explain like a politician.

They have been asked if their system would just encourage people to send coins back and forth between addresses they control, and the response was basically "oh no they won't need to do that, there wouldn't be a reason to" but then they say "the system rewards users who make transactions." So in other words this garbage will launch, and people will just send back and forth between their own addresses and abuse it, and the whole thing will be a clusterfuck.

Once the code is released, I'll have a look.  But if it is anything like rewarding people for sending coins, all you are going to get a bloated block chain.

The last thing HBN needs is adding more bloat to the chain. I was thinking about txcomments but then got to thinking that it adds extra bloat.

[brother3]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

I wouldn't get too excited about it. They can't seem to provide any meaningful information in the "whitepapers" and when questioned about the basic functionality they explain like a politician.

They have been asked if their system would just encourage people to send coins back and forth between addresses they control, and the response was basically "oh no they won't need to do that, there wouldn't be a reason to" but then they say "the system rewards users who make transactions." So in other words this garbage will launch, and people will just send back and forth between their own addresses and abuse it, and the whole thing will be a clusterfuck.

I can't believe they call that "innovation"!!!
What a freakin' mess 

[dogechode]

I can't believe they call that "innovation"!!!
What a freakin' mess 

Hey don't get me wrong, if they have some valid explanation of how it is actually some amazing revolutionary new thing, I am more than willing to hear it. But the papers they released are a joke and when questioned about basic things they just deflect/ignore.

[Tranz]

tranz,

wanted to get your opinion on Reddcoin's new innovation Proof of Stake Velocity (PoSV)

I wouldn't get too excited about it. They can't seem to provide any meaningful information in the "whitepapers" and when questioned about the basic functionality they explain like a politician.

They have been asked if their system would just encourage people to send coins back and forth between addresses they control, and the response was basically "oh no they won't need to do that, there wouldn't be a reason to" but then they say "the system rewards users who make transactions." So in other words this garbage will launch, and people will just send back and forth between their own addresses and abuse it, and the whole thing will be a clusterfuck.

Once the code is released, I'll have a look.  But if it is anything like rewarding people for sending coins, all you are going to get a bloated block chain.

The last thing HBN needs is adding more bloat to the chain. I was thinking about txcomments but then got to thinking that it adds extra bloat.

HBN is actually doing fairly well regarding block chain size.  Heading in on close to a year and just pushing 400meg size.    Also closing in on 1 million blocks.    So the size is good overall, just many small blocks.  I think this is a better problem to have then lower number of blocks, but bigger in size.

[emdje]

The new wallet 1.4.0.0 keeps crashing. I tried redownloading the blockchain several times, and after a while the wallet crashes. Anyone any ideas?