-
m-relay
<googlemozilla:matrix.org> Hello
-
m-relay
<googlemozilla:matrix.org> Why can't I register using the monero.social homeserver?
-
m-relay
<googlemozilla:matrix.org> It says registration has been disabled
-
m-relay
<root:kimapr.net> That is probably the reason.
-
m-relay
<ofrnxmr:xmr.mx> read from here:
-
m-relay
-
k4r4b3y
ofrnxmr did my message fail to reach the matrix side?
libera.monerologs.net/monero/20241110#c458471
-
m-relay
<ofrnxmr:xmr.mx> Yrs
-
m-relay
<ofrnxmr:xmr.mx> I dont see your msgs on matrix
-
ofrnxmr
I see them here
-
ofrnxmr
"the installation option is still the bootleg scripts, right? " they arent bootleg, but yes
-
ofrnxmr
" I remember some discussion about the prospects of providing AppImage for BSX install. Is that still in play?" << yes, but saving installers for after the post-install experience is more usee friendly
-
k4r4b3y
thanks for the update
-
ofrnxmr
"Providing .exe for Windows is good, and the installation UX for linux should be as close to that as well (ie, double click on the AppImage file and done)" << we took the exe down, as its counterproductive to onboard users who cant use a terminal, when the current experience still requires using terminal and knowing how to manage debugging etc
-
m-relay
<sethforprivacy:monero.social> Tried to DM you about this (guess you're only on IRC and not on Matrix anymore), but to clarify this did have Core's approval before anything happened.
-
m-relay
<sethforprivacy:monero.social> If you could DM me I'd really appreciate it, can't figure out a way to DM you directly but it's been a while since I did the Matrix/IRC dance.
-
ofrnxmr
The scripts are more of a POC of how to simolify the experience. They can be turned into a deb/rpn/appimage etc, but they still build from source (and require blockchains)
-
m-relay
<ofrnxmr:xmr.mx> Seth For Privacy debruyne cant see that youre responding to hin
-
m-relay
<sethforprivacy:monero.social> Ugh
-
m-relay
<ofrnxmr:xmr.mx> Yeah, dm from libera <> matrix doesnt work
-
m-relay
<sethforprivacy:monero.social> Nice
-
m-relay
<sethforprivacy:monero.social> I love interoperability
-
m-relay
<sethforprivacy:monero.social> 😅
-
k4r4b3y
ofrnxmr: "[...]when the current experience still requires using terminal and knowing how to manage debugging etc[...]" <--- when would you say that the UX moves beyond this proof of concept phase?
-
ofrnxmr
Installers are the last thing on the todo list
-
k4r4b3y
So, the BSX is still in development-phase, when compared to haveno, then?
-
k4r4b3y
Because Haveno has many installer options among which are deb, flatpak and appimage
-
ofrnxmr
haveno also has arbitrition
-
ofrnxmr
Basicswap has no mitm to fix your issues
-
k4r4b3y
I was looking to getting the BSX somewhat ready for general usage, before I start recommending it to my local monero users, that's why I am asking around this topic.
-
ofrnxmr
No trade limits, no refunds, no p2p communication
-
ofrnxmr
Bsx _does_ work wonderfully
-
k4r4b3y
Well what's on the todo list then
-
k4r4b3y
I sense that we are talking past each other.
-
ofrnxmr
But even putting offers on the orderbook frpm the gui is confusing. Using the market maker scripts is better, but requires configuring json and running it from terminal
-
k4r4b3y
If it does work wonderfully, why aren't the exe got pulled back? Why isnt there an AppImage?
-
k4r4b3y
Why did*
-
ofrnxmr
Because its not for noobs
-
k4r4b3y
what
-
k4r4b3y
OK, then, what is your "works wonderfully" criteria? And why do I sense that it doesn't include "does this work for noobs?"
-
ofrnxmr
again, just posting an offer has 100 options, all of them describes like you need a phd to understand them
-
ofrnxmr
The amm is nice, but not integrated into the gui
-
ofrnxmr
works wonderfully = if you dont plan on posting offers (just taking offers), bsx is pretty easy to use, even if still a bit confusing.
-
k4r4b3y
OK. Here are the things I catch from our convo so far: 1. BSX works well. 2. But its UI is not easy to understand and parse for a newcomer. 3. The .exe got pulled back because even though BSX works well, it still requires one to shuffle between the debug window and the BSX window itself. 4. Also, because BSX needs to download the blockchains of each cryptos it does trade with, there are some challenges with distributing it in
-
k4r4b3y
AppImage format.
-
ofrnxmr
example of ux issue: "auto accept all/known/none" status is not yet relayed to the network
-
ofrnxmr
By default its set to "accept none" because" accept all allows your offer to be taken repeatedly (even if you only meant to sell once)
-
ofrnxmr
Yes ^^
-
k4r4b3y
alright
-
k4r4b3y
godspeed
-
k4r4b3y
Monero needs ample decentralized liquidity.
-
k4r4b3y
Else, it is fucked.
-
ofrnxmr
This sprint there mighr be a breaking change, where the "auto accept" status is added to the message relay
-
ofrnxmr
This fixed an issue where ppl can post fake offers
-
ofrnxmr
adding fhe market maker functionality to the gui allows users to auto-accept without accidentally selling too much
-
ofrnxmr
1. windows users are recommended to use a vm or wsl. sort of a litmus test 2. Offer creators are recommended to use the terminal based market market maker script
-
ofrnxmr
Bsx doesnt also doesnt have built in update notifications yet, and (unless using scripts) requires manually updating the blockchain software separately from bsx
-
k4r4b3y
ofrnxmr: these two points are only for the early-stage status of the BSX development, right?
-
ofrnxmr
yea
-
k4r4b3y
++
-
m-relay
-
ofrnxmr
market maker script should become the default gui method of posting offers. We're improving the script as well too though. Example, we just added a feature/fix to allow the market maker to reduce the offer amount in increments. It also allows you to auto repost offers based on a % markup from spot
-
ofrnxmr
one of the scripts, bsx-placeorder, takes it further and lets you decide how much to buy or sell, choose your fiat currency, set a static rate in crypto or fiat or set %.
-
k4r4b3y
all these script stuff, albeit useful, should give way to "buttons" inside the gui.
-
m-relay
<ofrnxmr:xmr.mx> But yeah, things are moving along nicely and shouldnt be too long until its noob-friendly enough to provide noob-friendly installers
-
m-relay
<ofrnxmr:xmr.mx> K4r4, yes, the plan is to add the functionality to the gui
-
k4r4b3y
++
-
m-relay
<ofrnxmr:xmr.mx> you should install it 🙃
-
m-relay
<ofrnxmr:xmr.mx> Can see for yourself the weakspots in the gui
-
k4r4b3y
you are correct, I should
-
k4r4b3y
I will try to check it
-
k4r4b3y
currently busy with bunch of other stuff
-
m-relay
-
m-relay
<ofrnxmr:xmr.mx> Heres an example. This is what "past" swaps look like. Doesn't even show the coins or the amounts. Just a bunch of text that means nothing to anyone
-
m-relay
<ofrnxmr:xmr.mx> Note that these are all "expired" because i flooded the orderbook with fake offers to prove a point 🥲
-
k4r4b3y
++
-
m-relay
<ofrnxmr:monero.social> for now, i highly recommend the scripts as the most "complete" installation method
-
m-relay
<ofrnxmr:monero.social> Docker requires you to visit the docs website to do every little thing (updating, adding/removing coins, more confusing to backup/migrate)
-
m-relay
<ofrnxmr:monero.social> The script install manages everything and puts everything in your home folder for easy access if you wanted to, example, reuse your old blockchain file, modify monerod.conf, open your bsx wallet inside of feather etc.
-
m-relay
<ofrnxmr:monero.social> bsx-addcoin = activates the venv, and prompts you to enter the coin you'd like to add
-
m-relay
-
m-relay
-
m-relay
-
m-relay
<ofrnxmr:monero.social> > FYI: @monero does not have a partnership with @secretblockio, nor could a leaderless, decentralized, open-source project ever have a partnership with any project.
-
m-relay
<ofrnxmr:monero.social> Also
-
m-relay
-
m-relay
-
m-relay
<ofrnxmr:monero.social> > In case it wasn’t obvious, nobody has a “partnership with Monero” just like nobody has a “partnership with Bitcoin”. Not Zerononcense, not CryptoMedication, nobody.
-
m-relay
<ofrnxmr:monero.social> > You can’t partner with a decentralised cryptocurrency. Anybody claiming otherwise is a scammer.
-
plowsof
The original tweet is restricted? I cant see :(
-
m-relay
-
m-relay
<ofrnxmr:xmr.mx> Plowsof, no its there
-
m-relay
-
m-relay
<shrimp:envs.net> Hello. If anybody here has a proper monerod node under tor/whonix/qubes, could you please share your configuration?
-
m-relay
<shrimp:envs.net> Mine works but I am having troubles with the `anonymous-inbound` directives to allow people to find my node.
-
m-relay
<ofrnxmr:monero.social> What seems to be the problem with anon-inbound?
-
m-relay
<ofrnxmr:monero.social> Do you have an onion configured and running ?
-
m-relay
<shrimp:envs.net> Yes, I have an onion configured and running. It has downloaded the blockchain and I can reach it (using the onion address) from an external wallet. It uses the standard ports: 18080 for p2p and 18081 for RPC.
-
m-relay
<shrimp:envs.net> However if I try to add (in the config file) the following line ` anonymous-inbound=myonionaddress.onion:18080,127.0.0.1:18080,10` , when I launch `monerod` it crashes at startup with error:
-
m-relay
<shrimp:envs.net> E Exception in main! Failed to initialize p2p server.
-
m-relay
<ofrnxmr:monero.social> Your onion is wrong
-
m-relay
<ofrnxmr:monero.social> Should be port 18084
-
m-relay
<ofrnxmr:monero.social> For both torrc and anonymous-inbound
-
m-relay
<shrimp:envs.net> you are suggesting to use this? `anonymous-inbound=myonionaddress.onion:18084,127.0.0.1:18080,10` ?
-
m-relay
<shrimp:envs.net> I am using qubes/whonix, so I do not need to configure torrc, I think.
-
m-relay
<ofrnxmr:monero.social> 127.0.0.1:18084
-
m-relay
<ofrnxmr:monero.social> You need to configure the onion HiddenServicePort etc
-
m-relay
<shrimp:envs.net> I have configured HiddenServicePort for 18080 and 18081.
-
m-relay
<shrimp:envs.net> So, should I close 18080 and open 18081 and 18084 ?
-
m-relay
<ofrnxmr:monero.social> 18081 is dangerous since your peers will know your onion addr and can use it to connect to 18081
-
m-relay
<ofrnxmr:monero.social> Use 18089 for restricted rpc and 18084 for anon-inbound
-
m-relay
<ofrnxmr:monero.social> Add rpc-restricted-bind-port=18089 to your config
-
m-relay
-
m-relay
<ofrnxmr:monero.social> Like this
-
m-relay
<ofrnxmr:monero.social> ```
-
m-relay
<ofrnxmr:monero.social> HiddenServiceDir /var/lib/tor/monerod
-
m-relay
<ofrnxmr:monero.social> HiddenServicePort 18089 127.0.0.1:18089 # interface for wallet ("RPC")
-
m-relay
<ofrnxmr:monero.social> HiddenServicePort 18084 127.0.0.1:18084 # interface for P2P network
-
m-relay
<ofrnxmr:monero.social> ```
-
m-relay
<shrimp:envs.net> I still get the monerod crash. In fact, looking at the log, the error is the first thing being logged:
-
m-relay
<shrimp:envs.net> INFO logging contrib/epee/src/mlog.cpp:274 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO
-
m-relay
<ofrnxmr:xmr.mx> Whats your anon-ibbound line
-
m-relay
<shrimp:envs.net> `anonymous-inbound=myonionaddress.onion:18084,127.0.0.1:18084,10`
-
m-relay
<shrimp:envs.net> In the bitmonero.conf
-
m-relay
<shrimp:envs.net> (I am in whonix so all traffic is sent through the tor proxy)
-
m-relay
<ofrnxmr:xmr.mx> And monerod fails to start?
-
m-relay
<ofrnxmr:xmr.mx> different error than here ^
-
m-relay
<ofrnxmr:xmr.mx> Might need to add `rpc-restricted-bind-ip=0.0.0.0`
-
m-relay
<shrimp:envs.net> My apology, the error reported by `moderod` is exactly the same as before.
-
m-relay
<shrimp:envs.net> What is copy/pasted is the additional information the the log.
-
m-relay
<ofrnxmr:xmr.mx> did you change p2p-bind-ip? (dont)
-
m-relay
<ofrnxmr:xmr.mx> You can dm your config file if u want