Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1613. (Read 4670972 times)
I remember looking at a graph that showed the blockchain size vs time. Can anyone tell me where to find it?
Good news guys 
I will soon donate some more and i also i may can help with the DNS seeds.
P.S. I want that damn db
I will soon donate some more and i also i may can help with the DNS seeds. P.S. I want that damn db
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
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
from the op
But what if they were running nodes all over the planet and storing and time stamping all of the network traffic they received, could they then use timing analyses on this time stamped record of all network traffic?
Quote
This feature makes a timing analysis of the blockchain useless.
But what if they were running nodes all over the planet and storing and time stamping all of the network traffic they received, could they then use timing analyses on this time stamped record of all network traffic?
If you are monitoring a large portion of the Internet then yes you can identify where transactions originate. That doesn't necessarily tie the transaction to an individual (nor to other transactions on the block chain), though in some cases it might.
Note that the OP refers to timing analysis of the blockchain meaning that by analyzing the blockchain (at any time in the future) one can infer that all partners in a coinjoin transaction must have taken place at approximately the same time, which vastly narrows the list of candidate transactions. This is not true for outputs mixed using ring signatures. This is a distinct vulnerability from (and one accessible to many more adversaries than) real time monitoring of the Internet.
from the op
But what if they were running nodes all over the planet and storing and time stamping all of the network traffic they received, could they then use timing analyses on this time stamped record of all network traffic?
Quote
This feature makes a timing analysis of the blockchain useless.
But what if they were running nodes all over the planet and storing and time stamping all of the network traffic they received, could they then use timing analyses on this time stamped record of all network traffic?
what version are we on these days?
Still 0.8.8.1 - best place to check seems to be the OP of this thread, there is some risk of confusion because the old monero repo still exists on Github but is not maintained. Unfortunately its version number appears more recent (0.8.9.65 or similar I think) which has caught more than one person out as it uses the wrong fees for txes...
tnx
what version are we on these days?
Still 0.8.8.1 - best place to check seems to be the OP of this thread, there is some risk of confusion because the old monero repo still exists on Github but is not maintained. Unfortunately its version number appears more recent (0.8.9.65 or similar I think) which has caught more than one person out as it uses the wrong fees for txes...
what version are we on these days?
After much effort I can finanly inform you that:
GREEK TRANSLATION=DONE
no goole translate.
native speaker.
I hope it helps the coin to gain traction among Greek miners and traders.
https://bitcointalksearch.org/topic/m.7943676
Please add it to the OP
GREEK TRANSLATION=DONE
no goole translate.
native speaker.
I hope it helps the coin to gain traction among Greek miners and traders.
https://bitcointalksearch.org/topic/m.7943676
Please add it to the OP
I read your brief of your history in Crypto just now on polo trollbox. 6 months, huh?
You all in monero now or keep some change to trade?
Just trying to learn from experience...
Yes, I arrived in January 2014, after I finished writing my master's thesis. The worst thing is I wanted to join for one year... You all in monero now or keep some change to trade?
Just trying to learn from experience...
I am not all in Monero, I have other altcoins. But my next fiat is planned to be mostly Monero. If you plan to trade, have some BTC left for dumps. Or else short. But I am terrible at both. I'd say 60% of my money is on monero (depend on valuation) and the rest in other alts, all PoS save for some Zetacoin - NOBL, MINT, HBN, CAP, PHS, TEK, GRW, HYP.
I don't think this will help you in anyway, but hey, here it is
The thing is. I'm not very BTC wealthy (nor fiat wealthy either lol) and I would like get a feeling of if it was possible to gamble part of my monero in an initial oscilation in price.
But I guess its difficult to guess, huh?
Exactly the same situation. And talking from experience, don't short XMR if you're not good at trading. Just wait for XMR to equal BTC. Could take a couple of years.But I guess its difficult to guess, huh?
David,
I read your brief of your history in Crypto just now on polo trollbox. 6 months, huh?
You all in monero now or keep some change to trade?
Just trying to learn from experience...
blockchain is 1,6 GB ? Is that a joke ?
No, that is correct. It's about 1.7 GB here. It does depend a bit on the platform, but 1.6 GB seems in the right ballpark.
Some amount of that is database bloat (the same data being stored more than once) and can be improved with a better database implementation. The chart on monerochain records the actual size of blockchain data, currently 738 MB.
blockchain is 1,6 GB ? Is that a joke ?
No, that is correct. It's about 1.7 GB here. It does depend a bit on the platform, but 1.6 GB seems in the right ballpark.
http://redd.it/2b7gpd
Vitalik Buterin answers a question about anonymity on the Ethereum subreddit and mentions the cryptonote protocol. Someone could program the protocol on the ethereum network ... I wonder, if this is done, would we have another 'altnote' ? Maybe someone could port the whole Monero codebase to ethereum and make some sort of extended monerochain ?
Vitalik Buterin answers a question about anonymity on the Ethereum subreddit and mentions the cryptonote protocol. Someone could program the protocol on the ethereum network ... I wonder, if this is done, would we have another 'altnote' ? Maybe someone could port the whole Monero codebase to ethereum and make some sort of extended monerochain ?
blockchain is 1,6 GB ? Is that a joke ?
After the pool dust problem was fixed it's currently growing with ~10 MB a day: http://monerochain.info/charts/bcsize 
blockchain is 1,6 GB ? Is that a joke ?
^I think I won it on 19th with this buy, but still nothing officially:
Jul 19, 21:44:09.451 217868627 XMR\BTC Buy 0.01/0.01 0.004888 0.004888 0.00004888 BTC Filled
Jul 19, 21:44:09.451 217868627 XMR\BTC Buy 0.01/0.01 0.004888 0.004888 0.00004888 BTC Filled
cool!
but you're right, we'll have to wait for the offical announcement first
^I think I won it on 19th with this buy, but still nothing officially:
Jul 19, 21:44:09.451 217868627 XMR\BTC Buy 0.01/0.01 0.004888 0.004888 0.00004888 BTC Filled
Jul 19, 21:44:09.451 217868627 XMR\BTC Buy 0.01/0.01 0.004888 0.004888 0.00004888 BTC Filled
The two people who will buy Monero at our exchange at the highest price until today’s and tomorrow’s midnight UTC will get a 100 XMR reward!
so, is this contest still active guys or what?
What are the biggest possible amount of coins that can be sent in a transfer? 100 coins? 200 coins?
i think it depends on your mixin level and the wallet balance.
transfer 0 could send just about anything but it is not good for the anonymity
i usually break up my transactions in to smaller amounts like 100-200 coins with a mixin of 3
It's really situation dependent. The limiting factor is not the number of coins but the number of bytes when all is said and done. This depends on how many inputs you need to sum up to construct the desired output. So if you have a lot of dust in your wallet and you're trying to send an oddly specific amount, you may find you can't even send 1 XMR *. On the other hand you can easily send several thousand XMR in one tx if you happen to have a previous output of that value lying around.
* This is fixed by transaction splitting. There are also dust cleanup plans ahead.
Jump to: