Two questions:

1.) Will the command_server functionality on the development branch be merged into master and rolled out with 0.8.8.5?

2.) If not, has any or all of the following fixes been incorporated into the development branch?: the spam attack patch; block 202612 attack patch; block 202612 attack mitigation and fork fix (via a whole new block blob hash checkpointing system)

Either one of these items would help move things forward on the Monero Client .NET GUI.

Reason being is that, at the moment, we can't use the test version of Monero Client .NET because it requires the command_server functionality in the daemon to properly function. Unfortunately, the latest available bitmonerod.exe binary from the development branch that has this also doesn't have the aforementioned patches incorporated into it, meaning that we can't use it anymore.

On the other hand, the most recent version of Monero Client .NET that does NOT require the binary from the development branch also contains a number of bugs (that have since been fixed in the test version) that make it annoying to use.

Total curiosity question, just because i love knowing stuff..

Just transferred 64xmr and i noticed when i did a refresh the first transaction that showed up, before showing all my transfers in the purple text, was 3 transactions received: 1 for .6, 1 for 6, and 1 for 10.. for a total of 16.6xmr received and then all the purple text showing the transfers going out.. my final balance is correct, nothing extra received

see screengrab if necessary:

http://imgur.com/c7P6tmE

so i guess my question is now obvious, why is that? where did that 16.6xmr come from? is it part of my transfer? and why 16.6 when i sent 64?

ok so i guess that's 4 questions

i know i wen't a little overboard with the redacting, but once i started i couldn't stop!

Thanks,

That's your change. In order to send 64, the wallet used one or more outputs adding up to 80.6 (maybe a bit more with fee), of which 64 (60+4) went to the recipient and 16.6 (10+6+0.6) came back to you. Bitcoin works the same way and you can see these change transactions if you look on a chain explorer, but usually wallets don't normally show the low level details the way simplewallet does.

It's more than just a function served, it's the fundamental way how Bitcoin (and Monero, and all other cryptos) are designed. We don't send and receive amounts, but atomic inputs and outputs. Inputs can only be "spent" entirely, so the only way to "spend" a target amount is too spend one or several inputs entirely, and send the change back to yourself.

Makes sense, thanks!

You learn something new every day...

Thanks Smooth and BinaryFate. This is fascinating, but I don't want to hog up the thread with questions. Where would i go to find out more about the way crypto-currency functions at the atomic level? Or at the very least, a thorough explanation of the mining, wallet, and transaction process from A to Z.  

Is this wat's being talked about with atomic exchanges and cross chain transactions? So rather than communicating through a custom-built exchange API and trading numbers they make up for other numbers they make up, you're always exchanging the real thing for the real thing?

How would that be implemented with this codebase?

Don't think so, this is not plain JS code, you have to compile extensions like https://github.com/zone117x/node-multi-hashing. Not sure it will compile by default without tweaks. I guess you wanna run it for soloing? Then better install a VM or rent some cheap VPS with enough amount of RAM.

Noob question - What is LMDB and what does it do? I haven't been here for a while