David Latapie
|
|
May 12, 2014, 01:34:33 PM |
|
Yo, guys do You know witch coin got the fastest confirms in cryptoworld.?
I know that HBN is very fast;) Ultracoin, I think. It was its selling point - not that I understand the need for fast confirmation. I heard that fastcoin is the fastest with very low block time. 12 sec. What's the point of such fast time, BTW?
|
|
|
|
ElTomeko27
|
|
May 12, 2014, 01:39:58 PM |
|
Yo, guys do You know witch coin got the fastest confirms in cryptoworld.?
I know that HBN is very fast;) Ultracoin, I think. It was its selling point - not that I understand the need for fast confirmation. I heard that fastcoin is the fastest with very low block time. 12 sec. What's the point of such fast time, BTW? Fast transactions?
|
|
|
|
David Latapie
|
|
May 12, 2014, 01:40:53 PM Last edit: May 12, 2014, 01:54:12 PM by David Latapie |
|
Fast transactions? Except for Bitcoin, every transaction is fast enough, no?
|
|
|
|
ElTomeko27
|
|
May 12, 2014, 01:50:24 PM |
|
Not only BTC also NMC and PPC...I was just curious which one is the fastest...
|
|
|
|
Kergekoin
|
|
May 12, 2014, 01:52:37 PM |
|
I guess the speed of transaction is quick enough for all coins with 60s or faster block time. Besides, PoW/PoS coins have generally faster blocks than stated, because PoS difficulty being independent from PoW difficulty. If i am not mistaken, then Fastcoin has had many problems because of its 12s block time?
I have not seen any faster coin than Fastcoin tho.
|
|
|
|
gentacomp
|
|
May 12, 2014, 07:34:34 PM Last edit: May 12, 2014, 07:45:43 PM by gentacomp |
|
Helo Sir, I got this when open my wallet : Can anyone help please...
|
|
|
|
sandpaper
|
|
May 12, 2014, 08:43:42 PM |
|
I get that when I close out HBN wallet and try to reopen before it seems to have fully closed. Just restart your computer and opem it again, should work. If it doesn't then I don't know =(
PS. Except psych, I just looked more closely at your error. I don't know what that means, but I would suggest if you have no HBN in your wallet delete and re-download.
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1060
May the force bit with you.
|
|
May 12, 2014, 08:45:52 PM |
|
Helo Sir, I got this when open my wallet :
Can anyone help please...
This must be the first time you opened version 1.4.0.1. Please remove the directory %appdata%/HoboNickels/txleveldb. Then start up the client again. It will re-sync and remake the index from peers. if you want want to speed up the process, see this page. http://wiki.hobonickels.info/index.php?title=Replace_Blockchain
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
May 12, 2014, 10:30:49 PM |
|
I guess the speed of transaction is quick enough for all coins with 60s or faster block time. Besides, PoW/PoS coins have generally faster blocks than stated, because PoS difficulty being independent from PoW difficulty. If i am not mistaken, then Fastcoin has had many problems because of its 12s block time?
I have not seen any faster coin than Fastcoin tho.
Remember that there is a trade off between block speed and block chain size. I think HBN has the perfect balance between the two.
|
|
|
|
gentacomp
|
|
May 13, 2014, 02:30:24 AM |
|
Helo Sir, I got this when open my wallet :
Can anyone help please...
This must be the first time you opened version 1.4.0.1. Please remove the directory %appdata%/HoboNickels/txleveldb. Then start up the client again. It will re-sync and remake the index from peers. if you want want to speed up the process, see this page. http://wiki.hobonickels.info/index.php?title=Replace_BlockchainYay it works !!! Thank you Sir, coin saved
|
|
|
|
ElTomeko27
|
|
May 13, 2014, 04:50:36 AM |
|
I guess the speed of transaction is quick enough for all coins with 60s or faster block time. Besides, PoW/PoS coins have generally faster blocks than stated, because PoS difficulty being independent from PoW difficulty. If i am not mistaken, then Fastcoin has had many problems because of its 12s block time?
I have not seen any faster coin than Fastcoin tho.
Remember that there is a trade off between block speed and block chain size. I think HBN has the perfect balance between the two. Ok so what if the HBN block chain will be much bigger than now??
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
May 13, 2014, 04:58:59 PM |
|
Ok so what if the HBN block chain will be much bigger than now??
When the chain grows larger it just means it takes longer to sync and takes up more storage. Right now the HBN chain is something like 700mb (at least that is the size of my appdata HBN folder), which is not bad at all. It will be somewhere around 1 gb per year.
|
|
|
|
carloss
Member
Offline
Activity: 64
Merit: 10
|
|
May 13, 2014, 05:12:47 PM |
|
Unfortunately it is doing that all the time I have libboost 1.54...do you think it is worth to try upgrading to 1.55? Perfect tutorial here for libboost 1.55 https://coderwall.com/p/0atfugThank you, superresistant. I was curious about this as well. I have updated to libboost 1.55 (luckily in Ubuntu 14.04 is already in repo) and it seems to work better. There were few situations where hobonickelsd took 100% CPU, but not that long/often anymore. But today it crashed again (different cause)?: 05/13/14 10:46:31 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000014c891e8153bff84e187217e53bf0123ef5215f5c79b6fafb1349a55 05/13/14 10:46:31 sending: getblocks (1029 bytes) 05/13/14 10:46:31 askfor block 716d8fba33600c93fa69 1402087979000000 (20:52:59) 05/13/14 10:46:32 received: checkpoint (108 bytes) 05/13/14 10:46:32 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000b4a5a70483a2c1069559be9ff1259f49e6f94e0e14ad1d60fcd28d9 05/13/14 10:46:32 sending: getblocks (1029 bytes) 05/13/14 10:46:32 askfor block 716d8fba33600c93fa69 1402088099000000 (20:54:59) 05/13/14 10:46:32 received: inv (37 bytes) 05/13/14 10:46:32 got inventory: block 000000000b4a5a70483a have 05/13/14 10:46:32 sending: getblocks (1029 bytes) 05/13/14 10:46:33 received: inv (37 bytes) 05/13/14 10:46:33 got inventory: block ffd1e77b6676ca93358e have 05/13/14 10:46:35 ERROR: CTransaction::ReadFromDisk() : OpenBlockFile failed 05/13/14 10:46:35 ERROR: mempool transaction missing input
|
|
|
|
ElTomeko27
|
|
May 13, 2014, 07:34:19 PM |
|
Ok so what if the HBN block chain will be much bigger than now??
When the chain grows larger it just means it takes longer to sync and takes up more storage. Right now the HBN chain is something like 700mb (at least that is the size of my appdata HBN folder), which is not bad at all. It will be somewhere around 1 gb per year. Ok understood:)
|
|
|
|
unick
|
|
May 13, 2014, 08:31:03 PM |
|
Ok so what if the HBN block chain will be much bigger than now??
When the chain grows larger it just means it takes longer to sync and takes up more storage. Right now the HBN chain is something like 700mb (at least that is the size of my appdata HBN folder), which is not bad at all. It will be somewhere around 1 gb per year. Ok understood:) and when it gets a lot much bigger, we can use an hosted version or electrum/multibit type of solution for people wanting to jumpstart the inital load or don't want to host the whole block chain. With every problem there is a solution, right now this is not an issue. But it is a valid concern!
|
|
|
|
z0rr0
|
|
May 13, 2014, 10:05:43 PM |
|
Ok so what if the HBN block chain will be much bigger than now??
When the chain grows larger it just means it takes longer to sync and takes up more storage. Right now the HBN chain is something like 700mb (at least that is the size of my appdata HBN folder), which is not bad at all. It will be somewhere around 1 gb per year. Ok understood:) and when it gets a lot much bigger, we can use an hosted version or electrum/multibit type of solution for people wanting to jumpstart the inital load or don't want to host the whole block chain. With every problem there is a solution, right now this is not an issue. But it is a valid concern! Do you think staking will be working with such a "hosted version or electrum/multibit type" wallet? Looks doubtful to me.
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1060
May the force bit with you.
|
|
May 13, 2014, 11:45:22 PM |
|
Unfortunately it is doing that all the time I have libboost 1.54...do you think it is worth to try upgrading to 1.55? Perfect tutorial here for libboost 1.55 https://coderwall.com/p/0atfugThank you, superresistant. I was curious about this as well. I have updated to libboost 1.55 (luckily in Ubuntu 14.04 is already in repo) and it seems to work better. There were few situations where hobonickelsd took 100% CPU, but not that long/often anymore. But today it crashed again (different cause)?: 05/13/14 10:46:31 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000014c891e8153bff84e187217e53bf0123ef5215f5c79b6fafb1349a55 05/13/14 10:46:31 sending: getblocks (1029 bytes) 05/13/14 10:46:31 askfor block 716d8fba33600c93fa69 1402087979000000 (20:52:59) 05/13/14 10:46:32 received: checkpoint (108 bytes) 05/13/14 10:46:32 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000b4a5a70483a2c1069559be9ff1259f49e6f94e0e14ad1d60fcd28d9 05/13/14 10:46:32 sending: getblocks (1029 bytes) 05/13/14 10:46:32 askfor block 716d8fba33600c93fa69 1402088099000000 (20:54:59) 05/13/14 10:46:32 received: inv (37 bytes) 05/13/14 10:46:32 got inventory: block 000000000b4a5a70483a have 05/13/14 10:46:32 sending: getblocks (1029 bytes) 05/13/14 10:46:33 received: inv (37 bytes) 05/13/14 10:46:33 got inventory: block ffd1e77b6676ca93358e have 05/13/14 10:46:35 ERROR: CTransaction::ReadFromDisk() : OpenBlockFile failed 05/13/14 10:46:35 ERROR: mempool transaction missing input It can take CPU when it is getting a new block, or the client is working on a stake, it is normal for it is use 1 core, and on my quad sometimes it uses 2 full cores. That is the most I have seen. Not sure I have seen that error before. Your debug looks complely different then any I have seen before. From Ubuntu to win xp. Here is a how mine look. 7372 05/13/14 23:40:41 SetBestChain: new best=000000000319a40e64a4 height=844485 trust=2876684406729 date=05/13/14 23:40:21 05/13/14 23:40:41 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000319a40e64a48a459d9fad24d8fd3a1b714879acb9d202906ca2e446 05/13/14 23:40:41 ProcessBlock: ACCEPTED 05/13/14 23:40:42 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000c4610b528c49b8fc6d9a5a4453f298fa9891bf74c1742563bed0e7c 05/13/14 23:40:42 received block 000000000c4610b528c4 sent from 31.16.103.210:7372 05/13/14 23:40:42 SetBestChain: new best=000000000c4610b528c4 height=844486 trust=2876684440261 date=05/13/14 23:40:29 05/13/14 23:40:42 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000c4610b528c49b8fc6d9a5a4453f298fa9891bf74c1742563bed0e7c 05/13/14 23:40:42 ProcessBlock: ACCEPTED 05/13/14 23:40:44 getblocks 844482 to 0000000010fa5a846f4c limit 500 05/13/14 23:40:44 getblocks stopping at 844482 0000000010fa5a846f4c 05/13/14 23:40:44 getblocks 844482 to 000000001c32d30250a1 limit 500 05/13/14 23:40:44 getblocks stopping at 844483 000000001c32d30250a1 05/13/14 23:40:44 getblocks 844482 to 0000000011ec95f00024 limit 500 05/13/14 23:40:44 getblocks stopping at 844484 0000000011ec95f00024 05/13/14 23:40:44 getblocks 844482 to 000000000319a40e64a4 limit 500 05/13/14 23:40:44 getblocks stopping at 844485 000000000319a40e64a4 05/13/14 23:40:44 getblocks 844482 to 000000000c4610b528c4 limit 500 05/13/14 23:40:44 getblocks stopping at 844486 000000000c4610b528c4 05/13/14 23:40:44 getblocks -1 to 00000000000000000000 limit 500 05/13/14 23:40:45 Flushing wallet.dat
I don't see any indication of height or getting or receiving blocks in your log. Very odd.. Is your client fully up to sync with the block explorer? http://hbn.blockx.info/get/chain/HoboNickels Was this during the init download. Something seems off, you seem to have been caught up in an orphan loop check..
|
|
|
|
unick
|
|
May 14, 2014, 01:23:23 AM |
|
Ok so what if the HBN block chain will be much bigger than now??
When the chain grows larger it just means it takes longer to sync and takes up more storage. Right now the HBN chain is something like 700mb (at least that is the size of my appdata HBN folder), which is not bad at all. It will be somewhere around 1 gb per year. Ok understood:) and when it gets a lot much bigger, we can use an hosted version or electrum/multibit type of solution for people wanting to jumpstart the inital load or don't want to host the whole block chain. With every problem there is a solution, right now this is not an issue. But it is a valid concern! Do you think staking will be working with such a "hosted version or electrum/multibit type" wallet? Looks doubtful to me. as I understand it, I wouldn't see any reason why it shouldn't work. The staking process takes into consideration what is held in an address. It doesn't care if you have the block chain on your computer or not. Once the client finds a block, it need to broadcast that block to the network like it would do for any other transaction. So with an electrum/multibit type wallet, you already almost all you need in your wallet (meaning your public/private key pair and transaction ability). What those current implementation lack is the ability of mining PoS blocks. But I would imagine that feature being easily added to those wallets.
|
|
|
|
TillKoeln
Legendary
Offline
Activity: 2282
Merit: 1051
unnamed.Exchange, join the Cool Kids!!!
|
|
May 14, 2014, 06:20:47 AM |
|
i like the new wallet
|
|
|
|
carloss
Member
Offline
Activity: 64
Merit: 10
|
|
May 14, 2014, 07:52:37 AM |
|
I don't see any indication of height or getting or receiving blocks in your log. Very odd.. Is your client fully up to sync with the block explorer? http://hbn.blockx.info/get/chain/HoboNickels Was this during the init download. Something seems off, you seem to have been caught up in an orphan loop check.. I was not able to check it, because the hobonickelsd process already exited, so there was no RPC working. Probably it panicked after these lines in the log: 05/13/14 10:46:35 ERROR: CTransaction::ReadFromDisk() : OpenBlockFile failed 05/13/14 10:46:35 ERROR: mempool transaction missing input
So I have to restarted it again. Running with -debug flag. This was not during the initial load, the process was running for many hours before already.
|
|
|
|
|