Olá Peter,
O jogador nos enviou um recibo com o hash ID da transação a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54. Observe que isso é único e também mostrará qual endereço de carteira estava envolvido nessa transação.
O endereço do remetente para o hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 era bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h, mas o cliente forneceu o endereço enviado como 1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6. Esta é a primeira discrepância detectada, pois está bem visível neste link: https://blockchair.com/bitcoin/transaction/a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54
A segunda discrepância é:
https://blockchair.com/bitcoin/address/1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6
O jogador enviou a você seu endereço enviado como 1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6 e não houve 0,01819 BTC transacionado em 31 de maio de acordo com o hash da transação original fornecido como a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404 f510a9f0f7f54 pelo jogador. Com toda a honestidade, o hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 deve estar visível em https://blockchair.com/bitcoin/address/1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6
Mas este não é o caso porque não existe tal transação.
Mais uma vez, o ID de hash da transação a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 é único no blockchain e sempre exibirá o endereço enviado. Basta conferir com o recibo fornecido pelo jogador.
Nas capturas de tela adicionais do blockchain enviadas pelo jogador, é visível que o hash da transação é diferente, pois o jogador circulou "3f1d220d2fbf1091af75085ed11da5dda811bdda0ca42f7f83ba180c5e7c2293" como seu ID de hash de transação de $ 542,99, o que está incorreto.
Uma transação nunca terá dois IDs de hash na blockchain – será um ID para cada transação.
Pelas razões mencionadas acima, encerramos a conta do jogador.
Por favor, deixe-me saber se você tem mais perguntas.
Obrigado.
Juicy Vegas Team
Hi Peter,
The player sent us a receipt with transaction hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54. Please note that this is unique and it will also show you which wallet address was involved in that transaction.
The sender’s address for hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 was bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h, yet the client provided you with the sent address as 1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6. This is the first discrepancy spotted, since this is very visible on this link: https://blockchair.com/bitcoin/transaction/a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54
The second discrepancy is:
https://blockchair.com/bitcoin/address/1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6
The player did send you his sent from address as 1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6 and there was no 0.01819 BTC transacted on the 31st of May as per the original transaction hash given as a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 by the player. In all honesty, hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 should be visible on https://blockchair.com/bitcoin/address/1MAk2n1w1kSZwtambWnV8egDKcauG9GHW6
But this is not the case because there is no such transaction.
Once again, transaction hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 is unique on the blockchain and it will always display the sent from address. All it needs is to tally with the receipt provided by the player.
In the additional blockchain screenshots sent by the player, it is visible that the transaction hash is different as the player circled "3f1d220d2fbf1091af75085ed11da5dda811bdda0ca42f7f83ba180c5e7c2293" as his transaction hash ID for $542.99 which is incorrect.
One transaction will never have two hash ID’s on the blockchain – it will be one ID for each transaction.
We have for the reasons mentioned above closed the player's account.
Please let me know if you have further questions.
Thank you.
Juicy Vegas Team
Traduzido automaticamente: