Well, what shall I say, for Tipping Websites using domain adresses makes sense.
That is perhaps an almost infinite realm of possibility. You know you cannot fund your webpage using advertisement popups, somebody allready tried that. Nor offer an entry field for supporting people's credit card credentials, for known reasons.
A money in cash equivalent with a clean reputation and a common name fits into this in a perfect way.
Names always had that habit of designating someone. Maybe connecting names with anonymity is a misfit by design.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1241. (Read 4671575 times)
December 07, 2014, 10:29:04 PM
December 07, 2014, 08:51:17 PM
That makes sense.
Thanks, smooth and myagui.
Thanks, smooth and myagui.
December 07, 2014, 06:37:12 PM
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
I am not amused.
December 07, 2014, 06:36:37 PM
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
I am not amused.The idea of cryptonote public addresses is they don't need to be anonymous at all. You can safely publish your public address (on a web site, email sig, forum sig, domain name registration, DNS record, etc.) and these can't be linked to transactions on the blockchain, unlike bitcoin.
However, the whole openalias system is an optional convenience feature and is never required. If you prefer absolute privacy and independence (for example maybe you don't even want anyone to know you are using Monero at all -- though currently there is no way to hide this from your ISP unless you roll your own Tor/I2P wrapping) with no registration of any kind you can just use the regular public addresses.
December 07, 2014, 06:35:07 PM
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
I am not amused.we need one that accepts XMR
December 07, 2014, 06:29:03 PM
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
I am not amused. 
December 07, 2014, 06:26:53 PM
If I am mining with a given hashrate (let's say 1 kh), will I likely mine more XMR when the network hashrate is lower (~12Mh) versus higher (~20Mh as it is currently)?
I know that the difficulty retargets every block, which is every minute, but I am not certain about this comparison that I am asking about.
Thanks in advance for knowledgeable replies.
I know that the difficulty retargets every block, which is every minute, but I am not certain about this comparison that I am asking about.
Thanks in advance for knowledgeable replies.
The difficulty re-targeting does not have a direct impact to your first question, or rather, not an obvious one.
I'll try to address the 1st question (if that is a question) about mining rewards with variations in difficulty:
If nethash is ~12Mh, and you have ~1Kh, you are 1/12000 of the nethash.
You will find, on average, 1/12000 of the blocks, or in other words, 1 block every ~8.33 days.
If nethash is ~20Mh, and you have ~1Kh, you are 1/20000 of the nethash.
You will find, on average, 1/20000 of the blocks, or in other words, 1 block every ~13.88 days.
Happy Mining!
Edit: I see smooth just beat me to it. Keeping the post anyhow as the examples might be helpful.
December 07, 2014, 06:06:39 PM
WOW
Network Hash Rate: 20.97 MH/sec
Network Hash Rate: 20.97 MH/sec
If I am mining with a given hashrate (let's say 1 kh), will I likely mine more XMR when the network hashrate is lower (~12Mh) versus higher (~20Mh as it is currently)?
I know that the difficulty retargets every block, which is every minute, but I am not certain about this comparison that I am asking about.
Thanks in advance for knowledgeable replies.
The total number of XMR minted per day is approximately fixed so if you have a fixed hash rate then your share of the total (and therefore your amount mined) is higher if the network hash rate is lower.
That being said, a higher network hash rate is somewhat correlated to a higher price so the XMR you do mine may be worth more under conditions where the network hash rate is higher, all else being equal. In fact over the past few days the price has indeed been stronger (at least not dropping every day).
December 07, 2014, 06:04:31 PM
WOW
Network Hash Rate: 20.97 MH/sec
Network Hash Rate: 20.97 MH/sec
If I am mining with a given hashrate (let's say 1 kh), will I likely mine more XMR when the network hashrate is lower (~12Mh) versus higher (~20Mh as it is currently)?
I know that the difficulty retargets every block, which is every minute, but I am not certain about this comparison that I am asking about.
Thanks in advance for knowledgeable replies.
December 07, 2014, 05:50:06 PM
hey guys check this out. wow. no more having to copy and paste huge addresses! cool new feature in the 0.8.8.5, great work devs
go to https://openalias.org/ to learn how to make your own alias!
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
I already had moneroaddress.org sitting around not being used for anything yet, it was really easy to setup. Just add a TXT record to your domain like so:
Code:
oa1:xmr recipient_address=; recipient_name= ;
I have yet to configure the domain for DNSSEC, I am still reading up on how to do that.
Also it looks possible to add payment IDs to your alias, would be really cool for example to fund your account at crypto kingdom just by entering saddam.cryptokingdom.com or something like that.
December 07, 2014, 05:37:27 PM
hey guys check this out. wow. no more having to copy and paste huge addresses! cool new feature in the 0.8.8.5, great work devs
go to https://openalias.org/ to learn how to make your own alias!
That is cool! How did you get your the saddam.moneroaddress.org alias you reference in your sig? Did you have to register the domain name moneroaddress.org yourself? Does this mean that to get our own openalias to use with Monero, we have to find domain name registrars that allow anonymous registration?
December 07, 2014, 05:29:28 PM
Minor bug in simplewallet v0.8.8.5-unknown:
Follow status here: https://github.com/monero-project/bitmonero/issues/198
December 07, 2014, 05:28:17 PM
hey guys check this out. wow. no more having to copy and paste huge addresses! cool new feature in the 0.8.8.5, great work devs
go to https://openalias.org/ to learn how to make your own alias!
December 07, 2014, 05:24:25 PM
Minor bug in simplewallet v0.8.8.5-unknown:
After updated to 0.8.8.5, when I initially opened an old non-deterministic wallet, simplewallet detected that it was a deprecated version of the wallet and then produced a 25-word seed. I assumed that being given a new seed implied that my non-deterministic wallet had been upgraded to a deterministic wallet. But when I entered the "seed" command, I received the message: "Error: The wallet is non-deterministic. Cannot display seed." So my wallet remains in its original non-deterministic format.
Also when I ran simplewallet with the --restore-deterministic-wallet flag, and entered those 25 words at the "Specify electrum seed:" prompt, I received the message "Error: electrum-style wordlist failed verification." I exited and re-opened my non-deterministic wallet, this time without any flag, using my password. The funds are still there and I was not presented with the erroneous 25 word seed this time.
Summary: The new version of simplewallet erroneously presented me with a 25-word seed the first time (but not the second time) I used it to open a non-deterministic wallet.
Edit: It seems safe to just ignore the seed. The new version of simplewallet seems to work fine with a more recent deterministic wallet.
After updated to 0.8.8.5, when I initially opened an old non-deterministic wallet, simplewallet detected that it was a deprecated version of the wallet and then produced a 25-word seed. I assumed that being given a new seed implied that my non-deterministic wallet had been upgraded to a deterministic wallet. But when I entered the "seed" command, I received the message: "Error: The wallet is non-deterministic. Cannot display seed." So my wallet remains in its original non-deterministic format.
Also when I ran simplewallet with the --restore-deterministic-wallet flag, and entered those 25 words at the "Specify electrum seed:" prompt, I received the message "Error: electrum-style wordlist failed verification." I exited and re-opened my non-deterministic wallet, this time without any flag, using my password. The funds are still there and I was not presented with the erroneous 25 word seed this time.
Summary: The new version of simplewallet erroneously presented me with a 25-word seed the first time (but not the second time) I used it to open a non-deterministic wallet.
Edit: It seems safe to just ignore the seed. The new version of simplewallet seems to work fine with a more recent deterministic wallet.
December 07, 2014, 04:55:57 PM
I am beginning to suspect that my PMs are not getting through. If you are wondering why I have not responded to your PMs, I did, in fact.
December 07, 2014, 04:13:23 PM
I've got a problem trying to run 0.8.8.5 on OSX (10.10.1)...
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
dyld: Library not loaded: /usr/local/lib/libevent-2.0.5.dylib
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
Illegal instruction: 4
I can't help but I did get mine working on OSX 10.10.1 using Homebrew. I ran into a bit more trouble than usual. Did you run brew doctor? It advised me to link libevent and zeromq. I also had to brew install makedepend. During the build process I was seeing errors from curl, about certificate problems. But it seems to be working now.
Thanks, I ran brew doctor, brew upgrade, brew update and it did seem to make some progress.
Now when I try brew install --HEAD bitmonero, I get a cmake error. Sigh. I'll keep at it.
UPDATE: I got it!! For some reason it worked when I tried brew install bitmonero, not brew install --HEAD bitmonero.
December 07, 2014, 03:48:41 PM
I've got a problem trying to run 0.8.8.5 on OSX (10.10.1)...
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
dyld: Library not loaded: /usr/local/lib/libevent-2.0.5.dylib
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
Illegal instruction: 4
I can't help but I did get mine working on OSX 10.10.1 using Homebrew. I ran into a bit more trouble than usual. Did you run brew doctor? It advised me to link libevent and zeromq. I also had to brew install makedepend. During the build process I was seeing errors from curl, about certificate problems. But it seems to be working now.
December 07, 2014, 03:30:31 PM
WOW
Network Hash Rate: 20.97 MH/sec
Are there any more miners with video cards?
if so
it is in which country and how much electrical energy there
Good for Network but just if Miners dont dump Network Hash Rate: 20.97 MH/sec
Are there any more miners with video cards?
if so
it is in which country and how much electrical energy there
I think Miners dont dump , but Botnet Miners dump
dump doesnt matter now because xmr is becoming like bitcoin, a long period of low price is good for legitimacy of the coin if it ever reaches a lot higher in the future no one will be able to say that didn't bought xmr because it was too expensive, they can only say they didnt heard about monero or didnt believe on it.
December 07, 2014, 03:07:11 PM
I've got a problem trying to run 0.8.8.5 on OSX (10.10.1)...
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
dyld: Library not loaded: /usr/local/lib/libevent-2.0.5.dylib
I've tried updating libevent but the most recent version I can find is 2.0.21 - any ideas?
EDIT:
I tried brew unlink libevent && brew link libevent. Now I get a completely different error when I try to launch bitmonerod.
Code:
Illegal instruction: 4
December 07, 2014, 02:43:17 PM
Quote from: nullc (gmaxwell)
So, sure, there are also applications for increased transparency using Bitcoin, but you can always layer more transparency on top of a more private system... but not the other way around.
This is interesting.. has there been any talk of implementing transparency layers, and their potential function?
Yes there has been. Some of it is right in the original whitepaper, in terms of view keys and auditable addresses. We have also considered other methods of allowing for transparency on specific transactions. People want to be able to selectively prove payments on demand and generally open up to transparency in a controlled manner, without everything being linkable and traceable to the rest of their transactions.
Jump to: