[XMR] Monero - A secure, private, untraceable cryptocurrency

[bitkolik]

With a friendly platform makes me very confident with the future of Monero, maybe now Monero is still the second or third choice of most people, but for me Monero is the first choice, next year the price will raise at least $300...

[pehoko]

the wallet is really bad. it's pretty confusing using this on windows..

Agree - worst working cryptocurrency GUI wallet I have ever seen, but your problems will be solved with community support, be patient or try CLI - seems better working.

[notbatman]

Hi, Monroe Community, ...[REDACTED]...

Greetings!!!

[Chicken_76]

I have sigs turned off, so I can't see, but assume this is another farmer.  This shit is getting out of control on this forum.  2 and 3 posts per minute, continuously. W.T.F.

Farmer?

[Mefestofel_Mefis]

...and the guy who speaks publicly For Monero lies to the public to pump his coin and get rich (FluffyPonzi). I'm never touching Monero no matter how good its privacy is.

[garytheasshole]

...and the guy who speaks publicly For Monero lies to the public to pump his coin and get rich (FluffyPonzi). I'm never touching Monero no matter how good its privacy is.

Such analysis, Bravo *clap* *clap* *clap*

[explorer]

I have sigs turned off, so I can't see, but assume this is another farmer.  This shit is getting out of control on this forum.  2 and 3 posts per minute, continuously. W.T.F.

Farmer?

Satoshi farmer - signature campaigns

[Chicken_76]

OK, here's a more technical question: what filesystems would be better suited to hold the blockchain on *NIX OSes and how would you configure them for optimal performance if they were mainly used to store the blockchain?
I'm guessing CoW filesystems such as ZFS and btrfs aren't particularly good choices, though I don't have any data to support this hunch.

[semiwylson]

how do you thing what price of XMR we may have in the end of the year?

[Hueristic]

Monero is still a really good currency and the updates to make it private will make me invest in it more.

Monero has never been updated to make it private, are you in the wrong thread or are you just a spammer?

...and the guy who speaks publicly For Monero lies to the public to pump his coin and get rich (FluffyPonzi). I'm never touching Monero no matter how good its privacy is.

Thank you for dropping in and letting us know that you will never own this coin, do you do that for every coin or are we just Special?

OK, here's a more technical question: what filesystems would be better suited to hold the blockchain on *NIX OSes and how would you configure them for optimal performance if they were mainly used to store the blockchain?
I'm guessing CoW filesystems such as ZFS and btrfs aren't particularly good choices, though I don't have any data to support this hunch.

I'm not up on the latest partitioning types but what you want to choose is the least corruptible and most stable as well as recoverable of them all. Speed between all of them is pretty negligible in the real world. Also make sure you choice is future proof for drive sizing as you'll want to migrate that partition one day if you do it right the first time.

[TheFuzzStone]

how do you thing what price of XMR we may have in the end of the year?

Sorry man, Grandmother Vanga is dead so can't tell you anything about Monero price, accept that speculation thread is here

Thank you for dropping in and letting us know that you will never own this coin, do you do that for every coin or are we just Special?

LOL, that was nice 

[Chicken_76]

OK, here's a more technical question: what filesystems would be better suited to hold the blockchain on *NIX OSes and how would you configure them for optimal performance if they were mainly used to store the blockchain?
I'm guessing CoW filesystems such as ZFS and btrfs aren't particularly good choices, though I don't have any data to support this hunch.

I'm not up on the latest partitioning types but what you want to choose is the least corruptible and most stable as well as recoverable of them all. Speed between all of them is pretty negligible in the real world. Also make sure you choice is future proof for drive sizing as you'll want to migrate that partition one day if you do it right the first time.

I'm thinking as time goes by and the blockchain becomes bigger and bigger, the choice of filesystem for a node that handles many connections (open daemon for unlimited wallets) is going to be increasingly more important. You raise two points:

1. data integrity. For this copy-on-write filesystems are unmatched.

2. performance relative to one another being negligible. I beg to differ. Different filesystems handle fragmentation differently and that adds to the significant number of random reads for a node that has to handle a large number of wallet connections. For this I think filesystems without journal like ext2 might be fastest.

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

[garytheasshole]

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

rescan_bc

[dEBRUYNE]

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

rescan_bc

That's a wallet command.

@Chicken_76. You'd have to check bitmonero.log for any errors. See here (at the bottom):

https://monero.stackexchange.com/questions/4462/my-blockchain-is-stuck-how-do-i-unstuck-it

[Chicken_76]

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

rescan_bc

I don't see that in the help:

Code:

help
Monero 'Helium Hydra' (v0.11.1.0-release)
Commands:
  alt_chain_info          Print information about alternative chains
  ban                     Ban a given IP for a time
  bans                    Show the currently banned IPs
  bc_dyn_stats            Print information about current blockchain dynamic state
  diff                    Show difficulty
  exit                    Stop the daemon
  flush_txpool            Flush a transaction from the tx pool by its txid, or the whole tx pool
  hard_fork_info          Print hard fork voting information
  help                    Show this help
  hide_hr                 Stop showing hash rate
  is_key_image_spent      Prints whether a given key image is in the spent key images set, is_key_image_spent <key_image>
  limit                   limit <kB/s> - Set download and upload limit
  limit_down              limit <kB/s> - Set download limit
  limit_up                limit <kB/s> - Set upload limit
  out_peers               Set max number of out peers
  output_histogram        Print output histogram (amount, instances)
  print_bc                Print blockchain info in a given blocks range, print_bc <begin_height> [<end_height>]
  print_block             Print block, print_block <block_hash> | <block_height>
  print_cn                Print connections
  print_coinbase_tx_sum   Print sum of coinbase transactions (start height, block count)
  print_height            Print local blockchain height
  print_pl                Print peer list
  print_pl_stats          Print peer list stats
  print_pool              Print transaction pool (long format)
  print_pool_sh           Print transaction pool (short format)
  print_pool_stats        Print transaction pool statistics
  print_status            Prints daemon status
  print_tx                Print transaction, print_tx <transaction_hash>
  q                       ignored
  relay_tx                Relay a given transaction by its txid
  save                    Save blockchain
  set_log                 set_log <level>|<categories> - Change current loglevel, <level> is a number 0-4
  show_hr                 Start showing hash rate
  start_mining            Start mining for specified address, start_mining <addr> [<threads>] [do_background_mining] [ignore_battery], default 1 thread, no background mining
  start_save_graph        Start save data for dr monero
  status                  Show status
  stop_daemon             Stop the daemon
  stop_mining             Stop mining
  stop_save_graph         Stop save data for dr monero
  sync_info               Print information about blockchain sync state
  unban                   Unban a given IP
  update                  subcommands: check (check if an update is available), download (download it if there is), update (not implemented)

[Chicken_76]

rescan_bc

That's a wallet command.

@Chicken_76. You'd have to check bitmonero.log for any errors. See here (at the bottom):

https://monero.stackexchange.com/questions/4462/my-blockchain-is-stuck-how-do-i-unstuck-it

For a dedicated server that would be quite inconvenient. You would have to run something that scans the log file for that error, and on finding one, script a daemon stop, delete blockchain and daemon start.

Here's a proposal for a new daemon feature: a command that would pause syncing, scan the blockchain for corruption and in case there is some, delete every block starting with the first corrupted one and resync from that point. What do you guys think, is it worth adding? Unfortunately I have no C++ skills, or I would have added this myself. 

[Hueristic]

I'm thinking as time goes by and the blockchain becomes bigger and bigger, the choice of filesystem for a node that handles many connections (open daemon for unlimited wallets) is going to be increasingly more important. You raise two points:

1. data integrity. For this copy-on-write filesystems are unmatched.

2. performance relative to one another being negligible. I beg to differ. Different filesystems handle fragmentation differently and that adds to the significant number of random reads for a node that has to handle a large number of wallet connections. For this I think filesystems without journal like ext2 might be fastest.

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

I would think God created ECC memory and parity drives for data integrity and you will always lose speed with security and integrity being your number one priority you cannot have both that is just the nature of the beast. The partitions are the lowest denominator that really has less bearing then benchmarks would have you believe.

I challenge you to setup multiple partitions and do a weeks real world comparison and doubt there would be any noticeable speed difference. Anyway I have been out of the industry for 17 years and have no desire to research a more specific answer for you but my previous years as a Senior Hardware Engineer is probably good enough for your purposes.

Thank you for dropping in and letting us know that you will never own this coin, do you do that for every coin or are we just Special?

LOL, that was nice 

[smooth]

By the way, what is a sure way to identify blockchain corruption? Is there a command to make the daemon recheck all the blocks?

When your node gets forked off the network. Since the entire network is synchronized and massively replicated, there is enormous redundancy and inherent error checking.

There is no real need to introduce additional redundancy or error checking at the node layer, although for a high availability service you might want to run multiple nodes and introduce some middleware to ensure they are in sync.

[Gekkoo]

Monero will be the next to show off his great strength and get great prices! I have some Monero and there is no reason to sell.

[bitcrypto10101]

Monero will be the next to show off his great strength and get great prices! I have some Monero and there is no reason to sell.

Of course. Hold is the key to success.