Advertisement
riX2000

#bitcoin-otc scammer warning

Mar 2nd, 2013
483
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.94 KB | None | 0 0
  1. -----BEGIN PGP SIGNED MESSAGE-----
  2. Hash: SHA1
  3.  
  4. *****
  5. ** MAKE SURE THAT THIS MESSAGE IS SIGNED BY THE CORRECT PGP KEY OR BITCOIN ADDRESS! **
  6.  
  7. If you don't understand everything below, you are likely to become the victim of a scammer!
  8.  
  9.  
  10. If you're seeing this page you are buying bitcoin from riX (aka. riX2000).
  11. I'm using the email address rix2000@gmail.com.
  12. My public PGP key is listed at http://bitcoin-otc.com/viewgpg.php?nick=riX2000.
  13.  
  14. If you are doing business with me, make sure that it is indeed me you are dealing with, either by verifying the email address, making sure I'm authenticated at #bitcoin-otc in FreeNode / IRC or having me sign a text with PGP or my #bitcoin-otc registered bitcoin address.
  15. The text signed should contain specific details about our business, like ANY BITCOIN ADDRESSES INVOLVED and preferably also a date and other details that is unlikely to have been used by a scammer saving an old signed message from previous business with me.
  16. Also make sure to VERIFY the signed message. Google if you don't know how to do this.
  17. My public PGP key have the key id 79642F25. (Verify this via the #bitcoin-otc link above!)
  18. My #bitcon-otc registered bitcoin address is 1FeZXDcxSzdfCN1Svz8CSX5PbJDh2neaNT. (Verify this via the #bitcoin-otc link above!)
  19.  
  20. I will never deny proving myself through any of these methods, if I am, it is most likely that it is a scammer you are dealing with.
  21. This have happened several times before that I know of, and scammers will get smarter and find new methods all the time.
  22. Untraceable money like bitcoin is very attractive to scammers, since it is very easy to get away with a lot of money with very little risk of getting caught.
  23.  
  24. Common scams:
  25.  
  26. * The scammer is sending links to a #bitcon-otc ratings page or sending "screenshots" of bitcoin balances or similar. I would never send a screenshot since those are VERY easy to forge.
  27.  
  28. * The scammer is sending a signed message. You don't know how to verify it, and the scammer tells you some method that isn't correct and will show his false signature as correct. Make sure you know what you are doing. Use google instead of asking, or at least ask more than one person.
  29.  
  30. * The scammer is acting as a middle man for a non-bitcoin related transaction.
  31. Example (description borrowed from Mqrius):
  32. Imagine a scammer contacting me, riX, to buy Bitcoins.
  33. At the same time the scammer gets into contact with someone else, let's call him Bob.
  34. The Scammer sells Bob bitcoins, or something else, let's say a coat.
  35.  
  36. The scammer then gives Bob my bank account number. Bob pays, thinking he's paying for a coat (or even bitcoins).
  37. I get Bob's money, thinking I've been paid for bitcoins. Naturally, I send the scammer the requested bitcoins.
  38.  
  39. Later, Bob doesn't get his coat or bitcoins, and file charges against me, because I received Bob's money. Meanwhile, the scammer is nowhere to be found.
  40.  
  41. If you are not buying bitcoins, then you are Bob in the above story!
  42. If you are buying bitcoins but didn't verify that it is indeed me you are dealing with, then you might be Bob.
  43. If you have any doubts, please send me mail at riX2000@gmail.com.
  44.  
  45.  
  46. I'm also both riX and riX2000 at bitcointalk.org. riX is my primary account.
  47.  
  48. Btw, I got the idea for and also borrowed some of this text from Mqrius, thank you for that.
  49. *****
  50.  
  51. Bitcoin signature (text beginning and ending with *****):
  52. IHxGDqABCQDup1kl8aMF0MN/qizWCD47Bd3Bnxr83r7iq/FTobCigFtiZ9GwQ4M8+kw6knB8kCkltsst3KLqDx8=
  53. -----BEGIN PGP SIGNATURE-----
  54. Version: GnuPG v1.4.11 (GNU/Linux)
  55.  
  56. iQEcBAEBAgAGBQJRMm8zAAoJEJ8xgCx5ZC8lA9gH/3CdLV7/9vlHxvs8Q0DKkJdQ
  57. bjogUhVCBOzQHCfwN0aFJJMre0/p2/PJYdm0glMUbPJHMPkM0FbgMf8Hp5DY8nE3
  58. GDlxKtV1OkDwQYOwO5lVWhmO4mpbyc8o7EEt6ARYbkWDr9bJ1FlD2IPgvjYotxKh
  59. kz7GrKARia1PCNG3blWAnL5HTsSM0EZwSNWz+pPYzmkWz7Knwu9x+JrfDaLlmv0j
  60. SbnBOL5XiF+YWEXYffBN9CIAn8dZfuYN504wOO4N77of9+ePX7azpGZOjPhwTXkv
  61. H3FBTcQm5zJWgt/2i3/HeLpXvIvujUYonn1D395BN/HHemf28OLySD3ddMQMqpI=
  62. =i6kH
  63. -----END PGP SIGNATURE-----
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement