Prohashing audit finds Graviex improperly crediting deposits; customers advised to withdraw all money

Read about Prohashing, mining, and coins in general!
Forum rules
Sign up to be notified of new posts to the Prohashing Blog at http://eepurl.com/gx1e0j
Post Reply
User avatar
Steve Sokolowski
Posts: 4558
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Prohashing audit finds Graviex improperly crediting deposits; customers advised to withdraw all money

Post by Steve Sokolowski » Sun Oct 24, 2021 9:45 am

Prohashing performs regular audits of its systems to detect bugs and theft, and has determined that cryptocurrency exchange Graviex is failing to credit deposits to its platform from what appear to be randomly selected transactions. Additionally, Prohashing found that Graviex has listed some money as locked, with no ETA as to when the money will be able to be withdrawln or traded. When the errors were brought to the exchange's attention, Graviex's customer service representatives refused to correct the issue, causing Prohashing to cease trading with Graviex, and leading to a recommendation that all customers immediately withdrawal all money from Graviex.


Failure to credit deposits

Graviex failed to credit hundreds of deposits. The following DigiByte deposits alone are responsible for thousands of dollars of losses:

Code: Select all

475.7047  61242f8b19d7d5b70ce6ba4c39994643c7638240689108209d704283edb218de
268.7224  0d0d1c5c1ca9493e8bed0462fe31ae85da255381831ef09255148efd4232e5aa
515.7167  115be5e07f3adb6542f877e4b560b6dd1021cc28ae3de928359e69e6785ce08a
466.22989663  ece01aa75149f2db49525a4a554d6cdd473b1ab1ae50cad1ba02ce6d80c9f338
67.2268  1e95b05a6a919bb6fef4eb38ad40f9f37b4bd1b1eaea13a9e747d16f290d7541
74.074  081aab45e3aec84c479c4ba833b9c423bc7f84a6d2074a92e683df616cdbeea4
283.7209  e35e56e0bc71b7c68fe77f2a4bffc5232fd4841bf644c6c3d463ca366ab71849
2339.9272674  7773c00148e67b2a0a699386820e1e0a05c4510efed56d65ddd20a5ce1bf0263
4825.6478  aead8381f0cddf3f2a8eded952a2123e5c57a6739075a999034188a497b4e6d7
2336.29698217  f3459642bbbbca03ef8d681055efab522a7c84a3c530febd486dc72d6f5dcd82
4205.92299682  c5aa3fafe5a0e117647f9cec571f67a6918b7fc3ad01880de8cf613ec4302843
1106.17753674  b714290b71e62587874fad3f57f6e30170946dfb8d46b308533b870b8ac6723c 
3580.14801812  6086f1ad974aa9c4f15a49810ce886dfe61931469c502c6cbd2500656c3ca751 
2969.52923263 7b467c3a57bb0351f6b6c41f881c6873e248d07d1ebfc8b20a9c48a877bd9a0a
2960.8990998  b1c0adb11d97f1bea508b47cb11865dfd8851f527dad4cf834dea0ae61696029
5317.2253  551b3bd974af9990605b316230cd9d54fd83cf5c401407a08cac4c88783b38a6
5317.2253  1f355fa25b7c9b05d0e6c03fe03f6a9106503518fc677e7115462c51f097c19a
317.2253  a21b3aa3ffd2e6154665e2271b76964adc0f2fb19e3dc2b1362c2885495db483
317.2253  932608a4a60324d261295dca7363ee3625e4a2a262e395f6b24285a6e173e7fb
7306.7387  136ca37e2855a6285fd3277312d4dae8845ac587213f326bd1b02b5b872eb6e7
7306.7387  893d58b64c44d4eecba80d4af780ded3be158717cdd572773cbb123b29710cb0
5316.96534602  66d83d5816e38d1ddd46d67d68a65158d23d4213717a6576ba7b6af087fc7682
2000  c8858bfeb1af563e3065d1596f732bd8cfff773abf99d74e359cb14f2f79e42d
2000  37ff67566e9e6c6053aae82c38b0970147dc9170b25abdb73f7c8c150e7552cf
5308.2653  f52691a1c6a45998dd142443cb57616f3e63b91d501fcfdd7895bf9f90d1569b
5308.2653  ff221812f0a908011a694855aaadecbbe59b7fc18f484747110ca542bca21310
6029.7842  598810b8f566fdc3eeae2e43462be1fb0c3a67764c5e3f5c1f6b32475bfca54c
5888.91389132  b8611d6dce04247f92a7b502ed9d4f6b391f3b69e5c3ac1eb50141037dd5c2fd
5308.2653  054c399999686ac55fac9999b26e8a2d43b8372e1a73f8cbdbffbcdbd1f1ce52
6055.1007  0687eae276022866fe248ea6fc71400a387ecf41e0e1f4f2bdd6bf40a1c8cb69
6042.4425  2bb1cda8f9c2d9791ac9b0b57e57bff1302e12136f2cdfd5654fd97b67043b28
6029.7842  e04c26d95328642cff407025f42fe8d3c59fa0c2ea964d2e37c7351b360e96ec
6042.4425  0b36aea391660ad9bbe0e077276872d77f898551a43b69a3b218e6a28b6cbc56
5951.8251936  83db18d558c219bccf662f0a39a83c648d4325ab8d34b5109a483f4c6101d5bd
6042.4425  3b4ad3828d8bfffff4ac7145661601e0c70dce29cfbfa82f53a1671aab4534a4
6017.126  8cd18633554f2dcbd18040a642f8255e3e2d00081410924c6cb815b6c225a361
6029.7842  b42624a6b0f54a129890e25634b13d7f6ae8d032da6da5ec29a62ab621732d8e
6017.126  a5ae9cdfd6fde2832f48725afe369b19ddf029b058816e5c07b564fd2b6ffb17
5971.37685154  efa2e6576803135c8f95bbd353cc8407ae0c9b609851242edecc392d0621abd0
5991.8096  67b28c42a1322b9cdd89107f86c75e9a67288d25528bb79d9c7aec39d659de6e
5991.8096  c7ef17bfa82b21469ec76c18f0361c1edeeb15334d270b24095b34716bddf241 
696.2025  85e40453305a802c9d5e1516a749b70e63a2a35be3846787b308202fd31a39e3 
5337.37129693  a1400235183499087dea1314fceb4ec68ef0f294bc2aa2447b7de469d9648df7
6004.4678  6bc169530820ae7b3006500402b1570350462f1050d14d1c0d58489d26688ca9 
5999.22  a75abecf7d6625b82b83f966faf0b7936af808045ccfce4698b6a7431a7a8ad5 
5945.13238426  bb43c6098b3c91485a3d7649bcd46594ee777c6f62b607a7387f43eaf904151b 
6011.7828  e184363a494e38b73329ff5035baa8d67cb408371912f7cd038b6bc16dbfb99b 
1989.30317835  dbf292b60a65c52f15d3d3cedc0f6a5b48f54c6b104772204b2f841e4bfc79bd 
703.5175  fccb32782a9a41299b4ae259ebbc572711632e73eeef55c8c9fee2f22201f615 
716.0804  c318265e46f92225703a4478e7fc0e210dab11cc6ab6158d0f57328eafd39856 
703.5175  b0664887eed54d206472d6937dba993eb1787b7ed55a9e0eb6bd0f565d8ffe95 
690.9547 ae8eb67ccec3b9b6af2bbe3acac3a439a30d781d66ca6a9881b8ac11b1112622 
690.9547  6a9e3f1410566f0d7420151f6ddd75e4b45be7d73f5b99ed386baa14bf27de08 
678.3919  f651d4a255b5afc4746fbbea56c36947b3c8a3602cb5f74e94f61014d5a391d8
When Prohashing contacted Graviex about these deposits, Graviex refused to take any action. After first claiming that the deposits were being checked by a "security service," Graviex then falsely blamed the DigiByte developers for an unspecified issue in crediting the deposits:

Image

Graviex has a longstanding bug with crediting deposits; however, issues were resolved without incident in previous years. However, even though multiple instances of missing DigiByte deposits that was identified through the audit have been brought to Graviex's attention (this ticket alone was submitted on August 11), Graviex stopped resolving these issues in 2021.


Unable to withdrawal "locked" money

Graviex also has created a concept of "locked money," as indicated in the image below. Here, 20036485 NewYorkCoins are in a "locked" state:

Image

Until Prohashing ceased trading with Graviex, the "locked" balances continued to trend up over time - both in total value and in percentage of Prohashing's assets that were deposited at Graviex. Attempting to withdrawal "locked" money results in the following error:

Image

A text search of Graviex's "FAQ" at https://www.gravio.net/post/graviex-exc ... ervice-faq reveals that there is not even one mention of the word "locked" on the page, and support tickets requesting more information about why balances can be "locked" result in unclear answers. Furthermore, when Chris submitted a ticket to Graviex, he received no response:

Image


Conclusion and actions

Effective immediately, Prohashing has ceased trading with Graviex and is in the process of withdrawing all money from the exchange. We expect losses to be around $10,000. While Prohashing's terms of service allow losses from exchange thefts to be passed onto customers, we do not anticipate executing that option in this case. The exception is for coins that are only traded at Graviex, or coins where Graviex is the only exchange that both trades the coin and which accepts US customers. Since we have no way to obtain coins without other exchange options, those debts are, unfortunately, unpayable.

We strongly recommend that all customers who have accounts at Graviex close them and take steps to safeguard whatever money is still available immediately.
Sumoblei
Posts: 47
Joined: Sat May 29, 2021 8:34 am

Re: Prohashing audit finds Graviex improperly crediting deposits; customers advised to withdraw all money

Post by Sumoblei » Sun Oct 24, 2021 9:55 am

Another one bytes the dust! smh Good riddance to zero customer service!
Post Reply