 Show Posts
|
|
Pages: [1] 2 3 4 5
|
|
1
|
Economy / Scam Accusations / Re: CRYPTSY stopping withdraw locking accounts without notifying users! Class Action
|
on: September 18, 2015, 10:29:41 PM
|
THEY CLEARLY DID NOT TELL ME HOW. See 2 posts ago of mine.....
I don't see any response.
Community: these ppl trying to discredit me are Cryptsy's troll accounts. I opened the account with the same IP, put the funds in- they have my ID and all my info... There's really nothing else a human can do to prove the account is theirs, I've given them everything.
Well, at least I have on the record them saying the coins are in the account. So, If/when they mysteriously "disappear", there's going to be alot of explaining to do to the judge. I am just calling it here in advance(again): they are going to say the account is hacked and someone withdraw the $ and that it's my fault. Sorry Cryptsy, its not going to work. Also notice they haven't done a single thing to contact the "legitimate" owner(an email would be nice). They have done nothing. I know because its my account.
Cryptsy = reverse security. Security intended to keep the owner of the acct out, and put down all security barriers (three 2FA options simultaneously) so a "hacker" can get into the account and fuck around.
CRYPTSY/MULLICK/BITJOHN: Still waiting. Lets just get this over with.
The fact that you have not even tried to reset your password concerns me. You are willing to make forum posts and replies and make support tickets, but you are unwilling to take a few seconds to reset your password? This really makes no sense to me. It's good practice to change your passwords from time to time anyways. From our perspective, this really just looks like somebody trying to access an account that they are not authorized to access. We get people trying to social engineer their way into peoples accounts all the time, so we don't take this lightly. BigVern |
|
|
|
|
2
|
Economy / Service Discussion / Re: GAW / Josh Garza discussion. Paycoin XPY CoinStand Mineral. ALWAYS MAKE MONEY :)
|
on: April 28, 2015, 09:15:43 PM
|
everything going like mr garza planned with Big Vern of Cryptsy (thx PRODIGI). i dont remember if this was posted before  Yes, this email conversation took place. No, we did not end up doing any part of the idea. This was long before any of the drama took place, and even then I was not comfortable with the idea. I have no interest in GAW and they have no interest in Cryptsy. Reading over this forum really reaffirms my decision not to frequent here. There is so much misinformation and out of context information that this has really become more of a tabloid forum than one that actually helps users and the community. Paul BigVern |
|
|
|
|
8
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] Diamond (DMD) Evolution v 2.0 | NEW wallet, coin mechanics, 50% POS
|
on: June 28, 2014, 05:48:18 PM
|
I hope everyone knows that the first of July, cryptsy administered verification for their clients. Without verification, daily amount can not exceed $ 1,000 per day. Many people will not agree to such an exchanger. This is the way a broken exchanges mtgox. Diamond will be needed a new large exchanger.
This is an incorrect statement. We have not begun daily limitations on cryptocurrencies yet and will phase it in slowly when we do. In any case, if you do alot of large deposits and withdrawals, then you should really get verified now instead of later. BigVern |
|
|
|
|
10
|
Other / Archival / Re: deleted by request
|
on: June 03, 2014, 01:05:47 PM
|
|
I will look into what is going on with NXT. The devs changed the protocol awhile back and we had to rewrite some things to support the NQT stuff. We are 100% funded in the wallets, so that is not the issue.
BigVern
|
|
|
|
|
12
|
Economy / Service Discussion / Re: Cryptsy holding on NXT for forging themself
|
on: May 01, 2014, 12:54:15 AM
|
|
NXT is something we are continuing to improve on. Right now the process of deposits is a bit inefficient, and so it does tend to take longer than it should.
We don't forge any NXT currently and have not in the past. I would like to in the future because it will improve the network, but we need to the deposits working faster first.
BigVern
|
|
|
|
|
13
|
Economy / Service Discussion / Re: (Warning) Whats going on with cryptsy.com every one is losing there coins
|
on: February 02, 2014, 04:01:42 AM
|
|
There are several things going on here it seems. I'll see how many I can address.
1. Federal Money Transmitter License - There is actually no such thing at a federal level. The only thing the Fed's require is that you register and file SAR reports when deemed necessary. They also want us to check to ensure we aren't doing business with anybody on the OFAC list. We are registered and the list checking and reporting is fairly easy to do, but detecting suspicious activity is a very subjective thing. It's certainly easier to determine suspicious activity when dealing with USD. Before launching USD, we will have the necessary items in place.
2. State Level Licenses - The states aren't going to come and shut you down, but they may fine you and tell you not to deal with people in their state until you get licensed there. We are in the process of getting state licenses. Some are harder than others. This is another thing we are waiting on before doing USD. Many of the states who we previously thought would require a license have stated that we probably do not need one. Many states have laws which were written before the internet. Some state requirements are a little overboard.
3. SR stuff. Just because some coins passed through a service that ended up at SR doesn't mean that it would be covered under any laws which would result in forfeitures. Only if we were willfully and knowingly performing such actions, which we are not. We may be subpoenaed for information in such cases where funds pass through here, which of course we would comply with.
BigVern
|
|
|
|
|
14
|
Other / Archival / Re: delete
|
on: December 15, 2013, 04:16:45 AM
|
|
We do not operate with fractional reserves. Any exchange that does that will never get licensed. Part of getting licensed is having the financials audited, including customer held funds. I have to assume that any coin can and will have a "bank run" at some point. I'm not a bank and I do not lend coins out, so I have no business in misappropriating coins on deposit. If you want to move all funds out, then they are there to move. They may, however, need to be moved from our offline wallet to the hot wallet first.
Any overwithdrawals caused by a system issue in the past and going forward are covered either by myself or the profits of the exchange itself (if the user is not honorable enough to send them back). These issues are rare and getting rarer.
Paul
BigVern
|
|
|
|
|
18
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][SRC] SecureCoin | A Fast and Secure Version of Bitcoin | LAUNCHED
|
on: August 28, 2013, 09:05:25 PM
|
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/main.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/leveldb.o: In function `CLevelDB::CLevelDB(boost::filesystem3::path const&, unsigned long, bool, bool)':
/home/ubuntu/src/leveldb.cpp:37: undefined reference to `leveldb::Options::Options()'
obj/leveldb.o: In function `GetOptions':
/home/ubuntu/src/leveldb.cpp:28: undefined reference to `leveldb::Options::Options()'
/home/ubuntu/src/leveldb.cpp:29: undefined reference to `leveldb::NewLRUCache(unsigned long)'
/home/ubuntu/src/leveldb.cpp:31: undefined reference to `leveldb::NewBloomFilterPolicy(int)'
obj/leveldb.o: In function `CLevelDB::CLevelDB(boost::filesystem3::path const&, unsigned long, bool, bool)':
/home/ubuntu/src/leveldb.cpp:56: undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::string const&, leveldb::DB**)'
/home/ubuntu/src/leveldb.cpp:46: undefined reference to `leveldb::Env::Default()'
/home/ubuntu/src/leveldb.cpp:46: undefined reference to `leveldb::NewMemEnv(leveldb::Env*)'
/home/ubuntu/src/leveldb.cpp:51: undefined reference to `leveldb::DestroyDB(std::string const&, leveldb::Options const&)'
/home/ubuntu/src/leveldb.cpp:58: undefined reference to `leveldb::Status::ToString() const'
obj/leveldb.o: In function `CLevelDB::WriteBatch(CLevelDBBatch&, bool)':
/home/ubuntu/src/leveldb.cpp:76: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `Write<std::pair<char, uint256>, CDiskTxPos>':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `CLevelDBBatch::~CLevelDBBatch()':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `bool CLevelDB::Read<char, uint256>(char const&, uint256&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `bool CLevelDB::Read<char, int>(char const&, int&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `bool CLevelDB::Exists<char>(char const&)':
/home/ubuntu/src/leveldb.h:123: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `void CLevelDBBatch::Write<char, int>(char const&, int const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `void CLevelDBBatch::Write<char, char>(char const&, char const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `void CLevelDBBatch::Erase<char>(char const&)':
/home/ubuntu/src/leveldb.h:51: undefined reference to `leveldb::WriteBatch::Delete(leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `void CLevelDBBatch::Write<char, uint256>(char const&, uint256 const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `void CLevelDBBatch::Erase<std::pair<char, uint256> >(std::pair<char, uint256> const&)':
/home/ubuntu/src/leveldb.h:51: undefined reference to `leveldb::WriteBatch::Delete(leveldb::Slice const&)'
obj/txdb.o: In function `bool CLevelDB::Exists<std::pair<char, uint256> >(std::pair<char, uint256> const&)':
/home/ubuntu/src/leveldb.h:123: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `bool CLevelDB::Read<std::pair<char, std::string>, char>(std::pair<char, std::string> const&, char&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, std::string>, char>(std::pair<char, std::string> const&, char const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `void CLevelDBBatch::Write<char, CBigNum>(char const&, CBigNum const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `bool CLevelDB::Read<std::pair<char, uint256>, CDiskTxPos>(std::pair<char, uint256> const&, CDiskTxPos&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, uint256>, CDiskBlockIndex>(std::pair<char, uint256> const&, CDiskBlockIndex const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
obj/txdb.o: In function `bool CLevelDB::Read<char, CBigNum>(char const&, CBigNum&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `bool CLevelDB::Read<std::pair<char, int>, CBlockFileInfo>(std::pair<char, int> const&, CBlockFileInfo&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `bool CLevelDB::Read<std::pair<char, uint256>, CCoins>(std::pair<char, uint256> const&, CCoins&)':
/home/ubuntu/src/leveldb.h:94: undefined reference to `leveldb::Status::ToString() const'
obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, uint256>, CCoins>(std::pair<char, uint256> const&, CCoins const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, int>, CBlockFileInfo>(std::pair<char, int> const&, CBlockFileInfo const&)':
/home/ubuntu/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
obj/txdb.o: In function `CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()'
obj/txdb.o: In function `~CLevelDBBatch':
/home/ubuntu/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
collect2: error: ld returned 1 exit status
chmod +x src/leveldb/build_detect_platform The OP shouldnt have used braindead format like zip to distribute source code. Still doesn't want to work on my ubuntu 12.04 64bit platforms make clean -f makefile.unix Then try again |
|
|
|
|
19
|
Alternate cryptocurrencies / Altcoin Discussion / Re: is ok
|
on: August 02, 2013, 04:52:13 AM
|
|
The account was flagged for suspicious activity, such as depositing a large amount and immediately making a withdrawal of the same amount. These types of flags require manual review.
BigVern
|
|
|
|
|
20
|
Economy / Reputation / Re: Hydroponica's rep thread
|
on: July 24, 2013, 11:37:32 PM
|
Good day.
If you've ever had any dealings with me, please say that I haven't scammed you, or ripped you off.
P.S.
No one cares, if I hurt your feelings.
I'll vouch for Hydro. I don't agree with everything he says, but he's pretty high on my trust-o-meter. BigVern |
|
|
|
|
