I would like to write a small simple program in VB that can query the HBN network to check for the current work difficulty. Is there an easy way to do that?
If you are running the hbn deamon you can use the rpc command getdifficulty. Otherwise you could try the CCE api call http://www.cryptocoinexplorer.com/apimany need crutches )) for example: 1. cold start the daemon -> demon few minutes unresponsive rpc 2. no simple command - "staking work ?" ... The demon may take a few minutes to start up. But if you are using it for something all the time you wouldn't shut it down. getdifficutly shows both. 09:39:46  getdifficulty 09:39:46  { "proof-of-work" : 24.06406389, "proof-of-stake" : 0.00390625, "search-interval" : 0 } |
|
|
|
I would like to write a small simple program in VB that can query the HBN network to check for the current work difficulty. Is there an easy way to do that?
If you are running the hbn deamon you can use the rpc command getdifficulty. Otherwise you could try the CCE api call http://www.cryptocoinexplorer.com/api |
|
|
|
What updates do we want to see for 2.3?
I have had a request for Autosavings updates, including custom send address. I can do that.
I was planning on doing the windows safe shutdown, and the combine/split threshold updates, to help keep blocks more manageable.
Obviously the new icons.
Anything else?
Hi Tranz, So where do we stand? What do you need to be able to program the 2.3 version. If there's anything we can do to help, just let it be known! Not much, I just need the ability to clone myself. Send one off to work, one to work on crypto and one to keep the kids from killing each other!  Seriously though I was waiting to see what direction we wanted to go. It seems like there are a few core updates that are needed. Including updates for Autosavings, auto combine/split updates and a few other small core issues. It also seems we want to go the route of adding the ability to change the skin of the wallet on the fly. I can add this ability, but I still have yet to see one person come forth that wants to or has the knowledge of how to add new skins. Can anyone does this? If I just add the code to allow the wallet to switch on the fly, it will be useless unless people add new skins. Otherwise I do like the new icons and I can update to use them straight up. |
|
|
|
|
Ahh yes I see. Selecting rows in the transaction page has no effect, but that is a great idea. For now you can use the various filters to get totals.
|
|
|
|
Is there an immediate need for someone to upgrade from 1.4 to 1.5?
1.5 is not released yet. I am testing some of the hard fork changes. It should be ready soon. But right now, no, you can stay with what you have. If you want to try some of the new features that will be ready in 1.5, try out the beta version. by the way I would like to see the price in the tray selected values in the wallet surprising that it is not in the standard features  good luck Sorry I do not understand. Can you reword that? |
|
|
|
Is there an immediate need for someone to upgrade from 1.4 to 1.5?
1.5 is not released yet. I am testing some of the hard fork changes. It should be ready soon. But right now, no, you can stay with what you have. If you want to try some of the new features that will be ready in 1.5, try out the beta version. |
|
|
|
Question while im here.. I have quite a few blocks of 500 coins that are 19 days.. but then I look and the POS difficulty is only : proof-of-stake" : 0.00394398 . That seems really low. now I know that the blocks dont break exactly on the 10th day or even 11th, but 19 days seems really long for such a low POS diff... Is it time to raise my block size ? Yes I know about max reward, but Im losing money waiting 19+ days for them to cycle.
Vegas
I think you are quite good at 500, and in-fact much larger then I keep mine. And you are only loosing a very small yearly compounding percentage. I have just a handful of blocks over 19 days that haven't staked, they are 100-200 range. 500 should stake pretty quickly, assuming your wallet is unlocked and running on the right chain. |
|
|
|
Guys im having the worst time keeping my wallet in sync. Ive tried the following things:
1. -resync command after the exe file
2. Wallet repair (Everytime it launches , I do a walletrepair, and it says 3 coins in error +1500 and never adds the funds)
3. I created a hobonickels.conf and handpicked the nodes for version 1.4.99 (1.5 Final beta)
4. Tried to also add those nodes manually in console. Looked like it took, but then I look at peers, and its using mostly peers from .7.5 clients anyway!?!?
5. Deleted All but wallet.dat in roaming, and downloaded blockchain that goes to 10-21-14, its syncs until it gets about 10 minutes from finishing, then it stops syncing).
Its an old wallet.dat with 4100 transactions..is this too many? If this is the case , I just want to band aid it and create another wallet.dat because this is my 10th day for most of my 500 coin blocks. Cant move them anyway if it wont sync. I have 7000 coins bundled up in 500 coin blocks, but it doesnt help.
Any ideas?
Thanks in advance
Vegas
UPDATE: Renamed wallet.dat to wallet.old. Deleted all in roaming except walletfile. Used blockchain.zip file to 10-21-14 and resynced fine. turned off firewall. Closed HBN , renamed new wallet to wallet.new and re-renamed wallet.old to wallet.dat. SEEMS to be staying in sync. But I think at this point im going to start moving over my coins that have rewarded to new wallet. Hope this helps anyone else.
Sorry to hear about the issues, but glad you got them sorted. Sounds like you had an issue with the wallet and the index(database dir). Sometimes using the following switches can help without needing to resort to the renaming as you did. -rescan, -zapwallettxes and lastly -salvagewallet. Always be sure to have a good back-up of wallet(s) before doing any of the above. As far as 4,400 transactions being too much, I have over 30k and I stay in sync and stake 100s of times a day with blocks of 100+ |
|
|
|
love stacking HBNs Me 2!. My main client, with 7 loaded wallets is up to 33,000 transactions.  |
|
|
|
Hi everyone,
I am calculating the inflation rate again but I need some help the the HBN money supply at block 1357005. The abe Block explorer is not up to date so I can't figure it out. Tranz, you added this recently to the CAP wallet if you can remember, would that be an option too for HBN?
But just the money supply at 1357005 helps me out for now too. Or is there a command in the debug window that I can use?
thanks!
I don't think there is a RPC command that will give you historical value. I can give you an estimate right now(6,990,000), and an exact later. I'll add that money supply to the block explorer as well for 1.5 I had a very busy week outside of Crypto, so I haven't been able to get much done. But I should be able to get the hard fork coded up here, as it looks like the wallet is working pretty good. At least I haven't see many issues. Thanks, your estimate fits the data so I guess it's already pretty accurate. And as far as issue's I haven't encountered any actually. I am following two wallets with very small blocks to see the splitting and recombining at work and I came to the conclusion that it works just fine. I'll continue to do so, it's fun to see it happen. Added the money supply to the BE. The exact amount is......................................6990701.974698 HBN |
|
|
|
Hi everyone,
I am calculating the inflation rate again but I need some help the the HBN money supply at block 1357005. The abe Block explorer is not up to date so I can't figure it out. Tranz, you added this recently to the CAP wallet if you can remember, would that be an option too for HBN?
But just the money supply at 1357005 helps me out for now too. Or is there a command in the debug window that I can use?
thanks!
I don't think there is a RPC command that will give you historical value. I can give you an estimate right now(6,990,000), and an exact later. I'll add that money supply to the block explorer as well for 1.5 I had a very busy week outside of Crypto, so I haven't been able to get much done. But I should be able to get the hard fork coded up here, as it looks like the wallet is working pretty good. At least I haven't see many issues. |
|
|
|
Problem with S4C.
When the wallet sends coins to your S4C adres, it not automatically chooses one of the 2 blocks that were just created by the staking process. In my case it chose a 3,5 days old big block to do so. Destroying an unfortunate amount of stake...
I think it chose this block because it was a little smaller than the ones just produced. I don't know how the wallet decides to pick a certain block but the way its done now forces me to stop using S4C.
I think to solve it, the wallet when looking for blocks to send, needs an extra category called priority none, which consists of any block, regardless of size, with an amount of confirmations lower than 100. That way the just produced blocks will be first in line.
Is that a possibility?
PS. since CAP is pretty much the same, I guess this problem exists there as well.
Hello PressF1, yes this is a known risk of S4C in its current form. The full write-up when I originally coded S4C can be found here: https://cryptocointalk.com/topic/9606-hbn-trouble-shooting-and-user-guide-stake-for-charity/ see the Risk section. Generally if the wallet has a lot of smaller blocks, it will pick them. But it may pick one that more closely matches the amount being sent, rather then 1 that is lower confirms. I do think I can tweak this and make it choose lower confirms first. |
|
|
|
Hello all
Are they going to make an Android wallet that will do the POS ?
Not sure who they is. But I think there a few developers working on it. |
|
|
|
Hi All, now I can build it in 64bit Ubuntu, but If I found an block I get this error in debug.log: __________________ 2014-10-24 07:36:52 ERROR: CTransaction::CheckTransaction() : txout.nValue below minimum 2014-10-24 07:36:52 ERROR: CheckBlock() : CheckTransaction failed 2014-10-24 07:36:52 ERROR: ProcessBlock() : CheckBlock FAILED 2014-10-24 07:38:46 ERROR: AcceptBlock() : rejected by synchronized checkpoint 2014-10-24 07:38:46 ERROR: ProcessBlock() : AcceptBlock FAILED 2014-10-24 07:40:58 ERROR: CTransaction::CheckTransaction() : txout.nValue below minimum 2014-10-24 07:40:58 ERROR: CheckBlock() : CheckTransaction failed 2014-10-24 07:40:58 ERROR: ProcessBlock() : CheckBlock FAILED __________________ I use NOMP as Stratum and you can find my conf and getinfo below: CONF: rpcuser=xxxxxx rpcpassword=xxxxxx rpcallowip=192.168.100.* rpcconnect=127.0.0.1 listen=1 daemon=1 server=1 rpcport=7373 port=7372 maxconnections=20 alertnotify=echo %s | mail -s "HoboNickels Alert" ernstda@dec-com.de -r ernstda@dec-com.deblocknotify=node /home/coino/nomp/scripts02/cli.js blocknotify hobonickels %s blocknotify=node /home/coino/nomp/scripts01/cli.js blocknotify hobonickels %s blocknotify=node /home/coino/nomp/scripts/cli.js blocknotify hobonickels %s getinfo: { "version" : "v1.4.9.99-gfa9a1769-hobo", "protocolversion" : 70006, "blocks" : 1333797, "timeoffset" : -8, "moneysupply" : 6860038.66711100, "connections" : 16, "wallets" : 1, "walletversion" : 60002, "proxy" : "", "ip" : "5.56.222.69", "difficulty" : 23.18476548, "testnet" : false, "paytxfee" : 0.00100000, "mininput" : 0.00100000, "errors" : "" } Can someone help? I'll see if I can help you out. Could you tell me if other previous version of HBN worked. I just want to make sure it is something with the daemon and not your mining method. |
|
|
|
Now I come to think of it, I have another:
You mentioned before something to favor large stakeholders, top 20 I believe. To allow them higher split/combine levels. To make it easier for them just to stake away without the need for manual recombining all the time. Something quite valuable if you have a lot of coins that you don't want to see splitting until you end up having many thousands of small separate blocks.
So this would be my idea:
Defining a large stakeholder as any single address which holds >1% of the money supply. By this time it means just about the top 20 but because its related to the money supply, it will grow along as we develop.
Premium: I would suggest a Splitting/Recombining privilege that enables the large stake holders to limit their amount of blocks to an estimate of 500, corresponding with a Splitting/Recombining level of 0,2% of their wallet size.
Example:
Lets say you own 100Kcap on a single address and the money supply is 7000Kcap. In a case like that you would qualify for being a large stake holder (100/7000 = 1,43%).
Now, for being a large stake holder, your split/combine level shifts from a max of 20 to 0,2% of 100K which is 200. A pretty nice advantage I would say! Never more than 500 blocks and less need for manual recombining, serving the consensus function of POS as well.
I am really curious as to what everyone thinks of something like this.
I do plan to add the split/combine threshold to RPC command as well as start up. This will allow some of the additional control you have mentioned. May not make it for 2.3, but shouldn't be much further behind. Perhaps even to the gui later as well. |
|
|
|
What updates do we want to see for 2.3?
I have had a request for Autosavings updates, including custom send address. I can do that.
I was planning on doing the windows safe shutdown, and the combine/split threshold updates, to help keep blocks more manageable.
Obviously the new icons.
Anything else?
- Estimated stake - ala HYP
- Max stake popup reminders - Hit 1k mark, unencrypt & stake
- Percentage of total coin created in overview
- Percentage of Variation in top wallets 15/30day in overview
Other wallets have trading information some saving/staking related information is more relevant to our needs. As an aside is anyone else holding off staking to try and get the block with 7 Millionth coin or is it just me? Good stuff. I can definitely add some of the additional coin control stuff. Your 2nd point defeats the purpose of using stake to move the block chain. If this is something a user wants, I'm afraid they will have to do this themselves. What do you mean percentage of coins created? The network money supply is already available quickly by clicking the staking or block icon or using the network menu. The 4th point requires watch only be added to the code. This is not trivial, perhaps in the future, but not for 2.3. |
|
|
|
Oh, great ... https://github.com/Tranz5/HoboNickels/archive/master.zipAll arrived at default libraries Debian 6 (sic !!) And I have all successfully launched and running. Synchronized again purse. It will be a long time, but coins previously forwarded to the console version, are already visible. In any case it is a great and good work ! Tranz, my congratulations and gratitude )) Excellent. Glad it is working out. It shouldn't take more then 12-24 hours to sync. |
|
|
|
(btw, "sudo ./HoboNickels-qt", I see little reason to run it as superuser (sudo))
I got a permission denied on the .HoboNickels directory. Rather then trouble shoot it, I just took the user out of the equation. |
|
|
|
Would it be possible to code in customizable skins? Something like Hyp's wallet skin selector? That way we could potentially get some new visual styles working in the wallet
Possible, yes. It is a fair amount of work. Plus it requires some skin makers, not my specialty. I'm sure I can get the core of it going. Beauty over Function? GI Joe cartoons from the 80s say knowing is 1/2 the battle First Choice Haircutters says looking good is 1/2 the battle Conclusion > Need beauty and function to win the battle Touché! |
|
|
|
|
Show Posts
