Leaderboard

  1. rafi

    rafi

    Established Members


    • Points

      40

    • Content Count

      8,602


  2. garavel

    garavel

    Established Members


    • Points

      24

    • Content Count

      13


  3. techster

    techster

    Moderators


    • Points

      22

    • Content Count

      145


  4. xecutable

    xecutable

    Established Members


    • Points

      17

    • Content Count

      47



Popular Content

Showing content with the highest reputation since 07/29/2020 in all areas

  1. 7 points
    @techster We are going to appreciate some clear information on the update of Exchange system. Would be nice to also know how long we have to wait to see it live. Please provide some information for all the members that waiting to hear from you!
  2. 6 points
    Hello all ! I'am literaly reposting some cool dude material " Posted by u/lpxxfaintxx " Here is what really happening behind the scene. New information! Anyways, let's dive right in. On May 12th, the BTT Speed wallet exchange went down. The announcement was that it was going to be a 2 hour maintenance, but it actually ended up being... more than 2 weeks now. The exchange is still down. On May 12th, the day of the announced maintenance downtime, a new codebase used to facilitate the uTorrent and BT Client's Web API with the BTT exchange protocol was pushed out to all uTorrent 3.5.5 and BT 7.10.5 clients, regardless of whether you used BTT Speed or not. We stumbled across this by accident as we were attempting to reverse engineer some of their code to improve the back-end ourselves out of frustration. All the evidence and code can still be found and examined yourself in the webUI helper update that was pushed out (located in /AppData/Roaming/uTorrent/ folder) The BTT Speed wallet uses VueJS so it's not really code you can hide. You can obfuscate, but it seems that they didn't even attempt that. The Findings: New API Endpoints (lines 2423 - 2456): // GET REQUESTS email: { get: {}, post: {} }, "binance/binance_info": { get: {}, post: { body: String } }, "binance/quote_info": { get: {}, post: { params: { crypto_currency: String, base_currency: String, fiat_currency: String, requested_amount: String, pay_type: String, quote_id: String } } }, "binance/create_transaction": { post: { params: { order_id: String, quote_id: String } } }, "binance/recent_transactions": { get: {} } New VueJS Functions: fetchEmailInfo: { type: Function, default: function () {} }, emailInfo: { type: Object, default: function () { return { email: String, isVerified: Boolean } } }, createAndApproveQuote: { type: Function, default: function () {} }, checkBinanceUserStatus: { type: Function, default: function () {} }, preCheckRedirectUrl: { type: String, default: "" }, bindRedirectUrl: { type: String, default: "" }, fetchBinanceTransactions: { type: Function, default: function () {} }, binanceTransactions: { type: Object, default: function () { return { total: 0, rows: [] } } }, New Vue Data, Compute, and Misc Methods: data: function () { return { cryptoCurrencyStr: "", baseCurrencyStr: "", isValidatorEnabled: !1, step: 1, email: "", emailMessage: "Please check your email inbox to verify.", isEmailInvalid: !1, isLoading: !1, binancePoolInterval: null, redirectTimeout: 5, showTransferSuccessModal: !1, alert: { alertFirstMessage: "", alertSecondMessage: "", type: "", isShow: !1 } } }, computed: { currentBalance: function () { return c.default.formatMicroTokenToLocale(this.inAppBalance, { minimumFractionDigits: 0 }) }, maxTransactionAmount: function () { return this.transactionLimits.max }, minTransactionAmount: function () { return this.transactionLimits.min }, cryptoCurrencyAmount: function () { return c.default.isValidToken(this.cryptoCurrencyStr, "token") ? c.default.convertToMicroToken(this.cryptoCurrencyStr) : 0 }, baseCurrencyAmount: function () { return c.default.isValidToken(this.baseCurrencyStr, "token") ? c.default.convertToMicroToken(this.baseCurrencyStr) : 0 }, localeExchangeRate: function () { return c.default.formatMicroTokenToLocale(1 / this.exchangeRate, { minimumFractionDigits: 0 }) }, ........ } }, created: (l = v(regeneratorRuntime.mark((function e() { return regeneratorRuntime.wrap((function (e) { for (;;) switch (e.prev = e.next) { case 0: this.getInitialData(), this.startPoolBinance(), this.handleGAEvent("QuotePageScreen"); case 3: case "end": return e.stop() } }), e, this) }))), function () { return l.apply(this, arguments) }), destroyed: function () { clearInterval(this.binancePoolInterval) }, methods: { getInitialData: (s = v(regeneratorRuntime.mark((function e() { return regeneratorRuntime.wrap((function (e) { for (;;) switch (e.prev = e.next) { case 0: return this.handleLoading(!0), e.prev = 1, e.next = 4, Promise.all([this.fetchEmailInfo(), this.fetchExchangeRate()]); case 4: return e.next = 6, this.handleFetchBinanceTransactions(); case 6: e.next = 11; break; case 8: e.prev = 8, e.t0 = e.catch(1), this.handleLoading(!1); case 11: this.handleLoading(!1); case 12: case "end": return e.stop() } }), e, this, [ [1, 8] ]) }))), function () { return s.apply(this, arguments) }), startPoolBinance: function () { var e = this; this.binancePoolInterval = setInterval((function () { 1 === e.step && e.fetchExchangeRate() }), 1e4) }, ........ }, goNext: (o = v(regeneratorRuntime.mark((function e() { return regeneratorRuntime.wrap((function (e) { for (;;) switch (e.prev = e.next) { case 0: if (this.thiscryptoCurrencyStr || this.baseCurrencyStr || (this.isValidatorEnabled = !0), !this.isInvalidBaseCurrency) { e.next = 3; break } return e.abrupt("return"); case 3: if (this.handleGAEvent("QuotePageBuyClick"), this.emailInfo.isVerified && this.emailInfo.email) { e.next = 7; break } return this.handleStepChange(2), e.abrupt("return"); case 7: return this.handleLoading(!0), e.next = 10, this.handleCheckBinanceUserStatus(); case 10: if (!this.bindRedirectUrl) { e.next = 13; break } return this.handleLoading(!1), e.abrupt("return"); case 13: return e.next = 15, this.handleCreateAndApproveQuote(3); case 15: case "end": return e.stop() } }), e, this) }))), function () { return o.apply(this, arguments) }), handleStepChange: function (e) { e !== this.step && (this.step = e) }, handleCheckBinanceUserStatus: (i = v(regeneratorRuntime.mark((function e(t) { return regeneratorRuntime.wrap((function (e) { for (;;) switch (e.prev = e.next) { case 0: return e.next = 2, this.checkBinanceUserStatus(this.emailInfo.email, this.isBackendProd); ............... }, handleLoading: function (e) { this.isLoading = e }, handleFetchBinanceTransactions: (r = v(regeneratorRuntime.mark((function e() { return regeneratorRuntime.wrap((function (e) { for (;;) switch (e.prev = e.next) { case 0: if (!this.emailInfo.email) { e.next = 5; break } return this.handleLoading(!0), e.next = 4, this.fetchBinanceTransactions(this.emailInfo.email, this.isBackendProd); } }), e, this) }))), function () { return r.apply(this, arguments) }), closeTransferSuccessModal: function () { this.showTransferSuccessModal = !1 }, New Vue Front-End Components and Helpers: columns: function () { return [{ label: this.$t("Date & Time"), field: "created_time", width: "160px" }, { label: "Pay", field: "requested_amount", type: "number", thClass: "binance-table-th-content-center", tdClass: "binance-table-td-content-center" }, { label: "Receive", field: "obtain_amount", type: "number", formatFn: this.formatAmount, thClass: "binance-table-th-content-center", tdClass: "binance-table-td-content-center" }, { label: "Status", field: "status", width: "100px", thClass: "binance-table-th-content-center", tdClass: "binance-table-td-content-center" }] }, filterCheckedArr: function () { return this.filterArr.filter((function (e) { return e.isChecked })).map((function (e) { return e.name })) } ............................ created: function () { this.checkPreCheckRedirectUrl(), this.handleGAEvent("PaymentPageScreen") }, mounted: function () { this.waitUntillIframeLoaded() }, methods: { checkPreCheckRedirectUrl: function () { this.preCheckRedirectUrl.length }, waitUntillIframeLoaded: function () { var e = this; document.getElementById("binance-iframe").addEventListener("load", (function () { e.handleLoading(!1) })) } } ........................ [e._v("\n You will be redirected to Binance to complete the verification process after " + e._s(e.redirectTimeout) + " sec\n ")])]) : e._e(), e._v(" "), e._e(), e._v(" "), e.showTransferSuccessModal ? n("wallet-buy-success-modal", { attrs: { handleModalCancelClick: e.closeTransferSuccessModal } }) : e._e(), e._v(" "), 1 === e.step ? [n("div", { staticClass: "wallet-buy-step-1" }, [n("bt-card", { staticClass: "exchange-sell-card" }, [n("div", { staticClass: "card-item-grid" }, [n("div", { staticClass: "sub-card" }, [n("div", { staticClass: "title" }, [e._v("PAY")]), e._v(" "), n("div", { staticClass: "balance center" }, [n("bt-select", { attrs: { options: { first: { nativeName: "USD", value: "USD" } } } }, [n("div", { staticClass: "option-selected", attrs: { slot: "option-selected" }, slot: "option-selected" }, [n("div", { staticClass: "text" }, [e._v("\n USD\n ")])])]), e._v(" "), n("bt-input-box", { staticClass: "amount", attrs: { inputType: "crypto", "data-testid": "sell", placeholder: "0.00", message: e.baseCurrencyMessage, showMessage: e.isInvalidBaseCurrency, isInvalid: e.isInvalidBaseCurrency }, on: { input: e.updateCryptoCurrencyStr }, model: { value: e.baseCurrencyStr, callback: function (t) { e.baseCurrencyStr = t }, expression: "baseCurrencyStr" } })], 1)])])]), e._v(" "), n("svg-icon", { staticClass: "arrow-forward-icon", attrs: { icon: "arrow-forward" } }), e._v(" "), n("bt-card", { staticClass: "exchange-buy-card" }, [n("div", { staticClass: "card-item-grid" }, [n("div", { staticClass: "sub-card" }, [n("div", { staticClass: "title" }, [e._v("Estimated Receive")]), e._v(" "), n("div", { staticClass: "balance center" }, [n("div", { staticClass: "buy-btt-box" }, [n("div", { staticClass: "buy-btt-box-top" }, [n("svg-icon", { staticClass: "speed-icon", attrs: { icon: "speed" } }), e._v(" "), n("span", [e._v("BTT in-app")])], 1), e._v(" "), n("div", { staticClass: "buy-btt-box-bottom" }, [n("span", [e._v(e._s(e.currentBalance))])])]), e._v(" "), n("bt-input-box", { staticClass: "amount", attrs: { inputType: "crypto", "data-testid": "buy", placeholder: "0.00" }, on: { input: e.updateBaseCurrencyStr }, model: { value: e.cryptoCurrencyStr, callback: function (t) { e.cryptoCurrencyStr = t }, expression: "cryptoCurrencyStr" } .................. a = [function () { var e = this, t = e.$createElement, n = e._self._c || t; return n("div", { staticClass: "top" }, [n("span", { staticClass: "top-title" }, [e._v("Email Verification")]), e._v(" "), n("span", { staticClass: "content-text" }, [n("p", [e._v("\n To continue, please provide a valid email address. If you already have a Binance account, please use\n the same one.\n ")]), e._v(" "), n("p", [e._v("\n This service is provided in collaboration with\n "), n("a", { attrs: { href: "https://www.binance.com/", target: "_blank" } }, [e._v("Binance")]), e._v(" in accordance with our\n "), n("a", { attrs: { href: "https://www.bittorrent.com/legal/privacy-policy/", target: "_blank" } }, [e._v("Privacy Policy")]), e._v(".\n ")])])]) }] ... and it goes on, with 70 more mentions of "Binance" in the following 60,000 lines of code that follows. Okay, fast forward to more than 2 weeks later. The uTorrent forum, and BTT Speed communities are furious and getting very impatient about the exchange downtime. To understand a bit more, we'll get into how we are able to transfer BTT from uTorrent/BTorrent into our actual wallets. An API request is sent to the Tron network using your wallet and private key (this is done automatically when you make a withdrawal request) The exchange wallet (TA1EHWb1PymZ1qpBNfNj9uTaxd18ubrC7a) then processes the request, and sends real BTT to your wallet on-chain. Since May 12th, the exchange wallet has mostly been empty of BTT, frustrating seeders and not allowing people to withdraw. Yesterday, the exchange wallet was refilled with a considerable amount of BTT, more than the little amounts they filled here and there. If my memory serves correctly, it was around the ballpark of 50-200 million tokens (too lazy to go check atm, but it was enough for the exchange to come back online for a few hours). Of course, I began analysis right away, especially w/ monitoring the API calls being made and network traffic. And sure enough, there was plenty of chatter going back and forth that mentioned Binance. The temporary opening of the exchange was most likely devs doing more testing. I'm not the type to spread baseless FUD or pump-designed news, but I think there's evidence beyond reasonable doubt that an official BTT Speed wallet <> Binance exchange partnership or integration is coming soon. I know there's both a buy and sell function, but I can't speculate further on the exact nature of this direct integration, nor the official announcement date, but all the code and evidence is there. Yesterday's API activity was confirmation that there is indeed an API server out there that is responding to the newly added API calls and functions. So it's not just BTT dev(s) writing non-sense Binance related code into the BTT Speed backend. People also noticed that huge amounts of BTT were being moved to a few wallets, which was highly suspicious. However, it appears that those wallets actually belong to Binance. What's concerning: the initial code was pushed out on the 12th, but the exchange is yet to be back online, not a SINGLE dev has come out and explained why, PR is absolutely silent about the matter and posting memes on Twitter. They posted job listings for BTT Speed devs AFTER the failure to launch within the 2 hour timeframe that they initially announced, and it is clear that they are seriously lacking power in the JS dev department whether in SF or Asia. Something has either 1) gone horribly wrong to the point that they couldn't fix it in almost 3 weeks now, 2) the Binance integration isn't going as planned, and they are re-thinking the exchange protocol; 3) I don't fucking know. What's promising: although it seems that there is no activity going on in the world of BTT Speed, it is clear that they are up to something, though normal every day people don't get to see it because it's hidden in (a bit shitty) code. Nonetheless, a direct uTorrent/BitTorrent client <> Binance integration would be definitely be something that would propel the BTT ecosystem in the long-term. Closing thoughts: I'm sorry for waiting all this time to share this with you guys, but I thought everyone could use a little bit of good news. Tron is in so many projects right now I don't blame Justin for not making BTT a priority, but it would be an insult to all the OG uTorrent and BT protocol developers that worked tirelessly on what we can call one of the first "decentralized" networks if he just let it die out. They had two years to make improvements to the BT clients, as well as the BTT protocol, but there was been literally almost no changes, improvements, or upgrades in nearly 3 years since BitTorrent was acquired by Tron. Integration with Binance is great, but I want to see the protocol improve, because right now it's a mess. Hopefully this extremely prolonged downtime and the thousands of complaints pouring in is a wake up call to them. Let's keep pushing the team to work hard. Both on BTT Speed and BTFS.
  3. 5 points
    @techster When will the exchange be working again? We cant whitdraw from in-app to on-chain. We have 2 months waiting for a clear answer. Please check this post:
  4. 4 points
    Done, LAA flag added...
  5. 4 points
    Thanks for the update @techster! Appreciate it, and I'm sure most of us with some level of comprehension of how tricky and difficult it is to pioneer a new protocol appreciates it too... to some degree. I'm sure you guys are hard at work and it must be stressful to be bombarded with all the posts and complaints. I've dealt with many tech (both crypto and non-crypto) communities in the past (ranging from small 3K member dev communities to full fledged 150K member forums filled with boneheads to legit geniuses), and I want to help you by offering a universal truth: the more informative and specific the updates are, the less questions asked and less people bothering you. Not to mention the immense confidence that will be instilled within the community. Example update (this is completely pulled out of my ass, just used as a reference): Hey guys, we apologize for the prolonged downtime. The exchange hasn't been fully enabled yet, but we did do some testing over the weekend. We made some changes to: 1) Point / feature / explanation 2) Point / feature / explanation 3) Point / feature / explanation We are now analyzing the data, which could take 12 to 24 hours due to the nature of the protocol and its occasional delay in actual payments which are caused by X, Y, Z. We are looking to fix that in the future as well, but for now we are focused on analyzing the preliminary data before re-launching the exchange, which takes lots of movements of BTT and can get bit hectic. So before we re-launch, we want to be sure of our data analysis so we don't have to go offline again, which will cause even more delays. I will post an update as soon as we are confident with the data analysis, and we will then begin relaunching the exchange service! If it ends up taking longer than 24 hours, then please understand that we are doing this to make the entire BTT Speed ecosystem a much better experience for you and hopefully it won't take longer than another 48-72 hours to re-calibrate X, Y, Z. Team at BTT sincerely hopes that you understand, and let's create a much stronger system! Trust me, it'll help you a LOT with frustrated users and it will instill a LOT more faith in BTT. Vague answers, especially in crypto, are not the way to go. Sincerely, A nobody that's been a marketing and community consultant for projects like Matic, Chromia, Horizen, MetaHash, Harmony, and several top 50 coins that I can't say due to NDA On a more serious note, if you do need help with these kinds of things, I'm just a PM away.
  6. 4 points
    The teams are working hard on relaunching the updated service. Unfortunately it takes them more time than expected. We are sorry for the inconvenience.
  7. 3 points
    nice post! sadly, nobody will come and challenge your statements: this forum has been dead since last May
  8. 3 points
    Scam project, while Sun tweeting how he spent millions on nft shit arts, shitcoin btt down in price and devs of speed more than month couldn't make anything. No support, no dates, no nothing. Fuck you all, I can't wait for the day when all the investors will finally see that Justin Sun is a common crook.
  9. 3 points
    if you mean that "24th", I suspect it might be the issue number previous one was 23th
  10. 3 points
    Sir, We know maintenance can take weeks or months as bugs are the real issue.. but if you can give a date.. that wll keep us hopeful..
  11. 3 points
    It's been some days already! Will you log in and provide us with some information? It looking not serious from your side. I think that will be fair to tell us a real date that the payment system will work finaly!
  12. 3 points
    I think is a problem with the BTT / Tron Network, normaly I receive in my on-chain wallet the BTT transfers from this TRON address: TA1EHWb1PymZ1qpBNfNj9uTaxd18ubrC7a but if you check with Tronscan the account don't have available BTT balance to make the transfers: https://tronscan.io/#/address/TA1EHWb1PymZ1qpBNfNj9uTaxd18ubrC7a Maybe the problem is related to the weekend Cold storage movements see this note :
  13. 3 points
    why is there such a difference between earnings and in app credit ? And why are BTT deducted even though I have disabled the option ? It is very frustrating. I've been seeding for 2 weeks to earn ~1000 BTT and every now and then 100-200 BTT are suddenly gone. Image
  14. 2 points
    It's been 56 days and it's still not working. How long do I have to wait patiently? I also want to know if you are testing the upgraded version of Exchange.
  15. 2 points
    Speed is a dwarf compared to the 2nd biggest decentralized storage space platform. Which against begs the question, who are these thousands of people who rent for free and have been renting for free for the past 2 months.
  16. 2 points
    If you do not see, this project is thrown to the trash ... Seed if you want to help the community but throw away all your hope to try to get out the earnings via so called - BTT SPEED. Proof for my words - go check the last 2 weekly reports - not a single fucking word for BTT SPEED. Says enough from TRON
  17. 2 points
    And yet they claim they have more BTFS nodes than ever. Who the hell keeps renting out space for non-tradable tokens.
  18. 2 points
    Justin Sun is more into BTFS scamm nowadays, if you check Bittorrent's Medium and Twitter you will see that they don't give a fuck about Bittorrent Speed....
  19. 2 points
  20. 2 points
    All requests should be accompanied by a static-sustainable link to the build...
  21. 2 points
    The only result of the new version is a total downgrade of earnings. Before I earned 8 - 20k per day, and now 300 BTT max. Same settings, same number of torrents, same BTT connected users. Thank you, Justin Sun!
  22. 2 points
    they fucked up really big and those "btt community" reddit guys dont even know what is happening for real
  23. 2 points
    Somehow my wallet stoped working .... Tried like 33 times to reimprot it - stuck on loading screen .... this project is just garbage .... Good look folks P.S - i managed to import my wallet and guess what - i had 4.5k BTT on pending which are now gone. No history transactions, cant even prove that i made this try to transact .... Absolute disgrace and a spit in the face for all involved in this trash project
  24. 2 points
    Hello ! Since last 72 hours we have withdraw problems. When we move our earnings from IN APP Balance to On Chain Balance coins go to pending. After we stop utorrent / bittorrent client or just kill the process from taks manager and then we start it again the same coins that goes to pending are going back to our IN APP Balance. It's happening to me and all my friends to each of our computes / accouts / wallets. We have earnings more than enough on each client but they are all going on pending and in best scenarion after that are going back to IN APP balance and worst scenario just get stuck on pending. Is anything happening with the network at the moment ? ( any updates or something that may be the problem ) Should we wait for this to be fixed or ? ? Please provide some information about this problem. Its kinda frustrating because gathering works fine / wallet loads fine , but we can not move from in app to on chain !!! Thanks in advance.
  25. 2 points
    WoW. If you seed torrents just for the sole reason to earn some BTT - then the smart choice is to stop. Withdrawal of tokens is currently disabled, there isn't any official info since 18th of March and price is constantly dropping. There is some actual code push, that looks like Binance integration on the way. However there isn't any clear indicator that it will work properly or work at all in the end. So if you seed only to earn some BTT, it's better to stop your clients from running, at least until they enable the exchange service and transfers to on-chain. As far as I could dig into the code, there isn't anything unusual about it - however that doesn't guarantee that those few lines of code will ever be integrated and released, it could just be some automatic order generation to dump their tokens onto BTT/BNB pair on Binance. - This is just speculation tho' I'm not putting my head on the table. I'm still seeding, however the option for Speed Initialization is turned off. Where I'm from torrents are widely popular - so there is always Need for Seed. I seed for the benefit of others. BTT earnings were just nice bonus for my effort. This ain't the case anymore but whatever.
  26. 2 points
    Justin Sun wrote that he will complete the "TRC20" integration on June 10, maybe we are very close to the end. I do not know
  27. 2 points
    There's a reason why you see them Binance addresses. But it's not what you think. I hope they just announce it already.
  28. 2 points
    They added 30.000.000 Btt but has been emptied in 1 hour and 30 minute.... i think is normal.. as lots of people were waiting Managed to withdraw 66k BTT:) Evidence: https://tronscan.org/#/transaction/b19c3111f78a53960e0df3a24eea7da5974ee4067d94bb7f107bb672b1a6e528 Here is the 30 mil transaction... to the exchange
  29. 2 points
    Hi, has anyone actually have a solution to this problem? Customer service did respond twice, first time did not address the issue at all and the 2nd time somewhat addressed it but the solution of closing the client and deleting the helper file did not correct the issue. I have 2 PCs, one I can access my BitTorrent Speed dashboard/wallet with ease but my main PC that had a lot of earned BTT I lost access with this exact 'port error' issue once I sent to BTT - on chain. I have my private key and seed words but I cannot access my wallet page. It is extremely frustrating there is no direct login access like all other wallets. I also tried linking with my private key as suggest through Tronlink, I get access but it is for TRX which does not make sense. There has to be a way to access my wallet...... HELP? If an actual BTT tech is monitoring this forum, can you please email me directly to resolve this issue.
  30. 2 points
    For what? They've been copy pasting the same thing for 2 weeks now. This is why "a several days" sounds outdated because this has been the message from the first few days. It's so impersonal and disrespectful that you are not worth 15s of their time, for a simple message...
  31. 2 points
    Hi there! 404 page (AKA "Oops!" page) usually appears when Windows cannot assign a free port to the application. We are working on a solution with Microsoft.
  32. 2 points
    I call your fake news bs....
  33. 2 points
    Exchange is still down but the page upgraded from UI 1.9.4 to UI 1.9.5 don't know if you guys noticed
  34. 2 points
    similar happened to me. Does not motivate one to keep seeding....
  35. 2 points
    The maintenance will take more time to be complete. Please expect a different announcement when it's up again. Sorry for the inconvenience.
  36. 2 points
    Since there are a lot of threads around here asking the same thing over and over, I've decided to shed some light to what is and what isn't. Over the last month and a half I've made around 278,000 BTTs seeding. Via trial and error and/or reading the white paper I've found out a bit of info. First and foremost nevermind the Total Earnings number since it's just a projection. Your in-app balance is what counts. Second some of the transactions can take up to 24hours so it's not uncommon to see crazy upload speeds and suspect someone is spending BTT but to NOT see anything. Third amount of seeded GBs TBs makes no difference, you are being paid BTT when someone bids on a part of a torrent you are offering, so nvm those stats as well. As a tip, keep your upload slots low. With that being said here's a picture of part of my wallet transactions: For anyone who wants to further verify I'm not making stuff up :https://tronscan.org/#/address/TAaFMoCD7VU19gMd86aJGfEy4xKbBkbKA9/transfers set the IN transfers. These are all from seeding. Now according to @techster the demand for BTT went up at current price 0.007 and that's why the average earning are down. However this make no sense as you can see the picture above 54k , 9.7k 2.5k etc etc are around 21st of April. Look at the volume and price and from the graphs identify an uprising demand? And btw the Asian market is fine. Seedboxes towards the asian market still have decent earnings the EU/US are down to almost 0. I guess that's how averages work eh? To be honest, I'm not angry or annoyed at this, but I dislike not being told things the way they are. Tell us something that makes sense, tell us YES WE REDUCED THE INITIAL BID to 10 times less of what it was, tell us that everyone's option of SPEND BTT is now OFF, anything that actually makes sense. But don't tell us yes this is normal, cause of demand you went from roughly 9k BTT a day to 1K a week cause that's how average works. With the On/Off switch coming 'soon' but it's been now 10 days, these types of nonsense anomalies and the speed of which we get a reply, I highly doubt this project will ever take off the way it was meant to be. I mean the white paper talked about setting bid amounts after the 'initial phase'. Two years later we are still in initial phase I guess , as these options haven't hit us. Next time when you want the community to participate in your projects at least be opened up. And stop acting as an audience and keep telling us you are not the middle man. Yes it's a free market, yes it's a p2p, but in the same time your app caused many to burn BTTs with the option OFF and the same APP can cause tons of other issues like small to none-existing earnings. Update: May 11th 2021: A colleague and I ran a few experiments. One file around 40 MB hosted on an Asian seedbox, me the leecher with around 700 BTT in my wallet. According to the white paper the bid formula is: bid = (spending rate × remaining balance in BTT)/(remaining download in kilobytes). The first 2 tests were consistent both time I've got charged ~ 5 BTT. The next 2 tests were done on an EU seedbox, once through an Asian VPN and once with just like that. Keep in mind same file, nearly the same BTT in my wallet. I've got charged 75 BTT while downloading from the Seedbox through the Asian VPN, and 0.3 BTT for EU to EU. Somehow an EU bid is worth 250 times less for the same identical file with an identical amount of BTT in it. Ran it twice more the same results. What are we missing ? Why is there such a huge difference over the spawn of 3-4 minutes, on the same file, from the same seeder/leecher, with the same amount of BTT in wallet, with the only difference geographic locations changed through VPN?
  37. 2 points
    Anything expected to be reworked/fixed today ?
  38. 2 points
    uTorrent v3.5.5 build 46010 stable http://llsw.download3.utorrent.com/3.5.5/utorrent.46010.installer.exe
  39. 2 points
    Yep. We are working on it. Thanks for the report.
  40. 2 points
    http://llsw.download3.utorrent.com/3.5.5/utorrent.46006.installer.exe or http://ll.download3.utorrent.com/latest/uTorrent.exe
  41. 2 points
    3.5.5 build 46006 LAA (stable) version is available (links also @ my sig)
  42. 2 points
    Hello there! The Speed Exchange services are down for a few days for maintenance. We are going to test and deliver an upgraded version of the Exchange soon to help our users solve existing transfer issues. Thank you for your patience!
  43. 2 points
    Stable. LAA hosts updated...
  44. 2 points
    Yeah, that's why you want to use the 2 mb size version without the wrapper-installer. Just rename the small guy to utorrent.exe and overwrite the old with the new and launch it directly from its normal location [%appdata%\utorrent], it'll self-update with no fuss at all. If you launch the small guy from another location it will redo its [minimal] install , asking a few questions before overwriting itself, and you might loose a few settings but not many, it preserves your setup. But it's easiest to just overwrite it yourself and avoiding any sort of install at all. BTW, to find the small guy inside of large one, open the large one with 7zip; you'll see within a file called "carrier.exe", that's the small guy, everything else is "the installer" crap, which often offers up shareware...just extract carrier.exe, rename to utorrent.exe and do the overwrite - voila...you're updated...with all your settings intact [important if you turned off all the ads.] I've been overwritting for years and never once seen an ad or any shareware... Always look for the 2 mb size, or extract it yourself from the 4mb wrapper...
  45. 1 point
  46. 1 point
    Known issue - it is false positive. Please ignore defender message.
  47. 1 point
    You have a *good* A/V program, it checks for invalid signatures...
  48. 1 point
    Sorry for the inconvenience. Unfortunately it's hard to say what is the reason of this problem due to a unique combination of Operating System's settings, protection tools, and other 3rd party applications installed on each user's computer. We can only recommend the following. Please follow the instructions below: Backup your wallet Log in to the wallet Click on Recovery Information Provide your password Click on Reveal Save the Recovery Phrase and the Private Key in a safe place Never share this information with strangers Windows users: Stop your torrent clients that use Speed from running Check and stop uTorrent/BitTorrent processes from Task Manager Open File Explorer and type in %AppData% You may need to go one level up until you get to AppData > Local Find BitTorrent Helper folder and delete it Launch your torrent client Get to Speed and walk through welcome screens again Get to the point where you are offered to Import your wallet Click on Import Use previously-stored Recovery Phrase or the Private Key to import your wallet In a few seconds, your balances should be restored Mac users: Stop your torrent clients that use Speed from running Launch Finder Push combination: CMD + Shift + “.” You should start seeing hidden files Navigate to Users > “your user name” > Library > Application Support > BitTorrent OR BitTorrent Web Find BitTorrent Helper folder and delete it Launch your torrent client Get to Speed and walk through welcome screens again Get to the point where you are offered to Import your wallet Click on Import Use previously-stored Recovery Phrase or the Private Key to import your wallet In a few seconds, your balances should be restored Please, let us know if anything wasn’t fixed.
  49. 1 point
    There have been a new beta + stable after that... RTF[Thread]...
  50. 1 point
    I would not say it is "abandoned" but it would be nice if the developers / programmers would acknowledge the problems.. and ask for more details about the problem so they can fix it. I used to be a super programmer myself (I gave it up because I got very little appreciation for my efforts financially or otherwise). It is extremely difficult to fix bugs in software, especially if the code was written in a cryptic coding language such as C++. It is usually easier to write new code from scratch rather than try to debug existing code. This is not only true about trying to debug someone ELSE'S code, but even trying to debug one's OWN code (probably because one is not likely to find their OWN mistakes).