-
m-relay
<ofrnxmr:agoradesk.com> What chain was it that recently added that as a "feature"? Bch?
-
m-relay
<ofrnxmr:agoradesk.com> Let me rephrase:
-
m-relay
<ofrnxmr:agoradesk.com> i dont remember where i read about it. Maybe its a monero pr. Maybe is old news.
-
m-relay
<ofrnxmr:agoradesk.com> but i do remember that some chain'a feature was to spend before sync
-
n1oc
Boog900 full time work on Cuprate (3 months) has moved to funding!
ccs.getmonero.org/proposals/boog_3_months_cuprate.html
-
m-relay
<interestingband:matrix.org> "...work on the protocol ..."
-
m-relay
<interestingband:matrix.org> hahahaha
-
m-relay
<lakshmana:matrix.org> How can I contribute to the Monero project
-
m-relay
<monerobull:matrix.org> hi there, many different ways to do so :)
-
m-relay
<monerobull:matrix.org> can you code?
-
m-relay
<monerobull:matrix.org> a good place to get started might be
bounties.monero.social
-
m-relay
<lakshmana:matrix.org> I can code a little but I'm guessing the bar is too high for me to be of much use
-
m-relay
<lakshmana:matrix.org> Ill start running a full node 24/7 and look at the bounties I do know a few languages
-
m-relay
<monerobull:matrix.org> full node is already a great first step, also better for your own privacy :)
-
m-relay
<monerobull:matrix.org> be sure to open ports if you can
-
m-relay
<monerobull:matrix.org> helps make the network more decentralized
-
m-relay
<lakshmana:matrix.org> which ports
-
m-relay
-
m-relay
<gfdshygti53:monero.social> 18080 & 18089
-
m-relay
<gfdshygti53:monero.social> Actually I route my 18081 to internet 18089
-
m-relay
<monerobull:matrix.org> 18089?
-
m-relay
<gfdshygti53:monero.social> and 18089 to 18089
-
m-relay
<gfdshygti53:monero.social> I use 18081 for unrestricted rpc
-
m-relay
<lakshmana:matrix.org> Alright ill do that
-
m-relay
<gfdshygti53:monero.social> Actually I route my 18081 to internal 18089
-
m-relay
<monerobull:matrix.org> dont make unrestricted rpc public though
-
m-relay
<monerobull:matrix.org> im pretty sure someone could set your node to mine xmr that way :P
-
m-relay
<gfdshygti53:monero.social> Or shut your node down
-
m-relay
-
m-relay
<monerobull:matrix.org> its very nice
-
m-relay
<gfdshygti53:monero.social> I want these stats without installing the docker thing
-
m-relay
<lakshmana:matrix.org> This looks great Ill definitely use it
-
m-relay
<lakshmana:matrix.org> What linux distro should I try next?
-
m-relay
<lakshmana:matrix.org> And dont say Arch
-
m-relay
<gfdshygti53:monero.social> Alpine
-
m-relay
<monerobull:matrix.org> i think you can manually install it if you set up everything yourself
-
m-relay
<gfdshygti53:monero.social> I seam to use many stuff (prometheus, Grafana and nodemapper)
-
m-relay
<gfdshygti53:monero.social> Have to figure out how to use that stuff or just switch to the docker thing (I can probably do it while keeping the lmdb I already have)
-
m-relay
<lakshmana:matrix.org> Looks sweet thanks
-
m-relay
<monerobull:matrix.org> yeah
-
m-relay
<monerobull:matrix.org> you just need to tell it where the chaindata is
-
m-relay
<ajs_:matrix.org> Anyone have any idea of what’s the deal with the recent transaction influx
-
m-relay
<monerobull:matrix.org> could be binance
-
m-relay
<lakshmana:matrix.org> Market makers making the markets?
-
m-relay
<monerobull:matrix.org> more like shutting down shoü
-
m-relay
<monerobull:matrix.org> more like shutting down shop
-
m-relay
<preland:matrix.org> On that topic, does anyone know if xmr is affected by the “gamma squeeze” nonsense happening with Bitcoin?
-
sech1
the what
-
m-relay
<r4v3r23:monero.social> isnt bitcoin gamma squeeze resistant?
-
m-relay
<r4v3r23:monero.social> i thought it could resist all teh things?
-
m-relay
<gfdshygti53:monero.social> Did the "peer map" loaded initially or it take time?
-
m-relay
<gfdshygti53:monero.social> Or it's broken...
-
m-relay
<gfdshygti53:monero.social> top section have nothing in "peer counts" yet I have uploaded more than 1GB in 5 minutes...
-
m-relay
<monerobull:matrix.org> Is you node public?
-
m-relay
<monerobull:matrix.org> Is your node public?
-
m-relay
<gfdshygti53:monero.social> yes of course
-
m-relay
<gfdshygti53:monero.social> my non docker node hade like 12(out)+149(in) or something like that
-
m-relay
<monerobull:matrix.org> It uses rpc to get the data, didn't you say you changed some ports?
-
m-relay
<gfdshygti53:monero.social> I used the normal ports, that one use different one (unrestricted on 18083 and restricted on 18081). That should not matter as it's all configured in the docker stuff.
-
m-relay
<gfdshygti53:monero.social> I just adjusted my firewall to redirect all incoming (18081/83/89) to 18081.
-
m-relay
<gfdshygti53:monero.social> 18080 is also forwarder and did not touch to that one as it's not changed
-
m-relay
-
m-relay
<gfdshygti53:monero.social> I think the GEOIP stuff is broken
-
m-relay
<gfdshygti53:monero.social> or something
-
m-relay
<gfdshygti53:monero.social> probably why the peers don't show up in the dashboard
-
m-relay
<monerobull:matrix.org> You may have to generate an API key
-
m-relay
<monerobull:matrix.org> It's been a long time since I've set mine up
-
m-relay
<gfdshygti53:monero.social> I see, will take a look
-
m-relay
-
m-relay
<gfdshygti53:monero.social> Something definitively broken
-
m-relay
<gfdshygti53:monero.social> I'm going to keep it as other metrics do work (except the map and peer list)
-
m-relay
<monerobull:matrix.org> Cool
-
m-relay
<monerobull:matrix.org> Good luck figuring out the issue if you're going to pursue it
-
m-relay
<siren:kernal.eu> The geoip database it's trying to query is down.
-
m-relay
<siren:kernal.eu> Many things are down, could be that the geoip api was hosted on AWS.
downdetector.com
-
m-relay
<siren:kernal.eu> Python developers are great as usual
-
m-relay
<siren:kernal.eu> Something as minor as displaying a country flag can break your whole program, lovely
-
m-relay
<monerobull:matrix.org> lol
-
m-relay
<monerobull:matrix.org> internet gone again
-
m-relay
<siren:kernal.eu> Only the shit parts of it :D
-
sech1
-
m-relay
<rucknium:monero.social> There is a large backlog of Monero txs now. Try `print_pool_stats` in your monerod console, "estimated 14 block (28 minutes) backlog"
-
m-relay
<rucknium:monero.social> Increase your fee if you don't want your tx put into the backlog.
-
sech1
-
m-relay
<monerobull:matrix.org> sech1 it did
-
m-relay
<monerobull:matrix.org> there was a cable blown up i believe last week
-
m-relay
<monerobull:matrix.org> but that was where the rebels fight the US right now
-
m-relay
<monerobull:matrix.org> theres also that retard trying to reuse zeph hashrate
-
m-relay
<rucknium:monero.social> monerobull: Do you mean the monerod messages that say you are years behind in the blockchain? Probably not related to ZEPH. Their blockchain height is much lower than Monero's now.
-
m-relay
<monerobull:matrix.org> yeah those
-
m-relay
<monerobull:matrix.org> anyways, why do my rpc requests fail when im INSIDE THE DOCKER CONTAINER
-
m-relay
<monerobull:matrix.org> root@1e760f5471d3:/# monerod print_net_stats
-
m-relay
<monerobull:matrix.org> 2024-03-05 17:51:07.323 I Monero 'Fluorine Fermi' (v0.18.3.1-release)
-
m-relay
<monerobull:matrix.org> Error: Unsuccessful-- rpc_request:
-
m-relay
<rucknium:monero.social> Because Docker is hard to debug. I never really try to send those commands to monerod like that. I just keep the monerod console open and `screen` into it to ask it what is happening.
-
m-relay
<plowsof:matrix.org> sech1 jeffros deduct tx fee from output makes spamming the chain 50% more convenient and probably cheaper
-
nioCat
seems like some nodes are falling a-3 blocks behinds rn
-
nioCat
including mine
-
sech1
plowsof sweep_single does exactly the same (deduct fee from output), and it also creates 1/2 transactions
-
plowsof
ah good point, i should have mentioned "for a pleb like me" lol
-
plowsof
has p2pool been getting any luck with mining these full blocks?
-
plowsof
-
selsta
nioCat: my nodes so far have been fine
-
m-relay
<gfdshygti53:monero.social> Because the thing don't use the normal port
-
m-relay
<gfdshygti53:monero.social> unrestricted is 18081 normally while that docker thing put it to 18083 instead (and put 18081 as the restricted one)
-
nioCat
selsta: all are good now but wasn't when I posted, I was checking sync_info
-
selsta
nioCat: hmm i'm not sure but i think sync_info is sometimes delayed
-
m-relay
<gfdshygti53:monero.social> So it work fine for the container ecosystem, all the stuff configured to use 18083 for restricted but yeah, if you use monerod commands it will try to use 18081
-
selsta
the height of the other nodes in sync_info
-
nioCat
I was getting messages that I was 1 or 2 blocks behind for ~30mins
-
nioCat
same time that I checked sync_info
-
selsta
i'll keep an eye out on my nodes
-
m-relay
-
selsta
mine didn't have any behin messages
-
m-relay
<qq110245:matrix.org> Can you speak Chinese here?
-
plowsof
English only please
-
m-relay
<monerobull:matrix.org> how do i run them then?
-
m-relay
<ofrnxmr:agoradesk.com> ./monerod command
-
m-relay
<gfdshygti53:monero.social> 1> It's probably possible to tell monerod to connect to a different RPC port, in that case specify 18083 (don't have the parameters in my head
-
m-relay
<gfdshygti53:monero.social> 2 > You can edit all the containers stuff so it use 18081 for unrestricted and 18089 for restricted (the normal ports)
-
m-relay
<gfdshygti53:monero.social> Then route you're port appropriatly (internet 18081 -> local 18089, internet 18083 -> 18089... etc etc)
-
m-relay
<gfdshygti53:monero.social> Then you will be able to run monerod command
-
m-relay
<gfdshygti53:monero.social> 3 > You can probe the methodes manually (wget 127.0.0.1:18083/get_peer_list (or whatever command) then decode the json with your brain
-
m-relay
<gfdshygti53:monero.social> monerobull
-
m-relay
<ofrnxmr:agoradesk.com> Selsta - my node too, has not fallen behind or had any reorgs
-
m-relay
<ofrnxmr:agoradesk.com> And yes, its better to _add_ restricted rpc binds, not to restrict the unrestricted
-
m-relay
<ofrnxmr:agoradesk.com> Else you lose the ability to _use_ the unrestricted...
-
m-relay
<gfdshygti53:monero.social> It's just that the monero docker node decited to put restricted on 18081 😂
-
m-relay
<ofrnxmr:agoradesk.com> yes
-
m-relay
<ofrnxmr:agoradesk.com> Most configs are bad
-
m-relay
<gfdshygti53:monero.social> Like that's the default
-
m-relay
<gfdshygti53:monero.social> I assume it's fine for like if you install that on a VPS that is directly connected on the net or something
-
m-relay
<ofrnxmr:agoradesk.com> nah its still silly
-
m-relay
<ofrnxmr:agoradesk.com> You need unrestricted if you want to talk to the daemon
-
m-relay
<gfdshygti53:monero.social> Sorry, I ment, they pur unrestricted on 18081 and restricted on 18083
-
m-relay
<gfdshygti53:monero.social> While all tools normally expect unrestricted on 18081 and restricted on 18089
-
m-relay
<gfdshygti53:monero.social> Sorry, I ment, they pur restricted on 18081 and unrestricted on 18083
-
m-relay
<gfdshygti53:monero.social> While all tools normally expect unrestricted on 18081 and restricted on 18089
-
m-relay
<ofrnxmr:agoradesk.com> Lalanzas?
-
m-relay
<gfdshygti53:monero.social> yes
-
n1oc
Boog900 full time work on Cuprate (3 months) is now fully funded!
ccs.getmonero.org/proposals/boog_3_months_cuprate.html @luigi1111
-
m-relay
<shortwavesurfer2009:monero.social> With the high amount of transactions, it looks like we've had a hundred full blocks. Is the block size likely to expand? And where can I see the Monero Mempool?
-
Inge
.mempool
-
Inge
try xmrchain.net for mempool and related info
-
m-relay
<shortwavesurfer2009:monero.social> Thx
-
m-relay
<boog900:monero.social> wow, thank you ❤️
-
Lyza0
block size is already expanding
-
Lyza0
median block size limit is up to just over 300kB up from, what was it, 297?
-
m-relay
<shortwavesurfer2009:monero.social> I wasn't aware the blocks could shrink to anything under 300 kilobytes.
-
sech1
Median block size limit: 300.57 kB
-
sech1
300.57 kB = 307783 bytes
-
sech1
normally it's 300000 bytes = 292.97 kB
-
m-relay
<shortwavesurfer2009:monero.social> So blocks over that dont get the full .6xmr fee correct?
-
m-relay
<shortwavesurfer2009:monero.social> The tx fees have to be bigger than that loss
-
sech1
yes
-
plowsof
Monerobull was mad i didnt know that.. i dont think ive been forgiven
-
m-relay
<monerobull:matrix.org> lol
-
plowsof
Definitely not forgiven^ Tail emission video if youve not seen shortwavesurfer2009
yewtu.be/watch?v=sRwSqM0YBto
-
m-relay
<shortwavesurfer2009:monero.social> Thanks, does that kick in at the median like right now or is there some higher limit
-
m-relay
<shortwavesurfer2009:monero.social> I think 18081/get_info said something about something over 600k bytes
-
m-relay
<0xfffc:matrix.org> Honest question. Does anyone in entire cosmos use this?
github.com/mj-xmr/SolOptXMR
-
m-relay
<endor00:matrix.org> Once it's finished, I hope so
-
m-relay
<endor00:matrix.org> Currently working on the energy redistribution algorithm (i.e. prioritize mining during the most profitable hours within the predicted timeframe, while keeping the battery charge above a given threshold)
-
m-relay
<endor00:matrix.org> Getting the implementation right is a pain in the ass, so I'm in the process of rewriting it with heavy testing to ensure that everything is consistent
-
m-relay
<snowman:tetaneutral.net> I was able to just tie miners into home automation software. can start them, stop them and change cpu #'s. just this alone can allow an infinite number of usages
-
m-relay
<snowman:tetaneutral.net> Xmrig has a nice http api. That all is needed. No need for package, though I like people tinkering
-
m-relay
<snowman:tetaneutral.net> I was able to create a custom thermostat automation in home assistant that turn my miner on and off if temp gets too high or low depending on temp sensor in the room
-
m-relay
<snowman:tetaneutral.net> i can even pull in hashrate data- if it goes undetected, i get a notification.
-
m-relay
<snowman:tetaneutral.net> battery pack status can easily be pulled into automation by a simple arduino / voltage sensor.
-
m-relay
<endor00:matrix.org> Yeah, the automation part is not that complicated
-
m-relay
<endor00:matrix.org> What you're missing is a smarter criterium to choose when to turn your miners on for maximum profit
-
m-relay
<endor00:matrix.org> While also looking at weather forecasts to estimate solar energy production, and combining these two in the most efficient way
-
m-relay
<endor00:matrix.org> Otherwise you can end up mining when the difficulty is higher, and then your battery is drained just when the diff is starting to drop again