This doesn't seem to be Bittrex "fault"
Topic: [$XVG] VERGE [POW][MultiAlgo][TOR/i2P][no premine/ico!] - page 537. (Read 843777 times)
thats lame...
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
That is annoying. I Dont see why we can't cancel them.
if a site does anything like this to me twice i no longer use that exchange or service. i tried playing at a crypto casino (which i won't promote, but the last 2 letters of their URL are: ag) and both times after requesting a withdrawal they waited until i contacted their support before they would actually process the withdrawal. What if there's a crash in 10 minutes and i get word of it and want to sell before my coins are worth less, but instead they are frozen in an order on a site for whatever good reason?
thats lame...
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
That is annoying. I Dont see why we can't cancel them.
You have to get onto bittrex about that one !!
thats lame...
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
That is annoying. I Dont see why we can't cancel them.
electrum server (for android wallets) should be back up within an hour or so, its resyncing now.
so we got pwned?!
no, they tried to submit their own blocks but failed.
My android wallet has 0 balance what happened? All transaction history is also gone
Someone help I'm freaking out
there's nothing to freak about, just be patient. they are probably working on an update that we will have to download.
so we got pwned?!
no, they tried to submit their own blocks but failed.
My android wallet has 0 balance what happened? All transaction history is also gone
Someone help I'm freaking out
there's nothing to freak about, just be patient. they are probably working on an update that we will have to download.
so we got pwned?!
no, they tried to submit their own blocks but failed.
My android wallet has 0 balance what happened? All transaction history is also gone
Someone help I'm freaking out
so we got pwned?!
no, they tried to submit their own blocks but failed.
My android wallet has 0 balance what happened? All transaction history is also gone
so we got pwned?!
no, they tried to submit their own blocks but failed.
how would they even try this? arp-replay on already captured and sent packets?
so we got pwned?!
no, they tried to submit their own blocks but failed.
My android wallet shows 0 coinso what happened to them also says no connection
so we got pwned?!
no, they tried to submit their own blocks but failed.
so we got pwned?!
no it was an unsuccessful attack. but i bet there's prolly gonna be a dump on bittrex as soon as trading resumes and they wont let me cancel my order so i guess i'm the one getting dumped on.
so we got pwned?!
thats lame...
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
should be fine shortly.
thats lame...
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
i wish i could at least cancel my open orders. now i have 10.6 btc on verge order thats just stuck in limbo. at least let me cancel order so i can buy some doge or something.....
I do 2fa on most... (tho it depends on how they have it setup)
one site i couldnt. it must be able to TXT me. not that authenticator crap.(i cant use)
Raspberrypi...i forgot that was done. i remember it was being worked on. then...my mind is blank
To many things going on. ill check now , thanks
one site i couldnt. it must be able to TXT me. not that authenticator crap.(i cant use)
Raspberrypi...i forgot that was done. i remember it was being worked on. then...my mind is blank
To many things going on. ill check now , thanks
i save all my coins at local wallet
when me want to sell it
ill sent it to exchange
all markets enable 2fa
Hi
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
not that i am aware of. someone (maliciously) tried to submit blocks yesterday but failed. suprnova and blockexperts.com/xvg are on the correct block, as well as all our nodes.
new release will be out shortly, ill tweet you.
Has Bittrex given anytime frame on opening verge back up for trading ??
i just pm'd them n asked them to git pull our latest commits n sync. we'll see. not sure if theyre up still. either way, new release is just around the corner, so im not sweating it.
someone attacked our network again and again
im waiting multi-algo switch
Hi
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
not that i am aware of. someone (maliciously) tried to submit blocks yesterday but failed. suprnova and blockexperts.com/xvg are on the correct block, as well as all our nodes.
new release will be out shortly, ill tweet you.
Has Bittrex given anytime frame on opening verge back up for trading ??
i just pm'd them n asked them to git pull our latest commits n sync. we'll see. not sure if theyre up still. either way, new release is just around the corner, so im not sweating it.
Hi
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
I'm running verge(dogecoindark) mining pool, and had to stop pool due to sync problem.
Verge sync process seems have some bug.
When I start the wallet from scratch, it works quite well. rpc port opened, can sync upto the right blockchain height.
But when I restart the wallet after that, it doesn't work as before, rpc port not opened, debug.log just saying
"Loading block index..."
I tried this two times both from height 0, -reindex. One with our old wallet.dat, and one with fresh new wallet.dat just regenerated.
All two situation results same problem.
I'm using the latest version from github trunk.
Interestingly, dogecoindark, and verge both consumed too much CPU from two weeks ago. Did some malformed data inserted to blockchain at that time?
not that i am aware of. someone (maliciously) tried to submit blocks yesterday but failed. suprnova and blockexperts.com/xvg are on the correct block, as well as all our nodes.
new release will be out shortly, ill tweet you.
Has Bittrex given anytime frame on opening verge back up for trading ??
Jump to: