boboev

Established Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

5 Neutral

About boboev

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I strongly doubt it that techster misjudges or misinterprets the situation. He is quite an insider, so probably what he writes is true. However, this does not exclude two possibilities: 1. Speed Increase toggling ON all by itself - a known bug that may lead many or all of your BTT being spent; 2. Some other bug that may be not known to date. So, the best practice would be to attach the wallet.log file toghether with the screenshots, so that the support can better see what has actually happened. It is really strange what I can see from your screenshots but all I know is that currently the entire visualization of Speed is all messed up, this is why they're working on a better UI.
  2. @Katranov is really being rude modern where you come from? Because in the normal world aggression doesn't earn you much good (pun intended). So, blaming techster that he has responded uselessly is just ridiculous. He has explained many times, and very patiently, to numerous ppl asking the same question. Yes, there are bugs, there are parts of BTT Speed's user interface that are misleading and not very well thought of but that's how all gets better - by evolving. Sometimes Speed Increase really toggles on by itself, other times it is turned off, yet you spend btt when downloading, yes, we know it, techster knows it, the devs know it. This is why they are trying to make it better. The fact that your friends have earned more BTT with fewer seeded torrrents is just normal. The fact that you find this unfair means that you haven't actually tried to read how this thing works at all. Just take some time and read the second pinned post here, and probably BTTs Lite paper. It will shed some light.
  3. Привет, у меня руский очень плохой, поэтому я буду по английском ответит. Just see the port number in the url up there in the address bar of your browser and write it down. Then paste this in the address bar: http://127.0.0.1:XXXXX/gui/index.html?port=XXXXX where in place of the XXXXX put the port number you've previously written down. It should work.
  4. These are two separate things - one is the technical issue that the dev team has been struggling with for I think more than a week now, and the second is your earnings. There is no STRUGGLE for BTT earning - it is all a matter of bidding. You cannot control who will leech what, how many people will do it and how often they will do it. For sure there are several right things to do in order to have a better chance of earning more BTT - seed 24/7, limit the number of possible connections to a single torrent, use trackers within the same geo location (there have been some observations in a topic here, I haven't peer reviewed them, just saying), choose highly leeched but poorly seeded torrents, so that you have a better chance to get some BTT. Basically that's it. Earning BTT is not mining in the sense of predictable yield, proportional to the input investment. Imagine it as an open market where your price and your speed may or may not be attractive to the potential leechers. So, yes, we all agree that there is a need for a better and less confusing UI, which will lead to a better UX and fewer frustrated users, but as far as I have followed this forum, it has been announced already that a better version of Speed is already in the works. So, once again - we can press and demand for a good, functional, clear and comprehensive software and network from the Tron devs but it is really important to know how earning BTT through torrent seeding or BTFS storage sharing works before raising claims.
  5. Aaand have you read the pinned posts before writing? Is it really that hard? It seems so, actually. Just look at the latest 15 topics - ALL of them are about one and the same problem. And this exact problem has been explained in the uppermost pinned topic. THERE'S A MAINTENANCE GOING ON. THERE ARE OBVIOUSLY SOME ISSUES AND IT TAKSE MORE TIME THAN INITIALLY EXPECTED. It just happens in software world. Now, just stop moaning and whining and just wait for updates. Flooding the forum with carbon copies of your distress will not speed up the process.
  6. Not so far. Just be patient. I personally think that the fact they're working on it for so long, could mean that finally we are about to experience a much better Speed.
  7. Reading before writing helps minimize random posts that bring nothing to the community, mind you . Just three posts up you can clearly see that techster has already announced that maintenance will take longer and that a new announcement will follow.
  8. Just be patient, @techster has already explained that the maintenance will take longer and there will be an additional message when it's over and we can transfer BTTs again.
  9. They will return, don't worry. It may take some time but they will.
  10. Thanks, @techster, I believe that would explain the failing transfers since yesterday. So we are waiting for something better on the other end of the blackout, I hope
  11. Writing here as well. For some reason both in Speed and in BTFS all transactions fail since around 11/05 9:00 UTC, that is about 24 hours at the moment of writing this. It has been tested and peer-confirmed around 20 times since yesterday. This means it is something central. We are waiting for somebody to explain the situation.
  12. @techster, do you know why we are experiencing the same problem since yesterday? No transfer goes from in-app to on-chain, neither in BTT Speed, nor in BTFS. Strangely, none of the in-app amounts are actually visible in tronscan.org Normally any amount of BTT that appears in-app should be seen as an incoming transaction on tronscan. It seems like something has broken down big time. Any light on this will be highly appreciated. Thanks!
  13. This will not help. For more than 24 hours all transfers from in-app to on-chain both in Speed and BTFS fail.
  14. IT happened to me today as well. Probably the transfer from in-app to on-chain has been suspended again like it has been a couple of weeks ago. Maybe we should ask @techster?
  15. @lavski, I think I have found a temporary solution. When you get this error message, just copy the port number from the URL - it should be a five-digit number between 50 000 and 60 000. Then open a new tab and type in: http://127.0.0.1:XXXXX/gui/index.html?port=XXXXX Paste your copied port number in the place of the XXXXX at both places and hit Enter. It should let you in the Speed wallet. Bookmark this address and don't open Speed through the in-app button in BitTorrent Speed. Let me know if it has worked for you.