<<  >> (p.24)
    Author Topic: DASH Collapsing Monero UP  (Read 40432 times)
    This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
    qwizzie
    Legendary
    *
    Offline Offline

    Activity: 2548
    Merit: 1245



    View Profile
    September 09, 2019, 05:21:34 PM
    Last edit: September 09, 2019, 06:17:51 PM by qwizzie
     #461

    So your chasing ghosts.

    Am i chasing ghosts though ? And has it actually been resolved ? keejef's comment was first marked as "Informative" but essentially not a bug.
    Then it was deemed as valuable enough information that needed to be put in a readme.md on Github, which was merged into
    Monero's master 29 days ago. Merging something into a readme.md on Github is of course not the same as actually putting out a
    code fix to this locktime vulnerability. It just means that you hope people read that readme.md and behave correctly and hope that exchanges
    pay attention to the email that was sent to them (i call this shifting responsebility to users and exchanges), it however does nothing against
    that locktime vulnerability.

    Let me repeat that locktime vulnerability according Monero's own readme.md on Github :

    Quote
    ### Blockchain-based
    Certain blockchain "features" can be considered "bugs" if misused correctly. Consequently, please consider the following:

    - When receiving monero, be aware that it may be locked for an arbitrary time if the sender elected to, preventing you from spending that
      monero until the lock time expires. You may want to hold off acting upon such a transaction until the unlock time lapses. To get a sense of
      that time, you can consider the remaining blocktime until unlock as seen in the `show_transfers` command.

    The problem with this is that every single Monero transaction needs to be thoroughly checked on suspicious locktime activity by its
    receivers, which directly undermines Monero's trustless transaction capability. Why not remove/change this locktime or put a hardcap on it ?
    (to be automatically unlocked after x number of blocks). Or change it to how Bitcoin handles it ?

    Quote
    A key difference is that with Bitcoin the locktime doesn't let it enter a block until that height, whereas with Monero it goes into a
    block but can't be redeemed to that height.
     
    On second thought maybe its better that Monero keeps this vulnerability in its code, makes it that much more easy for competing
    cryptoprojects to point this out... yeah, lets forget about this whole thing.

    There is indeed really no need to change anything, i'm sure users will all read that readme.md on Github and behave perfectly correct
    and exchanges will ofcourse be more then happy to check each and every Monero transaction on this locktime vulnerability.

    Sorry for the off topic route here, i promise from now on it will all be about price, price and price.

    Learn from the past, set detailed and vivid goals for the future and live in the only moment of time over which you have any control : now
Page 23
Viewing Page: 24