• 0 Posts
  • 60 Comments
Joined 22 days ago
cake
Cake day: June 11th, 2024

help-circle

  • And other things about the project are also concerning me:

    • It uses Qt for UI, while modern browsers can draw UI with their own engines. A redundant dependency which also will harm modularity and embeddablity.
    • Modern browsers have complexity of operating systems. It’s just a waste of resources to build an independent browser from scratch, but not to make the engine reusable.

    This is a poor choice.

    The other things: It’s so independent (from google), but already got sponsorship and changed the landing page to a typical landing of a startup. This independence is populism. Just enough one for feeding their adepts with promises. I won’t be surprised of possible advertisement integrations made “for maintaining independence”.

    NGMI.



  • I wouldn’t assume the right strategy for inputs. To an outsider they are all indistinguishable, but the sender, an exchange for example, can mark operations (withdrawals) done with the same account and store that information. Every input has 16 potential members selected from the blockchain. But if tx has many inputs, and each input has among the ring one previously marked input associated with the same exchange account, it will be likely that tx was created by the person with that exchange account. If the person later will try to deposit this coins to another account of the exchange, probably exchange could link two account, at least as potentially linked. So input aggregation can give additional hints for EABE attack.

    Probably, it is better to aggregate inputs earlier, before churning, and don’t mix churned coins with unchurned. But Monero need more general improvements as FCMP/FCMP++.