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

[iCEBREAKER]

[ trolling of poor quality ]

Ooh, I wanna play 'feed the silly troll' too!

1) Name is intentionally lame for ironic hipster cred (*orders bright yellow Hulkamania tshirt*)
2) bitching in other threads is the point of bitcointalk
3) bitching about coins is the other point of bitcointalk
4) bitching in general is the overall point of bitcointalk
5) attacking other alts is an honored tradition of the sub
6) Monero doesn't need "innovated tech."  We have wild mustangs!
7) this is the same as number 3.  are you Rick "trouble counting past two" Perry?  Oops!
smiley face) We have official mascot; no need for official wallet.
9) wait, I missed the BBQ!?!  OMG
10) Monero is well distributed, directly into Risto's grubby paws
11) Monero has so little trade volume, who cares where it's at?
12) I missed the idol worship.  was it during the BBQ? sad face!1!!!1!
13) smug is the new humble; also - wild mustangs | your argument is invalid

[generalizethis]

I protest too much therefore I must be who I say I'm not.

Your perry woodin's, wanderlic's pseudo logic turned against you--Muuuhhahhahhaaaa  

[smoothie]

Figured some monero-aholics would be interested in this:

https://bitcointalk.org/index.php?topic=1123066.msg11881938#msg11881938

 

[elrippo]

Hy there,
in order to get MONERO on more exchanges, i did submit a coinvote on cryptopia.co.nz
Let's see what the moderators of the exchange will do in the next few weeks.

I'll keep you updated on this matter  

Hy ladies and gents  
[XMR] Monero is on voting at cryptopia.co.nz
If you have interest on getting Monero there, please vote, you can vote ONCE/DAY  

[newb4now]

Hy there,
in order to get MONERO on more exchanges, i did submit a coinvote on cryptopia.co.nz
Let's see what the moderators of the exchange will do in the next few weeks.

I'll keep you updated on this matter  

Hy ladies and gents  
[XMR] Monero is on voting at cryptopia.co.nz
If you have interest on getting Monero there, please vote, you can vote ONCE/DAY  

Thank you. Hope to see Monero on more exchanges soon
any updates for Cryptsy or BTC38?

[dEBRUYNE]

Worth a cross post:

What do you predict the XMR price will be once LMDB and the official GUI are released?

How close is LMDB to being tagged for official release? I have heard it has been very close for several months and doing well in testing

One key milestone is improving the meager performance of the first db implementation so the orphan rate doesn't shoot up and also so the node doesn't become impractical to use on low-end systems (which was part of the motivation for the database in the first place).

Good news! The excellent optimization work by Noodle Doodle (in some cases faster than the original in-memory version!) has been completed and a pull request was submitted moments ago: https://github.com/monero-project/bitmonero/pull/337

Additional testing will be needed and there are still a few loose ends but this is a major step toward the database being pushed out as a tagged build.

Bockchain:
1. Optim: Multi-thread long-hash computation when encountering groups of blocks.
2. Optim: Cache verified txs and return result from cache instead of re-checking whenever possible.
3. Optim: Preload output-keys when encoutering groups of blocks. Sort by amount and global-index before bulk querying database and multi-thread when possible.
4. Optim: Disable double spend check on block verification, double spend is already detected when trying to add blocks.
5. Optim: Multi-thread signature computation whenever possible.
6. Patch: Disable locking (recursive mutex) on called functions from check_tx_inputs which causes slowdowns (only seems to happen on ubuntu/VMs??? Reason: TBD)
7. Optim: Removed looped full-tx hash computation when retrieving transactions from pool ().
8. Optim: Cache difficulty/timestamps (735 blocks) for next-difficulty calculations so that only 2 db reads per new block is needed when a new block arrives (instead of 1470 reads).

Berkeley-DB:
1. Fix: 32-bit data errors causing wrong output global indices and failure to send blocks to peers (etc).
2. Fix: Unable to pop blocks on reorganize due to transaction errors.
3. Patch: Large number of transaction aborts when running multi-threaded bulk queries.
4. Patch: Insufficient locks error when running full sync.
5. Patch: Incorrect db stats when returning from an immediate exit from "pop block" operation.
6. Optim: Add bulk queries to get output global indices.
7. Optim: Modified output_keys table to store public_key+unlock_time+height for single transaction lookup (vs 3)
8. Optim: Used output_keys table retrieve public_keys instead of going through output_amounts->output_txs+output_indices->txs->output:public_key
9. Optim: Added thread-safe buffers used when multi-threading bulk queries.
10. Optim: Added support for nosync/write_nosync options for improved performance (*see --db-sync-mode option for details)
11. Mod: Added checkpoint thread and auto-remove-logs option.
12. *Now usable on 32-bit systems like RPI2.

LMDB:
1. Optim: Added custom comparison for 256-bit key tables (minor speed-up, TBD: get actual effect)
2. Optim: Modified output_keys table to store public_key+unlock_time+height for single transaction lookup (vs 3)
3. Optim: Used output_keys table retrieve public_keys instead of going through output_amounts->output_txs+output_indices->txs->output:public_key
4. Optim: Added support for sync/writemap options for improved performance (*see --db-sync-mode option for details)
5. Mod: Auto resize to +1GB instead of multiplier x1.5

ETC:
1. Minor optimizations for slow-hash for ARM (RPI2). Incomplete.
2. Fix: 32-bit saturation bug when computing next difficulty on large blocks.

[PENDING ISSUES]
1. Berkely db has a very slow "pop-block" operation. This is very noticeable on the RPI2 as it sometimes takes > 10 MINUTES to pop a block during reorganization.
   This does not happen very often however, most reorgs seem to take a few seconds but it possibly depends on the number of outputs present. TBD.
2. Berkeley db, possible bug "unable to allocate memory". TBD.

[NEW OPTIONS] (*Currently all enabled for testing purposes)
1. --fast-block-sync arg=[0:1] (default: 1)
   a. 0 = Compute long hash per block (may take a while depending on CPU)
   b. 1 = Skip long-hash and verify blocks based on embedded known good block hashes (faster, minimal CPU dependence)
2. --db-sync-mode arg=[[safe|fast|fastest]:[sync|async]:[nblocks_per_sync]] (default: fastest:async:1000)
   a. safe = fdatasync/fsync (or equivalent) per stored block. Very slow, but safest option to protect against power-out/crash conditions.
   b. fast/fastest = Enables asynchronous fdatasync/fsync (or equivalent). Useful for battery operated devices or STABLE systems with UPS and/or systems with battery backed write cache/solid state cache.
   Fast    - Write meta-data but defer data flush.
   Fastest - Defer meta-data and data flush.
   Sync    - Flush data after nblocks_per_sync and wait.
   Async   - Flush data after nblocks_per_sync but do not wait for the operation to finish.
3. --prep-blocks-threads arg=[n] (default: 4 or system max threads, whichever is lower)
        Max number of threads to use when computing long-hash in groups.
4. --show-time-stats arg=[0:1] (default: 1)
   Show benchmark related time stats.
5. --db-auto-remove-logs arg=[0:1] (default: 1)
   For berkeley-db only. Auto remove logs if enabled.

**Note: lmdb and berkeley-db have changes to the tables and are not compatible with official git head version.
   At the moment, you need a full resync to use this optimized version.

[PERFORMANCE COMPARISON]
**Some figures are approximations only.
Using a baseline machine of an i7-2600K+SSD+(with full pow computation):
1. The optimized lmdb/blockhain core can process blocks up to 585K for ~1.25 hours + download time, so it usually takes 2.5 hours to sync the full chain.
2. The current head with memory can process blocks up to 585K for ~4.2 hours + download time, so it usually takes 5.5 hours to sync the full chain.
3. The current head with lmdb can process blocks up to 585K for ~32 hours + download time and usually takes 36 hours to sync the full chain.

Averate procesing times (with full pow computation):
lmdb-optimized:
1. tx_ave = 2.5 ms / tx
2. block_ave = 5.87 ms / block
memory-official-repo:
1. tx_ave = 8.85 ms / tx
2. block_ave = 19.68 ms / block
lmdb-official-repo (0f4a036)
1. tx_ave = 47.8 ms / tx
2. block_ave = 64.2 ms / block

**Note: The following data denotes processing times only (does not include p2p download time)
lmdb-optimized processing times (with full pow computation):
1. Desktop,  Quad-core / 8-threads 2600k  (8Mb) - 1.25 hours processing time (--db-sync-mode=fastest:async:1000).
2. Laptop,   Dual-core / 4-threads U4200  (3Mb) - 4.90 hours processing time (--db-sync-mode=fastest:async:1000).
3. Embedded, Quad-core / 4-threads Z3735F (2x1Mb) - 12.0 hours processing time (--db-sync-mode=fastest:async:1000).

lmdb-optimized processing times (with per-block-checkpoint)
1. Desktop,  Quad-core / 8-threads 2600k  (8Mb) - 10 minutes processing time (--db-sync-mode=fastest:async:1000).

berkeley-db optimized processing times (with full pow computation)
1. Desktop, Quad-core / 8-threads 2600k  (8Mb) - 1.8 hours processing time (--db-sync-mode=fastest:async:1000).
2. RPI2. Improved from estimated 3 months() into 2.5 days (*Need 2AMP supply + Clock:1Ghz + [usb+ssd] to achieve this speed) (--db-sync-mode=fastest:async:1000).

berkeley-db optimized processing times (with per-block-checkpoint)
1. RPI2. 12-15 hours (*Need 2AMP supply + Clock:1Ghz + [usb+ssd] to achieve this speed) (--db-sync-mode=fastest:async:1000).

[elrippo]

Hy there,
in order to get MONERO on more exchanges, i did submit a coinvote on cryptopia.co.nz
Let's see what the moderators of the exchange will do in the next few weeks.

I'll keep you updated on this matter  

Hy ladies and gents  
[XMR] Monero is on voting at cryptopia.co.nz
If you have interest on getting Monero there, please vote, you can vote ONCE/DAY  

Thank you. Hope to see Monero on more exchanges soon
any updates for Cryptsy or BTC38?

You are welcome 
Take a look at https://www.cryptsy.com/coinvotes
BTC38 -> write a mail to their support with the wish to get Monero listed 

[child_harold]

[ trolling of poor quality ]

Ooh, I wanna play 'feed the silly troll' too!
…

Not one of my better posts admitedly. Too much use of the word bitching. I will re-phrase:

My problem with XMR is that you have not innovated tech and have no GUI wallet, and yet you satisfy yourselves by bashing Bytecoin and present yourselves as the only option when your scam assertions (while intriguing) remain unproven and Bytecoin continue to push development faster than you. If BCN continue to push development faster than you this will become increasingly embarrasing for Monero and your cries of "premine!" will, for better or worse, fall on deaf ears. Bytecoin have a very slick product which is about to get slicker. You're not out of the woodin yet.

[TheKoziTwo]

[ trolling of poor quality ]

Ooh, I wanna play 'feed the silly troll' too!
…

Not one of my better posts admitedly. Too much use of the word bitching. I will re-phrase:

My problem with XMR is that you have not innovated tech and have no GUI wallet, and yet you satisfy yourselves by bashing Bytecoin and present yourselves as the only option when your scam assertions (while intriguing) remain unproven and Bytecoin continue to push development faster than you. If BCN continue to push development faster than you this will become increasingly embarrasing for Monero and your cries of "premine!" will, for better or worse, fall on deaf ears. Bytecoin have a very slick product which is about to get slicker. You're not out of the woodin yet.

I'd argue that there is a major difference with incentives here. If you're going to work for free, where are you most likely to spend your time? In a company where you own 82% of the stocks, or in a company where you own maybe 0.1%?

Monero devs has to compete for the coins like everybody else. It's only natural that they can't spend as much time working for free as someone who, with roughly 82% premine, benefit massively from even minor price increases.

[papa_lazzarou]

@Myagui

Re: translation

https://bitcointalk.org/index.php?topic=563927.msg11884801#msg11884801

[child_harold]

[ trolling of poor quality ]

Ooh, I wanna play 'feed the silly troll' too!
…

Not one of my better posts admitedly. Too much use of the word bitching. I will re-phrase:

My problem with XMR is that you have not innovated tech and have no GUI wallet, and yet you satisfy yourselves by bashing Bytecoin and present yourselves as the only option when your scam assertions (while intriguing) remain unproven and Bytecoin continue to push development faster than you. If BCN continue to push development faster than you this will become increasingly embarrasing for Monero and your cries of "premine!" will, for better or worse, fall on deaf ears. Bytecoin have a very slick product which is about to get slicker. You're not out of the woodin yet.

I'd argue that there is a major difference with incentives here. If you're going to work for free, where are you most likely to spend your time? In a company where you own 82% of the stocks, or in a company where you own maybe 0.1%?

Monero devs has to compete for the coins like everybody else. It's only natural that they can't spend as much time working for free as someone who, with roughly 82% premine, benefit massively from even minor price increases.

Aren't the Monero Team full-time? Do they have day jobs? You are implying they'd be working harder/faster with a greater incentive. Could they be doing more? Is it true?

smooth spends an awful lot of time posting on BCT, not that I mind, I enjoy his posts. I assume that each dev holds more than 0.1% - thatd only be ~$4000! Dont they get donations too?

Im inclined to agree with your thought, BCN devs almost certainly do have a greater incentive. This means things may become more embarrassing for XMR as time continues which is regrettable since you're mostly a nice bunch of guys.

[myagui]

@Myagui

Re: translation

https://bitcointalk.org/index.php?topic=563927.msg11884801#msg11884801

Thanks for the heads up papa_lazzarou.  
I'm keeping an eye on translation developments both here and on the getmonero forums. I was not opening up a task just yet as the translation framework was still being put in place, but seeing as things are moving a bit faster at the moment, I'll make a post shortly.

Edit: Done. Now I suppose I need to wait for the respective task to be open, eventually accepted, and funding secured.
@GingerAle, please have a look?  Portuguese Translation
Not sure I'm following the expected procedure there 

[GingerAle]

@Myagui

Re: translation

https://bitcointalk.org/index.php?topic=563927.msg11884801#msg11884801

Thanks for the heads up papa_lazzarou.  
I'm keeping an eye on translation developments both here and on the getmonero forums. I was not opening up a task just yet as the translation framework was still being put in place, but seeing as things are moving a bit faster at the moment, I'll make a post shortly.

Edit: Done. Now I suppose I need to wait for the respective task to be open, eventually accepted, and funding secured.
@GingerAle, please have a look?  Portuguese Translation
Not sure I'm following the expected procedure there 

Yeah, thats spot on - however, my OP was off... so I edited it. Basically you have to post in the Open Tasks section. It helps tidy things up - for instance, that particular idea thread has a lot of noise.

eventually we'll iron this out

[myagui]

Done and done 
ty GingerAle!

[kazuki49]

**Note: lmdb and berkeley-db have changes to the tables and are not compatible with official git head version.
   At the moment, you need a full resync to use this optimized version.

Using a baseline machine of an i7-2600K+SSD+(with full pow computation):
1. The optimized lmdb/blockhain core can process blocks up to 585K for ~1.25 hours + download time, so it usually takes 2.5 hours to sync the full chain.

^This is why a new tagged release can not be rushed and wow awesome optimizations, this is very fast sync with extreme low RAM usage.

[medusa13]

huge commit from Noodle, a lot of respect for your work, thank you!

may i ask if david is still active? never seen him since we toped out  

also good to see warptanget commiting, love you all 

[smooth]

huge commit from Noodle, a lot of respect for your work, thank you!

may i ask if david is still active? never seen him since we toped out  

David is still in active contact with the rest of the core team but at the moment he's quite busy with some other activities, as we all are from time to time.

[newb4now]

Is this a new Monero fiat exchange?
https://xstock.io/

Who owns it?
rpietila perhaps since I found it linked here
http://moneroinvestment.com/?page_id=19

I think we have at least 3 fiat exchanges now including MoneroClub and altquick

Monero can be promoted to those new to crypto without first needing to deal with BTC!

[smooth]

Aren't the Monero Team full-time? Do they have day jobs? You are implying they'd be working harder/faster with a greater incentive. Could they be doing more? Is it true?

Since you are new here I'll repeat what has been said consistently for the past year. None of us is specifically full time on Monero. We are all involved in other activities, mostly running businesses. We took on leading the Monero project as a volunteer effort because as community members we saw promising technology that was, and is, going nowhere because some people decided to launch it as a fraudulent premine scam.

Our primary role is to direct the project, set priorities, and coordinate the efforts of the community. Some of us also contribute coding, but not all of us are even coders at all, or don't have a large enough block of time available for coding to be a good use of our time. The bulk of the coding is done by community members who submit pull requests on github which we review and usually accept (sometimes with feedback, discussion and/or modification). One of those community members got some crowdfunding to work regularly on Monero, but most of the work is volunteer, or in support of other businesses or projects that are Monaro-related.

I don't know how you compare this in terms of "greater incentive", or "working harder/faster" since it is a completely different model.

smooth spends an awful lot of time posting on BCT, not that I mind, I enjoy his posts. I assume that each dev holds more than 0.1% - thatd only be ~$4000! Dont they get donations too?

Our holdings vary, but none are particularly enormous (though I certainly wouldn't call $4K enormous) None of the donations have ever gone to enrich the core team, they go to cover part of the project expenses, the rest of which has been covered by the core team out of our own pockets.

Im inclined to agree with your thought, BCN devs almost certainly do have a greater incentive. This means things may become more embarrassing for XMR as time continues which is regrettable since you're mostly a nice bunch of guys.

Nothing is going to become embarrassing, because coins with massive fraud in their histories are going absolutely nowhere over the longer term. Serious investors and developers won't go near them. Sure, altcoin speculators and fanboys on bitcointalk will play with them, but that ends the way every other once-hot-but-now-failed altcoin does.

[rpietila]

There was likely less than 10 interested ones for a Malla XMR conference. So regrettably we won't be having one.

Luckily, though, Malla Summer Camp is constantly ongoing 20 July - 21 August, with me, my family, friends, relatives, and local gold/silver/BTC/XMR people attending for shorter and longer durations. If you request invitation, PM me