Beløbet er blevet krediteret, og det sætter jeg pris på. Jeg beder ikke om yderligere oplysninger. Jeg retter optegnelsen på to punkter.
Jeg accepterer to ting i casinoets forklaring. Der blev brugt en cross-chain bridge, og en CloseAccount-instruktion krævede husleje tilbage efter byttet. Begge dele er korrekte.
Men CloseAccount på en wrapped SOL-konto er, hvordan pengene leveres, ikke hvordan de går tabt. Lukning af en WSOL-konto udpakker den og udbetaler native SOL. Det er præcis, hvad ledger'en viser: 1.244483 SOL ankom som native SOL til G9t68Nzw9ntvBybmzqcNZeuVCYyk7YA5u9dAB9qebXJs, adressen som Rakebits eget indbetalingspanel viser som min tildelte SOL-indbetalingsadresse.
Tre punkter, hvor casinoets konto ikke stemmer overens med kæden:
1. Casinoet oplyser, at bevægelsen var "fuldstændig automatiseret af tredjepartsbroen". Deres indlæg oplyser også, at mine tidligere indbetalinger var direkte native overførsler, som deres gateway understøtter fuldt ud. Blockscan-historikken for G9t68 viser, at disse tidligere indbetalinger, 3,549025 SOL og 0,318647 SOL, blev fejet til BfP2dBiHbiqYvsmESsgHEL8wQtZt25sbDNKnwmNRB34G. Samme destination som den omstridte 1,244483 SOL. Der var ingen bro involveret i disse. Fejet til den wallet er Rakebits egen routing, anvendt på indbetalinger, de selv beskriver som fuldt understøttede.
2. Casinoet beskriver en "midlertidig mellemkonto", der blev "lukket øjeblikkeligt". Det beskriver den indpakkede SOL-tokenkonto i swap-transaktionen. Det beskriver ikke G9t68, som har 25 transaktioner over mere end en måned og er markeret som min indbetalingsadresse i deres brugerflade. Det er to forskellige konti.
3. Overførslen fra G9t68 fandt sted cirka tre timer efter levering, som en separat underskrevet transaktion. En bridge indeholder ikke den private nøgle til en adresse, som Rakebit har tildelt min konto. Kun nøgleindehaveren kunne underskrive overførslen.
Rakebits egen supportagent udtalte også skriftligt: "Pengene sidder i din tegnebog her - BfP2dBiHbiqYvsmESsgHEL8wQtZt25sbDNKnwmNRB34G."
Så pengene blev afviklet, og de blev dirigeret ad den samme vej som Rakebits understøttede indbetalinger. Dette var en afstemningsfejl på operatørsiden, ikke en uoprettelig fejl fra min side.
Andet punkt, til orientering. Dette er anden gang, at Rakebit først har krediteret min konto efter, at jeg har eskaleret sagen offentligt. I begge tilfælde var holdningen, at der ikke kunne gøres noget, før sagen var eskaleret, hvorefter beløbet blev krediteret og beskrevet som en gestus af velvilje. Jeg overlader betydningen af det til Casino.guru. Jeg er glad for, at dette er løst, og har ikke yderligere anmodninger.
The amount has been credited and I appreciate that. I am not asking for anything further. I am correcting the record on two points.
I accept two things in the casino's explanation. A cross-chain bridge was used, and a CloseAccount instruction reclaimed rent after the swap. Both are accurate.
But CloseAccount on a wrapped SOL account is how the funds are delivered, not how they are lost. Closing a WSOL account unwraps it and pays out native SOL. That is precisely what the ledger shows: 1.244483 SOL arrived as native SOL at G9t68Nzw9ntvBybmzqcNZeuVCYyk7YA5u9dAB9qebXJs, the address Rakebit's own deposit panel displays as my assigned SOL deposit address.
Three points where the casino's account does not match the chain:
1. The casino states the movement was "entirely automated by the third-party bridge." Their post also states my previous deposits were direct native transfers their gateway fully supports. The blockscan history for G9t68 shows those earlier deposits, 3.549025 SOL and 0.318647 SOL, were swept to BfP2dBiHbiqYvsmESsgHEL8wQtZt25sbDNKnwmNRB34G. The same destination as the disputed 1.244483 SOL. No bridge was involved in those. The sweep to that wallet is Rakebit's own routing, applied to deposits they themselves describe as fully supported.
2. The casino describes a "temporary intermediate account" that was "instantly closed." That describes the wrapped SOL token account inside the swap transaction. It does not describe G9t68, which has 25 transactions over more than a month and is labeled as my deposit address in their interface. These are two different accounts.
3. The transfer out of G9t68 occurred roughly three hours after delivery, as a separate signed transaction. A bridge does not hold the private key to an address Rakebit assigned to my account. Only the key holder could sign that transfer.
Rakebit's own support agent also stated in writing: "The funds are sitting in your wallet here - BfP2dBiHbiqYvsmESsgHEL8wQtZt25sbDNKnwmNRB34G."
So the funds did settle, and they were routed, by the same path Rakebit's supported deposits take. This was a reconciliation failure on the operator side, not an unrecoverable error on mine.
Second point, for the record. This is the second time funds have been credited to my account by Rakebit only after I escalated the matter publicly. In both cases the position was that nothing could be done, until it was escalated, at which point the amount was credited and described as a goodwill gesture. I will leave the significance of that to Casino.guru. I am glad this is resolved and have no further requests.
Automatisk oversættelse: