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

it's a very good app, I use it daily
(and I'm one of the donators)

I don't know if it's possible, but maybe a volume weighted average exchange rate?

Have you tried to refresh your balance?
It might not have gone through and came back to your wallet

hi,smooth.I have contact Bter,He said that blockchain have not record and let e contact monero,What should I do next,appreciate youe help!

Thank you for update!

That's smart.

what you really want is indistinguishable dummy transactions or running on a global clock heartbeat.  All blocks full every block.

Actually I vaguely remembered that when I wrote the above, but I didn't have time to go recollect and also my point was about the first 5 years of Bitcoin's adoption where it really mattered. Even if those are released in 2015, they won't be in most users' computer for another few years as it takes a while to retire old computers.

Now we have $17 ASICS, but much better they will there by default in every computer.

And yes AES-NI is already widely deployed.

My understanding is Intel has been on 22nm while ASICs have been 28 or 40nm (?), so Intel has inherent advantage if they decide to make a ubiquitously used instruction more efficient. As encryption becomes more used on everyone's computer, Intel is going to have an economic incentive to make AES-NI (and perhaps SHA-2?) more efficient.

Thanks for the news!

Thanks

http://monerochain.info/charts/bcsize

Yea I get it. This is a vulnerability that i hope will be looked into at some point since there are groups of people out there recording all internet traffic in giant data centres. Probably could be solved by staggering the outputs of a transaction with random time intervals between using a random number generator.

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

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

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?

tnx

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