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

Thanks for the link, you can be sure I'll keep researching this stuff, I have a lot at stake.  And I will get back to you, either here on the thread or by PM.

I think you should keep up with this thread https://bitcointalk.org/index.php?topic=589561.220
Its a bounty for an opensource GUI ( 1 July I think they are going to pick a winner)

If you need any help on the current wallet pm me or ask in this thread and I will answer

Yes, and I did also tell you about Alt + space + e which lets you paste as well

Ignore the connections failed. It's normal and it doesn't matter if your client work.


Devs are working on it but the aesthetic of the wallet is less important than the core functions.

Huh?

No - you don't get to divide by the # of AES/ALU units.  You need 2MB of storage per fast AES/ALU, period, because the algorithm modifies the scratchpad as it goes.  There's no great opportunity for space/time tradeoffs in this one.  Every independent execution requires a separate 2MB scratchpad because of the way the scratchpad is constructed (as a function of the block and nonce).

Keep your eyes open, fellas.
I am an investor who has bought heavily into xmr.
I asked a question in this thread, and didn't get an answer.
You guys have to be on the alert for the opportunity to reach out to people like me.
I asked a question that was so simple it was apparently worth ignoring in the high level discussion going on here.
If I can't get up to speed on the wallet I then must choose between leaving my holdings on an exchange into the indeterminate future or dumping, which is bad for me and bad for everybody else.
Please make monero useful to people who know less than you do.  It shouldn't be beneath you to give a beginner a helping hand.

Server is located in Czech Republic, EU (100 mbps for now, upgradeable to much more, Tier1 Premium BW). Payout treshold is 0.1. You can reach me on same IRC nickname as on forum.
Latest pool software, latest daemon.

Actually, fee is 1.9% + 0.1% for developers.

I am exploring (and mining!) Monero more then one month, so i am familiar with save, exit, refresh commands in daemon. Just yesterday tried to sync blockchain, and stuck at  block 98929 and nothing helps. First i deleted blockchain from %AppData% and synced - same. Now then i am waiting for Your help with download, trying a trick (maybe that will help)  - deleted bitmonerod.txt from C:\Monero & blockchain from %AppData% once again.

One thing i am worried now is here in pix:


Why so much "Connect failed"? :|

I don't have the 32 bit blockchain, but you could try to enter 'exit' or 'q' in the daemon in order to save the blockchain and quit. Is there any difference when you restart the daemon and start the sync from block 98929? Can you check your windows task manager for the bitmonerod.exe and how much RAM it's using and do you have enough RAM? In the 64 bit version it's currently using about 2.1 GB - the win 32 bit version should use less (32 bit memory addressing instead of 64 bit, so the same data structure is using less RAM in the 32x win) however this is going closer to the maximum a win 32 configuration could address (2.8 GB - 3.6 GB is the max with 32x bit windows on 32 bit processor depending on the configuration, video card, bios, windows, etc...). This won't be a problem when the blockchain is stored in a proper database or when the lightweight client is released.

O(n/2) = O(n)
Cache is amortized over the number of alus you pack in.  The ratio of alu to cache area has to be divided by the number of alus on the die, again approximated by the haswell to aes block ratio. (Also, associative cache is wasteful overkill when all you need to do is deliver shuffle bits to an alu. That 50% number is inflated.  But still O(n/1.4) = O(n).)

28/6/2014: xmr.farm updated to 0.98.7 !  

First, can't sync blockchain -> deleted it -> sync from start, but once again looped on same block 98929. Need Win32 blockchain to download.




THX in advance ;]

I've seem many people complaining about the 0.5 limit.
I just changed the payout threshold to 0.1 on monero.crypto-pool.fr.
Hope that help.

EDIT : To avoid dust payment, we are thinking about a minimum hours of mining before payout. Join the discussion on IRC #monero.

No -

Take the surface area dedicated to L3, because that's what limits the amount of cryptonight you can do concurrently.

... and that's not a freaking huge advantage, because the chips are already ~50% cache.

An ASIC could make slightly better use of the L3 -- by interspacing the AES units and the cache more optimally, it could slightly reduce read latency.  Perhaps a 30% reduction.  By specializing the reads instead of going through a more general memory controller, it could get another some %.  By optimizing the AES computation at the expense of space, a little more.

But even if you take the compute time to zero, the ASIC will be limited by the time needed to do 1 million fetches from a 2MB scratchpad.  Store that in SRAM, and you're area-limited at perhaps 3ns per retrieval.  Storing it in DRAM, you can fill your chip with AES units, but you're 128-bit random-read limited to the DRAM.

That's about 330 hashes/second/2MB of SRAM, so perhaps 1500 hashes/sec on a chip the size of a modern i7.

Of course, this is a very back of the envelope calculation, but the sky will not completely fall.  The advantage, of course, will be power - you'll be able to pack those densely - but it won't be the 2-3 order of magnitude gap you see with sha256.

(You can do an analogous computation for a DRAM-based solution.  The advantage is probably comparable, but I'll leave that as an exercise for the reader.)

Yes David thats why I mentioned off the top of my head as a bigger block of text would become very boring to most.
 

When the attack has a fab, the advantage is measured in cm^2/hps and process nodes. This is the only hash attack I worry about. Against commodity hardware, process nodes give the advantage to the good guys, maybe, but cm^2/hps is going overwhelmingly to the bad guys.  

For a first order estimate, take the surface area of a haswell compared to the portion dedicated to the aes-ni block. That is a freaking huge advantage.

 i agree, 0.5 XMR is far from being dust. 0.1 would be better for many. With more Hash rate, mining wil get onyl harder and we wil get less and less and eventually 0.5 XMR will become fortune.

For installing your wallet on windows, you have this monero wallet tutorial
https://monerotalk.org/t/bounty-create-a-useful-tutorial-on-how-to-setup-monero/13/8

Use the link on my thead instead.
Easy miner is a bit slow compared to other like Wolf miner.

You need a normal wallet or GUI wallet to get and address.

Have a look at this thread to see how to use the normal wallet. (EDIT : It's the same link that followtheboss posted under).

Tacotime and David Latapie are core team members. Other core team members include eizh, smooth, fluffypony, othe, and NoodleDoodle
rpietela, aminorex and GreekBitcoin are very active community members (well, Risto is not that active, but he is special). Other very active community members include Keyboard-Mash, drawingthesun, binaryFate, Quanttek... but also zone117, who developed the pool software, Wolf who optimised the cpuminer like crazy...

Location? Payout treshold? admin's IRC nickname?