[–] [S] 2 points 1 week ago

Yes you're right. This is why the swap/bridge UI will simply be a website using remote RPC nodes, like most other dapps today. Only liquidity providing will require installing a program, because it will have to operate 24 hours a day and sign transactions itself on behalf of the user. But even then, we could imagine a network of decentralized liquidity providers based on MPC, to whom users could delegate their liquidity directly from the web app, without installing anything.

And yes once BTC is implemented, it would likely work natively with most of its forks such as BCH.

  • source
  • parent
  • context
  • [–] [S] 2 points 1 week ago

    No, hyperliquid is a separate chain with its own (rather small) validator set, much like THORChain, Chainflip, and most "decentralized" bridges today. This one would directly settle atomic swaps between 2 arbitrary chains. Not a single additional validator trusted except those of the target and the destination chain.

  • source
  • parent
  • context
  •  

    cross-posted from: https://lemmy.ml/post/49912885

    Hi,

    I'd like to have your feedback on a project idea.

    I want to build a fast and efficient trustless bridge protocol based on atomic swaps, offering a user experience similar to that of popular custodial bridges.

    Unlike P2P DEXs such as BasicSwap, Bisq, and Haveno, users would trade against automated market makers. It would be an automated open-source program that anyone could self-host, which would automatically accept users' swap requests for preconfigured pairs, in exchange for a small fee paid to the node operator.

    The protocol would automatically aggregate liquidity from multiple market makers to fulfill large swaps, ensuring that liquidity isn't fragmented even if it's not deposited in a common pool.

    The protocol would use adaptor signatures based atomic swaps when possible, for greater privacy and efficiency compared to HTLCs. I plan to initially support EVM chains (both native and ERC20), BTC and XMR.

    The UI would be a simple web-based app, using RPC providers and light clients for blockchain interaction.

    Unlike side-chain based bridges like THORChain, this architecture would not require the users or market makers to trust a separate validator set. Additionally, market makers would not be required to lock up all of their funds in smart contracts until they're participating in a swap. In fact, they could even provide Just-in-Time liquidity and, the rest of the time, leave their funds deposited on another DeFi protocol such as AAVE, withdrawing only to fulfill a swap.

    I hope this design could attract users and liquidity providers looking for a simpler and faster protocol than existing P2P DEXs, but with greater security than today's leading bridges.

    What do you think about it?

    Could it reach a high level of adoption?

    Would you use it to bridge, or provide liquidity yourself to this protocol?

    [–] 4 points 1 year ago (2 children)

    Couldn't you use HMAC with shared secret key to authenticate messages while keeping plausible deniability? Since the key is only supposed to be known to the 2 parties, the recipient can deduce that a message was actually sent by the sender if he did not create it himself. I think that's what OTR was using.

  • source
  • DroidFS v2.2.0 (forge.chapril.org)
     

    cross-posted from: https://lemmy.ml/post/18512730

    DroidFS is an Android application providing rootless support for gocryptfs and CryFS encrypted file systems. It features an encrypted camera, biometric unlocking, integrated secure file viewers and allows decrypted files to be exposed to other applications. It is 100% FLOSS and developed voluntarily.

    This new version...

    • aims to improve the user interface
    • implements a foreground service to keep volumes open in the background
    • allows tweaking the file export method used for sharing content with other apps
    • adds new Turkish, Simplified Chinese and Hebrew translations
    • and of course, fixes a few bugs

    Official APKs are available for download now. It should land on F-Droid very soon, with a new per-ABI APKs split which will reduce quite a bit the download as well as the installed app size.

    Feel free to give some feedback, open bug reports, ask for help, contribute, or just discuss about the project!

    DroidFS v2.2.0 (forge.chapril.org)
     

    DroidFS is an Android application providing rootless support for gocryptfs and CryFS encrypted file systems. It features an encrypted camera, biometric unlocking, integrated secure file viewers and allows decrypted files to be exposed to other applications. It is 100% FLOSS and developed voluntarily.

    This new version...

    • aims to improve the user interface
    • implements a foreground service to keep volumes open in the background
    • allows tweaking the file export method used for sharing content with other apps
    • adds new Turkish, Simplified Chinese and Hebrew translations
    • and of course, fixes a few bugs

    Official APKs are available for download now. It should land on F-Droid very soon, with a new per-ABI APKs split which will reduce quite a bit the download as well as the installed app size.

    Feel free to give some feedback, open bug reports, ask for help, contribute, or just discuss about the project!

     

    Hi Lemmyverse,

    Having always been interested in IT and cybersecurity, I quickly became concerned about privacy. Over the years, I've gained a lot of experience. I started using only free software, hardening my OS, encrypting everything, using Tails... I even developed several security-focused software such as DroidFS, TorVirt and a few others.

    Today, I'm going freelance. I offer security and privacy consulting services tailored to your needs. Of course, I accept Monero and other cryptocurrencies. Check out my website if you're interested.

    Otherwise, apologies for the inconvenience, here's a project that's far too little known in my opinion: https://github.com/maqp/tfc

    view more: next ›