<<  >> (p.1879)
    Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 4675461 times)

    • rapi
    Member
    **
    Offline Offline

    Activity: 336
    Merit: 10


    View Profile
    February 21, 2018, 09:39:52 AM
     #37561
    What exactly can I gather at this Monerov fork? what is considered a bad thing?
    Maybe they will hurt XMR with the forking?

  • ozkraut
    Sr. Member
    ****
    Offline Offline

    Activity: 522
    Merit: 266


    View Profile
    February 21, 2018, 10:08:00 AM
     #37562
    Quote from: novag on February 21, 2018, 09:30:49 AM
    Please help i have error with send -

    "Can't create transaction: not enough outputs for specified ring size = 5:
    output amount = 0.000597493217, found outputs to use = 2

    output amount = 0.000849772414, found outputs to use = 1"



    mining revenue in drips and draps? Loads of small incoming transactions? You need to look up 'sweep' basically you seem to have the equivalent of 'change' everywhere and you need to consolidate by sweeping so can spend without huge overhead

    sdit: fat fingers
    Monero - Wir sind die Leute vor denen uns unsere Eltern gewarnt haben!

  • explorer
    Legendary
    *
    Offline Offline

    Activity: 2016
    Merit: 1259



    View Profile
    February 21, 2018, 10:53:20 AM
     #37563
    Quote from: rapi on February 21, 2018, 09:39:52 AM
    What exactly can I gather at this Monerov fork? what is considered a bad thing?
    Maybe they will hurt XMR with the forking?

    This may shed some light

    https://www.reddit.com/r/Monero/comments/7ydncd/question_about_monero_deanonymization_via_forks/

    https://www.reddit.com/r/Monero/comments/7xz0mz/monero_deanonymization_or_how_i_learned_to_stop/

  • novag
    Hero Member
    *****
    Offline Offline

    Activity: 687
    Merit: 500


    novag


    View Profile WWW
    February 21, 2018, 11:12:19 AM
     #37564
    Quote from: ozkraut on February 21, 2018, 10:08:00 AM
    Quote from: novag on February 21, 2018, 09:30:49 AM
    Please help i have error with send -

    "Can't create transaction: not enough outputs for specified ring size = 5:
    output amount = 0.000597493217, found outputs to use = 2

    output amount = 0.000849772414, found outputs to use = 1"



    mining revenue in drips and draps? Loads of small incoming transactions? You need to look up 'sweep' basically you seem to have the equivalent of 'change' everywhere and you need to consolidate by sweeping so can spend without huge overhead

    sdit: fat fingers

    I have 0.226 XMR, i can send it or not?
    Donate for the support of a new Martial arts Style - Aikivindo = Aikido + Wing-Chun (in Ukraine) 5168757318423326 PrivatBank.
    http://aikivindo.com.ua
    BTC:1DpRaQjdVmrkSopRV8p9RdwvBMWNA9faCS

  • Crypt0m0nster
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    February 21, 2018, 11:13:09 AM
     #37565
    hi guys,
    this might stupid question but can some one clarifiy for me please.

    1.Which wallet is best for storing Monero where i can claim XMV or the upcoming fork?I have download Windows wallet but it is taking ages i been syncing since last one week.i dont think i will able to sync whole blockchain by the fork happens.

    2.It says 1 XMR = 10 XMV,but when i have 0.98 XMR will i get 9.80 XMV or should i have one complete XMR?

    thanks

  • explorer
    Legendary
    *
    Offline Offline

    Activity: 2016
    Merit: 1259



    View Profile
    February 21, 2018, 11:21:43 AM
     #37566
    Quote from: Crypt0m0nster on February 21, 2018, 11:13:09 AM
    hi guys,
    this might stupid question but can some one clarifiy for me please.

    1.Which wallet is best for storing Monero where i can claim XMV or the upcoming fork?I have download Windows wallet but it is taking ages i been syncing since last one week.i dont think i will able to sync whole blockchain by the fork happens.

    2.It says 1 XMR = 10 XMV,but when i have 0.98 XMR will i get 9.80 XMV or should i have one complete XMR?

    thanks

    Find a thread related to the scam and ask there?

  • dEBRUYNE
    Legendary
    *
    Offline Offline

    Activity: 2268
    Merit: 1141


    View Profile
    February 21, 2018, 02:06:35 PM
     #37567
    Quote from: novag on February 21, 2018, 09:30:49 AM
    Please help i have error with send -

    "Can't create transaction: not enough outputs for specified ring size = 5:

    First type -> set priority 1. Thereafter, try using sweep_unmixable.
    Privacy matters, use Monero - A true untraceable cryptocurrency
    Why Monero matters? http://weuse.cash/2016/03/05/bitcoiners-hedge-your-position/

  • DeepOcean21
    Full Member
    ***
    Offline Offline

    Activity: 182
    Merit: 100


    View Profile
    February 21, 2018, 02:32:27 PM
     #37568
    I wish I had didn’t sell the monero. I sold it because I thought that market cap is very high and it is difficult to double it. I have learned anymore that the coins with high market cap and solid, it is easier to be doubled.

  • ultegra
    Jr. Member
    *
    Offline Offline

    Activity: 40
    Merit: 2


    View Profile
    February 21, 2018, 05:19:45 PM
     #37569
    Whats the least dodgiest monero android wallet at the moment?

    main stash is in cold, but going travelling so was just going to put a few in android wallet.

    cheers.

  • garytheasshole
    Full Member
    ***
    Offline Offline

    Activity: 406
    Merit: 105


    Chosŏn Minjujuŭi Inmin Konghwaguk


    View Profile WWW
    February 21, 2018, 05:22:02 PM
     #37570
    Quote from: ultegra on February 21, 2018, 05:19:45 PM
    Whats the least dodgiest monero android wallet at the moment?

    main stash is in cold, but going travelling so was just going to put a few in android wallet.

    cheers.
    https://play.google.com/store/apps/details?id=com.m2049r.xmrwallet&hl=en
    North Korea is the best Korea!

  • elrippos friend
    Full Member
    ***
    Offline Offline

    Activity: 1179
    Merit: 210


    only hodl what you understand and love!


    View Profile
    February 21, 2018, 05:46:09 PM
     #37571
    Quote from: garytheasshole on February 21, 2018, 05:22:02 PM
    Quote from: ultegra on February 21, 2018, 05:19:45 PM
    Whats the least dodgiest monero android wallet at the moment?

    main stash is in cold, but going travelling so was just going to put a few in android wallet.

    cheers.
    https://play.google.com/store/apps/details?id=com.m2049r.xmrwallet&hl=en

    Clearly https://monerujo.io with XMR.to integration  Grin
    Monero KOVRI

  • Neo.Prometheus
    Member
    **
    Offline Offline

    Activity: 238
    Merit: 11


    View Profile
    February 21, 2018, 06:04:15 PM
     #37572
    Hi! Who will answer me the question: when will altcoins be such a friendly system to move in the fairway of bitcoin? Is this day ever gonna happen? It obviously already hinders them to develop.

  • garytheasshole
    Full Member
    ***
    Offline Offline

    Activity: 406
    Merit: 105


    Chosŏn Minjujuŭi Inmin Konghwaguk


    View Profile WWW
    February 21, 2018, 06:38:57 PM
     #37573
    Quote from: Neo.Prometheus on February 21, 2018, 06:04:15 PM
    Hi! Who will answer me the question: when will altcoins be such a friendly system to move in the fairway of bitcoin? Is this day ever gonna happen? It obviously already hinders them to develop.
    That's a bad google translate. No idea what you're trying to say.
    North Korea is the best Korea!

  • M5M400
    Full Member
    ***
    Offline Offline

    Activity: 162
    Merit: 100

    supportXMR.com


    View Profile WWW
    February 22, 2018, 11:29:30 AM
     #37574
    Quote from: garytheasshole on February 21, 2018, 06:38:57 PM
    Quote from: Neo.Prometheus on February 21, 2018, 06:04:15 PM
    Hi! Who will answer me the question: when will altcoins be such a friendly system to move in the fairway of bitcoin? Is this day ever gonna happen? It obviously already hinders them to develop.
    That's a bad google translate. No idea what you're trying to say.
    probably "hardware wallet - when?"
    supportXMR.com :: EU(DE) based Monero pool :: 0.6% fee

  • Hueristic
    Legendary
    *
    Offline Offline

    Activity: 4368
    Merit: 6528


    Doomed to see the future and unable to prevent it


    View Profile
    February 22, 2018, 12:56:00 PM
     #37575
    Quote from: explorer on February 21, 2018, 01:38:26 AM
    Quote from: pönde on February 19, 2018, 11:25:39 AM
    Quote from: explorer on February 19, 2018, 08:56:04 AM
    They are way ahead of you the curve.  Go to getmonero.org and read some blogs.  Or just hold your nose, and go to reddit, where the news breaks these days.

    Great if the team really is aware and even ahead.

    Could you give some links on getmonero.org about this issue. There is too much info to search for me.

    Here's one:

    https://forum.getmonero.org/8/funding-required/89005/funding-for-sarang-at-mrl-for-q1-2018?page=&noscroll=1#post-93863

    Yes they are but if I remember correctly (as usual I am not 100% anymore and don't have the time to research this again) after vetting this proposal I noticed a few things and one of which was that this statement is not necessarily true.

    Quote
    my interest in SPECTRE has been renewed. Because it uses a more complex consensus algorithm than the Nakamoto longest-chain consensus method, there is a lot of testing and analysis that needs to be done. The benefits, however, are intriguing: an implementation could increase the block rate substantially without compromising the security of the network

    So even the papers from our Science team need to be vetted and I'm not sure who is responsible if anyone for this. I remember there was an issue where it was recommended that he be allowed to review his own work and that was ridiculous. PEER review is a BARE minimum on a security dependent project.

    I know I have the time to read and vet all these changes nor do I have the ability to check the pure math involved, only the methodology behind. I was gladdened to see the team had decided to hold off on BF until they could be properly vetted and hope that this continues into the future. As I've stated before, It will only take ONE mistake to ruin the credibility of this project. THIS IS NOT ETH! It cannot just become mutable because there is a fuckup.


    Quote from: Crypt0m0nster on February 21, 2018, 11:13:09 AM
    hi guys,
    this might stupid question but can some one clarifiy for me please.

    1.Which wallet is best for storing Monero where i can claim XMV or the upcoming fork?I have download Windows wallet but it is taking ages i been syncing since last one week.i dont think i will able to sync whole blockchain by the fork happens.

    2.It says 1 XMR = 10 XMV,but when i have 0.98 XMR will i get 9.80 XMV or should i have one complete XMR?

    thanks

    I think there's one called freedom or something. Cheesy
    “Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”

  • dEBRUYNE
    Legendary
    *
    Offline Offline

    Activity: 2268
    Merit: 1141


    View Profile
    February 22, 2018, 02:03:40 PM
     #37576
    "Ledger Hardware Wallet - Monero integration : some news #7"

    https://www.reddit.com/r/Monero/comments/7zez0g/ledger_hardware_wallet_monero_integration_some/
    Privacy matters, use Monero - A true untraceable cryptocurrency
    Why Monero matters? http://weuse.cash/2016/03/05/bitcoiners-hedge-your-position/

  • explorer
    Legendary
    *
    Offline Offline

    Activity: 2016
    Merit: 1259



    View Profile
    February 22, 2018, 10:23:03 PM
     #37577
    Quote from: Hueristic on February 22, 2018, 12:56:00 PM


    Yes they are but if I remember correctly (as usual I am not 100% anymore and don't have the time to research this again) after vetting this proposal I noticed a few things and one of which was that this statement is not necessarily true.

    Quote
    my interest in SPECTRE has been renewed. Because it uses a more complex consensus algorithm than the Nakamoto longest-chain consensus method, there is a lot of testing and analysis that needs to be done. The benefits, however, are intriguing: an implementation could increase the block rate substantially without compromising the security of the network

    So even the papers from our Science team need to be vetted and I'm not sure who is responsible if anyone for this. I remember there was an issue where it was recommended that he be allowed to review his own work and that was ridiculous. PEER review is a BARE minimum on a security dependent project.

    I know I have the time to read and vet all these changes nor do I have the ability to check the pure math involved, only the methodology behind. I was gladdened to see the team had decided to hold off on BF until they could be properly vetted and hope that this continues into the future. As I've stated before, It will only take ONE mistake to ruin the credibility of this project. THIS IS NOT ETH! It cannot just become mutable because there is a fuckup.



    Your points are good ones, but your concerns are addressed in the text.  Nobody is jumping into anything, just investigating possibilities.

      I  too am pleased to see the extended review time for bulletproofs (which has already netted improvements in the code/operation) despite my enthusiasm to embrace the advances.  Remember when it took years to advance one step, with a handful of contributors?  This is still lightspeed Smiley

  • Anon136
    Legendary
    *
    Offline Offline

    Activity: 1722
    Merit: 1217



    View Profile
    February 22, 2018, 11:08:54 PM
     #37578
    Quote from: explorer on February 22, 2018, 10:23:03 PM
    Your points are good ones, but your concerns are addressed in the text.  Nobody is jumping into anything, just investigating possibilities.

    I  too am pleased to see the extended review time for bulletproofs (which has already netted improvements in the code/operation) despite my enthusiasm to embrace the advances.  Remember when it took years to advance one step, with a handful of contributors?  This is still lightspeed Smiley

    Member waiting for the database to be completed mean while monero was sucking down 10+ gb of ram or something? I member.

    I might have lost hope and sold if I could have even gotten to my damned monero to sell it!
    Rep Thread: https://bt.irlbtc.com/view/381041
    If one can not confer upon another a right which he does not himself first possess, by what means does the state derive the right to engage in behaviors from which the public is prohibited?

  • Toda da Hodla
    Newbie
    *
    Offline Offline

    Activity: 8
    Merit: 0


    View Profile
    February 22, 2018, 11:30:06 PM
     #37579
    HELP!!  Huh

    Would anyone be kind enough to shed some light on how I might go about resolving this DB error.

    I noticed whilst downloading the blockchain (output from moenrod) that we had stopped @ 20:57 Block 1347628.

    I decided to reboot as the server had completely crashed.

    After I realised that the controller/hard disk had fallen over, I restarted but it refused 3 times on the trot.

    I'm guessing that as the last entry in the log before that block of corrupt data (....±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ.....) is 20:56 Block 1347408, that the data I saw from monerod (blocks 1347408 to 1347628) was the last amount of data the server had in memory before it simply couldn't write it to the hd.

    I have pasted the relevant bits below. Any help would be greatly appreciated!

    2018-02-22 20:56:28.076   [P2P6]   INFO    global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154   [144.76.67.70:18080 OUT]  Synced 1347368/1515381
    2018-02-22 20:56:29.720   [P2P6]   INFO    global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154   [144.76.67.70:18080 OUT]  Synced 1347388/1515381
    2018-02-22 20:56:31.987   [P2P6]   INFO    global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154   [144.76.67.70:18080 OUT]  Synced 1347408/1515381
    2018-02-22 20:56:34.927   [P2P6]   INFO    global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154   [144.76.67.70:18080 OUT]  Synced 134FÜýÕ§¡b #– ¶óòüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦]Cê±ÏüÞ¶o@¬Æ¦2018-02-22 22:21:01.094       7f9f7b325740   INFO    logging   contrib/epee/src/mlog.cpp:148   New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
    2018-02-22 22:21:01.100       7f9f7b325740   INFO    global   src/daemon/main.cpp:279   Monero 'Helium Hydra' (v0.11.1.0-release)
    2018-02-22 22:21:01.105       7f9f7b325740   INFO    global   src/daemon/protocol.h:55   Initializing cryptonote protocol...
    2018-02-22 22:21:01.105       7f9f7b325740   INFO    global   src/daemon/protocol.h:60   Cryptonote protocol initialized OK
    2018-02-22 22:21:01.129       7f9f7b325740   INFO    global   src/daemon/p2p.h:63   Initializing p2p server...
    2018-02-22 22:21:12.343       7f9f7b325740   INFO    global   src/daemon/p2p.h:68   P2p server initialized OK
    2018-02-22 22:21:12.362       7f9f7b325740   INFO    global   src/daemon/rpc.h:58   Initializing core rpc server...
    2018-02-22 22:21:12.372       7f9f7b325740   INFO    global   contrib/epee/include/net/http_server_impl_base.h:70   Binding on 127.0.0.1:18081
    2018-02-22 22:21:12.381       7f9f7b325740   INFO    global   src/daemon/rpc.h:63   Core rpc server initialized OK on port: 18081
    2018-02-22 22:21:12.381       7f9f7b325740   INFO    global   src/daemon/core.h:73   Initializing core...
    2018-02-22 22:21:12.445       7f9f7b325740   INFO    global   src/cryptonote_core/cryptonote_core.cpp:323   Loading blockchain from folderhome/toda/.bitmonero/lmdb ...
    2018-02-22 22:21:12.517       7f9f7b325740   WARN    blockchain.db.lmdb   src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:21:12.534       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR
    2018-02-22 22:21:12.534       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod() [0x7c8a24]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::BlockchainLMDB::open(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1b26 [0x7f1df6]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:cryptonote::core::init(boost::program_options::variables_map const&, cryptonote::test_options const*)+0xc69 [0x8341a9]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::run(bool)+0x1e0 [0x63cd10]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x2a [0x73f91a]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f9f7a64a830]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:21:12.645       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:21:12.672       7f9f7b325740   ERROR   cn   src/cryptonote_core/cryptonote_core.cpp:399   Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:21:12.673       7f9f7b325740   INFO    global   src/daemon/rpc.h:90   Deinitializing rpc server...
    2018-02-22 22:21:12.678       7f9f7b325740   INFO    global   src/daemon/p2p.h:90   Deinitializing p2p...
    2018-02-22 22:21:12.693       7f9f7b325740   INFO    global   src/daemon/core.h:89   Deinitializing core...
    2018-02-22 22:21:12.703       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR*
    2018-02-22 22:21:12.703       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:21:12.764       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:21:12.764       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod:cryptonote::Blockchain::deinit()+0x496 [0x7fe036]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::core::deinit()+0x25 [0x82af75]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:daemonize::t_core::~t_core()+0xcb [0x65a6eb]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::~t_daemon()+0xf7 [0x63b7a7]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x34 [0x73f924]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f9f7a64a830]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:21:12.765       7f9f7b325740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:21:12.775       7f9f7b325740   ERROR   daemon   src/daemon/core.h:94   Failed to deinitialize core...
    2018-02-22 22:21:12.775       7f9f7b325740   INFO    global   src/daemon/protocol.h:77   Stopping cryptonote protocol...
    2018-02-22 22:21:12.775       7f9f7b325740   INFO    global   src/daemon/protocol.h:81   Cryptonote protocol stopped successfully
    2018-02-22 22:21:34.238       7f4226e98740   INFO    logging   contrib/epee/src/mlog.cpp:148   New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
    2018-02-22 22:21:34.238       7f4226e98740   INFO    global   src/daemon/main.cpp:279   Monero 'Helium Hydra' (v0.11.1.0-release)
    2018-02-22 22:21:34.238       7f4226e98740   INFO    global   src/daemon/protocol.h:55   Initializing cryptonote protocol...
    2018-02-22 22:21:34.238       7f4226e98740   INFO    global   src/daemon/protocol.h:60   Cryptonote protocol initialized OK
    2018-02-22 22:21:34.239       7f4226e98740   INFO    global   src/daemon/p2p.h:63   Initializing p2p server...
    2018-02-22 22:21:45.930       7f4226e98740   INFO    global   src/daemon/p2p.h:68   P2p server initialized OK
    2018-02-22 22:21:45.930       7f4226e98740   INFO    global   src/daemon/rpc.h:58   Initializing core rpc server...
    2018-02-22 22:21:45.930       7f4226e98740   INFO    global   contrib/epee/include/net/http_server_impl_base.h:70   Binding on 127.0.0.1:18081
    2018-02-22 22:21:45.930       7f4226e98740   INFO    global   src/daemon/rpc.h:63   Core rpc server initialized OK on port: 18081
    2018-02-22 22:21:45.930       7f4226e98740   INFO    global   src/daemon/core.h:73   Initializing core...
    2018-02-22 22:21:45.931       7f4226e98740   INFO    global   src/cryptonote_core/cryptonote_core.cpp:323   Loading blockchain from folderhome/toda/.bitmonero/lmdb ...
    2018-02-22 22:21:45.931       7f4226e98740   WARN    blockchain.db.lmdb   src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:21:45.931       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR
    2018-02-22 22:21:45.931       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod() [0x7c8a24]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::BlockchainLMDB::open(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1b26 [0x7f1df6]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:cryptonote::core::init(boost::program_options::variables_map const&, cryptonote::test_options const*)+0xc69 [0x8341a9]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::run(bool)+0x1e0 [0x63cd10]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x2a [0x73f91a]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f42261bd830]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:21:45.935       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:21:45.935       7f4226e98740   ERROR   cn   src/cryptonote_core/cryptonote_core.cpp:399   Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:21:45.936       7f4226e98740   INFO    global   src/daemon/rpc.h:90   Deinitializing rpc server...
    2018-02-22 22:21:45.936       7f4226e98740   INFO    global   src/daemon/p2p.h:90   Deinitializing p2p...
    2018-02-22 22:21:45.941       7f4226e98740   INFO    global   src/daemon/core.h:89   Deinitializing core...
    2018-02-22 22:21:45.941       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR*
    2018-02-22 22:21:45.941       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod:cryptonote::Blockchain::deinit()+0x496 [0x7fe036]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::core::deinit()+0x25 [0x82af75]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:daemonize::t_core::~t_core()+0xcb [0x65a6eb]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::~t_daemon()+0xf7 [0x63b7a7]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x34 [0x73f924]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f42261bd830]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:21:45.945       7f4226e98740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:21:45.945       7f4226e98740   ERROR   daemon   src/daemon/core.h:94   Failed to deinitialize core...
    2018-02-22 22:21:45.946       7f4226e98740   INFO    global   src/daemon/protocol.h:77   Stopping cryptonote protocol...
    2018-02-22 22:21:45.946       7f4226e98740   INFO    global   src/daemon/protocol.h:81   Cryptonote protocol stopped successfully
    2018-02-22 22:22:23.980       7f5241203740   INFO    logging   contrib/epee/src/mlog.cpp:148   New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
    2018-02-22 22:22:23.980       7f5241203740   INFO    global   src/daemon/main.cpp:279   Monero 'Helium Hydra' (v0.11.1.0-release)
    2018-02-22 22:22:23.981       7f5241203740   INFO    global   src/daemon/protocol.h:55   Initializing cryptonote protocol...
    2018-02-22 22:22:23.981       7f5241203740   INFO    global   src/daemon/protocol.h:60   Cryptonote protocol initialized OK
    2018-02-22 22:22:23.981       7f5241203740   INFO    global   src/daemon/p2p.h:63   Initializing p2p server...
    2018-02-22 22:22:30.244       7f5241203740   INFO    global   src/daemon/p2p.h:68   P2p server initialized OK
    2018-02-22 22:22:30.244       7f5241203740   INFO    global   src/daemon/rpc.h:58   Initializing core rpc server...
    2018-02-22 22:22:30.244       7f5241203740   INFO    global   contrib/epee/include/net/http_server_impl_base.h:70   Binding on 127.0.0.1:18081
    2018-02-22 22:22:30.244       7f5241203740   INFO    global   src/daemon/rpc.h:63   Core rpc server initialized OK on port: 18081
    2018-02-22 22:22:30.244       7f5241203740   INFO    global   src/daemon/core.h:73   Initializing core...
    2018-02-22 22:22:30.245       7f5241203740   INFO    global   src/cryptonote_core/cryptonote_core.cpp:323   Loading blockchain from folderhome/toda/.bitmonero/lmdb ...
    2018-02-22 22:22:30.245       7f5241203740   WARN    blockchain.db.lmdb   src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:22:30.246       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR
    2018-02-22 22:22:30.246       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod() [0x7c8a24]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::BlockchainLMDB::open(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1b26 [0x7f1df6]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:cryptonote::core::init(boost::program_options::variables_map const&, cryptonote::test_options const*)+0xc69 [0x8341a9]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::run(bool)+0x1e0 [0x63cd10]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x2a [0x73f91a]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:22:30.249       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f5240528830]
    2018-02-22 22:22:30.250       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:22:30.250       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:22:30.250       7f5241203740   ERROR   cn   src/cryptonote_core/cryptonote_core.cpp:399   Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
    2018-02-22 22:22:30.250       7f5241203740   INFO    global   src/daemon/rpc.h:90   Deinitializing rpc server...
    2018-02-22 22:22:30.250       7f5241203740   INFO    global   src/daemon/p2p.h:90   Deinitializing p2p...
    2018-02-22 22:22:30.255       7f5241203740   INFO    global   src/daemon/core.h:89   Deinitializing core...
    2018-02-22 22:22:30.255       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:120   Exception: cryptonote::DB_ERROR*
    2018-02-22 22:22:30.255       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:121   Unwound call stack:
    2018-02-22 22:22:30.258       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [1] ./monerod:__wrap___cxa_throw+0x102 [0x8914e2]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [2] ./monerod:cryptonote::Blockchain::deinit()+0x496 [0x7fe036]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [3] ./monerod:cryptonote::core::deinit()+0x25 [0x82af75]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [4] ./monerod:daemonize::t_core::~t_core()+0xcb [0x65a6eb]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [5] ./monerod:daemonize::t_daemon::~t_daemon()+0xf7 [0x63b7a7]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [6] ./monerod:daemonize::t_executor::run_interactive(boost::program_options::variables_map const&)+0x34 [0x73f924]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [7] ./monerod:bool daemonizer::daemonize<daemonize::t_executor>(int, char const**, daemonize::t_executor&&, boost::program_options::variables_map const&)+0x18c [0x741d4c]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [8] ./monerod:main+0x14b7 [0x611bc7]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [9]lib/x86_64-linux-gnu/libc.so.6:__libc_start_main+0xf0 [0x7f5240528830]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159       [10] ./monerod:_start+0x29 [0x619389]
    2018-02-22 22:22:30.259       7f5241203740   INFO    stacktrace   src/common/stack_trace.cpp:159   
    2018-02-22 22:22:30.259       7f5241203740   ERROR   daemon   src/daemon/core.h:94   Failed to deinitialize core...
    2018-02-22 22:22:30.260       7f5241203740   INFO    global   src/daemon/protocol.h:77   Stopping cryptonote protocol...
    2018-02-22 22:22:30.260       7f5241203740   INFO    global   src/daemon/protocol.h:81   Cryptonote protocol stopped successfully

  • explorer
    Legendary
    *
    Offline Offline

    Activity: 2016
    Merit: 1259



    View Profile
    February 22, 2018, 11:37:10 PM
     #37580
    Quote from: Anon136 on February 22, 2018, 11:08:54 PM
    Quote from: explorer on February 22, 2018, 10:23:03 PM
    Your points are good ones, but your concerns are addressed in the text.  Nobody is jumping into anything, just investigating possibilities.

    I  too am pleased to see the extended review time for bulletproofs (which has already netted improvements in the code/operation) despite my enthusiasm to embrace the advances.  Remember when it took years to advance one step, with a handful of contributors?  This is still lightspeed Smiley

    Member waiting for the database to be completed mean while monero was sucking down 10+ gb of ram or something? I member.

    I might have lost hope and sold if I could have even gotten to my damned monero to sell it!

    haha ya I tried to set it up the first time in May 2014.  Couldn't even run it with 4GB RAM.  It didn't happen until Hydrogen Helix release with LMDB.  that was a long wait!  Now a few months is just... nothing.
    Pages: « 1 ... 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 [1879] 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 ... 2131 »
      Print  
Page 1878
Viewing Page: 1879

IRLBTC™ © 2025 IRLBTC.com