Untitled attachment

Notices where this attachment appears

1. チャノさん (japananon@mitra.anon-kenkai.com)'s status on Saturday, 25-May-2024 08:19:16 JST チャノさん

   I'm about to try the Haveno-Reto implementation of Haveno mainnet. My understanding is that multiple Haveno networks can exist, the keys for each being hardcoded into the client. Haveno itself is P2P (serverless), but the dev of each implementation holds the keys for the network, determining who can be granted roles as arbitrators etc.

   This differs from Bisq significantly, where the Bisq DAO is a central entity that makes these decisions (though technically Bisq could be forked and rival networks could be created in the same way). Haveno's maker(s) appear to want this approach, as multiple parties each running their own separate implementations of Haveno means there are more heads of the hydra to cut off when State actors come to shut things down... ideally speaking, anyway.

   Currently there are two known implementations of Haveno I managed to find...

   Haveno-Reto: https://github.com/retoaccess1/haveno-reto

   HardenedSteel (development stalled): https://github.com/HardenedSteel/haveno-mainnet

   This is still early days, and trading on these nascent networks is far from guaranteed. But I want to poke around and report back on how active and useful these implementations actually are for the average user.