[ANN][VTR] vTorrent - Share with freedom | 2FA | HD | @Bittrex

[coins101]

Can someone post some nodes, can't sync

I think more people need to be staking to keep the chain zinging along.

[1714469803]

1714469803

[1714469803]

1714469803

[Pickleninja]

Can someone post some nodes, can't sync

I think more people need to be staking to keep the chain zinging along.

Whats the average rate of return when it comes to staking?

[coins101]

Can someone post some nodes, can't sync

I think more people need to be staking to keep the chain zinging along.

Whats the average rate of return when it comes to staking?

OP has it at 5%/year

That's the rate of increase for the coin supply. I'll have a look at the repo to see what the stake reward is based on.

edit

I'll do it tomorrow.

[The BTC Painter]

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

[coins101]

It's interesting to note that the CIA leaks mean that VTR is one of the most secure wallets because it uses 2FA.

If hacks get access to your systems and can intercept before anything is encrypted or passwords are tracked (your funds can be taken at will), 2FA is one-time on demand protection.

I think we should create a royalties fund for Kim.com as he owns the patent to 2FA, then let him have access to those VTRs.

[Pickleninja]

It's interesting to note that the CIA leaks mean that VTR is one of the most secure wallets because it uses 2FA.

If hacks get access to your systems and can intercept before anything is encrypted or passwords are tracked (your funds can be taken at will), 2FA is one-time on demand protection.

I think we should create a royalties fund for Kim.com as he owns the patent to 2FA, then let him have access to those VTRs.

This is a very good point!

Encryption don't mean jack if people are logging your key strokes.

[coins101]

Can someone post some nodes, can't sync

I think more people need to be staking to keep the chain zinging along.

Whats the average rate of return when it comes to staking?

OP has it at 5%/year

That's the rate of increase for the coin supply. I'll have a look at the repo to see what the stake reward is based on.

edit

I'll do it tomorrow.

Well this is a bundle of fun.

Basically, it's 5% per year

Code:

static const int64_t COIN_YEAR_REWARD = 5 * CENT; // 5% per year

But it looks like there is a change to encourage people to be online

Code:

// miner's coin stake reward based on coin age spent (coin-days)
    int64_t nSubsidy;
    if (IsProtocolV3(pindexPrev->nHeight))
        nSubsidy = (pindexPrev->nMoneySupply / COIN) * COIN_YEAR_REWARD / (365 * 24 * (60 * 60 / 64));
    else
        nSubsidy = nCoinAge * COIN_YEAR_REWARD * 33 / (365 * 33 + 8);

    if (fDebug && GetBoolArg("-printcreation"))
        LogPrintf("GetProofOfStakeReward(): create=%s nCoinAge=%d\n", FormatMoney(nSubsidy).c_str(), nCoinAge);
    
    return nSubsidy + nFees;

So that you don't just earn 5% on your balance, but 5% on your balance if you keep your connection open. Well, something like that. I didn't go all the way down the rabbit hole.

[coins101]

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

the vTorrent youtube videos are pretty good for that sort of thing?

[ik_do]

23 active connections right now...

[ik_do]

a 0.8.2.1 node has been online for the past 35 minutes...

[coins101]

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

[hughbt]

Looks like a lot of work is being done behind the scenes.

[Pickleninja]

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

[slugmandrew]

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.

[kjadB]

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?

[coins101]

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?

[kjadB]

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

[ALCTEC]

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

[ALCTEC]

Big thanks to SEC for the cheap bitcorns and an even bigger thanks to the weak VTR hands

[kjadB]

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