Bitcoin Forum
November 15, 2026, 01:06:52 AM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: FaucetPay.io / Pasino (Basilisk Studio SRL) - 0.79923 BNB Withheld (No ToS Claus  (Read 11 times)
abuadelsaud (OP)
Newbie
*
Offline

Activity: 1
Merit: 0


View Profile
November 14, 2026, 10:22:46 PM
 #1

What happened:
On January 5, 2025 (15:36:56 UTC), I deposited 0.99923 BNB from Binance (0x001cEb373C83ae75b9f5CF78Fc2aBa3e185d09E2) to my assigned FaucetPay.io deposit address (0x51bC089B708342527C55ca7B59Bd768C958326Df) via the EVM-compatible opBNB network (Block 44337693). Because FaucetPay already supports BNB on BSC (BEP20), it holds the exact same secp256k1 private key controlling this deposit address on opBNB.

Months later, FaucetPay sent 0.20000 BNB from an operational wallet as a unilateral goodwill gesture without any signed release and without touching the 0.99923 BNB sitting in my deposit address. In January 2026 (Zendesk Ticket #212607) and March 2026, I offered to cover manual engineering recovery fees for the remaining 0.79923 BNB (~$468 USD) and pointed out that FaucetPay's Terms of Service contain zero forfeiture clauses. Instead of returning the accessible funds, Basilisk Studio S.R.L. terminated my account (enjazweb) and banned me again in November 2026 when I inquired whether their redesigned casino platform added opBNB recovery.

As of November 15, 2026 (over 22 months later), the full 0.99923 BNB still sits untouched inside FaucetPay's custody with 0 outgoing transactions.


Operator / Official Reference Links:
- Websites: https://faucetpay.io & sister casino https://pasino.com (operated by Basilisk Studio S.R.L., Costa Rica / Anjouan Licence ALSI-202606042-FI2)
- Official FaucetPay Bitcointalk Thread: https://bitcointalk.org/index.php?topic=5255740.0
- Terms of Service (Last Updated August 1, 2024 — Section 3 states wallet funds remain user property; ZERO clauses authorizing retention or forfeiture of unsupported-network deposits): https://faucetpay.io/legal/terms
- FaucetPay Knowledge Base Confirming Manual Developer Recovery With Fees Exists: https://faq.faucetpay.io/knowledge-base/can-i-deposit-tokens-in-faucetpay/
- Independent Compliance Profile (Amber Warning, Oct 28, 2026): https://listings.ratex42.com/radar/faucetpay/


Disputed / Withheld Amount:
0.79923 BNB net unreturned principal (~$468 USD at current market rate; 0.99923 BNB still untouched on-chain minus 0.20000 BNB prior unilateral goodwill payment).


Payment Method & Live On-Chain Proof:
- Deposit Address (FaucetPay Custody): 0x51bC089B708342527C55ca7B59Bd768C958326Df
- Deposit TxHash (opBNB Mainnet): 0x322f998e27db18ee687649608bdbb7de930cc66ab4980a5ff523522e2385ee4d
- Live Blockchain Explorer Proof (0.99923 BNB balance, 0 outgoing txns): https://opbnbscan.com/address/0x51bc089b708342527c55ca7b59bd768c958326df


Verbatim Support & Legal Correspondence (Zendesk #212607 / Ref 6Z3MZ6-3ED32):
Quote
FaucetPay Support (Vane) — Jan 3 & Jan 4, 2026:
As previously indicated, FaucetPay does not provide recovery services for deposits sent through unsupported or incorrect networks at this time... We do not handle recovery fees or estimated times, as we do not currently offer this service.

Quote
FaucetPay Legal Team / Basilisk Studio S.R.L. — Account Termination Notice:
FaucetPay has terminated any and all business relationship with you with immediate effect. You are no longer authorized to access or use FaucetPay... This matter is closed from our side.
(Original email headers and screenshots preserved and available for any DT investigator upon request.)


Requested Resolution:
Return the remaining net principal of 0.79923 BNB (less any reasonable technical handling fee) to my external BSC/opBNB refund wallet: 0x0eedb529dc008a2485cbed8932f124f0692a1dd7
Once resolved on-chain, I will immediately update this thread title to [SOLVED].
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!