Gaurav_IO @GauravTdhinait Twitter profile

Last Seen Profiles

@Matheus_gk01

@james_ajama

@anowyouu

@EricDHatfield

@MissLacyLennon

@dyh_s56333

@Dvzie

@nxck180599

@jenreadlynn

@Alexa13921092

@NaPitit

@missomeretta

@Rom_Munegu

@VUMCHospitalMed

@PE_SPORTS_

@whipcream2241

@genv

@magireco

@makiraanai_

@KatariyaPran

@setan147123

@ChenchiraSomko1

@hudasweety1

@TheIronHorse7

@Ro_Kolar

@nikocoliterus

@ClementF074

@bokeplokalmalam

@alepamub

@moon_cheese3

@sanri_ho

@kobe_mamba1

@JasamineBanks

@Magister_JP

@pr3nt1c3

@bokeplokalmalam

Gaurav_IO

@GauravTdhinait

4 months

🚨 On April 25th, we faced a serious attack. Read our latest Medium article to find out how we tackled the challenges and what we learned from the experience. 🛠️📖 It's a deep dive into problem-solving and resilience! 🔗 #CyberSecurity #IncidentResponse "

25th April Incident Report

Issue Overview

ionet.medium.com

33

59

141

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, I'm pleased to inform you that we've resolved the recent issues and have significantly enhanced our system by tripling the capacity with our vendors. We have also identified and eliminated the malicious actor involved. In collaboration with our provider, we've

31

49

135

Gaurav_IO

@GauravTdhinait

4 months

Dear Community, many of you have reported issues and questions regarding our binary. Here is a list of known issues: 1. The GPU is under load for a short period of time, while the UI indicates the worker is not hired. 2. The binary is flagged suspicious, similar to CoinMiner

23

59

111

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, Great news! You should now be able to view your previous wallet details on the platform. Thank you for your patience as we worked through these updates. However, we're still addressing a few ongoing issues and are committed to resolving them promptly. Here's a

29

49

100

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, We recently upgraded our authentication system to enhance security. However, some users may still have old tokens, which could prevent access to reward points resources. Quick Fix: Please log out and then log back into your account. This will refresh your session

34

49

95

Gaurav_IO

@GauravTdhinait

4 months

Hello Everyone, As part of our commitment to transparency, initiated by our CEO @shadid_io , we are starting to share Proof of Works (POW) logs from our devices. Below are the logs from the recent hours, showcasing actively connected devices, each possibly equipped with multiple

14

51

99

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, Update for our users facing visibility issues with their workers on Twitter: We link your Twitter account to your previous Google/Apple account based on the email used. If the emails differ, a new account is created, and you might not see your existing workers. If

34

46

97

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, I wanted to inform you that we've recently transitioned to a new platform. During this process, we encountered some challenges with the migration of certain metadata for wallets and other systems. As a result, you might have noticed that your wallet details are

28

42

93

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, We're currently facing some hiccups in our Auth0 flow with Okta (our third-party Auth provider) on our worker nodes, as we're hitting rate limits from the Okta end. This means that a subset of devices might experience issues accessing our uptime APIs due to

16

39

86

Gaurav_IO

@GauravTdhinait

3 months

@gregosuri @ionet Hi Greg, it looks like you created 7 clusters that are all working as expected except the one which you shared. Here are few of those IDs: ed5ca903-2c69-4d47-8598-a15a52c97573 522b39f1-2aa6-499c-9fb5-331502c86000 8865a4ee-6af2-4703-b403-a3dc71cfb391

5

3

53

Gaurav_IO

@GauravTdhinait

3 months

@MartinShkreli @ionet Hi Martin, it looks like Greg created 7+ clusters(creating more now) that are all working as expected except the one which he shared. Here are few of those IDs: ed5ca903-2c69-4d47-8598-a15a52c97573 522b39f1-2aa6-499c-9fb5-331502c86000 8865a4ee-6af2-4703-b403-a3dc71cfb391

4

1

34

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, I’m pleased to announce that we have looked into and successfully resolved/confirmed the following issues: 1/ Adding New Workers: You can now add new workers without any issues. 2/ Rewards Points Visibility: Upon investigating the numerous inquiries about missing

10

11

23

Gaurav_IO

@GauravTdhinait

4 months

@emad_ahi @eli5_defi @ionet @0xHushky @MartinShkreli On the engineering front, we're all hands on deck, fully focused on crafting our product. We’re really excited about rolling out a new version soon. The entire team is zeroed in on this, making sure everything is top-notch for the launch. It’s a busy but thrilling time here

1

10

20

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @ionet Hi Martin, Thanks a lot raising the concern, we encountered a rate limiting issue with our authentication process(…), which impacted the monitoring code on the worker side, causing disconnections. As a result, a reboot of some of the workers is

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, We're currently facing some hiccups in our Auth0 flow with Okta (our third-party Auth provider) on our worker nodes, as we're hitting rate limits from the Okta end. This means that a subset of devices might experience issues accessing our uptime APIs due to

16

39

86

1

7

17

Gaurav_IO

@GauravTdhinait

3 months

@gregosuri @ionet Hi Greg, I've noticed your efforts in creating clusters across various countries. While it's impressive that many of your clusters are set up quickly For example : Below cluster you created in US was created within 2 minutes and you immediately destroyed it.

0

1

12

Gaurav_IO

@GauravTdhinait

3 months

@MartinShkreli @ionet Hi Martin, With all due respect, it's important to verify your code before making accusations. Your own screenshots clearly show that our headnodes come equipped with GPUs(shared below), which is a standard we uphold. We handpick our headnodes and collaborate with data centers

1

12

Gaurav_IO

@GauravTdhinait

3 months

@MartinShkreli @ionet Isn't providing more than a user asked for, rather than failing the cluster, a better experience? Ideally, users should get exactly what they requested. However, in the IO community, we prioritize our users. Therefore, we decided to add more workers in such cases instead of

1

0

11

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @MartinShkreli Hi Martian, Thanks a lot raising the concern, we encountered a rate limiting issue with our authentication process(), which impacted the monitoring code on the worker side, causing disconnections. As a result, a reboot of some of the

Gaurav_IO

@GauravTdhinait

4 months

Hi Everyone, We're currently facing some hiccups in our Auth0 flow with Okta (our third-party Auth provider) on our worker nodes, as we're hitting rate limits from the Okta end. This means that a subset of devices might experience issues accessing our uptime APIs due to

16

39

86

0

9

Gaurav_IO

@GauravTdhinait

3 months

@MartinShkreli @ionet Hi Martin, I'm pleased that your cluster was created. The recent delay was due to network issues in some of our data centers in Hong Kong and Japan, which have been ongoing since last Thursday. As it was pointed in last thread, the data centers are actively working on improving

0

1

9

Gaurav_IO

@GauravTdhinait

3 months

@gregosuri @ionet Hi Greg , I am seeing you creating multiple clusters and immediately destroying after they getting created. Let me know if you need any help ?

2

0

6

Gaurav_IO

@GauravTdhinait

4 months

@PerConsAdAstra thank you for trying our platform , our team would be more than happy to help you if you have any issues in future as well.

0

2

5

Gaurav_IO

@GauravTdhinait

4 months

@PerConsAdAstra Thanks a lot for your kinds words, I really appreciate your patience and support !! @PerConsAdAstra

0

4

Gaurav_IO

@GauravTdhinait

4 months

@NiketanMishra1 Thank you for your kind words , the team really worked hard to get this done

0

3

Gaurav_IO

@GauravTdhinait

4 months

@elapacino It’s not our system which are broken , for every 3rd part which you work with. there is certain number of request they allow you to call /min , as they also have to plan capacity. If you cross that limit, they will start blocking you . Someone utilized that bandwidth

2

0

4

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @shadid_io Thank you for your attention to detail and for raising questions about our numbers. By now you’ve noticed how transparently we share our numbers, even though this openness can sometimes be to our detriment when certain details are misunderstood/ misinterpreted or wrong because of

1

4

Gaurav_IO

@GauravTdhinait

4 months

@njylhoDKkBulMRH Please share your user id , I ll take care of it

1

0

3

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @ionet thanks for flagging it , well noted.

0

3

Gaurav_IO

@GauravTdhinait

4 months

@disco_dictator @shadid_io Thank you for bringing this to our attention. We're already aware of this issue, and please note that for Mac systems, we use a different method to identify spoofs. We are currently in the process of tailoring the logs specifically for Mac users, as Macs are known to exhibit

1

0

1

Gaurav_IO

@GauravTdhinait

4 months

@CornerBTC @hanzthehuman @ionet @shadid_io @cornerstoneway can you please share your userID in DM

2

0

3

Gaurav_IO

@GauravTdhinait

4 months

@im_X_not_EX We are hiring please drop an email here, will connect with you

0

3

Gaurav_IO

@GauravTdhinait

4 months

@ClownTheArtist @shadid_io @ionet @ClownTheArtist , we appreciate your patience and understand your concerns. In response to urgent security needs, we initially had to implement a less-than-ideal solution. We're actively working on a new approach that will not require obfuscating the binary code, thereby

2

0

2

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @0xHushky @Trade2Prop @ionet @MartinShkreli The numbers on the left hand side are nodes connected today, but the right hand is the latest snapshot at this moment. These numbers on right may change due to two reasons: 1/ Another cluster allocation may have occurred in parallel, which utilized some of the

0

2

Gaurav_IO

@GauravTdhinait

4 months

@Kera34535196 @shadid_io @ionet have you faced any issues with it ?

0

Gaurav_IO

@GauravTdhinait

4 months

@starzqeth @shadid_io @ionet This should be fixed already , thanks a lot for raising this Much appreciated

1

0

1

Gaurav_IO

@GauravTdhinait

4 months

@SahilPandya04 @ionet This issue was identified and resolved a few days ago. Could you please verify whether the email address used for authentication on the Worker platform and the website is the same? We've noticed that discrepancies in email registration can cause failures. To address this, we are

2

0

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli @ionet Hi Martin, I hope you are doing well. Your input is invaluable as we strive to improve. Both of these are already in development and are good callouts.

0

1

Gaurav_IO

@GauravTdhinait

4 months

@disco_dictator @shadid_io @disco_dictator please raise it in our discord, the support team will help you there. If there is any delay, feel free to DM me.

1

0

1

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli Thank you for your report. You are creating a cluster with low bandwidth, which may lead to stability issues. We address this by alerting users with a prompt advising that low bandwidth clusters can be unstable and recommending higher bandwidth options for critical workloads.

2

0

1

Gaurav_IO

@GauravTdhinait

3 months

@DeepBinarySage @gregosuri @MartinShkreli @ionet can you please DM your email

0

1

Gaurav_IO

@GauravTdhinait

4 months

@GrezCrypto @shadid_io can you please share your userId and Device in DM

0

1

Gaurav_IO

@GauravTdhinait

4 months

@hentai_carlos Thank you for your encouraging words! We are committed to continually improving our service.

0

1

Gaurav_IO

@GauravTdhinait

4 months

@MartinShkreli Hi Martin, I hope you are doing well. Thanks for reporting this! It looks like this cluster is now fully operational. The issue here is due to one of the supplier's nodes had connectivity issues. Ordinarily we prioritize multiple nodes from the same supplier to optimize

0