-
gingeropolous
<moneromooo> If I was a single miner, I would not create hundred of addresses though. What a pain to manage. >>> im not sure if th stats are per address or per connection
-
gingeropolous
i think its honestly a mix
-
gingeropolous
but i don't know
-
nioc
it was discussed in pools but I don't remember clearly, I believe for most pools it was by address but that still means numbers could be inflated by the minority of pools that don't
-
sech1
Most of the number increase comes from minexmr (surprise surprise) and they count by addresses
-
Inge-
is this a case of the biggest pool attracting miners by force of gravity?
-
Inge-
did minexmr raise their fee? I see it is higher than supportxmr.
-
sech1
It has always been higher
-
sech1
minexmr 986.27 MH/s, 44.7%
-
Inge-
Is this the biggest unsolved issue in XMR?
-
sech1
minexmr should just stop accepting new XMR addresses to make noobs choose other pools
-
Inge-
or just slowly raise fees
-
Inge-
"When will 1 sat/byte clear again?" "Maybe March next year" "Why are you so bearish?" <-- Matt Odell etc discussing bitcoin fees. And recognizing that they are problematically high
-
DaveyJones
but is he really recognizing it ? IMO he is also apologizing it instead of coming to the clue that BTC might be flawed
-
DaveyJones
"is neccessary for the fee market to materialize, and will only climb from here on"
-
Inge-
heh. and the conflict between a) consolidating UTXOs for cheaper fees later vs b) privacy
-
Inge-
"I've had very expensive lessons - and those lessons where at 5 sats/byte"
-
hv-bridge
<\x> even with a well thought out utxo consolidation, youll never achieve any hint of privacy
-
hv-bridge
<\x> so yeaaah
-
Inge-
no wonder people don't understand Moneros value proposition - when even the maxis just stick their heads in the sand.
-
hv-bridge
<\x> it does help though, like proper coin control can help in like if you send someone small amounts, you dont need to use the largest utxo you have
-
gingeropolous
minexmr is 37% if you do 916 mh / 2470 mh (network hashrate). the % of known is frustrating
-
sech1
20% unknown blocks
-
sech1
probably big solo miners
-
SerHack
.usd
-
sech1
Miners 107730
-
NickvanSaberhagn
I still
-
NickvanSaberhagn
Think we need to raise funds via the CCS and pay for smaller pools to lower their fees or pay for larger pools to increase their fees
-
NickvanSaberhagn
I would contribute to that
-
NickvanSaberhagn
Or get xmrig to have stronger defaults in it that are smaller pools
-
sech1
xmrig defaults to hashvault IIRC
-
sech1
-
sech1
xmrig.com/wizard sorts pools alphabetically and 2 largest pools don't stand out
-
sech1
Miners 108512
-
NickvanSaberhagn
Ah interesting thanks. I more meant that it really pushes people harder one some direction or another. There is always potential to emphasize this stronger in the software but if you’ve already done all you can do then never mind :). What a gift that the project devs and the mining software maintainer are on such friendly terms!
-
NickvanSaberhagn
I bet a lot of crypto can’t say that
-
gingeropolous
i think we need to develop the pool delegate thing
-
sech1
Miners 109153
-
NickvanSaberhagn
Gingeropolous: What pool delegate thing?
-
gingeropolous
its kinda a hybrid between stratum-self-select and the existing stratum
-
gingeropolous
so, you'd have: pool operator <---> bunch of pool delegates <---> miners.
-
gingeropolous
pool delegates craft block templates. pool op just takes care of payments and tallying the delegates shares etc
-
sech1
So is it like delegate runs self-select but pool sends his template to other regular miners? And pool pays some % of the pool fee to the delegate?
-
sech1
I don't quite understand. Pool op still fully controls what normal miners do.
-
sech1
Or miners connect to delegates only?
-
gingeropolous
delegate runs self-select, so they are the ones creating the blocks. The pool delegate is 1 of many delegates. Miners connect to the delegates to get their work.
-
sech1
But delegates create block templates with pool's wallet address, right?
-
gingeropolous
the delegates coordinate with the pool op for payments and accounting of the other pool delegates
-
gingeropolous
yeah
-
sech1
so each delegate gets a share of pool fee, depending how much hashrate he supplies?
-
gingeropolous
yeah
-
sech1
Economic incentive for a delegate would be "run a stable fast node and get pool fee from miners in your geographic region"
-
sech1
interesting
-
gingeropolous
yep
-
gingeropolous
and the pool operator no longer has to pay for 90 thousand nodes to make sure the pool is stable
-
gingeropolous
because the pool delegates are running that infrastructure now
-
sech1
Economic incentive for miners doesn't change
-
gingeropolous
yep
-
gingeropolous
ure just creating a middleman for the sake of decentralization and cost sharing
-
gingeropolous
and leveraging the fact that some n% of miners cares about decentalization and will become delegates
-
gingeropolous
but most don't
-
gingeropolous
and also that pool ops are incentivized to minimize costs
-
sech1
But how do miners know address to connect to? From the pool getting started page?
-
gingeropolous
yep. "Choose your delegate"
-
sech1
Or will pool maintain single connect address and just do geo-DNS?
-
gingeropolous
well whatever
-
gingeropolous
it could be random unless specificied
-
sech1
So pool op still has quite a lot of control
-
gingeropolous
or delegates can compete by offering lower fees
-
sech1
He can just ban some delegates by not paying them
-
sech1
and removing them from all pages
-
gingeropolous
right.
-
sech1
If it was possible to make your node a delegate in a few simple steps and get some $$$, many would do it
-
gingeropolous
yep
-
sech1
so is it like reddit admins and subreddit admins system?
-
gingeropolous
i mean, its kinda like p2p pool, except the nodes report to a master pool instead of using a trustless consensus between them
-
gingeropolous
and this could go trustless somehow, but i think this hybrid approach is an easier first step
-
sech1
what about cheating? If some pool delegate reports higher hashrate than it really has?
-
gingeropolous
i dunno about reddit admin subreddit admin structure, but ... yeah kinda
-
gingeropolous
sech1, i tihnk that can all be taken care of using the existing protocol
-
sech1
or is it simply shared by blocks mined
-
gingeropolous
the delegates submit "shares" to the pool admin
-
sech1
each delegate has their own wallet address
-
gingeropolous
its kinda just a proxy system
-
gingeropolous
ideally the delegates would do no more than provide block templates to miners and relay share information to the pool op
-
sech1
pool op assigns a wallet address to each delegate (which delegate can't control) and just pays out them out of "their" wallets
-
sech1
so cheating doesn't matter if only real mined blocks are counted for each delegate
-
gingeropolous
right. a delegate would have a similar relationship to the pool op as any miner would
-
gingeropolous
they are just special
-
sech1
except delegate's mining wallet (the one block templates are created from) is controlled by pool op
-
gingeropolous
it would work in the same way that stratum-select works
-
gingeropolous
its essentially stratum select between pool op and delegate, and standard stratum between miners <-> delegate <-> pool op, though it sorta passes through the delegate
-
gingeropolous
i.e., the pool op would double check the work being provided to the delegate to confirm validity, in some manner thats more efficient than having 10k independent connections
-
sech1
Who checks shares from miners though?
-
gingeropolous
the delegate and the pool op, or just the delegate
-
sech1
delegate can collude with "his" miners to report more shares
-
sech1
so pool op must check everything
-
gingeropolous
sure, but could use the same trust model that exists today
-
gingeropolous
the pool code checks the first n shares, and then assumes miner is trustworthy
-
sech1
Today's trust model is check 100% shares because accidents happened
-
gingeropolous
ah
-
sech1
And servers that check shares are the bigger part of pool's expenses
-
sech1
checking shares can still be moved to delegates only if they are only paid from their mined blocks
-
sech1
then this problem moves to delegates and their miners
-
gingeropolous
well, the idea was to have the benefits of the larger pool
-
gingeropolous
for more frequent payouts
-
sech1
if some miner cheat, it's a problem only for other miners using this delegate, not everyone
-
sech1
so naturally delegates who check 100% shares will win the competition
-
gingeropolous
i.e., all of the miners in the larger pool get a reward if delegate A finds a block
-
sech1
So pool op has to check all shares
-
sech1
Single EPYC server will probably be enough
-
sech1
50,000 miners, each miners sends a share every 30 seconds = 1667 shares/second
-
sech1
even single Ryzen server should be enough
-
sech1
so not a problem
-
gingeropolous
and perhaps there are optimizations because all the shares come through a single connection
-
gingeropolous
or it could be done where the delegate and the delegates miners get some n% of the reward, and the rest of the pool distrubutes the rest
-
gingeropolous
so that the payout could come from the delegates wallet address, and there's a payout in that address to the pool op for further distribution
-
gingeropolous
eh, maybe thats different
-
gingeropolous
Snipa, how many servers is supportxmr up to?
-
gingeropolous
but yeah. it'd be like changing a pool ops connection count from 11k to 100
-
gingeropolous
or xnbya , how many servers are behind minexmr.com ?
-
Snipa
We've been stable for awhile around the 20-30-ish range, I'd have to check how many are support and how many are frontend.
-
Snipa
Technically, the delegate system is kind of a mess, we've discussed it in the past, but ran into the same issue sech1 described. You'd need a blind-trust/not-trust system, XNP got close with that, by essentially delegating the hard/small work downwards, but wasn't designed to handle payments on it's own, which is realistically the key, along with identifying something as a delegate so it can be issued a slice of pool fees.
-
Snipa
The way sxmr/xmrpool are designed is with a psuedo delegate systgem, where the edge servers authenticate, it'd be perfectly practical to essentially issue an API key and check results, tracking payments as part of the returned data sets from the delegate node.
-
Snipa
It's within tehcnical verification, but it's never been a particular goal of anyone to do.