• 0 Posts
  • 19 Comments
Joined 8 months ago
cake
Cake day: November 12th, 2023

help-circle

  • Great blog! does this have any benefit over a polyseed mnemonic where you also have a secret password? With polyseed as well as BIP39, even if your mnemonic is caught you can use that plain seed as a decoy that opens a fake wallet, while your real seed with your real funds can only be decrypted with the password, and this encrypted mnemonic by hand won’t result in a valid seed so the malicious actor can assume that a valid seed still exists and it still needs to be seized or brute forced?

    I think this method is better when using steganography combined since the mnemonic looks like a blob of nothing when reading the contents of the file, while if an actual seed was used it could reveal there is a Monero seed hidden in that file, but then I think a better encryption method can be used since using digital files loses the benefit of not using a computer?

    https://github.com/tevador/polyseed




  • ok no servers make sense, but choosing arbitrators is like choosing a server equivalent to a multisig wallet, there is “someone’s computer” that will have the third key to resolve arbitration issues, and also can it read chat messages? if so networks should be picked with care, but of course trades can complete without it, but I was confused and called it “federation” for the fact they should be merged in the UI



  • it was explained in the blog post I shared, but Ratatui’s share come from this: https://www.drips.network/app/drip-lists/34625983682950977210847096367816372822461201185275535522726531049130 so the Radicle project decided to split a certain value between all dependencies the project uses, and “Drips” is an ethereum based contract that is supposed to distribute a percentage to each projects “address” but in this case how I think it’s working is OpenCollective is the one holding the keys to the address that the smart contract sends funds to, so they basically collect the amount earned and send it to the project’s owner in this case Ratatui, otherwise that would be “lost” if no one were to claim those funds, and if Drips is contract based it means there is no one holding and distributing the rewards so this is why you have to claim the funds from the contract, and it’s why it’s not a direct contribution in my mind but also the difference is the previous support to crypto was native in the OpenCollective app and this is what is now disabled, but this is just an example of them receiving and holding funds via crypto means still



  • That is awesome, thank you for the write up and setting the precedent with an open mind!

    Their initial reasoning makes sense, with their crypto earnings being only 1.4% of the total usage, while technically having to manage the services to handle incoming payments for all different asset, and all mainstream coins having traceability as a feature making dealing with it way more complicated, so if they looked at it impartially and not politically biased they should definitely consider having a Monero only option by default, which curiously was also missing from the initial implementation, where I can send money I purchased, received or mined and no one can ever receive “tainted funds” but rather just receive digital cash, as like cash it is money that can move from various different hands without a trace, which then can all be equally spent to pay developers, goods, services, etc. and not face risk of what the real origin of funds is. It should come with the intent to be a saner option for payments rather than accepting many coins at once just for the sake of accepting it.

    but I hope the Drips approach has success




  • I just think it is a way simpler design, everything is a variation of the NIP-01 note https://github.com/nostr-protocol/nips/blob/master/01.md#events-and-signatures

    {
      "id": <32-bytes lowercase hex-encoded sha256 of the serialized event data>,
      "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
      "created_at": <unix timestamp in seconds>,
      "kind": <integer between 0 and 65535>,
      "tags": [
        [<arbitrary string>...],
        // ...
      ],
      "content": <arbitrary string>,
      "sig": <64-bytes lowercase hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field>
    }
    

    So data portability is enforced by default for the protocol, and it is flexible in a way that clients can support new event kinds without knowing about it, so adding a video event kind to create a youtube alternative would show up even on outdated clients as they’ll still be able to show every note events, and the same for outdated relays that will continue to store every note event you broadcast, you don’t need to spawn a new server to self-host a new instance of a nostr implementation, just use the same clients and same relays as always, so people have made torrent sharing sites (https://dtan.xyz) and video platforms for example and it doesn’t seem like the AP protocol is very open and flexible to these ideas and implementations




  • I think if you gave nostr a chance you would see some benefits even for those reasons, like you also get to be in contact with the people that maintain infrastructure (relay admins), some admins can require the payment of a fee or simply whitelist your pubkey to read/write notes, which creates “closed communities”, but the difference from AP is you are able to have many different relays at the same time for your infrastructure, so you don’t have a “single admin” that you may or may not like or trust that much, you can pick one or many at any time, or be your own