We have taken the servers down due to suspicious account activities.
|
|
|
Novacoin listed.
Happy trading.
|
|
|
Chncoin also trading now.
|
|
|
We are keeping the withdrawal still open so people can move their coins over.
|
|
|
Do you guys remember Geistgeld?
|
|
|
I like your project!
BUT how do you fight with scam?
Fighting scam? How is one to judge an honest business idea from a scam? This is a very subjective decision and therefore we will not make that call. Ultimately it is your decision, its your money, so make sure you do the necessary background checks on the investment you are planning to do.
|
|
|
Those emails used to be very prompt. They only slowed down recently. I gotta agree... It was the main reason I did most of my trading on VCX is because they have the best, most informative, trade notifications, and they were always very responsive. Something has to be going wrong, this isn't their normal behavior. -- Smoov We had some issues with our mailer daemon, - for initially unexplained but now finally identified reasons - the email daemon died on us every day or other. We put in a temp fix and working on a permanent solution.
|
|
|
We will not be charging the Freicoin demurrage fee in the month of May, we'll be absorbing the cost. Demurrage will be charged from 1st June onwards.
|
|
|
Freicoin can now be traded on Vircurex.com
|
|
|
I would assume that you have a database with the user balances on your web server, otherwise how can the server be displaying account balances, etc.
Therefore if the hacker gets into your web server, logs on to the database, increases his own user balance and then withdraws via the standard appliction interface? To be on the safe side he probably deducts the amount he added to his account from another account just incase you match total wallet balance with total account balance.
|
|
|
Trade your FTC for BTC, LTC, USD, EUR, and many more on Vircurex.com
|
|
|
Feathercoin is now listed on Vircurex.
|
|
|
Name of Exchange: Virexa Developer/ Operator / Owner: Vircurex Objective: Provide a trading platform for coins that are to risky to put on any larger exchange yet, just think of double spend attacks, malicious code embedded in the source code, etc. Read the small print here BEFORE using the exchange: - due to the high risk nature of this trading platform, we (neither Virexa nor Vircurex) assume any liabilities on funds held on the Exchange.
In case of losses due to double spend attacks or other security breaches, the losses will be shared proportionally among all account holders. - we will not be providing any sophisticated features at this point in time, i.e. no API, no eMail notifications, no 2FA, etc, though it may come in the future
- once currencies make it past a "comfort" level, we will delist it on Virexa and relist it on Vircurex. There will be no account transfers or any link between the two changes. All fund movements will need to be initiated by the account holder and will pass through the blockchains.
- the Exchange will be a test bed for various new technological changes we plan to implement on Vircurex, hence trading might be affected from time to time
- all support on the platform is on a best effort basis.
PS: The Exchange is still under development, and as such any or all statements above might change, up to a level that we might cancel the whole project.
|
|
|
I compiled the wallet from the source on Github. All well, got the binary, but when I start up the daemon I get the following message: Error: An error occured while setting up the RPC port 8994 for listening: Address family not supported by protocol
Any clues what's wrong here?
PS: Compiling on Ubuntu.
|
|
|
My PPC Wallet goes down like every other day since about a week. Anyone else observing similar issues?
|
|
|
System is currently down for an unplanned maintenance.
|
|
|
Works now, I did: install libupnp-dev set USE_UPNP:=- int the makefile instead of uncommenting the line.
|
|
|
Trying to compile Bytecoin on Ubuntu leaves me with the error message :
init.cpp:644:15: error: operator '!' has no right operand
This error appears on Ubuntu 11.04 as well as Ubuntu 12.04.
Any ideas?
|
|
|
|