Current model is as follow, seeding and uploading will NOT generate new coin. Sharer will be awarded directly from other user by sending (paying) them to download the content of the torrent they've uploaded or currently seeding, as a result, they should be able to cash out/exchange the VTR for BTC or fiat from the users that need to download the content providing by the sharer.

I hope this should clear up your confusion, we are always open to new ideas, and constructive criticism are always welcome.

Thank you for your support.

I am also building new Beta client for Windows users, but it will not be release until I could find a work around for Windows QT static build and Webkit limitation. (Please see. https://qt-project.org/doc/qt-4.7/platform-notes.html)

Please keep in mind that the currency part of this project is completely 'open source' as it should be for all crypto-currency.

I have decided to 'closed source' all of the unique features of vTorrent's client such as in-client trading, trading bot, push notification system, including new locking (encryption) system.

Source for BitTorrent implement in-client will most likely be closed at least until the first beta or the official release of the client with the BitTorrent functions implemented.

Thank you all for your support.

Thank you for your report,

All links has been updated and link for new beta (OSX version) is also posted in the first post as feedback from private beta has been good so far.

Thank you for your support.

My main idea is to have a complete solution in one client. I want anybody not just a veteran in the Bitcoin or Altcoin community to be able to use and understand vTorrent ecosystem with ease.

Users should not have to go find everything in separate place, such as the need to go look for exchanges to trade VTR for BTC along with ability to deposits and withdrawals and I plan to have all the main exchanges that support VTR build right in the client and not limit to just Bittrex.

Improving current in-client Block-Explorer and design a better encryption system such as implementing google authenticator is also needed and is being work on.

Details on torrent implementation will be released when it is ready.

Thank you for your feedback and support.

Any community member using any version of Mac OSX and willing to help us test the pre-public beta version of the client, feel free to contact me.

@Frigga77 I am sorry to let you down but I am seriously quite bad at GIMP  

Regards

Some updates on vTorrent development progress,

I have been working on vTorrent almost full time recently, adding many new unique features to the client, I just need to work on a few things more and new beta should be ready for public.

Here are some current screenshot,









To all community members, please do not hesitate to throw out some great idea for our upcoming betas.
 
Sorry for the delays and thank you for your support as always.

I may not be one of the best and fastest developer out there but real development work takes time, I am spending a lot of my quality time in both designing and coding the client.

Please understand that I am doing something, and updates will be release when they are ready.

Regards

I am currently working toward improving user friendly side of the client, main idea is to move away from just normal 'wallet' to a client which 'wallet' is just a small part of it. Any ideas from community is always welcome.

Thank you for your support.

I'm testing on Macbook 2.4 Core 2 Duo (Early 2008) as benchmark, there's no crashing just cpu usage fluctuate between 0.8% to 4% which is still a bit too high in my opinion.

Since I already know what might have causes the CPU spike, the next beta should be ready very soon.

Sorry for the delays and thank you for your support.

All the main functions for the in-client trading is completed and being tested.

CPU usage for the new client is rather high due to the real-time market update, I am working on some solution to optimized the client's CPU usage and I will post up a link for the new beta client once it's ready.

Thank you all for your support.

Still no updates on the bugs, but there will be new beta client with in-client trading and some small bugs fixed for all operating system in a few days.

Thank you all for your support.

Please understand that the reason for the delay is mainly due to the bug in client that we have.

I have posted the updates about this just a few days ago.


User pnoch is also working with me on the bug when he is able, in turn I will personally reward him with the same amount that he have lost due to this same bug.



xCash head developer, johnnyxcash is also looking into this issue.

Regards

I haven't been able to be as active as I would want in this thread due to my real-life work.

I am still deciding if I want to make some part of the client closed-source to prevent it from being clone by other projects.

As for the bug problem, I am currently working closely with user pnoch since he is one of the user that affected by the bug and have good knowledge in debugging.

Thank you for your support.

I have been and still working on debugging and try to identify parts of code which might have cause the problem with the encryption and unlock of the client.

In my opinion this bug or issue with the client is quite a serious one since its related to the core security of the client and funds of the users.

I check the thread quite often to check if there is anymore user affected by the bug.

Adding of any new aditional features to the client will be postpone until we could determine and successfully patch the issue.

Thank you all for your support.

It is perfectly 'safe' in using any version of the client as long as you DO NOT encrypted your client or by keeping a working backup of the encrypted client (wallet.dat) before you create any new address every time.

This possible bug with the client is NOT RELATED to hacking of any sort, my best guess and what I am focusing now is that the bug could be related to how the client generate new address in an already encrypted client and possibly in some circumstances affected the wallet.dat file making it impossible to get the client to unlock even with the correct passphrase.

My first priority right now is to try to duplicate the issue and try to find the real cause of the bug.

I have tried to get in touch with xCash developer since their users is apparently also affected by the same 'possible bug' but still haven't heard back from him so far.

Thank you all for understand and support.

Unfortunately, there has been another report from a user (a few hours ago) about a bug in the client which affected users cannot unlock their encrypted client with the correct passphrase.

Since the first report from our user, I have been debugging and researching on the issue. What disturb me the most is that there are also at least two xCash users reported the same issue in their thread (https://bitcointalk.org/index.php?topic=765360.msg9934379#msg9934379)
and the fact that vTorrent is largely based on xCash led to possible conclusion that both currency is affected by the same bug and not specific to our client.

As of now, I still cannot duplicate the issue myself and I am still unsure if this reported issue is a vaid bug, but so far there are 3 vTorrent users contacted me with the same similair issue.

For now, I would recommend all vTorrent users to not only have their wallet.dat backup but also to export a private key and keep in a safe place, in case that the bug is valid users will be able to regain access to their coins by importing exported private key.

Also, it might be best for all users to migrate to unencrypted client for now at least until I can find out more about the issue.

@SaulGray Please contact me through PM.



Next beta client with in-client trading for both Windows and OSX should be release sometime before or around next week.

Thank you all for your support.

Anonymity is not guaranteed with vTorrent.

Please check your PM for details.

Thank you all for your support.

Thanks @Joori for giving your time to help with issue.

@SaulGray It is possible that you will get this message after you run the above command depends on your linux distribution and installation.


If so please try install the missing dependencies with:


I have just tested the procedures with newly created VPS running Ubuntu 14.04 64-bit.

Please leave feedback here or PM me if you still have problem.

Thank you all for your support.

If you still having problem after adding nodes please reply in thread or PM me.



Please check your PM.