Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1572. (Read 4670972 times)

legendary
Activity: 2968
Merit: 1198
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S


Probably daemon crashing when you shutting down PC, try to run "exit" in a daemon CLI before restart.
Well, last night the PC has crashed... nothing I can do about it once a month its crashing. Probably running daemon which uses 3GB ram is the reason Sad

Run a RAM test. Replace the bad module if that's what it is. Bad RAM would definitely explain corruption of your blockchain.

full member
Activity: 243
Merit: 125
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S


Probably daemon crashing when you shutting down PC, try to run "exit" in a daemon CLI before restart.
Well, last night the PC has crashed... nothing I can do about it once a month its crashing. Probably running daemon which uses 3GB ram is the reason Sad

Don't you say you use 32-bit executables?!

With 64-bit exe, all seems nice. Although I always type "exit" at daemon prompt.

Devs are working on embedded database such as leveldb, with somewhat durability support against your monthly crashes.
legendary
Activity: 1151
Merit: 1001
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S


Probably daemon crashing when you shutting down PC, try to run "exit" in a daemon CLI before restart.
Well, last night the PC has crashed... nothing I can do about it once a month its crashing. Probably running daemon which uses 3GB ram is the reason Sad
legendary
Activity: 1596
Merit: 1030
Sine secretum non libertas
My blockchain is not corrupted since the beginning.
I start the daemon, I leave it sync, I make the transactions I need, I close nicely the wallet (exit), I close nicely the daemon (exit).

(But I agree the blockchain is huge and the deamon starts and stops very slowly, sometimes hangs too.)

But you're still a fish!

I ain't taking no advice from no fish with questionable emotional stability, no sir, not over the Internet, at least.
legendary
Activity: 1904
Merit: 1003
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S


Probably daemon crashing when you shutting down PC, try to run "exit" in a daemon CLI before restart.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S


My blockchain is not corrupted since the beginning.
I start the daemon, I leave it sync, I make the transactions I need, I close nicely the wallet (exit), I close nicely the daemon (exit).

(But I agree the blockchain is huge and the deamon starts and stops very slowly, sometimes hangs too.)
legendary
Activity: 1151
Merit: 1001
I'm using latest daemon for 50 days already. And thats 3rd time when blockchain is corrupted. Always after restart of PC and/or after daemon was offline for some hours.

PS: Wish I knew what is the common thing between dota and monero :S
legendary
Activity: 1904
Merit: 1003
Quote
  Initializing core...
 Loading blockchain...
 ERROR C:\Users\tom\Documents\GitHub\bitmonero\src\common/boost_serialization_helper.h:82 Exception at [unserialize_obj_from_file], what=array size too short
 Can't load blockchain storage from file, generating genesis block.
 ERROR ..\..\src\cryptonote_core\blockchain_storage.cpp:74 Failed to add genesis block to blockchain
 ERROR ..\..\src\cryptonote_core\cryptonote_core.cpp:120 Failed to initialize blockchain storage
 ERROR ..\..\src\daemon\daemon.cpp:164 Failed to initialize core
 Mining has been stopped, 0 finished

Any ideas, different than "download god damned 2GB blockchain?"

There are two pills:

1. http://blog.dota2.com/?l=english

2. http://monero.cc/downloads/monero.win.x64.latest.zip

You choose.
legendary
Activity: 1151
Merit: 1001
Quote
  Initializing core...
 Loading blockchain...
 ERROR C:\Users\tom\Documents\GitHub\bitmonero\src\common/boost_serialization_helper.h:82 Exception at [unserialize_obj_from_file], what=array size too short
 Can't load blockchain storage from file, generating genesis block.
 ERROR ..\..\src\cryptonote_core\blockchain_storage.cpp:74 Failed to add genesis block to blockchain
 ERROR ..\..\src\cryptonote_core\cryptonote_core.cpp:120 Failed to initialize blockchain storage
 ERROR ..\..\src\daemon\daemon.cpp:164 Failed to initialize core
 Mining has been stopped, 0 finished

Any ideas, different than "download god damned 2GB blockchain?"
sr. member
Activity: 263
Merit: 250
I don't have a user on HitBTC so I can't see the orderbooks, but as much as I like a good, funny, story with a lesson embedded in the consequences, if Kozi is right about the thickness, then he's also right about the fraud or bug. Unfortunately, life is often darker than the narratives we use to rationalize it. I'm (casually) waiting for an explanation as well.

Edit: Obligatory bait:

well almost happened to me on polo... was on a crappy coin and tought was on drk, so i almost bought 2k worth at last second i realized the curves where just not right, and saw i wasxnt on right coin.

Sounds like you were in the right place.
legendary
Activity: 1596
Merit: 1030
Sine secretum non libertas
measure twice, cut once
legendary
Activity: 2296
Merit: 1031
Yep, time to stop watching the price for another few months.
legendary
Activity: 3570
Merit: 1959
well almost happened to me on polo... was on a crappy coin and tought was on drk, so i almost bought 2k worth at last second i realized the curves where just not right, and saw i wasxnt on right coin.

thats what i meant. people fuck up. it's human nature. live and learn. glad you caught it before the burn! Cheesy
full member
Activity: 338
Merit: 100
https://eloncity.io/
well almost happened to me on polo... was on a crappy coin and tought was on drk, so i almost bought 2k worth at last second i realized the curves where just not right, and saw i wasxnt on right coin.
legendary
Activity: 3570
Merit: 1959
obviousely someone with lots of cash, else they would be here trying to explain,

most likely someone who saw the fall of xmr in graphs lately and attempted a mass buy over the top buy...

but then again not sure who has 6000$ to buy overpriced xmr .

from 0.003 to 0.8 its not possible to be a phat finger, its not a decimal place its a whole number, maybe a glitch where user tought he was on another coin.... and he wansnt...

Thats' what i was thinking. i mean if it was me, i'd never come here and admit i went full retard on a trade... i'd go cry and bury my head right?
full member
Activity: 338
Merit: 100
https://eloncity.io/
obviousely someone with lots of cash, else they would be here trying to explain,

most likely someone who saw the fall of xmr in graphs lately and attempted a mass buy over the top buy...

but then again not sure who has 6000$ to buy overpriced xmr .

from 0.003 to 0.8 its not possible to be a phat finger, its not a decimal place its a whole number, maybe a glitch where user tought he was on another coin.... and he wansnt...
sr. member
Activity: 264
Merit: 250
Having issues sending XMR to MintPal.
I tried using transfer 0,transfer 1 and even a lower amount of XMR keep getting an error.
I have updated to the latest wallet. Some help here please.



Do you suppose you might have an absurd amount of dust?

Not sure if I'm right, but the current beta version has a 'transfer_split' command available to automatically split larger TXes. It may also work on CLI... Smiley
legendary
Activity: 3570
Merit: 1959
Guys, can someone explain to me what happened on HitBTC earlier today that made the chart go crazy?
Someone realy bought all the way up to 0.08???

EDIT:
It seems so... Order book shows all trades up to 0.08... so wierd, why would someone do that...?

Oooops. Someone made a MAJOR mistake surely. 163 Moneros for 10 BTC  Shocked


I'm waiting for an official explanation.



Just curious, but from whom?

Well seeing as this is either a serious bug in their system or straight up fraud I expect hitbtc to provide an explanation.

Yep. The entire transaction was about 623 XMR in all. There's no way that was the entire order book from ~470k to 8000k.

Understood. but seriously. if you fat-finger a decimal point in a drunken trade, is the exchange liable for your fubar? Just curious/sayin/wonderin... Wink
This has nothing to do with a fat fingered user mistake. Either the exchange is putting up fake bids/asks that will vanish exactly when market order is executed thus leaving only the thin order book of legit orders to match with and once executed the fake bids/asks immediately are placed back (this would be fraud). The other alternative is that there is a bug of some sort in the matching engine. E.g a limit order set at 0.08 executes at that price instead of lower asks like it's supposed to. I'm not sure which it is, so it will be interesting to hear their response.

Last I checked (few hours ago) it took more than 100000 XMR to break 0.005. The volume is far less. There is no indication of this being legit.

One possible explanation could have been dark orders, but from what I can tell hitbtc don't have that. In other words, trades should be matched against the order book, and it's way too thick for a trade like this.

Ah ok, thanks i didn't read it that way, thanks for schooling me, and sorry to waste time! Smiley
legendary
Activity: 1722
Merit: 1217
Having issues sending XMR to MintPal.
I tried using transfer 0,transfer 1 and even a lower amount of XMR keep getting an error.
I have updated to the latest wallet. Some help here please.



Do you suppose you might have an absurd amount of dust?
legendary
Activity: 1552
Merit: 1047
Guys, can someone explain to me what happened on HitBTC earlier today that made the chart go crazy?
Someone realy bought all the way up to 0.08???

EDIT:
It seems so... Order book shows all trades up to 0.08... so wierd, why would someone do that...?

Oooops. Someone made a MAJOR mistake surely. 163 Moneros for 10 BTC  Shocked


I'm waiting for an official explanation.


Just curious, but from whom?

Well seeing as this is either a serious bug in their system or straight up fraud I expect hitbtc to provide an explanation.

Yep. The entire transaction was about 623 XMR in all. There's no way that was the entire order book from ~470k to 8000k.

Understood. but seriously. if you fat-finger a decimal point in a drunken trade, is the exchange liable for your fubar? Just curious/sayin/wonderin... Wink
This has nothing to do with a fat fingered user mistake. Either the exchange is putting up fake bids/asks that will vanish exactly when market order is executed thus leaving only the thin order book of legit orders to match with and once executed the fake bids/asks immediately are placed back (this would be fraud). The other alternative is that there is a bug of some sort in the matching engine. E.g a limit order set at 0.08 executes at that price instead of lower asks like it's supposed to. I'm not sure which it is, so it will be interesting to hear their response.

Last I checked (few hours ago) it took more than 100000 XMR to break 0.005. The volume is far less. There is no indication of this being legit.

One possible explanation could have been dark orders, but from what I can tell hitbtc don't have that. In other words, trades should be matched against the order book, and it's way too thick for a trade like this.
Jump to: