Hello sir. How are you? I hope all is well. I was trying to set 2fa again and I deleted my previous 2fa all by mistake and now I cannot sign in to my private wallet again. Could you please help recover it? Thank you so much. Is there any way I can do it? I really cannot log into it now!!! Please please help me
Sincerely yours, amis
Dear amis5818, Please contact us further on PM to see what we can do to help. Regards, vTorrent |
|
|
|
|
Dear all,
Just to clarify, we are NOT in any way related to 'torrentchain' or any other ICO projects.
Regards,
vTorrent
|
|
|
|
|
Dear all,
This project is indeed still being actively developed.
Due to nature of BitTorrent sharing, we have been experimenting with the possibility of migrating ZEC's zero-knowledge to VTR core to improve users anonymity and try to do without needing of reseting the current chain.
vTorrent 0.9.1z will be the first version to incorporate the zero-knowledge protocol and if resetting the chain is needed, there could possibly be a fork of vTorrent-Classic running by community keeping the 0.8.x chain.
There are some other plan along with this new chain, which is still being in discussion in our team.
Regards,
vTorrent
|
|
|
|
Torrent creator is making his own crypto currency now, VTR needs to get a wriggle on, first mover status is fast disappearing.
I read that he's going to create a new currency, I haven't heard that it will have anything to do with torrents. Also, he's going to finish up some stuff on Bittorrent first. IPFS is the future. Torrents are network identifiers rather than file identifiers. Unique file hashing and retrieval is the future and we are pioneers Please DO NOT post anything unrelated to VTR in this thread. |
|
|
|
|
Dear all,
Our developer team have absolutely no relationship with "vtorrent.info"
However, we are happy to work with the owner of that website to have them publish the accurate and up-to-date information of our project progress.
Regards,
vTorrent
|
|
|
|
Looking to create a bounty for Key Management (HD Wallet back-up) video. Anyone interested? I have already asked @e1ghtspace and waiting for his reply.
Dear coins101, You might want to wait a little for the new wallet for that. It is somewhat different from client version 0.8.1. Regards, vTorrent |
|
|
|
|
Dear all,
Before our project can move on to the next step, we need to ensure that our client will be completely scalable and stable from its core.
Please report if you are holding significant amount of VTR and experiencing low usability (client freezes) and if there is any improvement after block 1,300,000.
Regards,
vTorrent
|
|
|
|
Dear all, No, there is nothing to worry about. BUT If anybody encounter any problems or issues related to this bug please reply in thread and PM me with logs. Regards, vTorrent |
|
|
|
Feature request. Please add Riot chat into the vTorrent road map. As a pop out module, like BitTorrent and Trading tabs. Riot is intended to run on decentralised networks and it is open source. Matrix is the OS and Riot is an app that sits on Matrix. https://github.com/vector-imhttps://matrix.org/docs/spec/With Riot enabled, vTorrent will have its own BitTorrent forum, built in. You can then have channels on discussions to do with anything, but most importantly it can be the home of all private trackers. Dear all, Thanks to coins101 and community for support and suggestions. Riot chat will be implement natively to vTorrent soon, please PM me if anyone wants to help out testing the Riot chat and I will send out beta wallet with Riot enabled as soon as it is ready. Regards, vTorrent |
|
|
|
|
Dear all,
We have been monitoring the network and working with Bittrex to make sure there will be no issues and no coins will be lost during the hardfork.
I am pleased to inform you all that everything went smoothly and we have successfully switched the vTorrent network from Protocol v1 (80014 in 0.7.x) to v2 (80016 in 0.8.x) that took place on block 1,200,000.
As promised, new client with major upgrades is coming soon, it is still being worked on since there are some thread-related bugs causing the client to crash on certain conditions.
Regards,
vTorrent
|
|
|
|
|
Dear all,
Today, marks the second anniversary of our vTorrent project!
To this date, not only our project development still going strong, our Community continues to grow as well.
Innovation projects are said to fail 90% of the time, but I strongly believe in an importance of a solid foundations to be vital for the success of any projects.
To celebrate the annual anniversary, a major new version of the client that incorporated many new features will be released to public in about 2 weeks.
Specifically thanks to all of those strong supporters of our project.
Regards,
vTorrent
|
|
|
|
Dear all, For anyone still having problem with syncing or client have 0 peer, please follow steps as follow: 1. Create new text document with following content addnode=vtrseed.cloudns.asia
2. Save it as vTorrent.conf then move/copy it according to your operating system For Windows: The file AppData folder is hidden by default so make sure to enable viewing hidden files.
Windows drive (C:) -> Users -> $YOURUSERNAME -> AppData -> Roaming -> vTorrent-HD
For Mac: ~/Library/Application Support/vTorrent-HD/
There is no need to add more nodes since vtrseed.cloudns.asia is a crawler for our vTorrent network, which should able to provide list of reliable nodes by itself. It is also hardcoded since 0.8.1.1b and all soon to be released clients. DEV_MP:~ VTR_DEV08$ dig vtrseed.cloudns.asia
; <<>> DiG 9.8.3-P1 <<>> vtrseed.cloudns.asia
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50502
;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;vtrseed.cloudns.asia. IN A
;; ANSWER SECTION:
vtrseed.cloudns.asia. 3599 IN A 188.134.72.213
vtrseed.cloudns.asia. 3599 IN A 2.49.36.96
vtrseed.cloudns.asia. 3599 IN A 125.25.151.80
vtrseed.cloudns.asia. 3599 IN A 82.13.65.164
vtrseed.cloudns.asia. 3599 IN A 119.81.64.88
vtrseed.cloudns.asia. 3599 IN A 45.55.197.64
vtrseed.cloudns.asia. 3599 IN A 95.136.101.80
vtrseed.cloudns.asia. 3599 IN A 52.88.132.97
vtrseed.cloudns.asia. 3599 IN A 94.68.28.146
vtrseed.cloudns.asia. 3599 IN A 40.112.149.192
vtrseed.cloudns.asia. 3599 IN A 85.24.143.58
vtrseed.cloudns.asia. 3599 IN A 104.251.219.196
vtrseed.cloudns.asia. 3599 IN A 144.76.64.49
vtrseed.cloudns.asia. 3599 IN A 94.38.142.224
vtrseed.cloudns.asia. 3599 IN A 82.39.101.246
vtrseed.cloudns.asia. 3599 IN A 108.70.73.83
;; Query time: 284 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Dec 1 0:33:15 2016
;; MSG SIZE rcvd: 294
Regards, vTorrent |
|
|
|
Will the wallet be integrated with TOR like Shadowcash?
Dear rhinomonkey, Yes, vTorrent client will be compatible with both standard IP and TOR connectivity. Our next wallet release will bring our core wallet to match Shadow and more. Regards, vTorrent |
|
|
|
I like the idea of some instructional videos but can I please request the following from dev at some point: - Inbuilt data folder selection (some crypto projects offer this; as usually primary disk nowadays is an SSD and loading blockchain on a fast drive simply doesn't make sense and using shortcut cvars and bullshit to accomplish this is always confusing and time consuming)
Dear ik_do, Thank you for your suggestion, inbuilt data folder selection will be include in the next few releases (if not this coming release). if anyone have any suggestion especially on torrent implementation please do not hesitate to share it here or PM. Regards, vTorrent * People hate ads and bundled software because they bloat the experience. Nice light clients. * Protect seeders income. A way to prevent the race to zero fees because everyone copies a seed and charges a little less each time it gets copied. * Option to pay rights holders, perhpas through some way to avoid a race to zero seeders fees. * Small % take to pay a devs fund * First seeder gets a cut from those who copy and charge for a seed. So it's like MLM fees structure where a seeder becomes top of a pyramid. Perhpas the first seeder is a movie company. * Market for links, VPN service, etc. I think adding the market will be something for later next year once it's tested and bugs fixed. * I2p * ZEC anonymity tech * Group chat * Vlc media support * FileZilla FTP built in (maybe through some options to add your own plugins) * Something like the features in qBittorent would be cool. http://www.techradar.com/news/software/applications/best-torrent-client-8-we-recommend-1169584* 100% Chinese translation version, running off VTR token. Dear coins101, Thanks, some of these ideas are already being worked on and I will make sure to give each of your idea a good look. In other news, as ik_do requested, inbuilt data folder selection is already implemented and new beta client will be giving out to our core beta tester soon.  Regards, vTorrent |
|
|
|
I like the idea of some instructional videos but can I please request the following from dev at some point: - Inbuilt data folder selection (some crypto projects offer this; as usually primary disk nowadays is an SSD and loading blockchain on a fast drive simply doesn't make sense and using shortcut cvars and bullshit to accomplish this is always confusing and time consuming)
Dear ik_do, Thank you for your suggestion, inbuilt data folder selection will be include in the next few releases (if not this coming release). if anyone have any suggestion especially on torrent implementation please do not hesitate to share it here or PM. Regards, vTorrent |
|
|
|
Dear all, For more up-to-date available nodes, please check out
http://vtr.thechains.com/networkAs this block-explorer is still in early-development, responses may be slower than usual and please expect a bit of downtime as we will be running some testing and adding new module to the site. @ coins101, Thanks for your contribution for the community. Regards, vTorrent |
|
|
|
@dev First time in over a year that I've had any issues with the chain being behind by a few hours. Dear all, We are currently having some issue with our network, the problems lies within the way new client stakes, which isn't exactly a bug as it was actually designed to help reduce CPU usage and keep CPU cycles for other part of the client. Once we reached our next hardfork this staking problem should be solved by itself, but until then I am also working on a fix and actually anybody with decent coin weight should be able to move the block forward by staking. In other news, our own block-explorer is being tested and is catching up to the current block, if anybody interested please check it out at following address http://vtr.thechains.comOur block-explorer now maybe giving slow response as it is still on development server but it will be much better once we move to production server later on. Sorry for any inconvenience caused. Regards, vTorrent |
|
|
|
Dear all, vTorrent 0.8.1.1 released has been updated with instructions for 2FA in RPC calls What's NewThis release brings an update to daemon side of 2FA, as well as some other minor fixes. -Version bumped to 0.8.1.1 to indicate a new minor release -2FA fully implemented in daemon Instructions:To Encrypt Client“encryptwallet <passphrase> [otaenable]”
$ vTorrentd encryptwallet SuPer$tr0ngPa$$phra$E true
{
"The wallet encryption succesfully changed." : "Authenticator secret: KRNEORSRKNIE2N2Y"
}
"walletpassphrase <passphrase> <otpcode> <timeout> [stakingonly]”
$ vTorrentd walletpassphrase SuPer$tr0ngPa$$phra$E 381342 9999999 false
"walletpassphrase <passphrase> <otpcode> <timeout> [stakingonly]”
$ vTorrentd walletpassphrase SuPer$tr0ngPa$$phra$E ANY 9999999 true
“walletpassphrasechange <oldpassphrase> <newpassphrase> <oldotpcode> [otaenable]”
$ vTorrentd walletpassphrasechange SuPer$tr0ngPa$$phra$E SuPer$tr0ngPa$$phra$EnEW 453609 true
{
"The wallet encryption succesfully changed." : "Authenticator secret: HFIVASKHG5AUSQSG"
}
** 2FA Authenticator secret will be renewed every time there are changes to the client encryption. Troubleshooting$ vTorrentd walletpassphrase SuPer$tr0ngPa$$phra$E 112494 9999999 false
error: {"code":-14,"message":"Error: The wallet passphrase or authenticator code entered was incorrect."}
** If you are unable to unlock your client with correct passphrase, please check your time to make sure it is synced up. Scheduled hard-fork:-Posv2 at Block 1200000 -Posv3 at Block 1300000 Bug fixes:-Messages crashes problems MD5 Checksum:vTorrent-0.8.1.1-Win.zip - cb71216854d3c7e3385463f32078bff2
vTorrent-0.8.1.1-OSX.dmg - edd9bca9c41cbcb3242e00287ccd14b3
vTorrentd-0.8.1.1-OSX.zip - 6518e0edcb42c7a76c4ec237af54f2e4 Regards, vTorrent |
|
|
|
Let me just check what's going on...
Data is not going to be stored on the VTR network? The BitTorrent network is going to carry on doing what it does. This pricing structure is just a way to quantify the charge / bandwidth, not charge / storage space on the chain.
Yes I think it should be fairly known that it would be impossible to store actual 'data' on the VTR network, rather only a record of it. My point is that if a transaction is made every time a 512KB "piece size" is sent then if, say, 100TB is transferred within a day (in the scope of the larger picture of the torrent network this is nothing) then it would result in 195,312,500 "piece sizes". I'd say we set our eyes towards 100TB/day as the gold standard at this moment in development (or even 10TB/day) and if things progressed beyond that then adapt accordingly. How exactly that equates to VTR's blockchain is unknown at this point, but if it indeed resulted in that many transactions that would be a whole lot of bloat/data for the VTR blockchain to handle. I just want to imagine a project in which we are not envisioning 1TB/day (1.3 million "piece sizes") but rather looking far beyond that. Is there a set of options that vtorrent (dev) would like us to consider as opposed to 512 kb "piece sizes" (as per your post)? i.e. I think the reality is that any torrent with a file size of ~1-100MB is a unique scenario where seeding probably isn't a big deal, but for your bigger torrents what should this so-called "piece size" be determined as? Having a transaction on VTR network everytime when a block of 512K is transferred is indeed a big load on the network, and also the size of a VTR blocks will be really big (as each block should contain too many transactions in this case). Maybe those "pieces" should not be fixed in size, but be of different sizes depending on the size of the specific shared content (fixed for every torrent file - bigger for big torrents, smaller for small torrents)..? 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 |
|
|
|
|
Show Posts
