Quote from: coins101 on May 04, 2017, 04:15:33 PM

Quote from: DogTheHunter on May 04, 2017, 03:29:02 PM

Quote from: dev and Coins

@vTorrent

This image clearly shows you are building torrent functionality around Transmission, which is a great option. It also shows your client is fully syncd, that you have a fully working torrent implementation because your seed ratio clock is completely in sync with the public blockchain.

There looks like a stable release candidate on the network.

If you look at the bottom of the image it clearly shows torrent functionality is working on the devs client. The text in red looks like something cooking on the payment for torrents front Cool

I also just noticed that torrents are working on the current version of the client, so we probably don't have to do a hard fork to see it working (or do we?)

He is running this:

Code:

QString
132 TorrentDelegate :: shortTransferString( const Torrent& tor ) const
133 {
134 const bool haveDown( tor.peersWeAreDownloadingFrom( ) > 0 );
135 const bool haveUp( tor.peersWeAreUploadingTo( ) > 0 );
136 QString downStr, upStr, str;
137
138 if( haveDown )
139 downStr = Utils :: speedToString( tor.downloadSpeed( ) );
140 if( haveUp )
141 upStr = Utils :: speedToString( tor.uploadSpeed( ) );
142
143 if( haveDown && haveUp )
144 str = tr( "Down: %1, Up: %2" ).arg(downStr).arg(upStr);
145 else if( haveDown )
146 str = tr( "Down: %1" ).arg( downStr );
147 else if( haveUp )
148 str = tr( "Up: %1" ).arg( upStr );
149 else
150 str = tr( "Idle" );
151
152 return str;
153 }

Unless they have made some big changes, it's 100% Transmission

BUMP

Dig deep into the image above and you'll see that the devs do have a working torrent implementation. Just no idea why they can't or won't share a 5 second video clip of it to keep everyone happy