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

Then that's not the protocol's fault but that of the laziness of the user

Yep, that's a very good point. However, if BTC continues the current trend, XMR x100 will mean "only" 75x profit... :-/





On another note, did I miss a missive, or it didn't come at all? (Shouldn't they be every week?)

Original post is here

Monero Monday Missives

October 27th, 2014

Hello, and welcome to our sixteenth Monero Monday Missive!

Major Updates

1. We have made major strides in the initial database implementation (you'll recall from our last Missive that our first implementation will use LMDB), and it is very nearly ready for broader testing. Specifically: the new blockchain is working for most things, but there are bugs with certain aspects of block verification that need to be fixed before it can be more widely tested. If you are particularly intrepid you can already grab it here: https://github.com/tewinget/bitmonero/tree/blockchain and compile it, and thus assist in identifying areas where it breaks down, although such reports are probably best submitted as github issues to tewinget's repository to reduce duplication. Once these and any other major issues have been weeded out the next steps would involve a bit of refactoring, fix cross-platform nigglies, and open it up for general testing.

2. The testing of per-kb fees on testnet, too, has gone exceedingly well. We will be adding the functionality to simplewallet (previously it required manual creation) and hope to deploy that for general testing within the next week.

3. Kitware staff, Ben Boeckel in particular, have spent a lot of time completely reworking our CMake build system and bringing it up to best practices. The fruits of those efforts can be seen on the Pull Request currently undergoing testing: https://github.com/monero-project/bitmonero/pull/180 (feel free to checkout this PR if you'd like to test). Now that the build system is starting to come together in its final form, we are hoping to use it to tag and release 0.8.8.5 during the course of next week.

4. In order to more efficiently deal with changes in the on-disk wallet format we are moving away from the old serialised+encrypted .keys format, and have a new format which is effectively encrypted JSON. This change allows us to note the wordlist language in the wallet format (so that the "seed" command can reflect that choice) and allows for cross-platform compatibility of the .keys file, which we are sure is excellent news for anyone that moves wallets between operating systems and architectures. You can test this in PR 179.

5. There have been a constant string of improvements and changes to the forum software to make it more usable and useful. In particular, new comments in a thread are highlighted within that thread. Additionally, unread threads (or threads with new unread comments) are highlighted by having a green dot next to them. Both of these apply to logged in users only. If you haven't visited the forum, you are encouraged to do so: https://forum.monero.cc

Dev Diary

Core: LMDB implementation is rough but nearly working (details above). Worth testing cross-platform, least of all from a build perspective.

Core: since we have already had to perform the rather annoyingly complex task of offloading MoneroPulse checkpoint checks to a separate thread (so as not to tie anything up during checks) we have begun extending this to other parts of the core that could potentially be or currently are pain points. This does not include the flat-file blockchain saving, as that is going to be deprecated with the move to LMDB, so pools will just need to hang on and deal with that nuisance for a little bit longer.

Build: CMake is looking a lot cleaner and easier to grok. It also fixes cross-compile (see: http://www.cmake.org/Wiki/CMake_Cross_Compiling) which means that binaries for all our major supported platforms can be built on a single system.

Account: multilang wordlists are now inherent to the wallet/account, so that RPC and CLI calls that retrieve the mnemonic do so in the correct format. This has, in turn, necessitated moving away from the horrible serialised data format for account data. Since epee's JSON library is beyond redemption, we have opted to use RapidJSON instead (which is headers-only and thus straight in the source tree).

Until next week!

PS. this Missive has the very great honour of being the first one to be finalised and very nearly posted from the air

- updated by fluffypony

personally, I think BTC x100 is less likely than XMR x100, but that is just me speculating off course

Before the next btc bubble Monero will be usable by my fellow drooling masses.

Is btc going to explode 100x?  lol  This May I heard btc was going to be 5k in July.

I've given up dreams of being rich.  My dinner tonight is a peanut butter and jam sandwich.  Though it will contain fine French raspberry jam.

Yes that is correct. I think what he meant was something like: If you have your public address on your web site (along with your name) and use that same address for an (otherwise anonymous) exchange, then the exchange account can then be linked to you, not through the blockchain, but through the exchange's own records of your address matching the address on your website.

Even though somebody else knows that you own that address, they cannot see what is inside that address. You can send money from that address to another address. That would make it unlinkable.

If you buy your XMR on a centralized exchange, though, and the exchange keeps records of your withdrawals to that address, it could be linked back to your personal information if the exchange's records are ever disclosed.

Not a stupid question. It is possible and it is something we've discussed. There are a number of ways this could work, but here is one to think about: You could have multiple side chains just like the original except each with only a fraction of the transactions. In fact it is possible to imagine an almost arbitrary number of these. Some complications arise, but nothing that seems totally infeasible.

Interesting, huh?

Hello, and welcome to our sixteenth Monero Monday Missive!

Major Updates

1. We have made major strides in the initial database implementation (you'll recall from our last Missive that our first implementation will use LMDB), and it is very nearly ready for broader testing. Specifically: the new blockchain is working for most things, but there are bugs with certain aspects of block verification that need to be fixed before it can be more widely tested. If you are particularly intrepid you can already grab it here: https://github.com/tewinget/bitmonero/tree/blockchain and compile it, and thus assist in identifying areas where it breaks down, although such reports are probably best submitted as github issues to tewinget's repository to reduce duplication. Once these and any other major issues have been weeded out the next steps would involve a bit of refactoring, fix cross-platform nigglies, and open it up for general testing.

...SKIPPED...

PS. this Missive has the very great honour of being the first one to be finalised and very nearly posted from the air

- updated by fluffypony

Maybe a stupid question, but: Could side chains be used to mitigate scaling issues with a bloating block chain?

And the big difference with Bitcoin is that Monero is anonymous by default.

It is possible to extend Monero to include the facilities necessary for side chains.

Another thought: Would it be possible to implement side chains with Monero technology?

If you buy your XMR on a centralized exchange, though, and the exchange keeps records of your withdrawals to that address, it could be linked back to your personal information if the exchange's records are ever disclosed.

Does anyone here think monero could explode 100 times, during the next bitcoin bubble?

I've given up dreams of being rich.  My dinner tonight is a peanut butter and jam sandwich.  Though it will contain fine French raspberry jam.

There is more than one kind of Republican; the party is a three-legged stool.

The pro-business types are traditionally equated with fiscal conservatives, but have been deeply corrupted by crony capitalism despite most small enterprise owners still being honest.

The social conservatives are usually financially responsible unless they want to go to war against the enemies of Jesus, but they've Had Enough neocon foreign adventures for a while.  Having Johnny Biblethumper come home in a coffin with nothing to show for his sacrifice tends to do that.

The libertarians are by definition rock-ribbed beast-starvers; that wing of the party is now ascendent thanks to Ron/Rand Paul and their TEA (Taxed Enough Already) Party.

Given the disaster of Krugman's Obomanomics, many non-partisan voters now wish Romney and Ryan had been in charge for the last couple of years.

So we can hope for and reasonably expect the new Senate to reign in the crazy ZIRP/NIRP QE-Nth debt-monetization plunge-protection-team money printing crowd.

That (relative) austerity will tamp down the irrational exuberance of the stock market, and we may see money flowing back into hard assets like gold, BTC, and XMR.

Because Republicans have a great track record of fiscal responsibility? I think not. (More) divided government may have that effect though.