It's looking very likely that Slaxt is actually SellingHBOGo. The address is tied to SHG plus the fact that Slaxt said (via PM to me) that he had changed his password as soon as he had discovered PMs in his outbox that he claimed no knowledge of authoring. However, as indicated by replies in this thread, his password had not yet been changed.
|
|
|
Here's what I saw:
|
|
|
Done, pm sent to tomatocage.
Thanks for telling and posting here. Didn't you tell him to post here? -MZ I just woke up. Give me a few minutes
|
|
|
I just got your guys' PM. Escrow agreement sent. Blackheart13, you're clear to fund the address at your convenience.
|
|
|
Ill do it but you must send first, I will send coins within 4 hours(After I Go To The ATM to withdraw with my paypal debit that way if you chargeback the account I can just abandon the paypal account)
And I can hold your coins in escrow just to be safe. Shall I create a deposit address for you?
|
|
|
Confirmed. I will create an escrow wallet that will hold incoming funds for these units. However, at present I'm away from my escrow machine, so an address is not available at this time. All escrow addresses given by me will be PGP signed.
|
|
|
Gary Simmons at it again. ANY "exchange" with blogspot.com as the domain should be automatically assumed to be a scam.
|
|
|
Because I'm texting him and he just said he got jumped and his wife's on her way to get him to a hospital. And earlier on he texted me like there were people on his block roaming he never seen before. 3 days ago a guy was on his front porch just sitting there and moved after Marc came to the house.
Jesus fucking Christ you're gullible.
|
|
|
I've been offered 100 BTC for my account before, though I'm not sure how legit the offer was. Regardless, I told them to buzz off.
|
|
|
How long ago was this attempted scam? If its recent I would assume he has run out of funds to pay back his other victims IP and login times from the OP: IP Addresses, and times are UTC:
166.170.49.12 (2015-02-15 17:01:57.441373+00) 166.170.51.148 (2015-02-14 15:29:12.692309+00) 166.176.59.169 (2015-02-14 19:18:28.188283+00) 166.170.50.186 (2015-02-18 02:31:19.382578+00) If this is accurate and represent actual scam attempts, we can reasonably link where the money that he's paying back with is coming from.
|
|
|
timowheat99, for someone able to move $1k per day in PayPal Mycash codes, $5 isn't too much of a loss for you. Next time use escrow.
|
|
|
You're free to leave him negative trust, but I'm afraid that scamming him out of .02 BTC isn't the way to go, especially if he sent with PayPal.
|
|
|
txid 6c9a7813c1885eb39d9079394fa416e8c439f61f35b98c27e908cc3fe322dfa9
Looks good to me. Soha?
|
|
|
Soha Can you please send me my 5 dollars on paypal? I clearly see that you have received the bitcoin
Post the TxID.
|
|
|
Actually I meant to make it a neutral rating; hence the "Caution" in the note. TBH I think this is just a way to get money out of stolen CC info, but I'll give it a fair chance and let things play out. Feel free to leave your negative ratings on me though since they don't affect my score at all. In fact this account is an alt, designed to take the abuse so my main account doesn't
|
|
|
Wow, you guys really can't see (or at the very least are turning a blind eye) that this has all the earmarks of a money laundering scheme that ties your physical mailing address to very likely fraud? He's probably using stolen CC info and purchasing items shipped to your address and pocketing the BTC. What do you think happens when they start investigating these purchases and see your receiving address tied to a certain transaction?
|
|
|
Sorry, I've been out sick the past few days. I still have your 1.00 BTC in escrow and was wondering if there's a particular user this should be attached to.
|
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Escrow address: 1Q3nWE2WFjzKzddduvwt8Rfef7BLkd4VKJ
This address will hold 1.00 BTC, funded by iluvbitcoins, to secure his guarantee made in his thread url=https://bitcointalk.org/index.php?topic=956697 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBAgAGBQJU4OdpAAoJEI5wflVIgNhccqsH/0s9IcqUxqmexRVlFK1eWmEL Xrl5xVbRW0nlu8Pqe4/K7VBatSIwCLkUTxFTWRDtZ8ksd2IrGqZK+yDzTDDeJp3E bhcGBC2raU2LBrgccaMLvpxeyK4S5VzedDwVgBlFTQYfu6H1W6SWx8nRauiClzCQ XGYauFg3dDFj17RWqH4uqVqjOqmdCKpC8jqtWZ+pLbLuC5DOw9aXwJ7MLN8I9k6n WqR963MFOqmMwfHkklUGP7EJN/h9RqLjsuSWOPKccB2qi14V6DqHeDjNIjlOlFPl wK2oCGiRaL0FaK9keUhv1J/BgFYMh2kisleEdANhLuyqAOMPQ1fVbqxLCZjlcdA= =2QtV -----END PGP SIGNATURE-----
|
|
|
|