Topic: [POOL] [XMR] supportXMR.com - 0.6 % fee EU based PPLNS monero pool - page 4. (Read 31345 times)

Hello again .

It.s here ani way to reset counting Hashes [Valid Shares / Invalid Shares]? I now testing configuration and it's clearer when I start from 0.
Or see detail about worker and can delete worker.

Thanks for answer

my hashrate is 3.7k, feature request:
add each worker's 1 hour avg hashrate to web api.
show my last 24 hours earned coins on dashboard.
shoe estimated daily/weekly/monthly rewards on dashboard.

This is because of variance. Some days the pool is more lucky in finding blocks, some days less. If we find less blocks (like the past 3 days for example), then of course your rewards will be less than expected. This all evens out over time. You can ask poolbot on the onsite chat (lower left corner) about these statistics. just type "/help" in chat to get started. It can show you the current effort, effort of last n blocks, total pool effort since block 1 etc... Our total average effort is dead on 100% currently. It was 99.2% last week, so we had a few bad days this week.

One of our community members created this Graph http://poolburgers.000webhostapp.com/ which will give you an idea about variance. Check the past 7 days, which had a very similar average pool hashrate (~16MH), but the blocks per day range from 36 (ultra bad day) to 74 (ultra lucky day!)


You don't get better rewards with PPLNS. It's just the distribution is not in favor of pool hoppers who try to jump in shortly after block finds with high hashrates. PPLNS favors miners that are constantly mining.

The difference is that exchange wallets differentiate the deposits of different people either using paymentIDs or integrated addresses, which require the pool payouts to happen in single transactions instead of bundling 20+ payouts together to save on fees. Your local wallet or mymonero wallet does not use paymentID or integrated address, so they can be bundled. Check the payments tab. It will be quite obvious what I mean.

Hello.
I have few (meyby noob) Q, but I would like to understand .

1. How is reward from hash calculated? I mining last 3 day. Avg h/s is 280 H/s (24h). I was expecting something around 0.0143, but I only have 0.0117 [20+-% less]. Why is it like that?
Previous post was written something about maitenens, but i don't thing this ist the reason. Can anyone explain it to me please? +How i can calculate result correctly?
(i know cca 300H/s is low, but i only testing before start something bigger)


2. Why has PPLNS better rewards? When block is found, it has 100% value. 100% value is divided between miners. How is possible the system PPLNS get more like 100% value in long time? It is always 100%. Now, after year, two ... So where is catch or from where it's stolen ?

3. I try find difference between payout (Wallet) and payout (Exchange), but unsuccessful. All go to my wallet, so what's the difference?

Again sorry for this easy Q.
And thx for answer

Is there anywhere I can see the profitability BTC/MH/Day for current, 24 hours & 7 days somewhere? Or another Cryptonight pool has this available somewhere?

Thank you.

Yeah, god forbit that pool operators at least cover their expenses while making sure the pool does not go broke from fees. Damn greed.  

If it was up to me, I'd set the default and minimum threshold to 2 XMR and be done with it. But miners (especially hobby miners) are always asking for lower thresholds and faster payouts. Also payouts to exchange are on high demand and the fact that those payments cannot be bundled with other payouts to save fees doesn't bother people. They want their small payments and they want them NOW. This flexibility simply comes at a cost. At least on our pool you can chose which is best for you.

The alternative is increasing the pool fee to 2 %, setting payouts to daily to get the maximum bundling effect and keep insisting on a 5 XMR threshold for exchange wallets (currently it is default, but can be set down to 0.3 as well, if one chooses) or disabling them all together. Then all the features and flexibility that nodejs-pool platform offers are basically reverted and we are on the same fee structure as the stoneage node-cn-pools like dwarf, .fr etc... now where's the progress in that?

It's a default feature in nodejs-pool to cope with the fee burden and it's been there since we migrated to it. I have not seen a single nodejs-pool who mentions the existence of the payout fee structure so far, yet I am sure all of them use it to some extent.

I'm not very active on BCT because it's full of trolls and shills. I am active daily on #monero-pools on freenode and on our on-site pool chat and everyone who asks about our fee structure is freely getting this information.

I'll update the post here when I get to it. First I want to rework the fees to drop them a bit lower since the network fees went down a bit since the korea surge

Does seem a little shady, would take all of 60 seconds to update the first post on this thread

What do other pools charge?

It is not very legitimate to set on the one hand a quite low default treshold for payput of just 0.3 (other pools have 1 XMR or 0.6 XMR) and on the other hand take a 0.08% fee that is nowhere documented on the page. I also was not aware of that and I'Äm not happy with it. Imho this looks like a hidden way to generate profit, even if this might not be the intension behind it.

is that possible to add feature "payout to BTC address" using shapeshift.io or xmr.to?

--------------------------------------------------------------------
yikes!,  That should be one of the first parts of "getting started"

.008/.3= 2.6% transaction fee (.008xmr is roughly $.72 on a roughly $27 transaction)
So pool supportxmr is a 3.2% total payout (pool fee plus transaction) at the default .3 xmr payout (at todays price)

So, if I chose a payout of 2 xmr the tx fee is .004?


TX Fee   XMR Payout            TX %
0.0080   0.3                    2.67%
0.0071   0.711                    1.00%
0.0062   1.122                    0.55%
0.0053   1.533                    0.35%
0.0044   1.944                    0.23%
0.0036   2.356                    0.15%
0.0027   2.767                    0.10%
0.0018   3.178                    0.06%
0.0009   3.589                    0.02%
0           4                    0.00%

# telnet pool.supportxmr.com 7777
Trying 45.34.77.146...
telnet: connect to address 45.34.77.146: Connection refused


Website says

Network: 0 H/s
Pool: 0 H/s
You: 0 H/s

Eeek.

Easy. The balance you see in your dashboard is already the 0.6% pool fee deducted amount. However, as you probably can imagine, at our low 0.6% fees we can not cover the transaction fees for all miners as well. So what we do is at 0.3 Payouts, we charge a 0.008 XMR transaction fee to cover the network TX fee. This fee reduces linearly as your payout threshold increases. If you set your threshold to 4.0 XMR, the transaction fee is waved completely. This way a miner can choose if he wants immediate, low value payouts, or wait a bit and get charged with less/no TX fee.

I apologize for still not having that information on the website. We are currently still reworking the getting-started page.

Got my first payout yesterday, but the fee was more like 1.2% rather than .6%, any way to check what is going on?

1% blocks, every day

Hi,

you username is your payment address (but with correct caps like in the wallet 42sWrrpNcXYR...

your login password is the email you registered g***@*******.com. You an change this password after logging in.

If you need further help, send me an email to [email protected], since I am not checking in at BCT often.

BR
M

Good evening. I tried to talk you over the chatango app but I think with too much message income it gets too overloaded.I like your pool and the helpful people over there. My problem is just the login to change the payment threshold f.e.. Can you set a custom pw for the id below? It would make things much easier for the future.

id: 42swrrpncxyrbymgutlpdspeluxf5v8yb4rxhkvewydd9ury3auwjka19cehw4j89wtyp39vnr8mhbp 1dssrft633jwcsif


successful mining !

Still mining strong!

No, we just hit the most unlucky streak of blocks in pool history over the past week... Order shall be restored now. It can only get better from here