Version 0.4.0 (multithreaded) released!Version 0.4.0 is VERY fast! Local wallets loading in 0.2 sec. instead of 15 sec. (after first caching)! Progress is showing while synchronizing. Try new version. Note that core 0.4.0 does not work on Windows.You can use 0.3.x versions - https://github.com/cryptocurs/hidecoin-0.3.x I have found serious bug. So wallets is not fast now. Wait for version 0.4.1. Since 0.3.5 I have frequently wallets getting out of sync and stuck. Setting sync to 5 or 9 seems to have no effect. Also when wallets are synced there are often many wallets 1-4 blocks behind. It seems that the propagation of new height is slow. 0.4.X Great news. Will there be multi-thread for win in the future ? Keep up the good work !
|
|
|
Yes size of tx is still limited but I think it will be on the roadmap if not then it's not much of use.
It is on the roadmap. Version 0.3.5 releasedPlease update your core to 0.3.5. I am developing new version and I need you to install this update. Upgraded, no problems.
|
|
|
Can not run light wallet. WinXP-sp3 1st run : current tab walletHome, requested to set tab walletHome, reset=true byteball.js:3210 uncaughtException byteball.js:6755 stack Error: failed to write conf.json: Error: ENOENT: no such file or directory, open 'F:\Program Files\Byteball\undefined\byteball\conf.json' at Error (native) at chrome-extension://ppgbkonninhcodjcnbpghnagfadnfjck/public/byteball.js:9657:11 angular.js:28501 Showing err popup:Uncaught exception: Error: failed to write conf.json: Error: ENOENT: no such file or directory, open 'F:\Program Files\Byteball\undefined\byteball\conf.json' angular.js:28501 Showing fi-alert popup:Uncaught exception: Error: failed to write conf.json: Error: ENOENT: no such file or directory, open 'F:\Program Files\Byteball\undefined\byteball\conf.json' angular.js:28501 onGoingProcess Syncing true 2nd run and after conf.json created. uncaughtException byteball.js:6755 stack Error: Failed to switch to light, please restart the app at Error (native) at chrome-extension://ppgbkonninhcodjcnbpghnagfadnfjck/public/byteball.js:9660:11 angular.js:28501 Showing err popup:Uncaught exception: Error: Failed to switch to light, please restart the app angular.js:28501 Showing fi-alert popup:Uncaught exception: Error: Failed to switch to light, please restart the app angular.js:28501 onGoingProcess Syncing true
|
|
|
Just a thought. As you know, a fork is pretty much the worst thing that can happen to a coin. Orphans happen all the time in Bitcoin, which is essentially a brief fork, corrected by the network. So, instead of the horrendous word 'fork', perhaps better utilize something like 'orphan chain' or something. Again, just a thought. I suspect these are all debug messages that will be gone soon by default... The forks were once much longer than 1... so it's a legacy message used to debug longer forks. Are there any limitations on the size of tx? Has that been addressed and resolved? Yes size of tx is still limited but I think it will be on the roadmap if not then it's not much of use.
|
|
|
What's going on with PASC lately and the orphaned blocks on suprnova? I've been watching suprnova/nanopool closely and the past few days I'd say 75% of found blocks on suprnova are quickly orphaned and credited to nanopool. Sure, nanopool has a higher hash rate but watching closely it almost seems nanopool has found a way to take over suprnova's found blocks.
Just out of curiosity, if nanopool had control of enough nodes would it be possible for them to catch suprnova's found blocks, manipulate the block finder and spread it quickly to other nodes, which in turn would cancel out suprnova's find?
This is strange!!
Smells alot like the time warp exploit but whatever Nano is doing they show us that PaC has some serious issues that need to be fixed.
|
|
|
Chain working good. However, now and again, I still have an instance that is behind by a few hundred blocks.
What value is "sync" ?
|
|
|
Pascal frozen at POLO
|
|
|
@hidecoin2016 Could we please keep current solo cpu mining ? Right now its fun to mine even for small users. The moment pools with GPU or other high performance hardware is introduced it will be the usual small group who only think short term "mine and dump". Switching to POS would be even better.
|
|
|
Core 0.3.0 released!.... How much hidecoins do you have? Not enough !
|
|
|
Great work ! Web wallet UI gives time out error. Any progress on tx limitations ? Don't forget possible time warp exploit, Pascalcoin is latest project that has this problem. Also make sure that old wallets are rejected when there is an important update.
|
|
|
https://mega.nz/#!bRB2GBha!yrZLrx_hYc3JxOoGdoRIPWe7oQHjFWQKDlAkMg6a2OQ for those still way behind. pack includes current nodes and blockchain until block 1168xx something. download data.zip from mega. stop core. delete data/storage.json data/init-storage.json data/blockchain.dat data/blockchain.ind extract content from data.zip to your data/ folder restart node core enjoy Yes, this is very useful... Occasionally the blockchain can get corrupted and syncing cannot be restarted... so it's great to have this resource. It's happened to me only once... But I suggest people backup their blockchain data folder every 2-3 days. So far I never had a corrupt chain. If syncing fails because you have no connects then problem is init-storage.json. Well, replacing the data folder from a download solved my problem... maybe it was the nodes. I'm more concerned about how this coin gets on a decent exchange... Byteball had to list on cryptox.pl because it's so non-standard... It's extremely important for exchanges to have a standard and reliable wallet. Pascal also not standard got listed on Polo. But in line with your words, wallet has te be rock solid also important active development, block explorer. Right now too many show stoppers as listed in the roadmap. Would be nice to get an update of the dev.
|
|
|
https://mega.nz/#!bRB2GBha!yrZLrx_hYc3JxOoGdoRIPWe7oQHjFWQKDlAkMg6a2OQ for those still way behind. pack includes current nodes and blockchain until block 1168xx something. download data.zip from mega. stop core. delete data/storage.json data/init-storage.json data/blockchain.dat data/blockchain.ind extract content from data.zip to your data/ folder restart node core enjoy Yes, this is very useful... Occasionally the blockchain can get corrupted and syncing cannot be restarted... so it's great to have this resource. It's happened to me only once... But I suggest people backup their blockchain data folder every 2-3 days. So far I never had a corrupt chain. If syncing fails because you have no connects then problem is init-storage.json.
|
|
|
Does anyone know what the optimum value for sync is ? 9 speeds up download of chain but not sure what it does for mining.
no clue, i set it to 9, started 5 miners and wait 24h lol I had them at 9 but now at 5. But with increased competition I am not sure if I can tell what it did.
|
|
|
Does anyone know what the optimum value for sync is ? 9 speeds up download of chain but not sure what it does for mining.
|
|
|
would be nice to share you node ips, seems like the 2 nodes in data/init-storage.json are not responding. constantly degrading the rating when you look at data/storage.json also if you want to see the P2P messages go to core.js and replace "storage.logIgnoreModules = ['P2P']" with "//storage.logIgnoreModules = ['P2P']" (comment out) for those who can't sync.. based on what bitwonder put on mega i updated the init-storage.json. stop the node core replace your (not synching core) data/init-storage.json with this content http://pastebin.com/mVjx6fFY , delete data/storage.json, restart node core and see it synching again. Good info. I make use of my own backup of init-storage to get connected.
|
|
|
Block explorer offline.
Web wallet was also offline but both are back.
|
|
|
Program after shutdown is hanging an eternity on
[18:19:42 HRS]# Time difference: 0 F10 - quit CORE: blockchain caching... CORE: blockchain cached CORE: connection may take some time
No connections? Redownloading the blockchain? Some debug info here would be user friendly.
I have seen the same thing, it has problems getting connected with server. Chain is ok. same here, new to hidecoin, been waiting like a day now. no connection, snc 5 offline Have you checked your port forwarding ?
|
|
|
Program after shutdown is hanging an eternity on
[18:19:42 HRS]# Time difference: 0 F10 - quit CORE: blockchain caching... CORE: blockchain cached CORE: connection may take some time
No connections? Redownloading the blockchain? Some debug info here would be user friendly.
I have seen the same thing, it has problems getting connected with server. Chain is ok.
|
|
|
Would also be nice to know the difficulty of the coin. 1 address is now getting almost all of the blocks.
Not many ppl mining so very low diff. I think with RPC real miners can jump in and then the fun is over for the small guys.
|
|
|
|