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

[ik_do]

Also another note that Cryptoguru only ever displays nodes on a certain port which is why it only shows 5 or so active connections out of 22+

[coins101]

Remove the ports from all the nodes.  Just put it addresses.

What are ports? Can u writte a sample?

pm me your email address. I'll send you a file.

[Testudoguy]

Remove the ports from all the nodes.  Just put it addresses.

What are ports? Can u writte a sample?

pm me your email address. I'll send you a file.

I send u pm already

[AnotherNode]

Also another note that Cryptoguru only ever displays nodes on a certain port which is why it only shows 5 or so active connections out of 22+

I'm maxing out at 5 connections. Can you share the connection details in your conf file?

Not sure why the other guy can't get any connections. It's a little tricky, but the video is very good.

[coins101]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

[15266]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

Oeh so fun :p im on the 13th of dec, but admit that I have no ffing clue :p

[coins101]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

Oeh so fun :p im on the 13th of dec, but admit that I have no ffing clue :p

If you get 13 dec, based on that post, I'll triple your payout.

What time?

@mod

Can we post this here, or is there a better place to move to?

[Pickleninja]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

January 8th at 2:34pm


-Pickle

[coins101]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

January 8th at 2:34pm


-Pickle

Going long. Interesting.

I'll bump your payout by 4.444 for being so pessimistic. The possibility of a bigger payout might make you more.....hopeful.

[Testudoguy]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

January 8th at 2:34pm


-Pickle

Going long. Interesting.

I'll bump your payout by 4.444 for being so pessimistic. The possibility of a bigger payout might make you more.....hopeful.

What will acctualy happen 1 fork? What will be
New?

[leigh2k14]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

Just because i'm board, i'm gonna say, dec 17 11.59 pm

[leigh2k14]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

January 8th at 2:34pm


-Pickle

Going long. Interesting.

I'll bump your payout by 4.444 for being so pessimistic. The possibility of a bigger payout might make you more.....hopeful.

What will acctualy happen 1 fork? What will be
New?

[xxxccc]

How do content uploaders and seeders get compensated after the supply limit is reached?

[15266]

Guessing game:

101 VTRs to the person that can get closest to the the time of block 1,200,000

Closing date is 10 Dec, 00.00 GMT.

One entry per day allowed - so you can post one guess each day: up to 11.59 time, according to BCT post clock.

Oeh so fun :p im on the 13th of dec, but admit that I have no ffing clue :p

If you get 13 dec, based on that post, I'll triple your payout.

What time?

@ 01.13 GMT... =)

[gjhiggins]

Also another note that Cryptoguru only ever displays nodes on a certain port which is why it only shows 5 or so active connections out of 22+

I'm maxing out at 5 connections. Can you share the connection details in your conf file?

Not sure why the other guy can't get any connections. It's a little tricky, but the video is very good.

This is all there is according to getpeerinfo.

Code:

[
    {
        "addr" : "85.24.143.58:22524",
        "services" : "10000001b",
        "lastsend" : 1480458535,
        "lastrecv" : 1480458535,
        "bytessent" : 1678195,
        "bytesrecv" : 19072983,
        "conntime" : 1480446771,
        "timeoffset" : 1,
        "pingtime" : 0.14237000,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "2.49.36.96:22524",
        "services" : "10000001b",
        "lastsend" : 1480458535,
        "lastrecv" : 1480458533,
        "bytessent" : 1231017,
        "bytesrecv" : 13482046,
        "conntime" : 1480446772,
        "timeoffset" : -2,
        "pingtime" : 0.82182400,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "79.130.7.124:49958",
        "services" : "10000001b",
        "lastsend" : 1480458531,
        "lastrecv" : 1480458540,
        "bytessent" : 1167602,
        "bytesrecv" : 13179149,
        "conntime" : 1480446774,
        "timeoffset" : 1,
        "pingtime" : 0.27841800,
        "pingwait" : 25.25941000,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : true,
        "chainheight" : 1151925,
        "banscore" : 0
    },
    {
        "addr" : "94.38.142.104:22524",
        "services" : "10000001b",
        "lastsend" : 1480458520,
        "lastrecv" : 1480458520,
        "bytessent" : 417917,
        "bytesrecv" : 4781125,
        "conntime" : 1480453851,
        "timeoffset" : -31,
        "pingtime" : 0.13960300,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "45.55.197.64:22524",
        "services" : "10000001b",
        "lastsend" : 1480458458,
        "lastrecv" : 1480458539,
        "bytessent" : 67883,
        "bytesrecv" : 861030,
        "conntime" : 1480456161,
        "timeoffset" : -25,
        "pingtime" : 588.63883500,
        "pingwait" : 527.66639800,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151910,
        "banscore" : 0
    }
]

For best results, conf file should include:

Code:

addnode=85.24.143.58
addnode=2.49.36.96
addnode=79.130.7.124
addnode=94.38.142.104
addnode=45.55.197.64

Cheers

Graham

[leigh2k14]

Another one bites the dust: https://torrentfreak.com/police-shut-down-frances-largest-pirate-site161129/?utm_source=dlvr.it&utm_medium=twitter

[coins101]

VTR just crossed the first of its many ATH's

[coins101]

How do content uploaders and seeders get compensated after the supply limit is reached?

What supply limit would that be?

[coins101]

.....
Dear all,


Actually, the size of piece I stated here is only related to the way BitTorrent protocol works, by slicing up different size of torrent file in pieces and have each pieces verified by leacher's client using the SHA1 algorithm against the seeder's piece after each pieces is transferred, for example with 512kb piece size, 700mb would be divided into 1,400 pieces, piece size is the key that can make a torrent seeded on a slow connection scale well.

There is actually no theoretical limit for the bandwidth or file size that our network can handle at any given moment.

Moreover, each pieces of torrent file is unrelated to each transaction on VTR network, all of the transactions made to each seeders will be in micropayment channels which most of the transaction will be off-chain, and hence there should be no bloat issue for the VTR blockchain to handle.


Regards,

vTorrent

bump

Sounds like either a Lightning Network type payment channels; perhaps some sort of Factom approach; maybe collecting tx's and merging them into the merkle root as one hash output.

Your guess is, at the moment, as good as anyone's around here.

[AnotherNode]

This is all there is according to getpeerinfo.

Code:

[
    {
        "addr" : "85.24.143.58:22524",
        "services" : "10000001b",
        "lastsend" : 1480458535,
        "lastrecv" : 1480458535,
        "bytessent" : 1678195,
        "bytesrecv" : 19072983,
        "conntime" : 1480446771,
        "timeoffset" : 1,
        "pingtime" : 0.14237000,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "2.49.36.96:22524",
        "services" : "10000001b",
        "lastsend" : 1480458535,
        "lastrecv" : 1480458533,
        "bytessent" : 1231017,
        "bytesrecv" : 13482046,
        "conntime" : 1480446772,
        "timeoffset" : -2,
        "pingtime" : 0.82182400,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "79.130.7.124:49958",
        "services" : "10000001b",
        "lastsend" : 1480458531,
        "lastrecv" : 1480458540,
        "bytessent" : 1167602,
        "bytesrecv" : 13179149,
        "conntime" : 1480446774,
        "timeoffset" : 1,
        "pingtime" : 0.27841800,
        "pingwait" : 25.25941000,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : true,
        "chainheight" : 1151925,
        "banscore" : 0
    },
    {
        "addr" : "94.38.142.104:22524",
        "services" : "10000001b",
        "lastsend" : 1480458520,
        "lastrecv" : 1480458520,
        "bytessent" : 417917,
        "bytesrecv" : 4781125,
        "conntime" : 1480453851,
        "timeoffset" : -31,
        "pingtime" : 0.13960300,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1.1/",
        "inbound" : false,
        "chainheight" : 1151926,
        "banscore" : 0
    },
    {
        "addr" : "45.55.197.64:22524",
        "services" : "10000001b",
        "lastsend" : 1480458458,
        "lastrecv" : 1480458539,
        "bytessent" : 67883,
        "bytesrecv" : 861030,
        "conntime" : 1480456161,
        "timeoffset" : -25,
        "pingtime" : 588.63883500,
        "pingwait" : 527.66639800,
        "version" : 80016,
        "subver" : "/vTorrent-Core:0.8.1/",
        "inbound" : false,
        "chainheight" : 1151910,
        "banscore" : 0
    }
]

For best results, conf file should include:

Code:

addnode=85.24.143.58
addnode=2.49.36.96
addnode=79.130.7.124
addnode=94.38.142.104
addnode=45.55.197.64

Cheers

Graham

Should have thought of doing that 

Thanks for confirmation on the nodes.