I have a question for the community: is there any interest in having a resource to buy or sell HBN directly for fiat?
To me anything that can help spread the word, and create additional liquidity for HBN is a good thing. Having said that, I also agree with PressF1, the volume may or may not be there to support the additional market. But as always if someone is willing to put in the resources to make it happen, I will do whatever I can to help. |
|
|
|
Thanks for elaborating! I had the same feeling, that 0.008 was a little high. I guess because it built up to that level rather fast.
What you say about your hesitation towards releasing a wallet that enables the possibility of keeping blocks too big I do understand.
Only a few big blocks in stead of many small would fuel inflation and diminish network security. Is what I make of it. But almost every wallet, CAP/HBN in the top ten range manually recombines at the moment so their blocks would only diminish in size. Since the default split level will stay rather low (5 HBN, 10 CAP commit) I wouldn't expect much of a change in average staking-blocksize. In fact, like before, I think you found a sound balance.
Only the difference between HBN and CAP: the user allowable max start up split level, HBN at 4 times default (20) and CAP at 20 times default (200). That I don't quite get.
Honestly the difference between them is mostly me experimenting a bit. Also CAP will inflate faster than HBN, so the extra combining in CAP will even out a bit. |
|
|
|
It seems for some reason, HBN stake diff. is getting lower again to levels not seen for quite some weeks. Anyone an idea why this could be?
Or some other thing that I don't understand: HBN stake diff was a lot higher than CAP stake diff but there are more CAP out there than HBN and on top of that, HBN-block time is half that of CAP, so twice as much HBN should be able to stake before it's stake diff should rise faster than CAP.
It is a bit lower, but based on my calculations this should be right about where it should be. To me the .008 was pretty high, at least for the number of coins and the maturity. It could be a few things that causes the fluctuation. Perhaps a big wallet or 2 went off line for a bit, or did some combining. All true on what you say between CAP and HBN. Basically it all boils down to how many coins are actively staking and how big the average block size of those coins are. Look the the network weight between HBN and CAP. CAP is around 300,000 and HBN is around 1MM. This simply means there are more coins in the HBN network that are actively staking, and/or the average block size of HBN is smaller. This is also one of the reasons I am hesitant to release a wallet that will allow and keep HBN and CAP blocks to big. As the blocks are combined and the average of them is bigger, the number of coins participating in staking diminishes and the difficulty goes down. But I also know there are user reason to keep them from staking and splitting down to dust, so it is a fine line. |
|
|
|
I've updated the wallets on my Linux, OSX, and Windows machines. All synched and working well. Thanks, Tranz.
Great, glad to hear. Thanks for the feedback. |
|
|
|
Just upgraded to the latest wallet.
I have a warning message.
"Warning. Checkpoint is to old, wait for blockchain to download, or notify developers"
Thing is, I am fully synched , so there is no more blockchain to download.
Just thought I would let you know and check if I should do anything about it.
I am running win7 64
This will go away next time you restart the client. |
|
|
|
|
Cool 4.0! I like some of the enhancements you have proposed.
One thing that I always thought that would be cool, was an historical USD/BTC price. So when the block is created, the prices of HBN->BTC and BTC->USD is recorded on the CCE.
|
|
|
|
Why is that? I had some coins I wanted moved and now I cannot.
Its not true. But I do not know how long it will be in maintenance mode? I suspect it shouldn't take much longer, maybe another day or two. But I am as much in the dark as you all are. |
|
|
|
|
Seems like a lot of work, time, and money to attack a coin. Plus what could they do? They can't double spend if a coin is using Auto Checkpoints. Other attacks are not that damaging, and in fact can be migrated by code.
Still though I wouldn't my coins anywhere I didn't feel comfortable with.
|
|
|
|
|
FYI. I sent an alert last night to the older clients. This was a high priority alert, as we only have 10 days until the fork. This caused safe mode for old clients.
I think Cryptsy is still on an old client, despite my ticket opened 5 days after 1.5 was released. For now it looks like deposits are disabled. They are either upgrading or still stuck in safe mode. Either way I will see what can be done to escalate the issue.
|
|
|
|
I closed my 1.5.0.0 wallet yesterday with enabled S4C and restarted it again. After unlocking the wallet for POS, I double clicked the green arrow icon and it showed S4C was working like before I closed the wallet.
But I didn't sent any S4C when I staked a block. Subsequently I disabled S4C en re-enabled it. Now it seems to work fine again.
Maybe some glitch I don't know, I thought I should report it in.
Hmm, the only issue I have seen was if you closed an old 1.4 wallet and opened up it with 1.5, without first disabling s4c. I have closed and opened 1.5 a few times and it seems to keep the s4c. But I will double check and make sure all is well. |
|
|
|
Any idea why HBN is not showing up on Coinwarz anymore? Does it have anything to do with this Block Explorer not having any connections? http://hbn.blockx.info/How do you think we can get HBN on another exchange like Poloniex? Happy New Year HBN Not sure? The sub page is still active and correct. http://www.coinwarz.com/cryptocurrency/coins/hobonickelsWe also have our main Block Explorer here: hbn.cryptocoinexplorer.com/We've tried to get HBN on other exchanges, and infact we have succeeded. However there is little to no volume, so the site ends up de-listing it. We can try again, but unless we have someone who will take the roll of MM(market maker), and keep the volume up and trades flowing, it maybe futile. If someone wants/can do this, it could be a good help, to get and keep another exchange. |
|
|
|
Very cool as always, thanks for the update. |
|
|
|
EMC2 is working on a crowd funding campaign to help raise funds for scientific research: http://www.indiegogo.com/project/preview/f5c49cabHere is an opportunity to promote HoboNickels as a sponsor of the campaign. Take a look at the sponsor logos and the perks to see how your coin would be promoted. Let me know if you are interested and to what degree. I think this is cool. What can we do to get HBN on here? I will add this site to our Charity page: http://hobonickels.info/donate.php. |
|
|
|
I see nothing on this end. I see block 1532056, on the explorer and in my wallet. Perhaps it was lagged for some reason.
You must be right, nothing out the the ordinary anymore here as well. How come though, that the shown time in CCE sometimes shows 0,0 minutes for the newest blocks for a while? Is that the clock time of the wallet that solved it which is running a little ahead of the correct time? That could be it yes. Could also be an efficiency thing that the CCE does. It simply recognize the new block, but doesn't fully parse it for a bit. The 0 age display is due to inconsistency between block time and server time. Block time stamps are set by the client that produces the block. If the client clock is off by a few minutes or if somebody is purposely trying to "time warp", the block age can be negative if the block time is ahead of the explorer server time. Instead of showing a negative age, I have programmed it to just show 0 minutes. Once server time catches up with the block time, it will show an age again. In terms of missing information on new blocks, Tranz is correct, it simply means the database loader is still parsing blocks and has not yet committed the missing information. Thanks for the information! |
|
|
|
I see nothing on this end. I see block 1532056, on the explorer and in my wallet. Perhaps it was lagged for some reason.
You must be right, nothing out the the ordinary anymore here as well. How come though, that the shown time in CCE sometimes shows 0,0 minutes for the newest blocks for a while? Is that the clock time of the wallet that solved it which is running a little ahead of the correct time? That could be it yes. Could also be an efficiency thing that the CCE does. It simply recognize the new block, but doesn't fully parse it for a bit. |
|
|
|
I noticed something peculiar in our CCE-blockexplorer: It shows the newest block being more than 10 minutes old. 14 minutes as a type. Reloading the page takes longer than normal too. Everything seems to work though. Anyone?
It's at block 1231453 right now.
I see nothing on this end. I see block 1532056, on the explorer and in my wallet. Perhaps it was lagged for some reason. |
|
|
|
Sorry I don't run pools so I am not sure the methods being used. Which pool software is that, and is it open source? I'll have a look, but you might have better luck asking the coder of that software. |
|
|
|
WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers.
Anybody seeing this?
I'm running a 2.2 wallet with 4~9 active connections (drops when I restart). I seem to be stuck at block 794622.
Peers are at block 796255-796263.
Nevermind. I reloaded the blockchain from backup and it seems okay now. Lost today's POS mined, but whatever ... :-) The checkpoint server did crash last night. It is back up and running now. The chain looked perfect to me either way. I only saw a few minor re-orgs of 1-2 blocks. Not sure why you got stuck though. |
|
|
|
|
Well my TrackID was able to get the Song and Artist. But don't know the other 2. Good luck, its a fun game!
|
|
|
|
|
Show Posts
