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

[pfo]

Pools that need to be removed from OP:

- http://mon.hashharder.com (no api available)
- http://xmr.ext-pool.net/ (no api available)
- http://42.62.16.188:8080/ (website is down)

Done (the first too are pending confirmation for a day or two). Thanks surfer!

By the way, where is mropool.org located?

Amazon EC2, Ashburn, VA, United States

P.S. You can find the pool's IP by typing "host example.com" in bash (but make sure to use the url of the mining server if the mining server is a different IP than the web server). Then you can Google the IP for its location.

The guy maintaining the site (me) actually lives in the Netherlands (you know, the country that is going to beat Spain tonight  ) I am a developer and co-own a software company for about 17 years now, but this project is of course a hobby.

[dunchy]

Error executing the 64bit linux version (Ubuntu 13.10): Illegal instruction

are you executing wolf's miner? your cpu needs aes-ni.

No, the original simplewallet binary from OP

I would install it from the source: http://monero.cc/getting-started/#install_source

Can you please point me to the link to the source code of simplewallet on that page I'm not able to find it ?

[NeuroticFish]

In the meantime, everyone should try to move their hashing power around to non-major pools in an effort to cut down on dust. Note that mining dust hurts your profitability as well, as you need to generate more tx (and spend more fees) in order to transfer it anywhere.

Exactly. Try to find a pool that is no bigger than 100-200x your own hashrate.

If you are only using one computer with 200 H/s, try to find a smaller pool that is 20 KH/s or smaller.

If you a larger miner, you can use the larger pools, but try to keep to the above guideline to avoid the dust issue.

Shortly: it's so easy to ask others to do this!

I am a tiny miner. But I will not go to a pool with less that 100kH/s. Why? Because I am not patient enough to wait maybe one day for a block. And I am sure that many others think the same.
So, if you want the many small miners to move their hashing power, you big miners should do that first. From one pool of 1.5 GH/s there's plenty of you that can move around. The others (us) will have then real choices.

[smoothie]

This is what I get when I attempt to use the save_bc command (save blockchain):

Error: Blockchain can't be saved: possible lost connection to daemon

But in the terminal window for bitmonerod.exe it says:

SYNCHRONIZED OK

What am I doing wrong. It is a pain to have to continually wait for the blockchain to redownload each time I restart the bitmonerod.EXE file.

Type 'save' in the daemon window. Also, if you type "exit" in the daemon window when closing, it automatically saves blockchain before exiting.

That error is usually a bug as well, the daemon still usually saves the blockchain, it's just that the RPC timesout because the daemon is saving.

Im on Windows 7 starter 32bit. This was never a issue with the previous deamon/wallet.

The deamon sync in its normal slow time. If I sync everyday then the deamon will take about 1/2hr to sync but this problem with simple wallet is unbearable

The issue is due to both stealth addressing and the tx dust from the pool software, which is still being fixed. In a CryptoNote coin, you must test each transaction output to check to see if it is owned by your private key. Therefore, as more tx emerge, it takes longer to scan the blockchain.

There has got to be a better way to do this.

If this ever gets used by many the sync time will be FOREVER.

The problem right now is that obscene amounts of dust is being created by zone117x's pool software, which is causing slow resyncs. When the dust issue is properly addressed, this will be less of an issue.

In the meantime, everyone should try to move their hashing power around to non-major pools in an effort to cut down on dust. Note that mining dust hurts your profitability as well, as you need to generate more tx (and spend more fees) in order to transfer it anywhere.

Thanks. I didnt even think to type "save" into the daemon console. It didn't appear obvious as it did with the simple wallet console.

[Keyboard-Mash]

Kind of a cross post here .. I think my question is off topic for rpietila's thread

You could prove to a third party that you own the address by giving them the view key (which reveals that you own the public key) and then by signing from that public key using the private key that is generated for that public key via your secret key.

Can this now be done indefinitely with the introduction of the deterministic wallets you guys put in .. long after the file itself is gone .. provided the view key is not lost?

I can prove that I made payments for data that I delete/remove from all of my computers .. provided I can remember some words and a view key?

edit: I just tested it out finally .. it spits out the same view key and everything! That's probably the coolest damn thing I've seen added to CN yet  ! Sending XMR to dev wallet!

[smooth]

Kind of a cross post here .. I think my question is off topic for rpietila's thread

You could prove to a third party that you own the address by giving them the view key (which reveals that you own the public key) and then by signing from that public key using the private key that is generated for that public key via your secret key.

Can this now be done indefinitely with the introduction of the deterministic wallets you guys put in .. long after the file itself is gone .. provided the view key is not lost?

I can prove that I made payments for data that I delete/remove from all of my computers .. provided I can remember some words and a view key?

edit: I just tested it out finally .. it spits out the same view key and everything! That's probably the coolest damn thing I've seen added to CN yet  ! Sending XMR to dev wallet!

Yes the words are the seed. The other keys are derived from the seed.  Same words = same wallet.

[smooth]

In the meantime, everyone should try to move their hashing power around to non-major pools in an effort to cut down on dust. Note that mining dust hurts your profitability as well, as you need to generate more tx (and spend more fees) in order to transfer it anywhere.

Exactly. Try to find a pool that is no bigger than 100-200x your own hashrate.

If you are only using one computer with 200 H/s, try to find a smaller pool that is 20 KH/s or smaller.

If you a larger miner, you can use the larger pools, but try to keep to the above guideline to avoid the dust issue.

Shortly: it's so easy to ask others to do this!

I am a tiny miner. But I will not go to a pool with less that 100kH/s. Why? Because I am not patient enough to wait maybe one day for a block. And I am sure that many others think the same.
So, if you want the many small miners to move their hashing power, you big miners should do that first. From one pool of 1.5 GH/s there's plenty of you that can move around. The others (us) will have then real choices.

Honestly you have no choice. I'm not suggesting this here for the purpose of balancing the network, but for your own benefit. If you mine with a big pool using the current pool software, you will receive many tiny payments (dust) that you either won't be able to spend at all or will only be able to spend with a complex process of sending multiple transaction and paying a lot of transaction fees.

BTW, the net hash rate is about 5m. A pool with a hash rate of 50k should get about 1% of the network blocks, which is 14 blocks per day, much more than one per day.

Any pool with 50kh that makes you wait a day to find a block is broken, which unfortunately is more common than it should be given issues with the pool software.

Follow my advice if you want to get decent returns on your mining. Really.

[mr_random]

In the meantime, everyone should try to move their hashing power around to non-major pools in an effort to cut down on dust. Note that mining dust hurts your profitability as well, as you need to generate more tx (and spend more fees) in order to transfer it anywhere.

Exactly. Try to find a pool that is no bigger than 100-200x your own hashrate.

If you are only using one computer with 200 H/s, try to find a smaller pool that is 20 KH/s or smaller.

If you a larger miner, you can use the larger pools, but try to keep to the above guideline to avoid the dust issue.

Shortly: it's so easy to ask others to do this!

I am a tiny miner. But I will not go to a pool with less that 100kH/s. Why? Because I am not patient enough to wait maybe one day for a block. And I am sure that many others think the same.
So, if you want the many small miners to move their hashing power, you big miners should do that first. From one pool of 1.5 GH/s there's plenty of you that can move around. The others (us) will have then real choices.

Honestly you have no choice. I'm not suggesting this here for the purpose of balancing the network, but for your own benefit. If you mine with a big pool using the current pool software, you will receive many tiny payments (dust) that you either won't be able to spend at all or will only be able to spend with a complex process of sending multiple transaction and paying a lot of transaction fees.

BTW, the net hash rate is about 5m. A pool with a hash rate of 50k should get about 1% of the network blocks, which is 14 blocks per day, much more than one per day.

Any pool with 50kh that makes you wait a day to find a block is broken, which unfortunately is more common than it should be given issues with the pool software.

Follow my advice if you want to get decent returns on your mining. Really.

Thanks for the advice.

[Keyboard-Mash]

After about the 14th citation in the CN whitepaper there's no links. I found most of them are available for free online, maybe two are not. Here is the list with links that are easily clickable and in line with the citations as presented in the white paper so that anyone that wants to learn/understand can.

1. http://bitcoin.org

2. https://en.bitcoin.it/wiki/Category:MixingServices - dead link

3. http://blog.ezyang.com/2012/07/secure-multiparty-bitcoin-anonymization/

4. https://bitcointalk.org/index.php?topic=279249.0 - (an actual citation crediting gmaxwell in their paper )

5. http://msrvideo.vo.msecnd.net/rmcvideos/192058/dl/192058.pdf

6. https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki#Speci%0Ccation.

7. https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki#BackwardsCompatibility

8. https://en.bitcoin.it/wiki/Mininghardwarecomparison - dead link

9. https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki

10. http://luke.dashjr.org/programs/bitcoin/%0Cles/charts/branches.html - dead link

11. https://bitcointalk.org/index.php?topic=196259.0

12. https://en.bitcoin.it/wiki/Contracts

13. https://en.bitcoin.it/wiki/Script

14. http://litecoin.org

15. Moderately hard, memory-bound functions   

16. Ad-hoc-group signatures from hi-jacked keypairs
   
17. Short linkable ring signatures revisited

18. High-speed high-security signatures
   
19. Group signatures
   
20. Exponential memory-bound functions for proof of work protocols - I like this one the best so far by a lot .. I think it opens the idea well that a PoW protocol can be adapted to much more than just a currency implementation .. and using PoS as a messaging system will have a lot of trouble preventing spam without a PoW (favoring hybrid systems)
   
21. Proofs of partial knowledge and simplied design of witness hiding protocols
   
22. On memory-bound functions for fighting spam - another nice one
   
23. Sub-linear size traceable ring signatures without random oracles (free account required?)

24. Traceable ring signature
   
25. Peer review of "quantitative analysis of the full bitcoin transaction graph"
   
26. Linkable spontaneous anonymous group signature for ad hoc groups
   
27. Linkable ring signatures: Security models and new schemes (Link courtesy of binaryFate)

28. Zerocoin: Anonymous distributed e-cash from bitcoin
   
29.  Structure and anonymity of the bitcoin transaction graph
   
30. Universal electronic cash
   
31. The bitcoin transaction graph | anonymity - awesome thesis
   
32. Stronger key derivation via sequential memory-hard functions
   
33. An analysis of anonymity in the bitcoin system
   
34. How to leak a secret - Very nice rundown of what a ring signature is
   
35. Quantitative analysis of the full bitcoin transaction graph
   
36. Analysis of hashrate-based double-spending
   
37. Rational points on certain hyperelliptic curves over finite fields
   
38. Ad hoc group signatures (Link courtesy of binaryFate)

Lastly, here's a pastebin link of all of these: http://pastebin.com/tM2wCW3P

[foxill1]

who can help me
send mro from my wallet only 0.99   Cannot send more    who can help me

[dreamspark]

who can help me
send mro from my wallet only 0.99   Cannot send more    who can help me

Have you had lots of small inputs to that address?

[binaryFate]

After about the 14th citation in the CN whitepaper there's no links. I found most of them are available for free online, maybe two are not. Here is the list with links that are easily clickable and in line with the citations as presented in the white paper so that anyone that wants to learn/understand can.

[...]

Lastly, here's a pastebin link of all of these: http://pastebin.com/tM2wCW3P

Nice initiative.
Here are the two ones behind pay walls:
27. Linkable ring signatures: Security models and new schemes  -> https://anonfiles.com/file/1ade51fc9396705bed12079ab17b41ba
38. Ad hoc group signatures                                                -> https://anonfiles.com/file/5aae7a1f02c40d82aa76e255f0549ec1

[Keyboard-Mash]

Nice initiative.
Here are the two ones behind pay walls:

...

Thanks! updated!

[David Latapie]

Can you please point me to the link to the source code of simplewallet on that page I'm not able to find it ?

Follow the instructions, simplewallet will be installed for you. I will update the page to make it explicit.

[foxill1]

who can help me
send mro from my wallet only 0.99   Cannot send more    who can help me

Have you had lots of small inputs to that address?

yes  is my mining address

[Jshank]

Is cryptonotewallet working with Windows 64-bits binaries 0.8.8?

[dreamspark]

who can help me
send mro from my wallet only 0.99   Cannot send more    who can help me

Have you had lots of small inputs to that address?

yes  is my mining address

The issue is the size of transactions from lots of small payouts, this is why you want to mine on a pool with a lower HR so you get less regular payouts but bigger payouts which means your inputs wont be so small. In this case you have no option but to try and send in smaller chunks.

[foxill1]

who can help me
send mro from my wallet only 0.99   Cannot send more    who can help me

Have you had lots of small inputs to that address?

yes  is my mining address

The issue is the size of transactions from lots of small payouts, this is why you want to mine on a pool with a lower HR so you get less regular payouts but bigger payouts which means your inputs wont be so small. In this case you have no option but to try and send in smaller chunks.

I know
thanks very much

[jwinterm]

Error executing the 64bit linux version (Ubuntu 13.10): Illegal instruction

are you executing wolf's miner? your cpu needs aes-ni.

No, the original simplewallet binary from OP

I would install it from the source: http://monero.cc/getting-started/#install_source

Can you please point me to the link to the source code of simplewallet on that page I'm not able to find it ?

You just need to run:

Code:

 cd ~ && rm -f install_monero.sh && wget http://monero.cc/downloads/install_monero.sh && bash install_monero.sh

it'll compile the simplewallet for your system.

Source for simplewallet is here: https://github.com/monero-project/bitmonero/

[innergy]

Is http://moneropool.org/#pool_blocks OK?