SolCasino Payout Execution Bug: Address truncated from 44 to 43 characters (Withdrawal ID 1083182)
Detailed Description:
I am submitting a formal dispute against SolCasino regarding an unresolved withdrawal failure (Withdrawal ID: 1083182) amounting to 5.991 SOL, caused by a critical platform-side backend execution bug.
Technical Breakdown:
Intended Registered Wallet (44 characters): 75UZ1gVneRiXTnakHZnD8BhnZDJK7csFCec8nPai1mL2
Executed On-Chain Address (43 characters):
75UZ1gVneRiXTnakHZnD8BhnZDJK7csFCec8nPai1m6
Proof of Platform-Side Fault:
Frontend Validation Impossibility: SolCasino’s withdrawal form enforces standard Base58 address validation. If a user enters a 43-character string, the UI flags it as an "Invalid Address" and disables the submit button. It is mathematically impossible for a user to submit a 43-character string from the client side.
Backend String Truncation: The submission went through because I entered my valid 44-character address. The string dropped its 44th character (L2 -> 6) during backend API payload processing or RPC execution on their node.
Comparative Proof: Withdrawal ID 1083183 (submitted just 3 minutes later) executed perfectly to my exact 44-character address (...1mL2) without any edits on my end.
Because this 43-character address was created by SolCasino's execution script, no private key exists for it. The 5.991 SOL remain permanently locked on-chain in an empty account.
SolCasino support and Discord moderation have repeatedly refused to escalate this database log check to their engineering team, dismissing it with copy-paste script templates.
I request CasinoGuru's intervention to require SolCasino's engineering team to audit the internal database payload for Withdrawal ID 1083182 and refund the 5.991 SOL to my balance.
SolCasino Payout Execution Bug: Address truncated from 44 to 43 characters (Withdrawal ID 1083182)
Detailed Description:
I am submitting a formal dispute against SolCasino regarding an unresolved withdrawal failure (Withdrawal ID: 1083182) amounting to 5.991 SOL, caused by a critical platform-side backend execution bug.
Technical Breakdown:
Intended Registered Wallet (44 characters): 75UZ1gVneRiXTnakHZnD8BhnZDJK7csFCec8nPai1mL2
Executed On-Chain Address (43 characters):
75UZ1gVneRiXTnakHZnD8BhnZDJK7csFCec8nPai1m6
Proof of Platform-Side Fault:
Frontend Validation Impossibility: SolCasino’s withdrawal form enforces standard Base58 address validation. If a user enters a 43-character string, the UI flags it as an "Invalid Address" and disables the submit button. It is mathematically impossible for a user to submit a 43-character string from the client side.
Backend String Truncation: The submission went through because I entered my valid 44-character address. The string dropped its 44th character (L2 -> 6) during backend API payload processing or RPC execution on their node.
Comparative Proof: Withdrawal ID 1083183 (submitted just 3 minutes later) executed perfectly to my exact 44-character address (...1mL2) without any edits on my end.
Because this 43-character address was created by SolCasino's execution script, no private key exists for it. The 5.991 SOL remain permanently locked on-chain in an empty account.
SolCasino support and Discord moderation have repeatedly refused to escalate this database log check to their engineering team, dismissing it with copy-paste script templates.
I request CasinoGuru's intervention to require SolCasino's engineering team to audit the internal database payload for Withdrawal ID 1083182 and refund the 5.991 SOL to my balance.