Topic: [ANN][VTR] vTorrent - Share with freedom | 2FA | HD | @Bittrex - page 71. (Read 436207 times)
March 13, 2017, 05:50:36 AM
where can we see some work? github client's latest commit is oct 16, how is a hard fork coming?
March 13, 2017, 04:58:26 AM
It's block 1,300,000 right? Less than 9500 blocks remaining in that case. Has anyone done the math recently for the estimated date?
Should be an exciting week for VTR! Especially with all the money flowing into alts right now
Should be an exciting week for VTR! Especially with all the money flowing into alts right now
March 13, 2017, 04:03:14 AM
Only a few days remaining till the last fork, it will be interesting to see what happens afterwards.
Edit: Time for dev to produce, alts are booming right now, time to take advantage.
Edit: Time for dev to produce, alts are booming right now, time to take advantage.
March 12, 2017, 11:43:38 PM
Start by checking the clocks on your computer.
Unless you or your computer is trying to attack the network, that should fix the issue.
Unless you or your computer is trying to attack the network, that should fix the issue.
Thanks! Very weird, my clock was showing correct time, but when I checked vTorrent start time it was showing 12 hours earlier (swapped am & pm), so blocks looked like they were coming from the future. I resynced PC time with windows time server and all good now
Someone was cheating at candy crush
Heh Heh Heh
March 12, 2017, 09:39:16 PM
Start by checking the clocks on your computer.
Unless you or your computer is trying to attack the network, that should fix the issue.
Unless you or your computer is trying to attack the network, that should fix the issue.
Thanks! Very weird, my clock was showing correct time, but when I checked vTorrent start time it was showing 12 hours earlier (swapped am & pm), so blocks looked like they were coming from the future. I resynced PC time with windows time server and all good now
Someone was cheating at candy crush
March 11, 2017, 05:49:08 PM
Start by checking the clocks on your computer.
Unless you or your computer is trying to attack the network, that should fix the issue.
Unless you or your computer is trying to attack the network, that should fix the issue.
Thanks! Very weird, my clock was showing correct time, but when I checked vTorrent start time it was showing 12 hours earlier (swapped am & pm), so blocks looked like they were coming from the future. I resynced PC time with windows time server and all good now
March 11, 2017, 12:02:06 PM
Start by checking the clocks on your computer.
Unless you or your computer is trying to attack the network, that should fix the issue.
Unless you or your computer is trying to attack the network, that should fix the issue.
March 11, 2017, 04:23:40 AM
For about a week now my VTR wallet has been acting weird. I was fully synced and working well two weeks ago, then closed for about a week. When I started wallet up about 1 week ago it started to sync as normal, and when fully synced I unlocked as usual to start staking, but my wallet quickly fell behind block count an went into 'catching up'. Ever since whenever I restart the wallet continuously falls behind by about 5-50 blocks, so I never stake a block. If I close the wallet and restart it does the same behaviour, syncs up but before I stake a block it falls behind and never gets fully synced, continuously stays 5-50 blocks behind, perpetually 'catching up'. Has anyone seen this behaviour before?
What version are you running and what's is inside your .conf file?
my conf is below, nodes fom http://cryptoguru.tk/NetworkInfo/index.php?Currency=VTR
Code:
addnode=vtrseed.cloudns.asia
addnode=95.136.101.80:22524
addnode=182.55.186.7:22524
addnode=80.189.13.218:22524
addnode=87.97.98.60:22524
addnode=45.32.148.147:22524
addnode=94.145.177.190:22524
using wallet vTorrent-Core:0.8.1.1
I'm staking fine. PM dev, they may be able to help
Had a look in the debug file, this looks like where poblem happens after a restart just now.
Code:
SetBestChain: new best=3b67dd5cd6bed8081319eae163b4001131a6d596e883e83b34bffdec955518ea height=1288137 trust=43267431595747329523 blocktrust=360330196384528 date=03/11/17 09:06:56
ProcessBlock: ACCEPTED 3b67dd5cd6bed8081319
SetBestChain: new best=58ce7ba7b3c9d4fcf8e573426ca2b15003f4751329e8964af321497702404f47 height=1288138 trust=43267817664353547675 blocktrust=386068606218152 date=03/11/17 09:08:16
ProcessBlock: ACCEPTED 58ce7ba7b3c9d4fcf8e5
SetBestChain: new best=a4af9be0eb2920686e67afbddc0ce5f72a0935a47e93e42b69e8fcd5a4e92334 height=1288139 trust=43268191284430790490 blocktrust=373620077242815 date=03/11/17 09:09:36
ProcessBlock: ACCEPTED a4af9be0eb2920686e67
ERROR: CheckBlock() : block timestamp too far in the future
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckBlock() : block timestamp too far in the future
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckBlock() : block timestamp too far in the future
ERROR: ProcessBlock() : CheckBlock FAILED
Flushing wallet.dat
Flushed wallet.dat 122ms
Received mblk 1
ERROR: CheckBlock() : block timestamp too far in the future
ERROR: ProcessBlock() : CheckBlock FAILED
Maybe dev see this post, and other expert users ... help
March 11, 2017, 01:59:03 AM
Big thanks to SEC for the cheap bitcorns and an even bigger thanks to the weak VTR hands
March 10, 2017, 07:07:19 PM
For about a week now my VTR wallet has been acting weird. I was fully synced and working well two weeks ago, then closed for about a week. When I started wallet up about 1 week ago it started to sync as normal, and when fully synced I unlocked as usual to start staking, but my wallet quickly fell behind block count an went into 'catching up'. Ever since whenever I restart the wallet continuously falls behind by about 5-50 blocks, so I never stake a block. If I close the wallet and restart it does the same behaviour, syncs up but before I stake a block it falls behind and never gets fully synced, continuously stays 5-50 blocks behind, perpetually 'catching up'. Has anyone seen this behaviour before?
What version are you running and what's is inside your .conf file?
my conf is below, nodes fom http://cryptoguru.tk/NetworkInfo/index.php?Currency=VTR
Code:
addnode=vtrseed.cloudns.asia
addnode=95.136.101.80:22524
addnode=182.55.186.7:22524
addnode=80.189.13.218:22524
addnode=87.97.98.60:22524
addnode=45.32.148.147:22524
addnode=94.145.177.190:22524
using wallet vTorrent-Core:0.8.1.1
I'm staking fine. PM dev, they may be able to help
March 10, 2017, 06:16:15 PM
For about a week now my VTR wallet has been acting weird. I was fully synced and working well two weeks ago, then closed for about a week. When I started wallet up about 1 week ago it started to sync as normal, and when fully synced I unlocked as usual to start staking, but my wallet quickly fell behind block count an went into 'catching up'. Ever since whenever I restart the wallet continuously falls behind by about 5-50 blocks, so I never stake a block. If I close the wallet and restart it does the same behaviour, syncs up but before I stake a block it falls behind and never gets fully synced, continuously stays 5-50 blocks behind, perpetually 'catching up'. Has anyone seen this behaviour before?
What version are you running and what's is inside your .conf file?
my conf is below, nodes fom http://cryptoguru.tk/NetworkInfo/index.php?Currency=VTR
Code:
addnode=vtrseed.cloudns.asia
addnode=95.136.101.80:22524
addnode=182.55.186.7:22524
addnode=80.189.13.218:22524
addnode=87.97.98.60:22524
addnode=45.32.148.147:22524
addnode=94.145.177.190:22524
using wallet vTorrent-Core:0.8.1.1
March 10, 2017, 05:06:42 PM
For about a week now my VTR wallet has been acting weird. I was fully synced and working well two weeks ago, then closed for about a week. When I started wallet up about 1 week ago it started to sync as normal, and when fully synced I unlocked as usual to start staking, but my wallet quickly fell behind block count an went into 'catching up'. Ever since whenever I restart the wallet continuously falls behind by about 5-50 blocks, so I never stake a block. If I close the wallet and restart it does the same behaviour, syncs up but before I stake a block it falls behind and never gets fully synced, continuously stays 5-50 blocks behind, perpetually 'catching up'. Has anyone seen this behaviour before?
What version are you running and what's is inside your .conf file?
March 10, 2017, 04:55:34 PM
For about a week now my VTR wallet has been acting weird. I was fully synced and working well two weeks ago, then closed for about a week. When I started wallet up about 1 week ago it started to sync as normal, and when fully synced I unlocked as usual to start staking, but my wallet quickly fell behind block count an went into 'catching up'. Ever since whenever I restart the wallet continuously falls behind by about 5-50 blocks, so I never stake a block. If I close the wallet and restart it does the same behaviour, syncs up but before I stake a block it falls behind and never gets fully synced, continuously stays 5-50 blocks behind, perpetually 'catching up'. Has anyone seen this behaviour before?
March 10, 2017, 05:50:24 AM
Either way, it's exciting to know there is more progress being made. This project really excites me, and not just because of the possible financial payoffs, but the underlying tech has the potential to be SO disruptive if done right.
Fingers crossed... we are with you all the way dev.
Fingers crossed... we are with you all the way dev.
March 09, 2017, 12:12:28 PM
a 0.8.2.1 node has been online for the past 35 minutes...
ok, so now we need to know if 0.8.2.x is going to be compatible with 0.8.1.x clients or if this is another hard fork situation.
I'm guess that since we forked off 0.7.x clients, 0.8.x.x will run on the same chain so the next major fork would be 0.9.x.x
much guesswork
I would assume that 0.9.x.x would be the fork tbat would include the torrent... just a guess though. I've got really no insight into whats going on.
Edit: but i think its important to note that there is constantvwork on this project, and this should be irrefutable proof of that.
-pickle
March 09, 2017, 05:32:41 AM
Looks like a lot of work is being done behind the scenes.
March 09, 2017, 05:03:18 AM
a 0.8.2.1 node has been online for the past 35 minutes...
ok, so now we need to know if 0.8.2.x is going to be compatible with 0.8.1.x clients or if this is another hard fork situation.
I'm guess that since we forked off 0.7.x clients, 0.8.x.x will run on the same chain so the next major fork would be 0.9.x.x
much guesswork
March 09, 2017, 02:36:36 AM
a 0.8.2.1 node has been online for the past 35 minutes...
March 08, 2017, 02:15:04 PM
23 active connections right now...
March 08, 2017, 11:28:10 AM
Coins, when you post that info tomorrow can you possibly link back to your post about setting up your wallet for staking? Really good info there now unfortunately buried back in pages of dead PureVIDZ crap posts. Maybe some newer folks could use that to get some more coins staking to help the chain out.
Thanks
Thanks
the vTorrent youtube videos are pretty good for that sort of thing?
Jump to: