![User banner](https://monero.town/pictrs/image/173101e5-584e-4054-99e6-3990ef66ffe9.webp)
Yes it is an Amethyst fork with a Monero wallet and support for tipping
And then switching from Matrix to nostr channels and from IRC to SimpleX private messaging
It seems to be more like hiding coins in different addresses while obscuring it on chain & using some clever math to make the UX better.
You are accurate: you "hide" coins in different addresses which are only know to the receiver and the sender, I cannot paste a SP address in a block explorer and find what addresses belong to it, and what is the total balance of this BTC user. I can however send a payment to it and then have a "watch" on this entity, there is no obscuring happening on-chain so usual heuristics like when a coin is spent, to where, how much is change, etc still apply.
Which also means if they spend many SP payments together, they reveal to me & others all the addresses belonging to them and what the total balance was, you can think of it like if bitcoin users sent their BTC addresses to each other via DMs, but it removes the interactivity step from handling new addresses, while adding the scanning requirement so the receiver can also know which addresses were generated to them without having to ask senders each time
It is a good feature to have in general in my opinion, but definitely does not come any close to competing with Monero still
Based. I couldn't find it on annas archive before
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?
And trocador.app released gift cards :D people must be gift card shopping, I hear there's many options available
You can compare the diffs like so: https://github.com/haveno-dex/haveno/compare/master...retoaccess1:haveno-reto:master but for extra security build the binaries yourself if their repo's changes look good or as expected from the Haveno setup documentation
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
I didn't read the docs yet but what do the "haveno networks" do, wouldn't it be beneficial to have a federated design? I.e. even if they don't interact directly, I as a user of both can list their orders, make trades on each on the same 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
As per docs they removed this option for individual users to contribute using crypto as a payment method: https://docs.opencollective.com/help/financial-contributors/crypto but they still manage crypto assets, as shown by the recent Ratatui invoice paid by the "drips network" https://opencollective.com/ratatui/contributions/751695
fwiw Open Collective still manages crypto funds/grants for projects, I just saw this recently: https://blog.orhun.dev/open-source-funding-with-ratatui/ the Ratatui project set up a Open Collective to handle donations from the "DRIPS network" crypto
edit: also just looked more at the blog's site and at the donation page Crypto
only has Monero ;) https://donate.orhun.dev/ love it @[email protected] !
So I think that because of this, ease of development, ease of use, nostr has a big chance of staying around for 2 years still and maybe even bigger than AP but I may be wrong
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": ,
"kind": ,
"tags": [
[...],
// ...
],
"content": ,
"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
What would it take to have this in AP at the current state, and like could mitra and other clients start supporting these portable objects and just wait for others to catch on?
Or maybe a single attack by a bigger instance with more users is enough to put us down and be stopped from actually reach more people, and we'll never know what people actually feel by being constantly attacked for being small.
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
Choosing plugins during build are a great use case for a Gentoo ebuild with USE flags
hopefully they have a change of heart like they just did with randomx merge mining and confirm no pre-mine