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

Thanks a lot. I couldn't really run the old version anymore so I'll use this for balance checking for now. I'm holding what I have anyway.

Thanks!

I couldn't find the beta link on the getMonero site (I'm on windows). Where will the blockchain be saved appdata/Roaming/bitmonero as always? Will it overwrite the old data?

Are the binaries available for the newest version with improved memory management yet?

This is from last week: https://downloads.getmonero.org/monero.win.x64.v0-9-beta.zip

Exercise the appropriate level of care with it being a beta. We've recently found and solved what we hope to be the only major, breaking database issue (that could have caused major issues if we'd tagged prematurely), but that means that prior LMDB sync ups have to be resynced from scratch or imported from a fresh blockchain.raw export.

There are a handful of small things we need to finish and merge into development and master before we can release 0.9 RC, and then go from there.

[–]fluffyponyzaXMR Core Team[M] 6 points 22 hours ago

Ok to clear up what this exactly is, for /u/VedadoAnonimato and /u/101freezer specifically, let me first explain a little bit about how Monero's components work internally.

The Monero daemon is the piece of software that keeps you synced up with the Monero network. That's all it does, it doesn't know about "you" or "your funds" or "your transactions". If you want to do anything on the Monero network, and thus on the Monero blockchain, you have to talk to this daemon that will then talk to the network as a whole by rebroadcasting transactions you initiate. Similarly, if you want to get history from the blockchain, or the current memory pool of transactions, or outputs to mix with, you can ask the daemon for that information.

Now currently we use the JSON RPC API to talk to the daemon, but this is a horribly inefficient way of handling requests. It means that the daemon always has to have a thread that can answer requests, even if it's busy with something else, and it means that we have to spend a lot of effort and energy maintaining what is, in essence, an HTTP server. Securing it becomes an issue, and it's simply not scalable. Imagine a future where the block size has dynamically grown to 300mb per block - JSON RPC is simply not built to efficiently and securely move that type of data between the daemon and applications interacting with it.

Additionally, we have the problem of wanting to secure the communication to and from the daemon, as it might be on a different physical device to the one we're on. Resorting to things like self-signed SSL certificates or HTTP Simple Auth is...ok...but not ideal.

0MQ solves all those problems for us, and it provides bindings and libraries for most languages that client applications might be written in. Even better: it lets us get used to a new dependency now, so that when we decide to replace the network wire protocol (which currently uses Boost.Asio) we can do so easily, and alternative implementations (besides the main Monero project) can also just use a 0MQ wire protocol.

The initial merge of the 0MQ IPC functionality (nearly 30 000 new lines of code) went into the development branch 5 days ago: https://github.com/monero-project/bitmonero/commit/3daece9439e034104a007a3946714ee7a5aa8e07

Now this might all seem quite low-level and unimportant, but I can assure you that these are huge changes, and it will mean that we are getting closer to a point where the Monero daemon is so robust that it is just at home on a Raspberry Pi lying next to your router, or on a huge enterprise server handling thousands of queries a second.

    permalink

In case you guys missed it, a new missive has been posted -> https://getmonero.org/2015/08/31/monero-missive-for-the-week-of-2015-08-31.html

What is this 0MQ? I haven't really been following crypto for quite a few months now.

You definitely should have one. It's not stored (by default) with bitmonerod. It's stored in c:\ProgramData\bitmonero where the DB files are.

is it normal to have no bitmonerod log?
i have no idea how to route bitmonerod console output to a file on windows lol

guess i should just recompile on the weekend and see how it goes from there

anyway i have a simplewallet log, but i guess without the other log there is not enough info

Are you sure the transaction was deducted from your balance? If so then you should be able to rescan.

In any case, please report any error messages from your simplewallet.log and bitmonerod.log files.

It does sort of read like a hyperbole of techno babble satire.

I consider myself a cunning linguist, and this still reads like Hermetic alchemy or something.

yah know, light reading.