arseneSpeculoos

Founder @Speculoos Finance

blog

  • 15 Posts
  • 42 Comments
Joined 2 years ago
cake
Cake day: July 30th, 2023

help-circle
  • Hardware backdoors and exploits on Google Pixel (if they exist) are too prized to be shared and used to bust random drug dealers.

    The more people you share an exploit with, the more it risks getting exposed. You don’t want your million dollar hardware exploit to be discovered and patched just because a local police department sent an email to the wrong address.

    Here I think that the French want to be able to easily get into ALL mobile devices. They are just having a bad time with GrapheneOS.
    Their strategy is to use the media to make people avoid using pixels and GrapheneOS, and when few people use that, the idea that only criminals use that sounds more plausible. You become guilty just by using GrapheneOS, no further proof needed.



  • I like Lemmy, it’s more of a message board and I think it’s more adapted to the size of this community. I don’t have any experience with monstr.land, but Amethyst feels more like Twitter, and we would lose the connection with the rest of the federated world.

    Why not deploy a nostr instance on a sub domain of monero.town? That way we can try it out.

    If this instance disappears could you please give an advance notice so that we can migrate our accounts based here?

    Note: during the outage we had no way of contacting you to get more information or help out, and that was a bit frustrating. Could we agree to meetup for example on lemmy.ml/c/Monero if there is an outage next time?

    Thanks


  • I think the whole PoS finality layer thing got out of proportions because people heard PoS and flipped.
    At the beginning, the Monero Research Lab was just gathering ideas on how to deal with the situation and that was one of the ideas proposed.
    People heard PoS, and it went viral, with all the misunderstanding that virality and oversimplification bring.

    If you listen to KabayaNerve on MoneroTalk you will see that he proposed that and immediately said that the PoS finality layer will not get community approval and is very unlikely to be implemented.
    You still have people on Twitter saying that some undefined people that may or may not be Monero devs are pushing for Monero to become a PoS coin like Ethereum. It’s simple, it’s emotional, it got viral, the only issue is that it’s wrong (it’s not an accurate description of what is happening).

    For BTC, I think that the huge network effects are the main reasons for it maintaining its price and thus security budget until now (as for any coin, you could say).
    As you said, it will be interesting to see how the situation develops after 2 more halvings.
    A conclusion in my article is that BTC now has a king, and its name is Blockstream. They control the network and will update it as they see fit, what the plebs and jealous people like us think is of no importance. They will never let that much power evaporate from their hands, and will rather hardfork into PoS than letting that happen because some miner does not make enough money.
    The original Bitcoin is dead, long live Bitcoin


  • Haha! STDs for Monero devs! The analogy is funny.

    You got it, the finality layer is complex and needs a lot of conditions to be done right, and it’s outsourcing security to another network, not great.

    I don’t think that the current BTC POW is that elegant though. Mining rewards are declining, and the fees are not coming. So the security budget is declining at each halving. At some point, mining hashrate will decrease, because miners run a business, and BTC will also be open for the same kinds of disruptions.
    I once wrote an article on the topic.



  • I don’t think it will happen either, the community too much opposed.

    First there are people that don’t take the time to read about it and think it’s about changing from RandomX mining to staking. Then there are people like me that do not want to rely on another chain for the security of Monero.

    It’s still good to discuss it openly. This way, we can get to a better solution and the community can decide in what way this PoS finality layer can be a contingency plan or not.





  • It’s true that we should not rush into action without carefully considering the consequences in the short and long term.

    The attack still demonstrates an important point of improvement for the Monero ecosystem. We now have a hostile mining pool with too much hashrate and it’s time to dust off the theoretical attack scenarios and see what harm it can do and what we can do about it.

    The attacker can and does reorg blocks as a consequence of selfish mining. That means less mining rewards for the other miners.

    The attacker cannot censor any specific transaction (because the transactions are private so there is no easy way to differentiate any specific one). They could still decide to only mine empty blocks or their own transactions, and that would increase confirmation times for all the other users.

    The attacker can try a double spend attack, for example on an exchange. They can deposit XMR at the exchange, get BCH for it and withdraw it. Then they reorg the latest blocks up to before depositing their XMR to add a transaction before that deposit. That transaction will send that previously deposited XMR to one of their other wallets instead of going to the exchange.
    If this attack is successful, in the end, they will have both the BCH from the exchange and the XMR in their other wallet.
    This is actually why Kraken has increased their confirmation times for XMR to 24 hours. When you increase the confirmation time, you increase the number of blocks between the XMR deposit and the BCH withdrawal in the scenario above. So much so that even with 80% of the hashrate the attack is no longer feasible.

    There are other points I guess, but we need to address these. Some action needs to be taken to improve, but as you said, we need to be careful.


  • Not all coins should be privacy coins, not all flowers should be red. The diversity of the ecosystem is very important.

    It’s good that you are interested in it. Described like this, it seems a bit strange. Who’s paying for the security of the network if there are no fees?
    My first idea when I hear that is, someone is running the blockchain at his own cost, very few people can do this. So that part of the network will be quite centralized.

    If that’s good or bad depends on what dance you want for yourself over there.













  • arseneSpeculoostoMoneroIdea on how to fight qubic.
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    This is very close the the finality layer idea being discussed currently.
    The idea is to record somewhere that this or that block has been seen and is considered final. At that point, even if someone publishes a longer chain afterwards, the longer chain will be ignored as it does not continue from the blocks that have been finalized already.

    It is an interesting and good idea @[email protected]. There are some technical and community details that need consideration as to how exactly to implement that, but it’s one of the good options on the table.

    For example, one of the technical details is were/how should we record that a block is finalized.
    For this, we need to align a lot of decentralized nodes on a common state of things (which block is finalized), so that they are aligned on what has happened and what has not.
    We actually already have a solution for that: a blockchain. Blockchains are a solution to the byzantine general’s problem (a.k.a aligning decentralized actors with each other on a shared state of things, even though they do not all communicate with one another, they communicate at different speed, etc).
    So we could use a blockchain to record that this or that Monero block is finalized.
    It needs to be a different blockchain, and have some characteristics like fast enough block time, a way to avoid deep re-orgs (POW with enough security budget or POS),…
    Right now if you directly apply these conditions, you end up on the bright idea of using Ethereum or something like Litecoin.
    The Monero community does NOT want to have to rely on ETH or LTC for security.
    That would feel like a huge blow and a huge let down…

    But yeah, if need be, for me, this is still a perfectly acceptable temporary solution.
    What do you think?


  • If I remember correctly, that’s partly because p2pool requires access to a full node with the whole blockchain, while a lot (or some?) of the current hash rate is not running their own nodes.
    If you somehow force everyone to p2pool we are not sure of the distribution and decentralization of the remaining miners, as some mining will drop out instead of running their own node.
    Sometimes it’s because they don’t have the 200gb available for storing the blockchain. Sometimes they are mining multiple blockchains and requiring a full monero node is too much hassle.

    Granted, with p2pool you can mine using someone else’s full node and let it spy on you a bit. Do we want that?

    The other big issue is that you would have to hard-fork changes to the protocol to impose p2pool and that’s a big change that should be carefully considered, not done in a rush.

    We have to remember that Monero is fine for now (as in not dying right now), we are preparing mitigations for POW centralization issues and the cure should not be more severe than the disease.