-
br-m
<ofrnxmr:xmr.mx> I might be retardrd and there is no --enable
-
br-m
<ofrnxmr:xmr.mx> Just --disable and --enforce
-
br-m
<ofrnxmr:xmr.mx> And disable should be the default imo
-
nioc
node thought so as well :)
-
nioc
no --enable
-
br-m
<ofrnxmr:xmr.mx> Yeah lol, just checked.
-
br-m
<ofrnxmr:xmr.mx> I remember that wallets used to be enabled by default too 🥲🥲
-
br-m
<basses:matrix.org> btw, as Syn already said, for domains. dont pick a proxy registrar as they are the ones that own that domain not you. Njalia for example.
-
br-m
<ofrnxmr:xmr.mx> Would ping moneropulse as soon as you tried to make a tx
-
br-m
<basses:matrix.org> Njalla*
-
DataHoarder
added this to the qubic snooper
-
DataHoarder
> Qubic blocks orphaned in last 1440 blocks: 111/365 (30.41%)
-
DataHoarder
> Other blocks orphaned in last 1440 blocks: 129/1315 (9.81%)
-
DataHoarder
changed wording of blocks to heights
-
br-m
<gingeropolous> wow, so they are losing money compared to honestly mining
-
tevador
To clarify: 2/3+1 means 5/7, not 6/7. It's rounded down.
-
midipoet
might be beneficial to ensure domains are registered/hosted in distinct jurisdictions. that might mean we require 7 (which might be difficult to do if you consider Europe as a homogenous jurisdiction).
-
sech1
Qubic blocks orphaned in last 1440 heights: 97/337
-
sech1
Other blocks orphaned in last 1440 heights: 119/1319
-
sech1
Doesn't it mean that Qubic gets more extra blocks than they lose?
-
helene
looks like it to me, yes
-
helene
which means it probably is profitable
-
br-m
<lordx3nu:matrix.org> Looks like qubic started their mining marathon earlier than usual
-
DataHoarder
sadly not, their ticking just got stuck
-
DataHoarder
last tick was a couple hours ago
explorer.qubic.org/network/tick/32454207 UTC wise
-
DataHoarder
so no transactions can't be made at all, they are in the idle mining phase tick wise
-
DataHoarder
from shared messages they are doing their "consensus via Discord" phase now
-
helene
a phase that all real distributed systems have :D
-
DataHoarder
it's quite common on qubic
-
DataHoarder
from logs they introduced a mul overflow bug that has been hit
github.com/qubic/core/compare/v1.259.0...v1.259.1
-
br-m
<rbrunner7> You mean their network came to a standstill and currently isn't processing any transactions?
-
br-m
<rbrunner7> Well, you probably said it already: "so no transactions can't be made at all"
-
br-m
<rbrunner7> Cool
-
br-m
<rbrunner7> So from fastest "blockchain" in the world to slowest right now :)
-
br-m
<17lifers:mikuplushfarm.ovh> is this a win
-
br-m
<17lifers:mikuplushfarm.ovh> yeeeee
-
DataHoarder
12:34:00 <br-m> <rbrunner7> You mean their network came to a standstill and currently isn't processing any transactions?
-
DataHoarder
correct
-
DataHoarder
this has happened a few times, it's nothing new on their network
-
DataHoarder
And when I talk about consensus via discord I mean it :D
-
DataHoarder
telling people to press keys to skip ticks or force-issue ticks
-
DataHoarder
it's such a regular occurrence they have an "Auto-F5" feature that automatically issues these commands to bypass their ticking system
-
DataHoarder
-
DataHoarder
most have commented short descriptions
-
br-m
<rbrunner7> Can you believe it ...
-
DataHoarder
they are still not ticking, ofc, but due to how the system doesn't care they still mine as that is more important for them than actually handling transactions
-
DataHoarder
-
DataHoarder
> Hotfix to ignore wrong votes on specific tick.
-
DataHoarder
-
sech1
"Ignore wrong votes" ah, when democracy doesn't work :D
-
DataHoarder
well, they voted wrong. this must be rectified or they get removed by the single-key arbitrator that has authority on who is a computor in the network
-
br-m
<barthman132:matrix.org> sech1: “Its only democracy if I get what I want”
-
br-m
<chowbungaman:matrix.org> Anyone here down to jump on a Monero Talk tomorrow night to discuss latest proposals, specifically the dns Checkpointing . And get overall take on where things are likely headed . 🙏
-
br-m
<ofrnxmr:xmr.mx> @rucknium:monero.social the testnet checkpointed nodes got forked off again. Someone did some nonsense reorgs
-
br-m
<ofrnxmr:xmr.mx> Were 1783 blocks behind
-
br-m
<ofrnxmr:xmr.mx> Like 250 blocks sent at once