zdravo Peter,
Igra? nam je poslao priznanicu sa he? ID-om transakcije a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54. Imajte na umu da je ovo jedinstveno i da ?e vam tako?e pokazati koja je adresa nov?anika uklju?ena u tu transakciju.
Adresa po?iljaoca za hash ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 je bila bc1km34lsc65zpv79lkes69zk, klijent je dostavljen sa klijentom jo? je naveden poslao adresu kao 1MAk2n1v1kSZvtambVnV8egDKcauG9GHV6. Ovo je prvo uo?eno neslaganje, po?to je ovo veoma vidljivo na ovom linku: https://blockchair.com/bitcoin/transaction/a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f
Druga neslaganja je:
https://blockchair.com/bitcoin/address/1MAk2n1v1kSZvtambVnV8egDKcauG9GHV6
Igra? vam je poslao svoje poslato sa adrese kao 1MAk2n1v1kSZvtambVnV8egDKcauG9GHV6 i nije bilo transakcije od 0,01819 BTC 31. maja prema originalnom he?u transakcije datom kao a88cae6bb8969d201c21032b16b0b20b16b10b0b0b0b0b0b0b0b0b0b0b0b0b00b 510a9f0f7f54 od strane igra?a. Iskreno govore?i, he? ID a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 bi trebalo da bude vidljiv na https://blockchair.com/bitcoin/address/1MAkSZGvgamVDK
Ali to nije slu?aj jer takve transakcije nema.
Jo? jednom, he? ID transakcije a88cae6bb8969d201c21032b10a6a7e63098e1b1b92db22a404f510a9f0f7f54 je jedinstven na blockchainu i uvek ?e prikazivati poslatu sa adrese. Sve ?to treba je da se uskladi sa ra?unom koji je dao igra?.
Na dodatnim snimcima ekrana bloka blokova koje je poslao igra?, vidljivo je da je he? transakcije druga?iji jer je igra? zaokru?io ?3f1d220d2fbf1091af75085ed11da5dda811bdda0ca42f7f83ba180c5e7c2293" kao ?to je njegov ID transakcije 4 he?.99 za $5.
Jedna transakcija nikada ne?e imati dva he? ID-a na blok?ejnu – bi?e jedan ID za svaku transakciju.
Iz gore navedenih razloga zatvorili smo nalog igra?a.
Obavestite me ako imate dodatnih pitanja.
Hvala vam.
Juici 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
Automatski prevedeno: