I understand the instinct, but SQLite is an RDBMS, and as such it is ill-suited to this. Functionality will be provided through RPC calls, not by sacrificing speed because we implemented an entire RDBMS (albeit one that is self-contained). The blockchain needs to be in a fast key-value store so that commonly hit functions (network catch-up, scanning when restoring a wallet or re-syncing one, key image scanning for double-spend prevention) are blazingly fast both now and in future. Given the size of the key image table / index, it would take tens of seconds for you to send a transaction if we used SQLite.

Of course, the fact is that we are abstracting the DB functionality, so someone else can have an active fork that uses SQLite.

RAM issues are being solved by moving to an embedded database, thus negating the need for the whole blockchain to be loaded into RAM when Monero is running. The current progress of this is occurring in this branch on github: https://github.com/tewinget/bitmonero/tree/blockchain - currently the work is focused around very generic code to do allow for the blockchain to live in an embedded database. I hate putting timelines down, as there are moving goal posts and the amount of time that we spend actively developing is dependent on how much time we can free up from other projects via donations, but I'm confident that we'll start testing different embedded databases within a week or so. After we've determined which is most suited to our workload, we'll finalise the integration and start proper testing on testnet, after which we can get some of the smaller pools to make the switch and see how it holds up, and then we will release it as part of the main system.

Bandwidth issues are being solved by a "quality of service" system that will allow for limitations on a bandwidth level. There's been a stack of work that was done on that over the past 2 days that hasn't been pushed up to a branch yet, but barring a little bit of cleaning up this should hopefully be ready for testing within a few days.

We're busy putting together specifications for this - we've made a number of changes from the reference code, so checking the two RPC maps in the source code is your best bet right now.

Also, you can't run wallet commands against the daemon - the daemon is not a wallet, it just syncs up to the network. You'd run wallet RPC calls against simplewallet in RPC mode, but bear in mind that it is being deprecated in favour of a drop-in replacement called rpcwallet (dev branch for this is linked in the last Missive iirc).

That's not a valid transaction: http://monerochain.info/tx/0ced61d7bf937af91a84f36227bb8da7fa1773d25f715790647e3200f605a8ba - is that a key image for an input or a tx id?

Details would include things like your operating system, CPU/RAM/available disk space, what errors show up in the daemon window (if any).

Your next step would be to check if there is an open github issue for the problem you're facing, and if not you should open one: https://github.com/monero-project/bitmonero/issues

At the end of the day, this is an open-source project that is in very early alpha stages, and you are most welcome to fix the problems you've described and submit your code via a pull-request.

That would be 600 per block, something is clearly wrong with monerochain's dataset:)

Edit: apologies, I thought that was number of transactions, it's bed time for me!

Your best bet is to hop on to #monero-dev on Freenode and ask about it, but off the top of my head: make sure you're querying http://127.0.0.1:9005/json_rpc (unless you've changed the port), and make sure it's well-formed JSON RPC API 2.0 calls. getbalance / getaddress are probably the easiest, as they don't have any optional arguments (JSON RPC API parameters).

So where are we copy-pasting from? Are the CryptoNote whitepaper annotations and the whitepaper review copy-pasted from somewhere as well?

That wasn't directed at you, sorry about that - read my whole post:) I was quoting you to prove that a DLL isn't in the binary package.

That file isn't part of the Monero distributable package - literally a few posts up Brad_BCK confirmed the contents of the Monero binaries:


That file you linked is from this thread where he confirms it as being xptMiner, which is for mining Riecoin.

Seriously, go troll elsewhere you two.

The biggest culprit is the key image index, which is necessary to prevent double-spend attempts. It's somewhat solvable through normalisation, we'll see how it goes once the database abstraction stuff is complete.

Spot on - thankful_for_today is no longer involved in Monero, and despite being asked he has refused to take down both of those dead resources. Anyone can report the github repo as being unmaintained and thus containing potentially dangerous code, and maybe github will take the repo down, but the unmaintained website is going to be a tough one. Thankfully, we only link to current and active resources in the OP, so I would imagine that, with time, those abandoned resources will become less and less important.

I know you don't read the Dev Diary in the weekly Missive, otherwise you'd know that development is done in branches on individual developer's forks. Work-in-progress branches are regularly linked on the Missives and elsewhere.

You're being disingenuous. That was a discussion on /r/bitcoin, and my comments did not "complain" about Darkcoin. Don't conflate a technical debate with complaining. I pointed out technical deficiencies. I have done the same for Monero, and I have vocally pointed out Bitcoin's flaws.


This is utter nonsense. I made 1 comment on Coindesk 2 months ago pointing out that Darksend's closed-source release means that there are no checks-and-balances for the architecture and the code. Every other comment has been explaining CryptoNote or pointing out the failure that is MaidSafe. I'm completely entitled to opinions, you're not obligated to agree with them.


What's your point? A large portion of my immediate work is architectural in nature, which would not equate to direct commits.


If I wasn't passionate about my opinions, and I didn't express my opinions, there would never be active debate and discussion. I'd also never have my errors pointed out (factual errors, not differences of opinion) and would not be able to correct my thinking where I have made a misstep in judgement or believe something based on an incorrect premise. The value in expressing my opinions and thereby improving my knowledge through rigorous debate is immeasurable. If you disagree with me on something, feel free to engage me on it.

The viewkey is published in the OP, but we'll also look at publishing a running total of all donations.

You are my favourite troll of all time:)

Because of the news. Didn't you read the news? The market only ever moves on the news.

/thread

Just refreshed the dev wallet - confirmed:)

*raises eyebrow*

We've only ever had good things to say about Boolberry publicly and privately, and have exchanged both code and ideas with CryptoZoidberg over the aisle.

You'd do well to think carefully about spewing puerile vitriol as a representative of Boolberry, Michael.

Key images are a unique property of the CryptoNote protocol that prevent double spends.

To quote gmaxwell and andytoshi, one of which is a core Bitcoin developer and the other is someone who truly understands both mathematics and cryptography:


That is the end of this discussion, and I would suggest we not get caught up in random and nonsensical panic attacks just because someone claims a particular flaw exists when it doesn't.