effectsToCause (OP)
|
|
September 09, 2016, 09:32:26 PM |
|
Yeah needed enough miners to get past that block at it's current difficulty. You can do file menu blockchain reload if you think you have a problem but it's not necessary it's the same chain continued.
|
|
|
|
Walrusbonzo
|
|
September 09, 2016, 09:46:32 PM |
|
We're moving again
|
|
|
|
eBit
Member
Offline
Activity: 91
Merit: 10
|
|
September 09, 2016, 11:46:14 PM |
|
Won't sync after update... tried deleting everything except wallet.dat and reinstall. Now it won't start.
I can confirm this issue. When doing an in wallet upgrade to 1.02 the wallet is fine. When doing a clean install of 1.02 with only the old wallet.dat file in place, the wallet crashes. I think the status before crashing was something like loading block index. I'm on Win 7 Ultimate 64bit. I got around this issue by installing an older wallet version and then doing an in wallet upgrade to 1.02.
|
|
|
|
Crypt0bull
|
|
September 10, 2016, 12:20:47 AM |
|
Won't sync after update... tried deleting everything except wallet.dat and reinstall. Now it won't start.
I can confirm this issue. When doing an in wallet upgrade to 1.02 the wallet is fine. When doing a clean install of 1.02 with only the old wallet.dat file in place, the wallet crashes. I think the status before crashing was something like loading block index. I'm on Win 7 Ultimate 64bit. I got around this issue by installing an older wallet version and then doing an in wallet upgrade to 1.02. I'm on win 10 64b, had to do the same workaround.
|
|
|
|
effectsToCause (OP)
|
|
September 10, 2016, 02:00:14 AM |
|
Won't sync after update... tried deleting everything except wallet.dat and reinstall. Now it won't start.
I can confirm this issue. When doing an in wallet upgrade to 1.02 the wallet is fine. When doing a clean install of 1.02 with only the old wallet.dat file in place, the wallet crashes. I think the status before crashing was something like loading block index. I'm on Win 7 Ultimate 64bit. I got around this issue by installing an older wallet version and then doing an in wallet upgrade to 1.02. I'm on win 10 64b, had to do the same workaround. Ok thanks looking into it.
|
|
|
|
Wh1teKn1ght
|
|
September 10, 2016, 02:07:36 AM |
|
working fine here...make sure you are running the wallet as admin if using Windows. I encountered different errors with the previous wallet until I figured out that I needed to Run As Administrator.
Any ETA on the Win 64-bit wallet?
|
|
|
|
pnosker
|
|
September 10, 2016, 03:12:49 AM |
|
working fine here...make sure you are running the wallet as admin if using Windows. I encountered different errors with the previous wallet until I figured out that I needed to Run As Administrator.
Any ETA on the Win 64-bit wallet?
Do you have more than 22 cores? If not, 32 bit is faster.
|
Support the VeriFund Endowment. VRC: VFEndownxxnHea9mv59kZx8c7TysGbndYx
|
|
|
hulahoof
Newbie
Offline
Activity: 18
Merit: 0
|
|
September 10, 2016, 03:54:05 AM Last edit: September 10, 2016, 05:06:52 AM by hulahoof |
|
Chainz explorer is still stuck at 2394 https://chainz.cryptoid.info/vrm/Edit
it's updating now
|
|
|
|
rolik2001
|
|
September 10, 2016, 04:46:00 AM |
|
when will be avaible exchange
|
|
|
|
.m.
|
|
September 10, 2016, 07:41:26 AM |
|
My trick with soft links does not work again. Please pack your version libcrypto.so.1.0.0 (./libs directory) into the installation package. You already have libssl there. Thank you. LD_LIBRARY_PATH=. ./verium-qt ./verium-qt: ./libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./verium-qt) ./verium-qt: ./libcrypto.so.1.0.0: version `OPENSSL_1.0.1d' not found (required by ./libs/libssl.so.1.0.0) ./verium-qt: ./libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./libs/libssl.so.1.0.0)
|
|
|
|
MAD945
|
|
September 10, 2016, 08:14:35 AM |
|
Updated and mining back up! Running smooth
|
|
|
|
wgd
Legendary
Offline
Activity: 1815
Merit: 1005
|
|
September 10, 2016, 08:26:14 AM |
|
diff grows again nothing
|
|
|
|
Hhampuz
Legendary
Offline
Activity: 3038
Merit: 6181
Meh.
|
|
September 10, 2016, 08:33:30 AM |
|
I was mining on 5 machines when the estimated time for blocks were 1hour. Was mining the entire night and found 0 blocks. Now we are back at 26hours estimation per block for me. Hmmmmm
|
|
|
|
MAD945
|
|
September 10, 2016, 08:37:49 AM |
|
I was mining on 5 machines when the estimated time for blocks were 1hour. Was mining the entire night and found 0 blocks. Now we are back at 26hours estimation per block for me. Hmmmmm
Doug explained that it's like ripples in a pond the estimated block time and difficulty will settle over time. I'm sure after about 12-24hours the network will calm and be back to more reliable estimates.
|
|
|
|
Walrusbonzo
|
|
September 10, 2016, 08:48:34 AM |
|
2 blocks for me last night on my 4790k
|
|
|
|
souljah1h
Legendary
Offline
Activity: 1092
Merit: 1000
Hyperspace snail
|
|
September 10, 2016, 09:16:13 AM |
|
2 blocks for me last night on my 4790k Same here, 2 blocks with X4 860k!
|
_@/'
|
|
|
endlessskill
|
|
September 10, 2016, 10:08:57 AM |
|
1 block with 4790
|
|
|
|
Crypt0bull
|
|
September 10, 2016, 11:51:53 AM |
|
0 blocks with 6700
|
|
|
|
thesilex
Member
Offline
Activity: 61
Merit: 10
|
|
September 10, 2016, 12:29:19 PM |
|
Why does mining reward fluctuate between 7.56933819 VRM and 8.40230135 VRM? As far as i see, it does not depend on block time.
|
|
|
|
effectsToCause (OP)
|
|
September 10, 2016, 01:23:06 PM |
|
Why does mining reward fluctuate between 7.56933819 VRM and 8.40230135 VRM? As far as i see, it does not depend on block time.
It is solely dependent on blocktime, small changes in the blocktime can change the reward. The network is still equilibrating to the restart after the frozen block, so there is more fluctuations still for another day or so probably as the difficulty, corresponding blocktime and total power of miners find equilibrium. https://github.com/VeriumReserve/verium/blob/master/src/main.cpp#L958
|
|
|
|
|