I must admit, I didn't expect to receive anything, but today I was pleasantly surprised when I received the tokens in my wallet.

I will watch this project more closely from now on.

What is then the point of this data here: https://tokensale-eos.io/main.html
It says only 6000 ETH was collected so far.  That is a lot of money for a token, but still is 100 times less then those figures.

Where you got it from?

Eizh,

Nice work, looks awesome.

Is there a list of planned features available yet for this GUI?

Monero Missives

August 3rd, 2014

Hello, and welcome to our ninth Monero Missive! Sincerest apologies for the late posting of this one, there were some interesting statistics we were finalising that you will find below.

Major Updates

1. We had a lot of fun giving a Git Crash Course last week Wednesday, and it was well received by all despite some technical issues with the sound. To that end, we've decided to launch a regular "Monero Fireside Chat" session as a way of both introducing the occasional new feature even before its announcement in the Monero Missives, and as an ongoing developer technical resource. We aren't sure of the frequency we'll do these, so we'll announce them as they're planned. Our first one will be this Friday, August 8th, 2014, at 9:00 EST (note: EST, not EDT) which is 14:00 UTC and 16:00 UTC +2 (aka FOST - fluffypony and othe standard time). This week Friday we will have a very special announcement, before going in to a technical discussion, so if you are able to join us live for that then please do so. It will be broadcast live via Google Hangouts on Air, so you'll be able to watch it on YouTube, and during the dev discussion portion following the announcement we'll be available to take questions on IRC in #monero-dev on Freenode.

2. We've only recently started tracking our download stats (since July 15th), and we thought we'd share with you some download stats for Monero over the past 3 weeks. Our most popular download has been our blockchain bootstrap, which has seen 41 425 completed downloads in 3 weeks, around 74tb of traffic usage! Leading the pack on these downloads is Windows with around 78.2%, followed by OS X with 14.5%, and the remaining 7.3% snagged by Linux. The client downloads are quite interesting, too - of a total of 15 000 downloads in 3 weeks, Windows again grabbed 78.4%, OS X only grabbing 9%, and Linux grabbing a surprising 12.6%! This obviously excludes those that clone the github repo and compile, which is the majority of Linux users and OS X users (thanks to sammy007's Homebrew recipe). We'd like to thank the donations we've received thus far - it goes directly to many things, including covering costs like the bandwidth provision to help bootstrap new users.

3. As mentioned in our last Monero Missive, Poloniex added a number of XMR market pairs. In the 12 days since, those markets have had a combined volume of 5830 XMR, and it is growing on a daily basis. The additional liquidity for both miners and traders is certainly a boon to cementing Monero's market position.

4. We're happy to announce that Monero has been added to the CoinsSource Trust Index, with a rating of 6 out of a possible 7 stars. More information on the Trust Index can be found on the CoinsSource Trust Index page.

5. Most of the dev effort recently has been around a smoother and cleaner build process, which is important as we move towards continuous integration (through Jenkins) as well as deterministic builds (through Gitian). This will mean that binaries of the code that is currently undergoing testing will be readily available, and it also means that we will have a secure build process so that the binaries you download from the Monero website will be verified and verifiable. Over and above that, the QoS bandwidth management system is functionally complete, and will go into the main staging branch for testing within the next few days. Finally, the backend for DNS seed nodes has been completed, the source code has been published, and the Monero seed nodes are up and running. Integration of DNS seeds into the network seed procedure still has to be completed, but when complete this will ensure a safer and vastly more secure method of discovering the Monero network and connecting to it.

Dev Diary

Build: we've added a Windows build script to make building on Windows easier (it's in /utils/build_scripts/windows.bat). Tangentially to that, we are moving away from the VS 2013 requirement on Windows, and switching to msys2 for dependency management and mingw64 for Windows C / C++ compilation. Progress on this can be tracked in mikezackles' branch: https://github.com/mikezackles/bitmonero/tree/mingw

Core: QoS is feature complete, although some peripheral components such as bandwidth utilisation tracking is still WIP. Completed work will be pushed upstream to staging for broader testing within the next week. Progress can be tracked on rfree's branch: https://github.com/rfree2monero/bitmonero/tree/dev-rfree

Blockchain: the embedded DB work is exceedingly complex work that requires a lot of thought, but it is progressing at a clip. Abstracted code is being refactored, and tewinget has moved to a clean branch for this. Progress can be tracked here: https://github.com/tewinget/bitmonero/tree/bc2

Core: jakoblind has closed a number of github issues. The first major one is adding an optional blockheight parameter to a wallet refresh (ie. refresh from that point).

Core: the second issue closed by jakoblind is the addition of a set of RPC and CLI calls to retrieve the mnemonic seed or the view key for an open wallet. The new RPC call is query_key (a generalised call that lets you specify 'mnemonic' or 'view_key' as the key type). The CLI command is 'seed' to retrieve the mnemonic seed, and 'viewkey' to retrieve the view key. Wallets that are not deterministic (ie. very old wallets, or wallets that are specifically created as non-deterministic) will error out when trying to retrieve the mnemonic.

Core: as mentioned in the Missive, the source code for the DNS seeder is available: https://github.com/monero-project/xmr-seeder. It is as simple as possible (and even a little hacky), but it is beneficial in that we don't have to run BIND to service requests. Instead, we use Gandi.net's API, which is advantageous in that Gandi supports AnyCast for DNS (rapid updates). DNS seeds are by and large a convenience feature, so a group of superpeers will still be available as hard-coded seed nodes, and there will be an option to forego the use of DNS seeds. DNS seed support still needs to be added to the client, possibly along with DNSSEC support. The four DNS seeds (delivered as A records for ipv4, and later on as AAA records for ipv6 when ipv6 support is better baked in) are at: seeds.moneroseeds.ch, seeds.moneroseeds.li, seeds.moneroseeds.ae.org, and seeds.moneroseeds.se

Until next week!

- updated by fluffypony

Monero Missives

July 20th, 2014

Hello, and welcome to our seventh Monero Missive!

Major Updates

1. We've had an incredibly positive response to our ongoing need for donations, and we'd like to thank everyone that has donated and continues to donate. Several pools have stepped up to donate some of their fees to us - CryptonotepoolUK, for instance, has a 1% fee, but the entirety of the fee is donated. Risto Pietila has also kindly setup a donation "Hall of Fame", which has been taken over by cAPSLOCK, and can be found here. This, and all the ongoing donations, are critical to our ability to spend even more time and energy on Monero, and are greatly appreciated.

2. Now that the CryptoNote whitepaper has been peer reviewed by our mathematicians and cryptographers, they have begun initial work reviewing the implementation thereof. This is most especially important, as Monero has inherited quite a bit from the CryptoNote reference code. The initial focus is on the cryptographic primitives and higher-level cryptographic functions, which will be evaluated by code analysis as well as by running test vectors (that are different from those in the Monero test suite) against those functions. The methodologies and results will, of course, be published in due time.

3. A number of important and critical dev efforts are under way, most notably the embedded database work (to cut down on the RAM requirement), the daemonising work (to allow for a much more stable environment for exchanges, pools, merchants, and other automated systems), and the QoS work (to reduce and limit the bandwidth requirements). Technical updates on these are in the dev diary below.

4. We'd like to officially welcome Pavel Kravchenko as a key technical contributor to Monero. With a PhD in Information Security, specialising in public key infrastructures, he will be devoting some time to tackling the larger issues that Monero faces in its drive to become a truly private, untraceable cryptocurrency.

5. Further to the last missive, the German word list has been completed, and work has begun on the Portuguese version. This is very early work, and is very important to our ensuring that it fits well with our current mnemonic system.

Dev Diary

Blockchain: abstraction of the blockchain storage functions is basically complete, and the next step will be to start integrating LevelDB so that we have a baseline for our performance testing. A number of the key-value stores / embedded databases that we will be evaluating are forked from LevelDB, so it makes sense to start with that. This is moving out of "core" and into "blockchain" for categorisation going forward. The ongoing progress on this can be followed here: https://github.com/tewinget/bitmonero/tree/blockchain

Core / Wallet: much of the work on daemonising Monero has been complete. On Unix-like systems (Linux, OS X) the daemon backgrounds correctly, and commands can be run against the daemon (through command line arguments or RPC calls). On Windows the daemon can install itself as a Windows service, and can subsequently be managed through the standard Windows service system. The Windows service can also be removed by the daemon. Similarly, rpcwallet has inherited this functionality, with the difference that rpcwallet can run in multiple instances (whereas the daemon only allows a single instance). This covers edge cases where a single machine needs to have multiple wallets accessible via multiple rpcwallet instances.

RPC: a new get_connections RPC call has been added to the daemon and merged into master. This is needed by the DNS seed control software, which is at a very early stage. Once complete the hardcoded seed nodes will be removed in lieu of DNS seeds. At a later stage when the DNS seed control software is feature complete, there will be a call for 4 or 5 people who are happy to run DNS seeds on an extremely long-term basis.

RPC: due to some exchanges finding it difficult to poll get_payments, an urgent change has been made to allow for get_payments to take multiple payment IDs are input, as well as a block height to scan from (excluding older transactions). This will break compatibility with the classic get_payments, and will thus be moved to a call of its own. The initial commit can be found here, and tested if you are feeling particularly brave: https://github.com/mikezackles/bitmonero/commit/65c6b193e406fe23944c63eb0a6b69165ef5666b

Core: initial work has been completed on the QoS bandwidth control. If you'd like to take a look at the commits to have an extra set of eyes on it, it can be found here: https://github.com/rfree2monero/bitmonero/tree/dev-rfree

Until next week!

- updated by fluffypony

Monero Missives

July 13th, 2014

Hello, and welcome to our sixth Monero Missive!

Major Updates

1. The GUI bounty is completed and all payouts have been made. You can view the confirmation of payouts in this post, and bounty recipients have confirmed receipt of their bounties. Just to reiterate the comments made by us in that thread: "As it stands right now, we won't be integrating any of these GUI clients into the main codebase just yet, as there is still a great deal of underlying work that must be done before we can ship a GUI wallet that just about anyone can run (unless we want to make the minimum memory requirement 8gb and the minimum Internet connection requirement 20mbps;) That having been said, we will continue to recommend the actively developed GUI wallets to anyone who prefers to use a GUI wallet, and that is the main purpose behind closing and awarding this bounty now: to have a short-list of recommended GUI wallets." The two GUI wallets we recommend using and that are being actively and continuously developed are:

neozaru's wallet: https://github.com/Neozaru/bitmonero-qt

Jojatekok's Monero Client .NET: https://github.com/Jojatekok/monero-client / https://bitcointalk.org/index.php?topic=683365.0

2. As you may be aware, there's been a great deal of discussion around dev donations. It wasn't something we thought to raise previously, as it is generally accepted that if you are making money from an open-source project (eg. mining, buying and holding for future profit, whatever) you will generally donate as that is the best way to secure an increase in your "investment". It is important to note that this is not a cryptocurrency that has a big, fat premine (or any sort of instamine / ninjamine / premine), and we are, therefore, completely reliant on the donations of our users. We really, truly appreciate all of the donations that we have received, from early pools such as the now-defunct monero.farm contributing a large portion of their earnings, to our largest donation from ceger, to the ramp-up in dev donations from a screed of pools. Thank you, you guys are the ones that are helping us cover costs and pay for contributors where necessary.

3. The initial work has been completed on analysing the CryptoNote whitepaper, and the review that has come out of it is now available to all. This is an academic approach to analysing it, and is the first step in figuring out whether the principles it espouses are reflected in the Monero code, and (further to that) how we can improve on its deficiencies. You can grab the whitepaper review here: http://monero.cc/downloads/whitepaper_review.pdf

4. Very early work has begun on reimplementing the mnemonic wordlists in other languages. We are currently doing a German one as a tester to see the amount of effort involved. If you are interested in producing a mnemonic wordlist (1626 words, following a small set of rules) in a language other than German or English please drop us a pm. There will be other translation work coming up (website, tooling etc.), and we will definitely be distributing donations to translators where possible (although they may be relatively small for the work involved).

Dev Diary

Core: major work has begun on moving to an embedded database. The ongoing progress on this can be followed here: https://github.com/tewinget/bitmonero/tree/blockchain

Core / Wallet: both the new daemonized daemon and rpcwallet are nearing a stage where they can be merged into master. The final step is to finalise the daemonizing code in rpcwallet, in such a way that it acts the same as the daemon, and we can move from there.

I8N: mnemonic word list German version is in progress and about 90% complete.

I2P: subsequent to discussions with the I2P team, we are going to be making a bit of a diagonal movement from libi2pcpp to i2pd. This should end up with us slightly ahead on the I2P integration project than we would've been. The major focus at the moment is getting TCP streaming (for persistent connections) to work, and that is where the largest focus is at present.

Until next week!

- updated by fluffypony

wallet is disabled on bittrex