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
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 159. (Read 478852 times)
January 06, 2015, 09:21:03 AM
January 03, 2015, 05:10:29 AM
Another inflation update for anyone who is interested
https://bitcointalksearch.org/topic/m.10020752
https://bitcointalksearch.org/topic/m.10020752
January 02, 2015, 12:12:50 AM
EMC2 is working on a crowd funding campaign to help raise funds for scientific research:
http://www.indiegogo.com/project/preview/f5c49cab
Here 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.
http://www.indiegogo.com/project/preview/f5c49cab
Here 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.
January 01, 2015, 05:24:55 PM
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!
January 01, 2015, 02:55:27 PM
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.
December 31, 2014, 09:32:17 AM
All the best in new year to Hobonickels devs and fans.
There is new quite fancy cryptoexchange , still in beta but give Hobo a qote on voting once its ready
https://lazycoins.com/coinvote?
There is new quite fancy cryptoexchange , still in beta but give Hobo a qote on voting once its ready
https://lazycoins.com/coinvote?
December 26, 2014, 10:59:21 PM
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.
December 25, 2014, 10:58:47 PM
HBN still one of my fav coins!
December 25, 2014, 04:28:39 AM
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?
December 24, 2014, 04:49:10 PM
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.
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.
December 24, 2014, 12:48:08 PM
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 1531453 right now.
It's at block 1531453 right now.
December 22, 2014, 01:02:25 PM
Linux is good, I use it on a daily basis. But I have seen disc corruption on it.
I also saw a car with worn tires ))
Quote
I've even see the kernel get corrupted on a system patch. (Bad weekend!) So although it is very robust it is not 100% fault tolerant.
I can always upload multiple cores of their choice
there are no problems:
$ wajig list linux-image*
ii linux-image-2.6.32-5-amd64 2.6.32-48squeeze9 Linux 2.6.32 for 64-bit PCs
ii linux-image-2.6-amd64 3.2+46~bpo60+1 Linux for 64-bit PCs (dummy package)
ii linux-image-3.2.0-0.bpo.4-amd64 3.2.63-2+deb7u2~bpo60+1 Linux 3.2 for 64-bit PCs
ii linux-image-amd64 3.2+46~bpo60+1 Linux for 64-bit PCs (meta-package)
December 22, 2014, 12:50:17 PM
Maybe it`s good idea to add quick-backup feature into client itself?
or better not to use for such applications windows ))
is also a good idea
or better not to use for such applications windows ))
is also a good idea
Corruption on other OS is also possible. Less likely. But if you pull the disk out from under an application that is currently writing to it, you will get unpredictable results.
hmmm
no
for example xfs set to zero all "unpredictable results".
ps:
due to the loss of important data under win xp
I moved to the Linux (Debian) 14 years ago.
Linux is good, I use it on a daily basis. But I have seen disc corruption on it. I've even see the kernel get corrupted on a system patch. (Bad weekend!) So although it is very robust it is not 100% fault tolerant.
December 22, 2014, 12:18:56 PM
Maybe it`s good idea to add quick-backup feature into client itself?
or better not to use for such applications windows ))
is also a good idea
or better not to use for such applications windows ))
is also a good idea
Corruption on other OS is also possible. Less likely. But if you pull the disk out from under an application that is currently writing to it, you will get unpredictable results.
hmmm
no
for example xfs set to zero all "unpredictable results".
ps:
due to the loss of important data under win xp
I moved to the Linux (Debian) 14 years ago.
December 22, 2014, 12:11:21 PM
Maybe it`s good idea to add quick-backup feature into client itself?
or better not to use for such applications windows ))
is also a good idea
or better not to use for such applications windows ))
is also a good idea
Corruption on other OS is also possible. Less likely. But if you pull the disk out from under an application that is currently writing to it, you will get unpredictable results.
December 22, 2014, 11:59:01 AM
Maybe it`s good idea to add quick-backup feature into client itself?
or better not to use for such applications windows ))
is also a good idea
or better not to use for such applications windows ))
is also a good idea
December 22, 2014, 11:53:11 AM
The way I do it is before a windows update or other reason I know I am shutting down. I shut down the client and then create a backup_date folder and copy those 4 things mention above into that folder. I only do it once in a while.
Doing same - pretty usefull as i had problems before... once after accident power off wallet dat was corrupted. Backup helped me greatly.
Maybe it`s good idea to add quick-backup feature into client itself?
There is one for the wallet already, under file. I think adding one for the block chain is a good idea as well. It maybe tricky or not doable with txleveldb, and allowing the client to still be active. But might be worth investigating.
December 22, 2014, 11:39:27 AM
The way I do it is before a windows update or other reason I know I am shutting down. I shut down the client and then create a backup_date folder and copy those 4 things mention above into that folder. I only do it once in a while.
Doing same - pretty usefull as i had problems before... once after accident power off wallet dat was corrupted. Backup helped me greatly.
Maybe it`s good idea to add quick-backup feature into client itself?
December 22, 2014, 10:52:09 AM
Can I simply archive the txleveldb folder, when it's done syncing, and simply use the latest copy the next time it gets munged up? It's the only thing I deleted and my coins are all showing up again. Whew!
Yes, you can. I myself do a backup of txleveldb+database+blk0001.dat once a week.To save the block chain you backup txleveldb + blk001.dat. The wallet uses wallet.dat and database. Saving those 4 files, while the client is NOT running, is a great way to quickly backup.
The way I do it is before a windows update or other reason I know I am shutting down. I shut down the client and then create a backup_date folder and copy those 4 things mention above into that folder. I only do it once in a while.
December 22, 2014, 06:33:53 AM
Can I simply archive the txleveldb folder, when it's done syncing, and simply use the latest copy the next time it gets munged up? It's the only thing I deleted and my coins are all showing up again. Whew!
Yes, you can. I myself do a backup of txleveldb+database+blk0001.dat once a week. Jump to: