I hope that normalize soon. 
Topic: [ANN][EXCHANGE] Poloniex - Crypto Exchange with BTC/NXT - page 151. (Read 272454 times)
I can't login since yesterday. I hope that normalize soon.
I hope that normalize soon.
Fucking ddosers. I'm missing tons of opportunities right now. fuck
If the site is under DDOS he is not going to correct anything , its not a bug , its massive spam of requests to the server .
And i don't know if DDOS protection softs exist
And i don't know if DDOS protection softs exist
Not soft but service, like Cloudflare, Incapsula, etc.
If the site is under DDOS he is not going to correct anything , its not a bug , its massive spam of requests to the server .
And i don't know if DDOS protection softs exist
And i don't know if DDOS protection softs exist
Yes very slow and error 500 now when logging in,,,hope they get corrected soon! I need my BTC and to sell some more coinage! 
yeah i think under DDOS
Poloniex still down........................................
Works for me...
But very slowly. Maybe dossed?
Down for me again
Poloniex still down........................................
Works for me...
But very slowly. Maybe dossed?
Poloniex still down........................................
Works for me...
Poloniex still down........................................
Hello Busoni, I lost quite a bit of BTC due to Counterparty Hacker,
will you kindly Release:
If you will not, then please say Why not?
will you kindly Release:
- the text of emails exchanged between you and the hacker + email headers;
- the email address he used on poloniex;
- the IP address used in poloniex
If you will not, then please say Why not?
please add MYR/BTC
2014 best innovative coin！
https://bitcointalksearch.org/topic/annxmy-myriad-multi-algo-fair-secure-483515
2014 best innovative coin！
https://bitcointalksearch.org/topic/annxmy-myriad-multi-algo-fair-secure-483515
Bleh. Waiting on BTCs. Damn you rescans!!!
At this point, I believe I have gotten to all support tickets, so please submit another if you're still missing something.
it tooks you quite a time
so now it's time to say "Sorry" ... i just recieved my funds ... will edit my postings !
Next time please, be more communicative !
thanks
Bleh. Waiting on BTCs. Damn you rescans!!!
At this point, I believe I have gotten to all support tickets, so please submit another if you're still missing something.
Bleh. Waiting on BTCs. Damn you rescans!!!
Received my bitcoins. Thanks Busoni. I really was hoping it wasn't a scam. You know how it is with this. This is the wild west of the internet and people make off with money every day. So no harm done. I will continue to trade on poloniex.
Yeah! I want to see Myriad coin (MYR) on Poloniex too.
THIS!! MYR!!!
agree.
I receive my bitcoin
Uy. I guess I won't go another day without checking this thread.
I have been very busy answering tickets and resolving issues. There are still a few open with missing withdrawals, and I'm getting to them as fast as I can.
As I said, if you send too many transactions in too short a space of time, something goes wrong and the transactions are invalid. I did not know how many were invalid, though, because they all got txids. Yesterday, thinking I had resent most of the missing withdrawals, I spent several hours getting the trading API finished, as people have been asking about that a lot.
Then I come back to support and see loads and loads of tickets and emails. Now, I understand your coins are missing, and it isn't your fault... but when you submit several tickets and send the same request to the email address, you slow things down. Really. I have to check each one and find it's a duplicate. I estimate I could have taken care of literally twice the number of tickets if people had only submitted one for each problem.
At first, there were only a few complaints of unconfirmed withdrawals, and I didn't know why. I wanted to give them a bit of time before resending, because the Bitcoin client will keep trying to submit transactions that aren't getting confirmations, and I didn't want withdrawals to be sent twice. This is what caused the initial delay.
I spent a good portion of this evening setting the wallet in order (deleting all transactions and rescanning) and resigning the withdrawal daemon to used "sendmany" instead of "sendtoaddress". I will now see if I can finish up with the tickets related to missing withdrawals.
About the XCP issues, I will post here about it if people want. All the communication has so far been done in the Counterparty thread. Some quick facts (which have been posted there):
Total missing BTC: 120. Missing BTC will be paid off as funds are raised from community donations and the 2.5% trading fee on the BTC/XCP market. Additionally, the developers made a sizable donation, and I will be contributing some of my own funds.
I imagine I have missed a lot over in the Counterparty thread, so I will check back here after I've caught up over there.
If anyone still has questions, please ask--but please do not ask for technical support here.
I have been very busy answering tickets and resolving issues. There are still a few open with missing withdrawals, and I'm getting to them as fast as I can.
As I said, if you send too many transactions in too short a space of time, something goes wrong and the transactions are invalid. I did not know how many were invalid, though, because they all got txids. Yesterday, thinking I had resent most of the missing withdrawals, I spent several hours getting the trading API finished, as people have been asking about that a lot.
Then I come back to support and see loads and loads of tickets and emails. Now, I understand your coins are missing, and it isn't your fault... but when you submit several tickets and send the same request to the email address, you slow things down. Really. I have to check each one and find it's a duplicate. I estimate I could have taken care of literally twice the number of tickets if people had only submitted one for each problem.
At first, there were only a few complaints of unconfirmed withdrawals, and I didn't know why. I wanted to give them a bit of time before resending, because the Bitcoin client will keep trying to submit transactions that aren't getting confirmations, and I didn't want withdrawals to be sent twice. This is what caused the initial delay.
I spent a good portion of this evening setting the wallet in order (deleting all transactions and rescanning) and resigning the withdrawal daemon to used "sendmany" instead of "sendtoaddress". I will now see if I can finish up with the tickets related to missing withdrawals.
About the XCP issues, I will post here about it if people want. All the communication has so far been done in the Counterparty thread. Some quick facts (which have been posted there):
Total missing BTC: 120. Missing BTC will be paid off as funds are raised from community donations and the 2.5% trading fee on the BTC/XCP market. Additionally, the developers made a sizable donation, and I will be contributing some of my own funds.
I imagine I have missed a lot over in the Counterparty thread, so I will check back here after I've caught up over there.
If anyone still has questions, please ask--but please do not ask for technical support here.
I am glad you find the issue and has been addressed, keep it good and going...
Uy. I guess I won't go another day without checking this thread.
I have been very busy answering tickets and resolving issues. There are still a few open with missing withdrawals, and I'm getting to them as fast as I can.
As I said, if you send too many transactions in too short a space of time, something goes wrong and the transactions are invalid. I did not know how many were invalid, though, because they all got txids. Yesterday, thinking I had resent most of the missing withdrawals, I spent several hours getting the trading API finished, as people have been asking about that a lot.
Then I come back to support and see loads and loads of tickets and emails. Now, I understand your coins are missing, and it isn't your fault... but when you submit several tickets and send the same request to the email address, you slow things down. Really. I have to check each one and find it's a duplicate. I estimate I could have taken care of literally twice the number of tickets if people had only submitted one for each problem.
At first, there were only a few complaints of unconfirmed withdrawals, and I didn't know why. I wanted to give them a bit of time before resending, because the Bitcoin client will keep trying to submit transactions that aren't getting confirmations, and I didn't want withdrawals to be sent twice. This is what caused the initial delay.
I spent a good portion of this evening setting the wallet in order (deleting all transactions and rescanning) and resigning the withdrawal daemon to used "sendmany" instead of "sendtoaddress". I will now see if I can finish up with the tickets related to missing withdrawals.
About the XCP issues, I will post here about it if people want. All the communication has so far been done in the Counterparty thread. Some quick facts (which have been posted there):
Total missing BTC: 120. Missing BTC will be paid off as funds are raised from community donations and the 2.5% trading fee on the BTC/XCP market. Additionally, the developers made a sizable donation, and I will be contributing some of my own funds.
I imagine I have missed a lot over in the Counterparty thread, so I will check back here after I've caught up over there.
If anyone still has questions, please ask--but please do not ask for technical support here.
I have been very busy answering tickets and resolving issues. There are still a few open with missing withdrawals, and I'm getting to them as fast as I can.
As I said, if you send too many transactions in too short a space of time, something goes wrong and the transactions are invalid. I did not know how many were invalid, though, because they all got txids. Yesterday, thinking I had resent most of the missing withdrawals, I spent several hours getting the trading API finished, as people have been asking about that a lot.
Then I come back to support and see loads and loads of tickets and emails. Now, I understand your coins are missing, and it isn't your fault... but when you submit several tickets and send the same request to the email address, you slow things down. Really. I have to check each one and find it's a duplicate. I estimate I could have taken care of literally twice the number of tickets if people had only submitted one for each problem.
At first, there were only a few complaints of unconfirmed withdrawals, and I didn't know why. I wanted to give them a bit of time before resending, because the Bitcoin client will keep trying to submit transactions that aren't getting confirmations, and I didn't want withdrawals to be sent twice. This is what caused the initial delay.
I spent a good portion of this evening setting the wallet in order (deleting all transactions and rescanning) and resigning the withdrawal daemon to used "sendmany" instead of "sendtoaddress". I will now see if I can finish up with the tickets related to missing withdrawals.
About the XCP issues, I will post here about it if people want. All the communication has so far been done in the Counterparty thread. Some quick facts (which have been posted there):
Total missing BTC: 120. Missing BTC will be paid off as funds are raised from community donations and the 2.5% trading fee on the BTC/XCP market. Additionally, the developers made a sizable donation, and I will be contributing some of my own funds.
I imagine I have missed a lot over in the Counterparty thread, so I will check back here after I've caught up over there.
If anyone still has questions, please ask--but please do not ask for technical support here.
Jump to: