Bitcoin Forum
March 26, 2025, 02:12:20 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 [1992] 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 ... 2127 »
  Print  
Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 4672494 times)
Hueristic
Legendary
*
Offline Offline

Activity: 4130
Merit: 5788


Doomed to see the future and unable to prevent it


View Profile
October 14, 2018, 05:05:54 PM
 #39821

Meanwile diff grows to 80, so sad((

Yup, stronger security is always sad...WTF

“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
sportscliche
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
October 15, 2018, 05:41:09 AM
 #39822

I've been running a full node and switched over to 13.0.2 CLI.  It immediately had trouble synching .  I keep getting notified about "Error adding block" and "Attempting to add transaction that's already in the db".  If I go back to 12.3.0 the daemon tells me to "Please delete the existing database and resync."  Do I have to spend a week re-synching this thing from scratch?
Globb0
Legendary
*
Offline Offline

Activity: 2702
Merit: 2053


Free spirit


View Profile
October 15, 2018, 09:39:43 AM
 #39823

https://www.ccn.com/monero-developers-new-startup-is-launching-a-free-blockchain-university/

Interesting
johnfoss
Full Member
***
Offline Offline

Activity: 147
Merit: 133


View Profile
October 15, 2018, 02:47:59 PM
 #39824

Extra extra, read all about it!
The Monero Moon (Issue 6) is hot off the printing press and there's no doubt about it!
https://medium.com/@johnfoss/the-monero-moon-issue-6-2c2e7d0dccb4


dEBRUYNE
Legendary
*
Offline Offline

Activity: 2268
Merit: 1141


View Profile
October 15, 2018, 04:14:15 PM
 #39825

I've been running a full node and switched over to 13.0.2 CLI.  It immediately had trouble synching .  I keep getting notified about "Error adding block" and "Attempting to add transaction that's already in the db".  If I go back to 12.3.0 the daemon tells me to "Please delete the existing database and resync."  Do I have to spend a week re-synching this thing from scratch?


Did your system shut down unexpectedly whilst the daemon was upgrading the database version? Or shortly thereafter? Because those error messages kind of insinuate your blockchain is corrupt. A blockchain resync from scratch, even though tedious, is probably the easiest way to resolve your issue.

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

Activity: 861
Merit: 1010


View Profile
October 15, 2018, 07:16:21 PM
 #39826

When I try to make a transaction with Ledger GUI wallet I have the following error message:

unexpected error: Fail SCard API : (-2146435042) 0x8010001E Device=0, hCard=16861477009170104320, hContext=14771806782070194176

What does that mean?

Which operating system are you using and which version of the CLI (or GUI)?
I am using Windows 10 and the GUI v0.12.3 with Ledger Nano S.

Have you tried using a different USB cable and/or USB port? Your cable might not be working properly anymore, which inhibits the GUI from functioning properly (in conjunction with a Ledger device).

I have tried with two different USB cable with the same result.

With a second USB cable I have something new though, I have an other error message
unexpected error: Fail SCard API : (-2146435025) 0x8010002F Device=0, hCard=16861477009170104320, hContext=14771806816429932544

And on the Ledger, it's dispayed "Fee 0.00838096" then when I go down it is displayed "Reject fee", then when I go down again  it is displayed "Accept fee", but I cannot really choose to accept or reject the fee, I don't have the option to validate. Anyway there is the above error message on the GUI.
theleaf
Full Member
***
Offline Offline

Activity: 448
Merit: 100



View Profile
October 16, 2018, 01:36:40 AM
 #39827

Monero was down almost throughout last week but the community is confident that the price action will change this week. This is because the developer community is making plans to release updates that will implement Bulletproofs and make the Monero platform ASIC mining resistant.

purpose of implementing bulletproofs? heard that bulletproofs privacy is being tested on bitcoin? If Monero is already a privacy coin, why need to implement bulletproofs? dumb question but whats ASIC mining resistant means?
jwinterm
Legendary
*
Offline Offline

Activity: 3192
Merit: 1119



View Profile
October 16, 2018, 02:11:16 AM
 #39828

Monero was down almost throughout last week but the community is confident that the price action will change this week. This is because the developer community is making plans to release updates that will implement Bulletproofs and make the Monero platform ASIC mining resistant.

purpose of implementing bulletproofs? heard that bulletproofs privacy is being tested on bitcoin? If Monero is already a privacy coin, why need to implement bulletproofs? dumb question but whats ASIC mining resistant means?

Due to Monero privacy the transactions are much larger than Bitcoin - bullet proofs will reduce the tx size significantly. ASIC resistant basically means hard forking every six months and tweaking the PoW.
elrippos friend
Full Member
***
Offline Offline

Activity: 1179
Merit: 210


only hodl what you understand and love!


View Profile
October 16, 2018, 05:01:29 AM
 #39829

Since the last upgrade to beryllium my node doesn't accept my Monerujo client anymore.
Everytime i try to connect i get the error message "Node unavailable. Please check User/Password"
Node is up an running  Wink
Any of you guys having the same issues  Roll Eyes

dEBRUYNE
Legendary
*
Offline Offline

Activity: 2268
Merit: 1141


View Profile
October 16, 2018, 07:38:13 AM
 #39830

GUI v0.13.0.3 'Beryllium Bullet' released!

https://www.reddit.com/r/Monero/comments/9ol2ic/gui_v01303_beryllium_bullet_released/

This is the GUI v0.13.0.3 'Beryllium Bullet' point release, which a user should run to be sufficiently prepared for the scheduled protocol upgrade of October 18 (for which more information can be found here). 

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

Activity: 2268
Merit: 1141


View Profile
October 16, 2018, 07:45:15 AM
 #39831

Since the last upgrade to beryllium my node doesn't accept my Monerujo client anymore.
Everytime i try to connect i get the error message "Node unavailable. Please check User/Password"
Node is up an running  Wink
Any of you guys having the same issues  Roll Eyes

Are you running the latest version of both monerod and monerujo?

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

Activity: 2268
Merit: 1141


View Profile
October 16, 2018, 07:45:58 AM
 #39832

When I try to make a transaction with Ledger GUI wallet I have the following error message:

unexpected error: Fail SCard API : (-2146435042) 0x8010001E Device=0, hCard=16861477009170104320, hContext=14771806782070194176

What does that mean?

Which operating system are you using and which version of the CLI (or GUI)?
I am using Windows 10 and the GUI v0.12.3 with Ledger Nano S.

Have you tried using a different USB cable and/or USB port? Your cable might not be working properly anymore, which inhibits the GUI from functioning properly (in conjunction with a Ledger device).

I have tried with two different USB cable with the same result.

With a second USB cable I have something new though, I have an other error message
unexpected error: Fail SCard API : (-2146435025) 0x8010002F Device=0, hCard=16861477009170104320, hContext=14771806816429932544

And on the Ledger, it's dispayed "Fee 0.00838096" then when I go down it is displayed "Reject fee", then when I go down again  it is displayed "Accept fee", but I cannot really choose to accept or reject the fee, I don't have the option to validate. Anyway there is the above error message on the GUI.

Could you perhaps try the new release?

GUI v0.13.0.3 'Beryllium Bullet' released!

https://www.reddit.com/r/Monero/comments/9ol2ic/gui_v01303_beryllium_bullet_released/

This is the GUI v0.13.0.3 'Beryllium Bullet' point release, which a user should run to be sufficiently prepared for the scheduled protocol upgrade of October 18 (for which more information can be found here). 


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

Activity: 425
Merit: 250


View Profile WWW
October 16, 2018, 04:18:37 PM
 #39833

Hi,

After updating the new version of the GUI wallet, this issue has occurred. How do I solve it? I see that blocks are increasing, but this message bothers me. Should I worry about something?


Thanks!

dEBRUYNE
Legendary
*
Offline Offline

Activity: 2268
Merit: 1141


View Profile
October 16, 2018, 04:29:41 PM
 #39834

Hi,

After updating the new version of the GUI wallet, this issue has occurred. How do I solve it? I see that blocks are increasing, but this message bothers me. Should I worry about something?

Thanks!

Did you already successfully complete the database migration? In addition, what version numbers are listed on the Settings page (under Debug info)?

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

Activity: 425
Merit: 250


View Profile WWW
October 16, 2018, 04:34:52 PM
 #39835

Hi,

After updating the new version of the GUI wallet, this issue has occurred. How do I solve it? I see that blocks are increasing, but this message bothers me. Should I worry about something?

Thanks!

Did you already successfully complete the database migration? In addition, what version numbers are listed on the Settings page (under Debug info)?

I did not do anything about data migration !!! What should I do. Delete the old and start from block 0 again? Version v0.13.0.3 (Qt 5.7.0)

dEBRUYNE
Legendary
*
Offline Offline

Activity: 2268
Merit: 1141


View Profile
October 16, 2018, 06:24:38 PM
 #39836

Hi,

After updating the new version of the GUI wallet, this issue has occurred. How do I solve it? I see that blocks are increasing, but this message bothers me. Should I worry about something?

Thanks!

Did you already successfully complete the database migration? In addition, what version numbers are listed on the Settings page (under Debug info)?

I did not do anything about data migration !!! What should I do. Delete the old and start from block 0 again? Version v0.13.0.3 (Qt 5.7.0)

Hold off on that for a second. To be clear, you're using your own (local) node right? Or are you using a remote node?

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

Activity: 425
Merit: 250


View Profile WWW
October 16, 2018, 06:47:27 PM
 #39837

Hi,

After updating the new version of the GUI wallet, this issue has occurred. How do I solve it? I see that blocks are increasing, but this message bothers me. Should I worry about something?

Thanks!

Did you already successfully complete the database migration? In addition, what version numbers are listed on the Settings page (under Debug info)?

I did not do anything about data migration !!! What should I do. Delete the old and start from block 0 again? Version v0.13.0.3 (Qt 5.7.0)

Hold off on that for a second. To be clear, you're using your own (local) node right? Or are you using a remote node?

Thanks for the help dEBRUYNE!
It's all over now. I waited a bit and the messages disappeared! Otherwise, I use a remote node.

irwanjabryg
Hero Member
*****
Offline Offline

Activity: 980
Merit: 512



View Profile
October 17, 2018, 01:15:36 AM
 #39838

Perhaps he was referring to a bug in the cryptonote code that was found by Monero devs. That would allow to create coins out of thin hair. Bytecoin was the one affected by this bug and eventually your friend might be thinking it was Monero.

https://shellcode.se/hacking/bytecoin_exploited/
Rossi46
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
October 17, 2018, 01:26:17 AM
 #39839

Is your wallet called mywallet.bin or mywallet? The keys file is whatever name you give it plus .keys.
vothuong1
Jr. Member
*
Offline Offline

Activity: 238
Merit: 3


View Profile
October 17, 2018, 02:49:15 AM
 #39840

monero network upgrade happening October 18. Make sure you know your hard forks! Will there be more moneros after the fork on Oct 18?
https://twitter.com/xmroutreach/status/1051886595786203136/photo/1?ref_src=twsrc%5Etfw%7Ctwcamp%5Eembeddedtimeline%7Ctwterm%5Eprofile%3Amonero&ref_url=https%3A%2F%2Fcoinmarketcap.com%2Fcurrencies%2Fmonero%2F
Pages: « 1 ... 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 [1992] 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 ... 2127 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!