Bitcoin Forum
March 24, 2019, 06:09:56 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 [910] 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 ... 2037 »
  Print  
Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 4548056 times)
GingerAle
Legendary
*
Offline Offline

Activity: 1176
Merit: 1004


View Profile WWW
December 16, 2014, 07:13:10 PM
 #18181

granted, my noob status probably doesn't give my opinion much weight, but I'd vote for the permanent, but low, inflation model. This would solve the mining reward and deflation problem, both of which some consider not to be problems, and maybe they aren't, but I would vote for B.

If anything, a permanent but low inflation could simply offset lost coins.

< Track your bitcoins! > < Track them again! > <<< [url=https://www.reddit.com/r/Bitcoin/comments/1qomqt/what_a_landmark_legal_case_from_mid1700s_scotland/] What is fungibility? >>> 46P88uZ4edEgsk7iKQUGu2FUDYcdHm2HtLFiGLp1inG4e4f9PTb4mbHWYWFZGYUeQidJ8hFym2WUmWc p34X8HHmFS2LXJkf <<< Free subdomains at moneroworld.com!! >>> <<< If you don't want to run your own node, point your wallet to node.moneroworld.com, and get connected to a random node! @@@@ FUCK ALL THE PROFITEERS! PROOF OF WORK OR ITS A SCAM !!! @@@@
1553407796
Hero Member
*
Offline Offline

Posts: 1553407796

View Profile Personal Message (Offline)

Ignore
1553407796
Reply with quote  #2

1553407796
Report to moderator
1553407796
Hero Member
*
Offline Offline

Posts: 1553407796

View Profile Personal Message (Offline)

Ignore
1553407796
Reply with quote  #2

1553407796
Report to moderator
+
=
Equity on offer
in the world's largest
crypto enabled
marketplace
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
liteon
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000


I'm a Firestarter!


View Profile WWW
December 16, 2014, 07:38:45 PM
 #18182

Looks like B is more safe.
Any new projects in last few days?

Selling NordVPN account with premium sub - expires 2021! PM me to buy.
pandacoin
Legendary
*
Offline Offline

Activity: 1554
Merit: 1000


View Profile
December 16, 2014, 08:13:41 PM
 #18183

I lost all my hopes about XMR sadly. Sad
I hope everybody can gain their losses again.
Eastwind
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000



View Profile
December 16, 2014, 08:22:18 PM
 #18184

I lost all my hopes about XMR sadly. Sad
I hope everybody can gain their losses again.

Are you related to Pandacoin? or Do you have lots of pandacoin?
dEBRUYNE
Legendary
*
Offline Offline

Activity: 1708
Merit: 1098


View Profile
December 16, 2014, 10:15:02 PM
 #18185


Thanks for the links, was the infaltion idea of charts B in the graphs in the above link chosen.  Or has it yet to still be decided.

Nothing was decided yet for the "tail emission". Should be in the next few months.


I would like to add that the current emission isn't changed. So charts of A are still valid.

Privacy matters, use Monero - A true untraceable cryptocurrency
Why Monero matters? http://weuse.cash/2016/03/05/bitcoiners-hedge-your-position/
ArticMine
Legendary
*
Offline Offline

Activity: 2268
Merit: 1037


Monero Core Team


View Profile
December 17, 2014, 12:44:14 AM
 #18186

does the new wallet still require 64-bit system?

Yea, because it still uses simplewallet, it's really just a wrapper. If someone could compile a 32 bit version of simplewallet for windows though, then it would work (I'm not sure if the daemon is the limiting factor keeping things 64-bit at the moment, but I think it is).

Last week I was trying to compile a 32-bits linux version of the daemon and the wallet. I had to tweak the code a little bit for the compilation to go through and complete without complains.
But after that I got a seg fault at execution. I checked for bitmonerod, gdb tells me it fails on an AES instruction (called from slowhash() if I remember well). Pretty sure it's an issue with a memory alignement that is not as assumed on 32-bits systems. Didn't check further after that, and didn't check where was the simplewallet error (it fails on wallet creation, after asking for the language) but I presume it is the same origin.


 

Right now one needs PAE  https://en.wikipedia.org/wiki/Physical_Address_Extension to run Monero on 32 bit systems making them effectively 36 bit. This is because Monero needs to address more than 4GB of memory (bitmonerod takes approximately 4.8GB on 64bit Kubuntu). This can work on GNU/Linux. On 32 bit Windows however, Microsoft cripples the desktop versions to 4GB RAM (that is the nature of a propriety OS) so even though they support PAE it still will not work. It is possible to enable PAE on certain 32 bit versions of Windows Server (The advance datacenter versions of Windows server 2000 or 2003 for example) and theoretically make this work. Here are the memory limits on various versions of Windows. msdn.microsoft.com/en-ca/library/windows/desktop/aa366778(v=vs.85).aspx One should keep in mind that anything under 64GB for 32 bit version is a deliberate crippling in order to sell more expensive licenses and not a real technical limitation.

Once the database is complete and tested then it should be possible to run Monero on 32bit windows with its much lower memory availability.

Concerned that blockchain bloat will lead to centralization? Storing less than 4 GB of data once required the budget of a superpower and a warehouse full of punched cards. https://upload.wikimedia.org/wikipedia/commons/8/87/IBM_card_storage.NARA.jpg https://en.wikipedia.org/wiki/Punched_card
kenns
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
December 17, 2014, 01:17:05 AM
 #18187

hello. I'm going to work on a client in c# for monero in the next week with spare time.
my plans for it to look basic and be dependent on the the daemon and the wallet
just a heads up
going to see how far with features i can get if you have any in mind of what the other client do not have lemme know i can try to implement em.
bclcjunkie
Legendary
*
Online Online

Activity: 839
Merit: 1000



View Profile
December 17, 2014, 01:39:22 AM
 #18188

what kind of hopes did you have? get rich overnight? Roll Eyes if you're in this for speculative trading then this sort of outcome is expected of any volatile cryptocurrency, including bitcoin but if you have long term plans for xmr and know its potential then you shouldn't be seeing it as a loss...

I lost all my hopes about XMR sadly. Sad
I hope everybody can gain their losses again.
smooth
Legendary
*
Offline Offline

Activity: 2072
Merit: 1077



View Profile
December 17, 2014, 01:42:14 AM
 #18189

does the new wallet still require 64-bit system?

Yea, because it still uses simplewallet, it's really just a wrapper. If someone could compile a 32 bit version of simplewallet for windows though, then it would work (I'm not sure if the daemon is the limiting factor keeping things 64-bit at the moment, but I think it is).

Last week I was trying to compile a 32-bits linux version of the daemon and the wallet. I had to tweak the code a little bit for the compilation to go through and complete without complains.
But after that I got a seg fault at execution. I checked for bitmonerod, gdb tells me it fails on an AES instruction (called from slowhash() if I remember well). Pretty sure it's an issue with a memory alignement that is not as assumed on 32-bits systems. Didn't check further after that, and didn't check where was the simplewallet error (it fails on wallet creation, after asking for the language) but I presume it is the same origin.

If you aren't mining just tweak the useAes variable so it never uses AES instructions.

smooth
Legendary
*
Offline Offline

Activity: 2072
Merit: 1077



View Profile
December 17, 2014, 01:47:32 AM
Last edit: December 17, 2014, 03:35:19 AM by smooth
 #18190

Please, be aware that using a remote daemon compromises your privacy, as it leaks your transactions data. Someone in the middle sniffing your connection would be able to take a look at it, as well as the people operating the remote daemon. So basically you are trusting the person running the daemon and that no one is snooping your connection .

Quoting smooth from https://forum.monero.cc/4/academic-and-technical/10/remote-monero-deamon :

I think it is possible to mostly fix this model of light wallet by connecting to multiple nodes getting mixins from all of them. Then randomly choose some of the mixins from each. None of them individually will be able to tell which is your coin source; they would have to collude.

Snooping of transactions doesn't really matter -- they are public anyway --although snooping of the mixins could matter, and snooping of your IP could matter. Both issue can be largely fixed (granted not NSA-proof) by connecting to the nodes over Tor. A simple proxy setup should work.

EDIT: clarify that any number of nodes (>1) can be used, not just two.
binaryFate
Legendary
*
Offline Offline

Activity: 1372
Merit: 1001


Still wild and free


View Profile
December 17, 2014, 01:53:48 AM
 #18191

does the new wallet still require 64-bit system?

Yea, because it still uses simplewallet, it's really just a wrapper. If someone could compile a 32 bit version of simplewallet for windows though, then it would work (I'm not sure if the daemon is the limiting factor keeping things 64-bit at the moment, but I think it is).

Last week I was trying to compile a 32-bits linux version of the daemon and the wallet. I had to tweak the code a little bit for the compilation to go through and complete without complains.
But after that I got a seg fault at execution. I checked for bitmonerod, gdb tells me it fails on an AES instruction (called from slowhash() if I remember well). Pretty sure it's an issue with a memory alignement that is not as assumed on 32-bits systems. Didn't check further after that, and didn't check where was the simplewallet error (it fails on wallet creation, after asking for the language) but I presume it is the same origin.

If you aren't mining just tweak the useAes variable so it never uses AES instructions.



Now that you say this, I think I tried that already by force setting the support_aes (or whatever it is called) variable to -1 instead of actually testing for hardware AES support. Then it was failing shorlty afterwards on something else than AES, and I think I gave up at that point. Like always after fiddling, I should have taken some notes!

And I realize it was on pae-capable hardware but without pae kernel.  Embarrassed
Will try again after upgrading kernel then, and let you know.

Monero's privacy and therefore fungibility are MUCH stronger than Bitcoin's. 
This makes Monero a better candidate to deserve the term "digital cash".
jwinterm
Legendary
*
Offline Offline

Activity: 1890
Merit: 1022



View Profile
December 17, 2014, 01:57:55 AM
 #18192


Right now one needs PAE  https://en.wikipedia.org/wiki/Physical_Address_Extension to run Monero on 32 bit systems making them effectively 36 bit. This is because Monero needs to address more than 4GB of memory (bitmonerod takes approximately 4.8GB on 64bit Kubuntu). This can work on GNU/Linux. On 32 bit Windows however, Microsoft cripples the desktop versions to 4GB RAM (that is the nature of a propriety OS) so even though they support PAE it still will not work.

So in theory you should just be able to compile a 32 bit version of simplewallet, and then run simplewallet using a remote 64 bit version of bitmonerod? Or this is impossible because of some incompatibility between 32 bit simplewallet and 64 bit bitmonerod?
osensei
Member
**
Offline Offline

Activity: 70
Merit: 10

https://monerohash.com


View Profile WWW
December 17, 2014, 02:05:21 AM
 #18193

Please, be aware that using a remote daemon compromises your privacy, as it leaks your transactions data. Someone in the middle sniffing your connection would be able to take a look at it, as well as the people operating the remote daemon. So basically you are trusting the person running the daemon and that no one is snooping your connection .

Quoting smooth from https://forum.monero.cc/4/academic-and-technical/10/remote-monero-deamon :

I think it is possible to mostly fix this model of light wallet by connecting to two nodes getting mixins from both. Then randomly choose have the mixins from each. Neither will be able to tell which is your coin source.

Snooping of transactions doesn't really matter -- they are public anyway --although snooping of the mixins could matter, and snooping of your IP could matter. Both issue can be largely fixed (granted not NSA-proof) by connecting to the nodes over Tor. A simple proxy setup should work.



Even over Tor, wouldn't it leak destination addresses and transactions amounts?

EDIT: Oh, OK, if the node is running as an .onion service then the channel would be secure, but would the node be able to get addresses and amounts?

MoneroHash.com - U.S. Mining Pool
jwinterm
Legendary
*
Offline Offline

Activity: 1890
Merit: 1022



View Profile
December 17, 2014, 02:07:16 AM
 #18194

Please, be aware that using a remote daemon compromises your privacy, as it leaks your transactions data. Someone in the middle sniffing your connection would be able to take a look at it, as well as the people operating the remote daemon. So basically you are trusting the person running the daemon and that no one is snooping your connection .

Quoting smooth from https://forum.monero.cc/4/academic-and-technical/10/remote-monero-deamon :

I think it is possible to mostly fix this model of light wallet by connecting to two nodes getting mixins from both. Then randomly choose have the mixins from each. Neither will be able to tell which is your coin source.

Snooping of transactions doesn't really matter -- they are public anyway --although snooping of the mixins could matter, and snooping of your IP could matter. Both issue can be largely fixed (granted not NSA-proof) by connecting to the nodes over Tor. A simple proxy setup should work.



Even over Tor, wouldn't it leak destination addresses and transactions amounts?

If the remote node is trusted, in the light wallet user's opinion, would it be possible to eliminate snooping by using https?
smooth
Legendary
*
Offline Offline

Activity: 2072
Merit: 1077



View Profile
December 17, 2014, 03:28:25 AM
 #18195

Please, be aware that using a remote daemon compromises your privacy, as it leaks your transactions data. Someone in the middle sniffing your connection would be able to take a look at it, as well as the people operating the remote daemon. So basically you are trusting the person running the daemon and that no one is snooping your connection .

Quoting smooth from https://forum.monero.cc/4/academic-and-technical/10/remote-monero-deamon :

I think it is possible to mostly fix this model of light wallet by connecting to two nodes getting mixins from both. Then randomly choose have the mixins from each. Neither will be able to tell which is your coin source.

Snooping of transactions doesn't really matter -- they are public anyway --although snooping of the mixins could matter, and snooping of your IP could matter. Both issue can be largely fixed (granted not NSA-proof) by connecting to the nodes over Tor. A simple proxy setup should work.



Even over Tor, wouldn't it leak destination addresses and transactions amounts?

If the remote node is trusted, in the light wallet user's opinion, would it be possible to eliminate snooping by using https?

Sure. The node operator can even do this without modifying the node with stunnel.

smooth
Legendary
*
Offline Offline

Activity: 2072
Merit: 1077



View Profile
December 17, 2014, 03:32:12 AM
 #18196

Please, be aware that using a remote daemon compromises your privacy, as it leaks your transactions data. Someone in the middle sniffing your connection would be able to take a look at it, as well as the people operating the remote daemon. So basically you are trusting the person running the daemon and that no one is snooping your connection .

Quoting smooth from https://forum.monero.cc/4/academic-and-technical/10/remote-monero-deamon :

I think it is possible to mostly fix this model of light wallet by connecting to two nodes getting mixins from both. Then randomly choose have the mixins from each. Neither will be able to tell which is your coin source.

Snooping of transactions doesn't really matter -- they are public anyway --although snooping of the mixins could matter, and snooping of your IP could matter. Both issue can be largely fixed (granted not NSA-proof) by connecting to the nodes over Tor. A simple proxy setup should work.



Even over Tor, wouldn't it leak destination addresses and transactions amounts?

EDIT: Oh, OK, if the node is running as an .onion service then the channel would be secure, but would the node be able to get addresses and amounts?

No, the node sees the same transaction everyone else sees (e.g. by looking on chainexplorer.com, or the blockchain itself). That by itself doesn't include anything particularly useful (and can't).

With Tor the node could not correlate this with an IP address, which would be the only extra information it has if the mixins are blinded using multiple nodes as I described. The nodes would have to collude to identify the real source of the transaction.

smooth
Legendary
*
Offline Offline

Activity: 2072
Merit: 1077



View Profile
December 17, 2014, 03:33:57 AM
 #18197


Right now one needs PAE  https://en.wikipedia.org/wiki/Physical_Address_Extension to run Monero on 32 bit systems making them effectively 36 bit. This is because Monero needs to address more than 4GB of memory (bitmonerod takes approximately 4.8GB on 64bit Kubuntu). This can work on GNU/Linux. On 32 bit Windows however, Microsoft cripples the desktop versions to 4GB RAM (that is the nature of a propriety OS) so even though they support PAE it still will not work.

So in theory you should just be able to compile a 32 bit version of simplewallet, and then run simplewallet using a remote 64 bit version of bitmonerod? Or this is impossible because of some incompatibility between 32 bit simplewallet and 64 bit bitmonerod?

Possibly. It depends if anything in the encoding of the .bin http requests is architecture specific. I don't know either way.
kawa900jc
Hero Member
*****
Offline Offline

Activity: 644
Merit: 500


StakeChain Community leader


View Profile WWW
December 17, 2014, 06:53:31 AM
 #18198

The 0.001 lever is broke. New low levels has to be discovered.
I invested 0.12 BTC @ 0.0012 but for now is was not a good choice.
Hopefully is was just a spike below 0.001 but the presure is to high I afraid.
Maybe I buy extra @ 0.0005?

e-coinomist
Legendary
*
Offline Offline

Activity: 1624
Merit: 1050


Money often costs too much.


View Profile
December 17, 2014, 07:16:31 AM
 #18199

what kind of hopes did you have? get rich overnight? Roll Eyes if you're in this for speculative trading then this sort of outcome is expected of any volatile cryptocurrency, including bitcoin but if you have long term plans for xmr and know its potential then you shouldn't be seeing it as a loss...
what kind of hopes ... and if it means "had" or "have" not sure, either. I am watching market numbers, naturaly, and they show me a change in the 2nd and 3rd top trade positions. LTC got replaced, sunken onto 3rd position today which is a first timer.

And then I have Hopes, meaning any crypto based technology could break out of the monetary system as we experience it on our everyday use cases. I still buy grocery using classical paper bills. Dont own credit card.

That newcomer on 2nd position worries me. It feels like monetary system with it's centralized banking is invading the crypto sphere. Only 65.77 % or $ 30,000,000 had been Bitcoin trades the last day, Ripple is now up to 16.80 % market share on the trades. They pushed almost $ 8,000,000 into this and I have a feeling this is not all gunpowder available.
generalizethis
Legendary
*
Offline Offline

Activity: 1666
Merit: 1023


Facts are more efficient than fud


View Profile WWW
December 17, 2014, 07:18:46 AM
 #18200

The 0.001 lever is broke. New low levels has to be discovered.
I invested 0.12 BTC @ 0.0012 but for now is was not a good choice.
Hopefully is was just a spike below 0.001 but the presure is to high I afraid.
Maybe I buy extra @ 0.0005?


Pages: « 1 ... 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 [910] 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 ... 2037 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!