[ANN][P2POOL] p2pools on the siberia.mine.nu & crypto.mine.nu

[sawa]

The first transaction in 2KZC is gone:
http://chain.kzcash.kz/tx/bf2d80aa042d41eadc710310de8421877fc00a90d91d54e6953debd132bbe186

[1714121790]

1714121790

[1714121790]

1714121790

[sawa]

The second transaction in 6KZC is gone:
http://chain.kzcash.kz/tx/0c83bdc88362b0cbc50c92c37923bd9557a9f3655427ef5014c37df2984cb834

[sawa]

Dear miners!
The P2Pool community announcing an unprecedented promotion.
All miners, who mine KZCash coins on any P2Pool node will get bonuses on November 16, 2017! The total amount of coins for the share is 250 KZC.
The distribution of bonuses will be made automatically on November 16 at 24 h 00 min by Astana local time (18:00 GMT) in accordance with the current % in the distribution stayed from the next found block.
Example - if your wallet should receive 0.45KZC from the found block (2.25 KZC) at the moment of distribution of coins, then you will receive 20% of the bonus fund - 50KZC.
Given the feature of accruals on P2Pool - smooth achievement of maximum payments, we advise you to switch to work with any of the P2Pool nodes mining KZC in advance (at least 3 days).
List of nodes:
http://crypto.mine.nu:8279
http://pool.penza.me:8279
http://tomsk.mine.nu:8279
http://mine.janche.ru:8279

We wish you a successful mining!
P2Pool Community.

[sawa]

I sent 250 KZC at the appointed time to all the miners who mine on the p2pool.
Here is the transaction in the block explorer: https://chain.kzcash.kz/tx/3bcdec6e4cf018547924c6410de1ee54bc16c4747e116deb486c8a9d6358bd99
Thank you all! We wish you a successful mining!

[visutrac]

Is there a problem with the AuroraCoin SHA256d pool?
no global hash rate and all I am getting is rejected shares.

Thanks in advance.


Nov 22nd. still appears to be in a bad state.

[sawa]

Is there a problem with the AuroraCoin SHA256d pool?
no global hash rate and all I am getting is rejected shares.

Thanks in advance.


Nov 22nd. still appears to be in a bad state.

There are a lot of old shares on this node. It is necessary to enter a small power and gradually raise it. Do not allow the DOA to be about 100 percent. As soon as the old shares are knocked out of the shareshain, then the node will start working normally

[visutrac]

I'm not sure what you mean by enter a small power.

I've got a 5GH/s ASIC device.
the pool is setting my difficulty to basically 0.007
I've tried forcing it to /0+6 but it won't go above pool settings.
I've also tried setting expiry,queue and scan setting with no difference.

I've got an additional 40GH I'd like to put on it but it just creates more Rejects/DOA and stales than anything.

EDIT:

Ok, it looks like after a couple of hours of submitting replacement shares .. it's back to normal.

Thanks.

[sawa]

A new Siberian server started its work in Krasnoyarsk
You can use 'syberia' instead of 'siberia'
Mine here:
+ AUR (GROESTL) http://siberia.mine.nu:12351
+ AUR (QUBIT) http://siberia.mine.nu:12355
+ AUR (SCRYPT) http://siberia.mine.nu:12347
+ AUR (SHA256D) http://siberia.mine.nu:12349
+ AUR (SKEIN) http://siberia.mine.nu:12353
+ BBQ (Scrypt algorithm) http://siberia.mine.nu:19324
+ BELA (Scrypt algorithm) http://siberia.mine.nu:7878
+ BTC (1% fee, jtoomimnet) http://siberia.mine.nu:9334
+ BTC (0% fee, jtoomimnet) http://siberia.mine.nu:9330
+ BTC (classic p2pool from Forrest) http://siberia.mine.nu:9332
+ CANN (x11 algorithm) http://siberia.mine.nu:28741
+ DASH (x11 algorithm) http://siberia.mine.nu:7903
+ DGB (myriadcoin-groestl algorithm) http://siberia.mine.nu:5021
+ DGB (qubit algorithm) http://siberia.mine.nu:5023
+ DGB (scrypt algorithm) http://siberia.mine.nu:5025
+ DGB (sha256d algorithm) http://siberia.mine.nu:5027
+ DGB (skein algorithm) http://siberia.mine.nu:5029
+ DPC (x11 algorithm) http://siberia.mine.nu:2932
+ EMD (scrypt algorithm) http://siberia.mine.nu:12125
+ FRK (scrypt algorithm) http://siberia.mine.nu:9797
+ FTC (neoscrypt algorithm) http://siberia.mine.nu:19327
+ FUNK (scrypt algorithm) http://siberia.mine.nu:36363
+ GLD (scrypt algorithm) http://siberia.mine.nu:8124
+ KZC (x11 algorithm) http://siberia.mine.nu:8279
+ LTC (scrypt algorithm) http://siberia.mine.nu:9327
+ MUE (x11 algorithm) http://siberia.mine.nu:8963
+ NLG (scrypt algorithm) http://siberia.mine.nu:27100
+ NVC (scrypt algorithm) http://siberia.mine.nu:8336
+ RBBT (scrypt algorithm) http://siberia.mine.nu:30303
+ SIB (x11-GOST algorithm - !!!NOT x11)  http://siberia.mine.nu:9345
+ VTC (lyra2rev2 algorithm) http://siberia.mine.nu:9171
+ VTC 2nd (lyra2rev2 algorithm), node for miners with low hashrate: http://siberia.mine.nu:9181

[sawa]

Started a third vertcoin network on my servers:
http://crypto.mine.nu:9191
http://siberia.mine.nu:9191
For all, who has less than 100 megahash, it is advisable to switch workers to this network

[sawa]

Added nodes of the BCH p2pool:
http://crypto.mine.nu:9338
http://siberia.mine.nu:9338

[sawa]

Added nodes of the MonaCoin p2pool (Lyra2REv2 algorithm):
http://crypto.mine.nu:2942
http://siberia.mine.nu:2942

[sawa]

BLOCK! On BTC p2pool (jtoomimnet) https://blockchain.info/ru/block-index/1654337

[sawa]

Monacoin p2pool works fine - 4 blocks today. Connect your farms, links to p2pool nodes:
http://crypto.mine.nu:2942
http://siberia.mine.nu:2942


Settings for GPU mining:

SGMINER: "sgminer -k Lyra2REv2 -o stratum+tcp://crypto.mine.nu:2942 -u Your_MONA_PayoutAddress -p x"
SGMINER: "sgminer -k Lyra2REv2 -o stratum+tcp://siberia.mine.nu:2942 -u Your_MONA_PayoutAddress -p x"

CCMINER: "ccminer -a lyra2v2 -o stratum+tcp://crypto.mine.nu:2942 -u Your_MONA_PayoutAddress -p x"
CCMINER: "ccminer -a lyra2v2 -o stratum+tcp://siberia.mine.nu:2942 -u Your_MONA_PayoutAddress -p x" 

[TLC01]

I’ve been mining on the dash pools for a while now and just seen something I’ve never seen before...
My wallet address is missing the last 3 block payments and the last payment was for a block not even on the pool block list...
My hashrate has been consistent and no drop outs so don’t understand why my wallet receipts suddenly don’t match the pool block list.
Can anyone help explain?

[sawa]

I’ve been mining on the dash pools for a while now and just seen something I’ve never seen before...
My wallet address is missing the last 3 block payments and the last payment was for a block not even on the pool block list...
My hashrate has been consistent and no drop outs so don’t understand why my wallet receipts suddenly don’t match the pool block list.
Can anyone help explain?

Three blocks in statistics - orphans,
http://crypto.mine.nu:7903/static/classic/share.html#00000000000000222f0af4f43ff173987fde9410fc5f9865f34a5b410ed0f92f
http://crypto.mine.nu:7903/static/classic/share.html#00000000000000251e04dc738858a29f214e24c061f9194bc4eea23e42fb86b5
http://crypto.mine.nu:7903/static/classic/share.html#0000000000000000f012b91a259d3cd5af4bba44eacc02aa11bf9ca73c3f9c2b
On what node they were found I do not know. Probably these nodes are experiencing network problems.
You can find them at the addresses of workers if you want: XcADs7dYBgZwp7GY4r25GV9Bzx6BdVj6DY, XnwuwfPhuFANd9Bz8fPEt9G3wZSgJS9126,  XhXMahooTgty7jLQAbbRLLHBWeJWy4F1Lv
And one real block did not register in statistics

I asked the developers of DASH p2pool: https://github.com/dashpay/p2pool-dash/issues/43
https://www.dash.org/forum/threads/so-many-orphaned-blocks-as-found-today-have-never-been.23115/

[sawa]

For all miners,  who mine on the DASH p2pool (not only on my nodes).
After updating the DASH wallets to version 0.12.2.2, the DASH network began to generate many orphans.
This can be seen on the graph: https://chainz.cryptoid.info/dash/orphans.dws
Almost 90% of the blocks found by the P2Pool are Orphans. I informed the developers of the DASH P2Pool
https://github.com/dashpay/p2pool-dash/issues/43

A similar message was received by the developers of the coin itself from the owner of another pool https://github.com/dashpay/dash/issues/1822

In both cases, the developers claim that everything is normal and there are no problems, we must wait until the network is stabilized.
So the miners have only 2 options: either to wait for the network to stabilize, or to go to other coins with the X11 algorithm.
If you stay on the DASH p2pole, then only at your own risk. I do not see a decline in the number of orphans in a couple of days.

[sawa]

For all miners,  who mine on the DASH p2pool (not only on my nodes).
After updating the DASH wallets to version 0.12.2.2, the DASH network began to generate many orphans.
This can be seen on the graph: https://chainz.cryptoid.info/dash/orphans.dws
Almost 90% of the blocks found by the P2Pool are Orphans. I informed the developers of the DASH P2Pool
https://github.com/dashpay/p2pool-dash/issues/43

A similar message was received by the developers of the coin itself from the owner of another pool https://github.com/dashpay/dash/issues/1822

In both cases, the developers claim that everything is normal and there are no problems, we must wait until the network is stabilized.
So the miners have only 2 options: either to wait for the network to stabilize, or to go to other coins with the X11 algorithm.
If you stay on the DASH p2pole, then only at your own risk. I do not see a decline in the number of orphans in a couple of days.

The problem with orphans disappeared. You can mine further

[TLC01]

Looking at CANN and keep seeing a wallet address appearing every hour which has only 1-2GH/s but is immediately earning 3-4 times in CANN what is being earned per share using 50-60GH/s.
I looked at the wallet and it is a Bittrex account with over 6,500+ wallet addresses attached to it.

Anyone got any idea about this and how they get immediate high income with such low hashing power??

[sawa]

Looking at CANN and keep seeing a wallet address appearing every hour which has only 1-2GH/s but is immediately earning 3-4 times in CANN what is being earned per share using 50-60GH/s.
I looked at the wallet and it is a Bittrex account with over 6,500+ wallet addresses attached to it.

Anyone got any idea about this and how they get immediate high income with such low hashing power??

You were need to specify the address, that caused your suspicion. Likely, that it's way more simple that it looks: someone is with high power mining to this address on one of connected nodes. Several ASICs have a bad connection and they periodically switch to my node, that is specified as the backup.

[TLC01]

Looking at CANN and keep seeing a wallet address appearing every hour which has only 1-2GH/s but is immediately earning 3-4 times in CANN what is being earned per share using 50-60GH/s.
I looked at the wallet and it is a Bittrex account with over 6,500+ wallet addresses attached to it.

Anyone got any idea about this and how they get immediate high income with such low hashing power??

You were need to specify the address, that caused your suspicion. Likely, that it's way more simple that it looks: someone is with high power mining to this address on one of connected nodes. Several ASICs have a bad connection and they periodically switch to my node, that is specified as the backup.

Siberian CANN pool....
address is CWiTpo813WHyX6xcbmXqQLKsRnuxMX9jpX
It's just come back on the pool now... 2.04 GH/s and 2.97 CANN immediately (Most others have to wait for share to build up).
CcYkzj27VDK5TtQjzJ6UyYekdWbLGTt7k4 on the pool for some time, hashing at 39.09 GH/s and receiving 0.93 CANN.