|
Cryptopia will NOT be listing this scam
Thanks
Cryptopia Team
|
|
|
|
Very amateurish tactic from Cryptopia to Delist BECAUSE THEY CAN this coin.
This is unacceptable. I cant even keep myself calm right now
In WHAT RIGHT DO THEY DELIST WITHOUT WARNING A COIN , KEEPING THE WALLETS IN MAINTENANCE AFTER LETTING THE COIN PUMP TO 3X ?!?!
ARE YOU SERIOUS GUYS??!?!
And NO LAW CAN HARM THEM? IS THAT WHAT CRYPTOS IS ALL ABOUT??
If one exchange doesnt feel like it or CANT HANDLE COMMUNITY FAIR OR UNFAIR ACCUSATIONS , THEY CAN JUST DELIST A COIN SIMPLY BECAUSE THEY CAN?!?!?!??
JESUS IF THIS WOULD EVER HAPPEN IN THE REAL WORLD THE LAWSUITS WOULD FALL LIKE RAIN
I DEMAND AN OFFICIAL STATEMENT FROM SAFEX TEAM ON THIS
THIS WAS THE MOST UNPROFESSIONAL MOVE EVER AND COULD ONLY RESULT IN A MAJOR LOSS OF TRUST AND ACCOUNTS TO CRYPTOPIA IF THEY DONT TAKE THEIR ANNOUNCEMENT BACK.
VERY UNPROFESSIONAL AND UNETHICAL.
THIS COULD ALL BE AVOIDED IF THEY HAD ANNOUNCED YESTERDAY THAT THE WALLET IS IN MAINTENANCE BECAUSE OF THE BLOCKCHAIN UPDATING.
THIS NEVER HAPPENED.
THEY LET THE MARKET PUMP THE COIN.
THEN STOPPED THE MARKET IN ORDER TO PROTECT CONSUMERS..
THEN THEY FORCED A COIN DELISTING.
NO , CRYPTOPIA THIS WAS NOT HANDLED WELL AND YOU HAVE NO EXCUSE. NOT A FUCKING EXCUSE.
YOU HANDLED THE SITUATION IN A POOR UNETHICAL AND UNPROFESSIONAL MANNER SHOWING A GREAT DISRESPECT TO THE COMMUNITY.
shit like this is why it was delisted. |
|
|
|
Coin is only on yobit and trae satoshi....
Why coin is not listed in big exchange s like bittrex and ed
Cryptopia
Because HTML5 already fucked over Cryptopia and were delisted. They will NEVER be allowed back. |
|
|
|
@everyone
COIN SUPPLY RESOLUTION
Through the extremely talented skillsets and hard efforts of both b3coindev aka Joshafest, and Jamie Woodruff, the B3 Team is elated to announce that a solution to the “#1 wallet” has been devised. The #1 wallet, along with its associated wallets have had their assets tracked, and once this upgrade is in place the wallet is frozen and no funds can be transferred or otherwise recovered.
At block 78,000 of the network, we will be performing a hard fork which will immediately, and irrevocably remove the coins in these predetermined wallets from the circulating supply. Once the dust settles we will share the exact amount that was burned. In addition, the team has engineered safeguards in the codebase which will permanently prevent this scenario from ever occurring again.
Can we please have an explanation on why these funds have been frozen? Please don't ignore us!!! Thanks Cryptopia Team |
|
|
|
@everyone
COIN SUPPLY RESOLUTION
Through the extremely talented skillsets and hard efforts of both b3coindev aka Joshafest, and Jamie Woodruff, the B3 Team is elated to announce that a solution to the “#1 wallet” has been devised. The #1 wallet, along with its associated wallets have had their assets tracked, and once this upgrade is in place the wallet is frozen and no funds can be transferred or otherwise recovered.
At block 78,000 of the network, we will be performing a hard fork which will immediately, and irrevocably remove the coins in these predetermined wallets from the circulating supply. Once the dust settles we will share the exact amount that was burned. In addition, the team has engineered safeguards in the codebase which will permanently prevent this scenario from ever occurring again.
Can we please have an explanation on why these funds have been frozen? Thanks Cryptopia Team |
|
|
|
By the way, that jankekek's comment about cryptopia's deposits and withdrawals reminded me that there is indeed a problem with the interface of the site. When I open either the deposit or withdrawal history, I see a table with all the relevant data like "currency", "amount" etc. One of the most important columns in those tables is "transaction ID": when a withdrawal is "stuck", for example (ie it says "complete" but nothing arrived to the wallet after an hour of waiting), I copy the TX ID and paste it into a blockchain explorer to see what's going on with the transaction. Except cryptopia's tables are broken and they don't display TX ID's properly:  The only way to actually get the full TX ID is to export the table (and btw, your PDF's are also broken, although it is possible to copy the full TX ID from the PDF — it's just the formatting that is messed up there). I don't think that's how it's supposed to be, all the other exchanges I've been to don't have this kind of problem (and some better ones not only display the TX ID, but present it as a link to the blockchain explorer website so the user doesn't even have to copy/paste). The Datatables are not broken. if you copy the TxId it will copy the whole TxId not the truncated version |
|
|
|
There 2 way to use the Wallet 140106 on a Linux Server, you can compile it from the Git : git clone https://github.com/LIMXTEC/BitCore.git
./autogen.sh
./configure
make
or you can use the release Ubuntu release : cd
wget https://github.com/LIMXTEC/BitCore/releases/download/0.14.1.6/Xenial-0-14-1-6.tar.gz
tar xvf Xenial-0-14-1-6.tar.gz
mkdir .bitcore
cp bitcore.conf .bitcore/
./bitcored
If you use a new server there cant problem with old files, if you update a running maschine its better to do it like this : cd
cd .bitcore/
rm peers.dat
rm banlist.dat
rm -rf blocks/
rm -rf chainstate/   Sync Time on a new Server was like 3 Minutes and Block High is : "blocks": 22456 You dont need any addnode in your config file because the main nodes will spread the other ips to you, just connect with a small config file like its in the tar.gz file rpcallowip=127.0.0.1
rpcuser=RANDOMUSERNAME3402934803294823094
rpcpassword=RANDOMPASSWORDrgkdhfgkjdfhgkdjfghdfkjg
server=1
daemon=1
listen=1 That build made no difference, however I think I found the issue
There seems to be a few nodes on the network that are totally breaking sync, the only way we could sync was to find a good node an connect to it directly, to do this you need to set listen=0 in your bitcore.conf and replace "addnode" with "connect" to some nodes you know are synced.
e.g.
listen=0
connect=105.235.159.43
If we set listen=1 it stops syncing immediately, and will kill the wallet at block 3799 on resync, not sure if this information will help anyone else.
we use fresh vm's for new compiles (automated deploy) so old files are not the issue listen=1 breaks the wallet immediately, I just tried it again, even without addnodes, connect=xxx.xxx.xxx.xxx and listen=0 is the only fix we have found soon as we connect to one of those bad nodes, the syncing stops, all connection drop, then the wallet silently crashes |
|
|
|
New wallet does not sync
2017-07-30 10:44:39 UpdateTip: new best=a40fd316ef64321c4d916edbac1edf575ce33e5aef62f7d42afca596e0074fca height=3799 version=0x30000003 log2_work=53.841636 tx=7092 date='2017-05-19 04:16:33' progress=0.000002 cache=1.7MiB(6297tx) warning='100 of last 100 blocks have unexpected version'
2017-07-30 10:44:39 AddToWallet 15d1e8de01f1d7e567f4d430dccdf498cfa45b242012cc51887d805a8971f474
2017-07-30 10:44:39 AddToWallet 86b395a54876acc60128e93431fe2a9a7b9f041326c9b2e7209353e0cd3c7efe
Wallet crashes at block 3799 every time, and on restart starts syncing from scratch, then crashes at same spot any ideas??
Do you use the newest version 14-1-6 ? What is your OS? Please use this link for source download. https://github.com/LIMXTEC/BitCore/archive/master.zipsame OS (Xenial) as the last version before this update, after update the wallet would not sync, was stuck at 20906, so deleted the entire blockchain now we cant sync past 3799 Tried removing the wallet, same issue I compiled directly from the link provided in the support ticket "version": 140106, "protocolversion": 70015, "walletversion": 130000, We are unable to compile from an archive zip for obvious security reasons A final Xenial build isn't online. You can use this Source here https://github.com/LIMXTEC/BitCore/archive/master.zip or you wait. I going to ask Jon to build a new Xenial client. That build made no difference, however I think I found the issue There seems to be a few nodes on the network that are totally breaking sync, the only way we could sync was to find a good node an connect to it directly, to do this you need to set listen=0 in your bitcore.conf and replace "addnode" with "connect" to some nodes you know are synced. e.g. listen=0 connect=105.235.159.43 If we set listen=1 it stops syncing immediately, and will kill the wallet at block 3799 on resync, not sure if this information will help anyone else. |
|
|
|
New wallet does not sync
2017-07-30 10:44:39 UpdateTip: new best=a40fd316ef64321c4d916edbac1edf575ce33e5aef62f7d42afca596e0074fca height=3799 version=0x30000003 log2_work=53.841636 tx=7092 date='2017-05-19 04:16:33' progress=0.000002 cache=1.7MiB(6297tx) warning='100 of last 100 blocks have unexpected version'
2017-07-30 10:44:39 AddToWallet 15d1e8de01f1d7e567f4d430dccdf498cfa45b242012cc51887d805a8971f474
2017-07-30 10:44:39 AddToWallet 86b395a54876acc60128e93431fe2a9a7b9f041326c9b2e7209353e0cd3c7efe
Wallet crashes at block 3799 every time, and on restart starts syncing from scratch, then crashes at same spot any ideas??
Do you use the newest version 14-1-6 ? What is your OS? Please use this link for source download. https://github.com/LIMXTEC/BitCore/archive/master.zipsame OS (Xenial) as the last version before this update, after update the wallet would not sync, was stuck at 20906, so deleted the entire blockchain now we cant sync past 3799 Tried removing the wallet, same issue I compiled directly from the link provided in the support ticket "version": 140106, "protocolversion": 70015, "walletversion": 130000, We are unable to compile from an archive zip for obvious security reasons |
|
|
|
|
New wallet does not sync
2017-07-30 10:44:39 UpdateTip: new best=a40fd316ef64321c4d916edbac1edf575ce33e5aef62f7d42afca596e0074fca height=3799 version=0x30000003 log2_work=53.841636 tx=7092 date='2017-05-19 04:16:33' progress=0.000002 cache=1.7MiB(6297tx) warning='100 of last 100 blocks have unexpected version'
2017-07-30 10:44:39 AddToWallet 15d1e8de01f1d7e567f4d430dccdf498cfa45b242012cc51887d805a8971f474
2017-07-30 10:44:39 AddToWallet 86b395a54876acc60128e93431fe2a9a7b9f041326c9b2e7209353e0cd3c7efe
Wallet crashes at block 3799 every time, and on restart starts syncing from scratch, then crashes at same spot any ideas??
|
|
|
|
200 confirmations is horrible.
They just need it in order to get enough time to sell their coins if there is a pump so you cannot send your coins and profit.
I am out of cryptopia because of this practice.
If this is what people think we will just delist all coins with insecure networks |
|
|
|
Looks pretty dead to me....the occasional scammer trying to get rid of their coins shouting "we're massively undervalued" but no developer activity or any reasoning behind it. Would stay away from it..
LOL https://www.cryptopia.co.nz/Paytopia |
|
|
|
problems on cryptopia again ...when will pasl go to some other exchange
We are sorry you are having issues again, we will look into PASL and try find the issue you are having, but since this seems to be a common occurrence and we get the blame perhaps its time to part ways as this is affecting the reputation of both PASL and Cryptopia Poloniex also support PASC based coins so perhaps you can apply there as they may be able to list PASL and you wont have to use Cryptopia anymore otherwise I recommend withdrawing to your personal PASL wallets. Thanks |
|
|
|
|
Cryptopia has lost all connections and is unable to sync the chain
Logs just fill of:
connect() to 151.80.42.180:30104 failed after select(): Connection refused
connect() to 94.176.237.207:30104 failed after select(): Connection refused
connect() to 151.80.42.180:30104 failed after select(): Connection refused
connect() to 94.176.237.207:30104 failed after select(): Connection refused
connect() to 151.80.42.180:30104 failed after select(): Connection refused
connect() to 94.176.237.207:30104 failed after select(): Connection refused
connect() to 151.80.42.180:30104 failed after select(): Connection refused
Anyone have any nodes so we can get Crave back online, thanks
|
|
|
|
DEV!
Add to the TOP that need to use payment id on the exchange!
A habit I have sent without it and lost coins.
Login and create a support ticket and we can probably sort it out  https://www.cryptopia.co.nz/UserSupport |
|
|
|
Someone needs to help cryptopia fix the sprouts wallet. They are most likely going to "delist" it after they fix the wallet issue. copy and paste below to my ticket there.
we only have an issue with sprts wallet constantly crashing (30-40 times a day)
Perhaps you might be able to persuade these apparent numpties that they are experiencing an issue unique to them and to include the output from the debug log? Client version and host platform architecture are also sort of vaguely useful for remote diagnosis of locality-specific issues. Is anyone else's installation of the Sprouts client also crashing 30-40 times a day or is it just an issue for Cryptopia? Just a thought, ask them what value they have assigned to reservebalance. Cheers Graham Edit: added reservebalance suggestionNumpties, lol Ok, that just sealed the deal Good luck |
|
|
|
|
Show Posts
