[XMR] Monero - A secure, private, untraceable cryptocurrency

[thankful_for_today]

Updated binaries (all changes from BCN and other CN-coins included) are available at http://bitmonero.org.

Win 32
Win 64
Unix
Mac

[trand]

anyone can help me
i was try 3 pool for mining MRO, but no one MRO i got from come to my account
any idea for that

First, need to know a few things.

Have you checked to insure your address is correct?
Is your address to a exchange?
What is your current Hash?
Is your bitmonerod synced?
Have you mined long enough to get shares of a block?

1. yes i've check my address and its correct
2. no i use simplewalet
3. i use cpu-cloud and my has around 120-150 H/s
4. yes my bimonerod have sync
5. i have minned 12h and got 0.5 MRO in total paid

[DemocraticRepublicOfDave]

Wohoo! Got my minerd going under ubuntu 14.04.  And my old server is now hashing at an incredible 18H/s 

However the current version of cpu-miner I downloaded from github https://github.com/Lucasjones/cpuminer-multi has some build issues under ubuntu 14.04

./autogen.sh
configure.ac:13: installing './compile'
configure.ac:4: installing './config.guess'
configure.ac:4: installing './config.sub'
configure.ac:6: installing './install-sh'
configure.ac:6: installing './missing'
Makefile.am:12: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
Makefile.am:18: warning: source file 'sha3/sph_keccak.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
Makefile.am:18: warning: source file 'sha3/sph_hefty1.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'sha3/sph_groestl.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'sha3/sph_skein.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'sha3/sph_bmw.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'sha3/sph_jh.c' is in a subdirectory,                                                                                           
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_shavite.c' is in a subdirectory,                                                                                       
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_blake.c' is in a subdirectory,                                                                                         
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_luffa.c' is in a subdirectory,                                                                                         
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_cubehash.c' is in a subdirectory,                                                                                     
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_simd.c' is in a subdirectory,                                                                                         
Makefile.am:18: but option 'subdir-objects' is disabled                                                                                                               
Makefile.am:18: warning: source file 'sha3/sph_echo.c' is in a subdirectory,                                                                                         
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/oaes_lib.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/c_keccak.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/c_groestl.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/c_blake256.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/c_jh.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/c_skein.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/hash.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'crypto/aesb.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:54: warning: source file 'crypto/aesb-x86-impl.c' is in a subdirectory,
Makefile.am:54: but option 'subdir-objects' is disabled
Makefile.am: installing './depcomp'

To bypass this issue I changed "INCLUDE" to "AM_CPPFLAGS" in line 12 of Makefile.am, and changed line 6 in configure.ac (AM_INIT_AUTOMAKE) to

AM_INIT_AUTOMAKE([foreign] subdir-objects)

then...

./autogen.sh
./configure CFLAGS="-O3"
make

and all was well.

ah...
someone has already raised a ticket for this...

https://github.com/LucasJones/cpuminer-multi/issues/7


Cheers

Dave

[Shrikez]

I'm holding a substantial and expensive bag here....I trust you will keep pushing forward and keep the community updated.

[giveBTCpls]

Im extremely happy about the i2p support. i2p > TOR, MRO > DRK.

To the Moonero.

[nakaone]

i am not in the irc chat - is there something fundamentally broken or other fud? or is this just market madness?

[DemocraticRepublicOfDave]

If you are referring to the price drop, bitcoin is on a bit of a surge at the moment, most alts are dropping against it.

Cheers

Dave

[TTM]

This coin was hot on first days on Polo just because those day traders was thinking that MRO would be added to Mintpal soon so they could make some quick profits. It's turned out that Mintpal either has no interest on MRO or has problem with implementing a totally new protocol. As results, day traders quickly lost their patience, volume and price decrease slowly. PoW coins could take months to start kicking in. I'm still a big believer in CryptoNote and gonna buy some more if the price continue dropping lower.

[bitcoin.newsfeed]

So I am IN, my first ALT, i bought some MRO and DRK today, i threw 1btc into each, so another thread to watch, good luck to all 

[Spekulatius]

So if all thats required to authenticate your deposit into some exchange wallet is the publicly available tx ID, arent we just waiting for some scammers to claim deposits that never happened?

If a sender/buyer/exchanger doesnt send his/her MRO to your address but claims to have done it, then there is no recourse right? Any way to get around this?

[kurious]

If you are referring to the price drop, bitcoin is on a bit of a surge at the moment, most alts are dropping against it.

Cheers

Dave

Most alts are not dropping anywhere near as much.   And Yes - I do have MRO, but let's get real, it has collapsed even in the past 24 hours...!

[wizzardTim]

Why the heck is MRO cheaper than DRK?

[parker928]

it's cus people are cloud mining monero and dumping it just chill they can only push it down to the point where it is not profitable...which i think happened in the low 20's. price seems to be coming back up just fine.

[parker928]

Why the heck is MRO cheaper than DRK?

because you haven't bought them up yet =)

go go go

[giveBTCpls]

Why the heck is MRO cheaper than DRK?

DRK is older, has a cool logo, has a big community... basically hype.
It's a matter of time MRO surpases DRK as the to-go anonymous currency because it's technically better, be in a month or a in a year. Working with i2p is huge news, most whales are clueless about actual technology so it will take time for the money to flow into the MRO economy.

[wizzardTim]

Thank you all for the answers. In time people will realise MRO is so much more than DRK.

[fluffypony]

Yes - but remember: 1 address = 1 wallet. They'd have to manually balance funds between wallets for withdrawals etc. It could be done, but it would be massively inefficient and a PITA to code up. Payment IDs are the easiest / best way.

It is pretty common in bitcoin world to sweep payment wallets into master wallets (some in cold storage) anyway, so this is not necessarily a show stopper.

I'd like to see the payment IDs removed from the block chain eventually and replaced with something else. That could be a payment protocol (i.e. off blockchain) or some other approach. I don't know that address-per-customer or address-per-transaction is necessarily the way to go with MRO but it isn't on its face unworkable.

In any case it works for now. Once we have GUI wallets the UI issues should be reduced.

Yeah - it definitely needs a bit of thought as to what can be done in future. Multiple addresses seem a less elegant solution given the untraceable nature of transactions, but the current payment IDs aren't amazing either.

[Whylolzz]

Hey guys,

I authorized a withdrawal from an exchange site to the GUI wallet (CryptoNoteWallet.exe). I used the address provided under the 'wallet' tab but I still have not received anything and it has been over 24 hours (the exchange has already approved of the withdrawal). The status is ready so it's synced. How could the money just disappear like that? Please help. 

[fluffypony]

So if all thats required to authenticate your deposit into some exchange wallet is the publicly available tx ID, arent we just waiting for some scammers to claim deposits that never happened?

If a sender/buyer/exchanger doesnt send his/her MRO to your address but claims to have done it, then there is no recourse right? Any way to get around this?

You would have to reveal your 1-time private and public keys for that transaction. We are looking at tooling for this later on, but right now the exchanges wouldn't even know how to verify it if you gave them the data. Nonetheless, between the core team and monerochain.info we would be able to verify and prove the validity of a transaction, so even before that tooling exists it's unlikely anyone is going to be able to run that sort of scam. Plus it's unlikely an exchange would go "well, our balance syncs up with what we're expecting, so it's unlikely the transaction occurred...I guess we'll just conjure the Monero up out of thin air and credit this guy's balance", so scammers would have nothing to gain.

[fluffypony]

Hey guys,

I authorized a withdrawal from an exchange site to the GUI wallet (CryptoNoteWallet.exe). I used the address provided under the 'wallet' tab but I still have not received anything and it has been over 24 hours (the exchange has already approved of the withdrawal). The status is ready so it's synced. How could the money just disappear like that? Please help. 

Your best bet is to check with the specific exchange that it has gone through and there wasn't a problem with it.