It doesn't matter if your address is known, as it's impossible (with our current cryptography) to analyse the blockchain and find transactions you were involved in. Even if that was possible it still wouldn't be disastrous, as all that can be observed are transactions you *may or may not* have been involved in (thanks to ring signatures). The only time multiple wallets are necessary are for separating your personal and business accounts, for instance, or for a company that wants each department to have its own address and accounts.

Sophia was one of the embedded databases we initially considered, but ultimately went for LMDB because it is better suited to our workloads (based on casual observation, it was impossible to test that theory at that stage;)

Ultimately we aren't preventing anyone from writing an additional implementation and submitting a PR, and we will at the very least have a BerkleyDB fall-back implementation for environments that don't play well with large MMAPs.

You only have one address in Monero. Since outputs use dual-key stealth addresses there's really no need to have multiple addresses in a single wallet:)

Unfortunately no, not possible.


Moore's law is a worthy discussion - the average Bitcoin transaction is 250 bytes, and Moore's law says that "it" doubles every 2 years (Moore's law is too slow to apply to everything, mind you, Kryder's law is typically applied to disk storage density, and that predicts 40tb drives costing $40 by the time we hit 2020). If we go solely based on Moore's law, though, we get January 2009 (Bitcoin genesis block) to today as around 6 years, so a transaction size growth of 3x = average Monero transaction size of 750 bytes.


Here's a similar, recent Bitcoin transactions: https://blockchain.info/tx/239a93ab087b57b6e4ab98a28030546e88c976bd5d66d2eae2bf311ada9d98b8

That transaction has 122 inputs and is 18.589kb. To give you some baseline, the 22.783kb Monero transaction has 12 inputs, but with a mixin of 28 that's a total of 336 signatures. It does seem that like-for-like Monero has smaller transactions - this Monero transaction with 5 inputs, no mixins, has a size of 763 bytes, this Bitcoin transaction with 5 inputs has a size of 816 bytes.


This is a tough one - which is more applicable? Kryder's law or Moore's? What about bandwidth?

The bottom line is this: Bitcoin's transaction size is only going to increase if privacy becomes an issue and people start using mixers or similar as a daily occurrence. Transactional privacy requires a trade-off. It's clear that ZeroCoin's trade-off is too large *right now*, but in 10 years time maybe even that will be acceptable. For the moment Monero's transaction size/privacy trade-off is at an acceptable ratio, and whilst we aren't blind to alternatives that may allow us to reduce the per-tx size we're also not going to chase a linear reduction. Our efforts at reducing size implication would be far better spent on finding a solution, in the future, to completely pruning the blockchain.

Unfortunately there are gaping holes in the whitepaper (gmaxwell has touched on some in this thread), not to mention the blockchain bloat that will be incurred by having all assets of every class on a single chain. It's definitely a step in the right direction, but unfortunately does not meet the design goals inherent in Monero for us to consider implementing it.

What operating system? And are you trying to connect to mainnet or testnet?

Hi Roman,

Very cool - I'll take a look at the whitepaper over the weekend, as will the rest of the Monero Research Lab (including surae;)

I see you've cross-posted this same message into three different sections of the forum - in order to avoid getting flagged for spam is it possible for you to pick a single post you'd like to use for further discussion?

Terrorists clearly need to play dice games too!

Who?

The only Isidor Zeuner I can find is this guy: https://de.linkedin.com/pub/isidor-zeuner/76/b39/604


I don't see much about his qualifications or his knowledge of cryptography.

My next go-to was to see if he had any papers on arXiv, but that seems to not be the case either: http://arxiv.org/find/all/1/all:+AND+Isidor+Zeuner/0/1/0/all/0/1

Incidentally, I agree that a review is beneficial, but let's not overstate someone's abilities and qualifications, ok?

xmrmonero.com is a MEW project and is not a core team project (that is not to say that we don't support it or contribute to it or whatever).

The only sanctioned, official forum is forum.monero.cc

We haven't even started development on the new RPC API calls:)

With git you don't commit to the main repo every 5 minutes, that would make it exceedingly difficult to coordinate work between contributors. So developers work in their own forks and branches, and then submit pull requests to the upstream (main) repo.

I can't speak to peripheral projects, but if you want to read some rationale for why we've gone down a certain route on monero.cc read this post which details why SendGrid reached the same conclusions we did (although they first had to make two missteps with Wikimedia and Wordpress first, which we've avoided) - https://sendgrid.com/blog/creating-sustainable-documentation-with-jekyll/

No, it's just something we use for aspects related to protocol and design development.

In case anyone is wondering, the full URI spec is here: http://monero.wikia.com/wiki/URI_formatting

That wikia also has the new RPC API spec, if anyone wants to modify / add before it gets ratified in the coming months. Same goes for the URI format.

Hi guys,

Just a little side project I've put together (the current Monero price in various fiat currencies, based on market depth and the BitPay rates)



You can access it at https://MoneroPric.es (such domain hack, much clever, wow)

JSON rates are at: https://moneropric.es/fiat.json

To go straight to a specific fiat currency (default is USD) you can just append it to the URL, eg. https://moneropric.es/EUR or https://moneropric.es/ZAR etc.

I am grabbing price history, and when I get a chance I will add graphs etc.

Fun. If you PM me I can get it setup on our infrastructure, forwarding to monero.cc, but you'll be unable to use it as your host mask on IRC (Freenode needs the reverse DNS / PTR records to match the forward DNS).

"He" Skyped in, but audio only.



Apparently the audio was terrible, they held the microphone to a laptop speaker.



Such technologiez.

Pics are via @bitcoinpotato on Twitter.

Yes - we're remerging/updating daemonize, working on RPC -> IPC (via 0MQ), beginning the refactor/extrapolation to libraries, and working on non-64-bit comparability. This is all directly related to the GUI effort

Plenty! I suggest you start by familiarising yourself with all the things Monero has done in 2014, here is our year in review report: https://forum.monero.cc/1/news-and-announcements/134/monday-monero-missives-22-year-in-review-january-5th-2015

Here's a counter-point: http://infosecurity.ch/20100926/not-every-elliptic-curve-is-the-same-trough-on-ecc-security/

According to that the only safe curves are NIST P-256 and NIST P-384. SafeCurves says those two are unsafe.

Who's right?