The closed network of the p2pool was started, ONLY FOR REGISTERED MINEERS 500+ TH. Send a message to @I_sawa in Telegram to connect to the network
Scanners of VIP nodes:
http://p2pool.top/scanner/btc-vip/
http://www.p2pool.site/btcv.html
2 blocks were found already
2018-05-11 18:44:14
https://bitinfocharts.com/bitcoin/block/522202/00000000000000000002726e0d79a257667d1794a064001659db77a1a2415e00
and
2018-05-17 14:24:43
https://bitinfocharts.com/bitcoin/block/523089/0000000000000000002be8b6954f6930c1d9d1d1e436cdb7db5f1e613c746377
Hashrate of the network is 32.99 PH/s at this moment.
Topic: [ANN][P2POOL] p2pools on the siberia.mine.nu & crypto.mine.nu - page 2. (Read 33403 times)
Hi ,
We CIF , Crypto improvement fund request adding cif coin to your pool .
For more info you can visit our official website www.cif.global
https://github.com/CIF-Github
www.cif.global
Crypto Improvement Fund © 2018 Crypto Improvement Fund. All Rights
Reserved. 125-720 King Street West, Suite 2000 Toronto, ON M5V 3S5
Home All information set forth in this business plan, the website
(www.cryptoimprovementfund.io, cif.global, blockchainedu.io) and all
associated forums represents forward-looking statements. The only
information that does not represent forward looking statements are
historical and… www.cif.global
Best Regards
msc
CIF GLOBAL
We CIF , Crypto improvement fund request adding cif coin to your pool .
For more info you can visit our official website www.cif.global
https://github.com/CIF-Github
www.cif.global
Crypto Improvement Fund © 2018 Crypto Improvement Fund. All Rights
Reserved. 125-720 King Street West, Suite 2000 Toronto, ON M5V 3S5
Home All information set forth in this business plan, the website
(www.cryptoimprovementfund.io, cif.global, blockchainedu.io) and all
associated forums represents forward-looking statements. The only
information that does not represent forward looking statements are
historical and… www.cif.global
Best Regards
msc
CIF GLOBAL
He's having problems with Franko, he connects but he does not get work for hours.
Google translator.
Google translator.
The DGB node (sha256) behind the IP address 69.138.110.229 generates orphan blocks.
Most likely the configuration of the daemon is incorrectly configured.
In the digibyte.conf configuration file, you need to specify the algorithm:
algo = sha256d
Most likely the configuration of the daemon is incorrectly configured.
In the digibyte.conf configuration file, you need to specify the algorithm:
algo = sha256d
February 21, 2018, 10:02:55 AM
I made LitecoiCash p2pool based on source code from jtoomim p2pool
LCC p2pool nodes:
http://crypto.mine.nu:5055
http://siberia.mine.nu:5055
LCC p2pool source code:
https://github.com/ilsawa/p2pool-lcc
LitecoinCash Home page https://litecoinca.sh/
LCC p2pool nodes:
http://crypto.mine.nu:5055
http://siberia.mine.nu:5055
LCC p2pool source code:
https://github.com/ilsawa/p2pool-lcc
LitecoinCash Home page https://litecoinca.sh/
February 10, 2018, 05:18:56 AM
Another BCH block, mined by 1EN7cctiCdSU3jhdYZ8rwLLk1nRjGpWT5E:
https://blockchair.com/bitcoin-cash/block/00000000000000000027a67aad7c2556d84c29efe08f036da77b293792b75e48
All BCH blocks found in the network of jtoomimnet p2pool from the start.:
516777 https://blockchair.com/bitcoin-cash/block/00000000000000000027a67aad7c2556d84c29efe08f036da77b293792b75e48 43 minutes ago
516492 https://www.blocktrail.com/BCC/block/0000000000000000021b5aee046f2829c220652fd7ab486b97aa61614f4d4635 1 day 22 hours ago
515827 https://blockchair.com/bitcoin-cash/block/00000000000000000242abe408a650a10eaf356f4547bb3e91a3e7033d57b6d2 6 days 9 hours ago
https://blockchair.com/bitcoin-cash/block/00000000000000000027a67aad7c2556d84c29efe08f036da77b293792b75e48
All BCH blocks found in the network of jtoomimnet p2pool from the start.:
516777 https://blockchair.com/bitcoin-cash/block/00000000000000000027a67aad7c2556d84c29efe08f036da77b293792b75e48 43 minutes ago
516492 https://www.blocktrail.com/BCC/block/0000000000000000021b5aee046f2829c220652fd7ab486b97aa61614f4d4635 1 day 22 hours ago
515827 https://blockchair.com/bitcoin-cash/block/00000000000000000242abe408a650a10eaf356f4547bb3e91a3e7033d57b6d2 6 days 9 hours ago
February 03, 2018, 07:41:29 PM
February 03, 2018, 01:59:47 PM
4 petahashes has come to BCH p2pool. The predicted time for the block was reduced from 20 to 4 days
You can connect to the BCH mining if you want
Addresses of nodes:
http://crypto.mine.nu:9338
http://siberia.mine.nu:9338
Accordingly, here is the configuration of the asic:
URL: crypto.mine.nu:9338, Login: Your_BCH_Address, Password: x
URL: siberia.mine.nu:9338, Login: Your_BCH_Address, Password: x
You can find the wallet of 0.16.2 version here: https://download.bitcoinabc.org/0.16.2/
Wallets of the latest version generate addresses in Bech32 format
You can convert new BCH addresses of Bech32 format to the old format here: https://cashaddr.bitcoincash.org/
You should mine to addresses in the old format, starting with '1'
You can connect to the BCH mining if you want
Addresses of nodes:
http://crypto.mine.nu:9338
http://siberia.mine.nu:9338
Accordingly, here is the configuration of the asic:
URL: crypto.mine.nu:9338, Login: Your_BCH_Address, Password: x
URL: siberia.mine.nu:9338, Login: Your_BCH_Address, Password: x
You can find the wallet of 0.16.2 version here: https://download.bitcoinabc.org/0.16.2/
Wallets of the latest version generate addresses in Bech32 format
You can convert new BCH addresses of Bech32 format to the old format here: https://cashaddr.bitcoincash.org/
You should mine to addresses in the old format, starting with '1'
February 01, 2018, 10:38:55 AM
Added a p2pool nodes for mining UNIT with the algorithm SHA256:
http://crypto.mine.nu:2936
http://siberia.mine.nu:2936
http://crypto.mine.nu:2936
http://siberia.mine.nu:2936
Heads up... we might be getting orphaned blocks on the Dash pool again...
Can anyone confirm?
Update: Looks like an isolated incident
Can anyone confirm?
Update: Looks like an isolated incident
understand now... Thanks for the explanation Sawa 
I see this worker on another node: http://crypto.mine.nu:28741/static/
CWiTpo813WHyX6xcbmXqQLKsRnuxMX9jpX 142.29 GH/s
Everything is like I supposed. He mines at http://crypto.mine.nu:28741 and sometimes several his ASICs switch to the Siberian node of the p2pool.
Since the nodes are linked into one pool, it shows a big payout at this adress
[/quote]
I see this worker on another node: http://crypto.mine.nu:28741/static/
CWiTpo813WHyX6xcbmXqQLKsRnuxMX9jpX 142.29 GH/s
Everything is like I supposed. He mines at http://crypto.mine.nu:28741 and sometimes several his ASICs switch to the Siberian node of the p2pool.
Since the nodes are linked into one pool, it shows a big payout at this adress
[/quote]
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??
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.
I see this worker on another node: http://crypto.mine.nu:28741/static/
CWiTpo813WHyX6xcbmXqQLKsRnuxMX9jpX 142.29 GH/s
Everything is like I supposed. He mines at http://crypto.mine.nu:28741 and sometimes several his ASICs switch to the Siberian node of the p2pool.
Since the nodes are linked into one pool, it shows a big payout at this adress
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??
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.
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??
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.
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??
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??
December 30, 2017, 07:06:38 AM
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 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.
December 29, 2017, 09:35:03 AM
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.
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.
December 27, 2017, 06:10:54 AM
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,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?
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/
December 27, 2017, 04:42:06 AM
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?
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?
Jump to: