Guys is there a problem with the Musicoin payments ?
Hi I check. All works fine I've been mining Ubiq on Pool Sexy for about a week now with my humble GTX 1050 Ti. Average hashrate reported by pool seems realistic at 14.2MH/s and I've been receiving regular payouts much quickly than when I was on Suprnova (difficulty is much higher now, too). One question: is there any kind of bonus when you, find a block and if so how long does it take to mature if different from the normal share time confirmation of approx. 88 minutes?
No bonus  |
|
|
|
|
No, at the moment we have other priorities.
|
|
|
|
Where is the dash-pool? Removed from list..?
It was closed two months ago, nobody was connected for a long time |
|
|
|
is dbix3.pool.sexy work normally?
Yes, only we have low hashrate on dbix3 |
|
|
|
A miner of 950 kh/s is added to the zcash pool. The hashrate is equivalent to 2500 GTX 1070 which is ridiculous. My round share was 38%. Now 28% and still decreasing. Plus with that hash a block should be found by now. Whats happening
smthing is wrong with dbix pool too we have more blocks but my daily revard droped from 1.3 to 0.7 some explenation from admins plss?
All works fine guys.it's depends only from luck |
|
|
|
Discord  https://discord.gg/C3MkJZYAll new users have only read access. To be verified set a profile image and contact one of the admin @Mitch pool.sexy @Ambros @faith_ . You will be added to the verified user group as soon as possible |
|
|
|
Last night the EXPANSE network had a planned fork, at block 800’000, as we anticipated in our telegram chat. Unfortunately the parity wallet (last version) that we used on the pool.sexy is not compatible with the fork, this lead the pool on a wrong chain. We recognised the problem and changed our wallet to gexp and we brought the pool on the right chain, we also informed the parity development team about the problem (please dev team see: https://github.com/paritytech/parity/issues/7061 For network security it is good to have two different wallets) During the mining on the wrong chain the pool found 2 blocks and sent 9 payments. Even tough we did not receive valid coins from those blocks, we decided to use our founds to refund users using our previous gains. Good mining Because you are stand up guys, send me a pm and ill send you a few coins to cover your outage. Dont worry man for coins.. I'm more interested that parity be it again compatible |
|
|
|
Hi, I hope as soon as possible ..depends only on luck |
|
|
|
Last night the EXPANSE network had a planned fork, at block 800’000, as we anticipated in our telegram chat. Unfortunately the parity wallet (last version) that we used on the pool.sexy is not compatible with the fork, this lead the pool on a wrong chain. We recognised the problem and changed our wallet to gexp and we brought the pool on the right chain, we also informed the parity development team about the problem (please dev team see: https://github.com/paritytech/parity/issues/7061 For network security it is good to have two different wallets) During the mining on the wrong chain the pool found 2 blocks and sent 9 payments. Even tough we did not receive valid coins from those blocks, we decided to use our founds to refund users using our previous gains. Good mining |
|
|
|
Last night the EXPANSE network had a planned fork, at block 800’000, as we anticipated in our telegram chat. Unfortunately the parity wallet (last version) that we used on the pool is not compatible with the fork, this lead the pool on a wrong chain. We recognised the problem and changed our wallet to gexp and we brought the pool on the right chain, we also informed the parity development team about the problem ( https://github.com/paritytech/parity/issues/7061) During the mining on the wrong chain the pool found 2 blocks and sent 9 payments:   Even tough we did not receive valid coins from those blocks, we decided to use our founds to refund users using our previous gains: Manual payouts:
15/11/2017, 06:05:08 1.022 0xb5d7152d3c37ee7a309c26a5bdf7060300718e45
TX ID 0x0eef86784bedee4adbf27ac5f6e28b2ea5cd82a75c181fd1f5f140ecdf6559d2
15/11/2017, 06:02:11 1.17 0x0dbd3a50f1acad58bdc35973fc7eb39cbf90bcea
TX ID 0x8bcd2b83fd73624eb302c2670192c0e34c917425e34eb88e27680abf52442641
15/11/2017, 06:00:55 1.05 0x8846abf4bc408cfe02364635e02359dff4a4afa6
TX ID 0xae364cf0aec242b93eefd5dd264e52fc265b16d7ec601564138526a8608ac846
15/11/2017, 05:58:48 1.142 0x61a1b60e8af12d72a5875e7a9d575f64573ceb23
TX ID 0x32185219e67149378a11f7483defa1d0bc959e9b7f7506f8b56c099ab48441c9
15/11/2017, 05:54:36 1.062 0xb2d337568d7b348429eecb937b945c67edae0c9b
TX ID 0x6e35750e87fa1e56073eb256659c6509a10c599ce4bb5c788f92b20cf1258c67
15/11/2017, 05:52:24 1.297 0x7410fc8da51eb1fc8249314209f012154400032e
TX ID 0xc603991aa5e982dc2f66a6e452e4efc7ed54a0d622909b6c43abe03b9768de18
15/11/2017, 04:00:56 1.229 0xd8f992807793efa7c63179b08cb9bc5467db622a
TX ID 0x963307537c4943bb11ae4fc9eaf93ee95c778f54ab4f1d1ae5c08286c5ae0a28
15/11/2017, 03:57:48 1.102 0x8846abf4bc408cfe02364635e02359dff4a4afa6
TX ID 0xabdb1dffe82a203e47e4297ace99b375bb014ab08864f194364e54dcc1eefb59
15/11/2017, 03:56:39 1.022 0x1e35722adcb2c5c55216f974cf742ec125385b4b
TX ID 0xe60aa52104f245197a0da103d76500179b75f0a5c639a4f01ace4559a2d85eb8 We would like you to know that the problem was caused by the expanse dev team, but we care about our miners. We are sorry for the inconvenience. |
|
|
|
I sent now to the correct chain all EXP transactions sent to the wrong chain this night now I have little time, later I'll be clearer |
|
|
|
Is mining poolhub on the correct chain?
yes |
|
|
|
Anyone using parity for EXP is now on the wrong chain. It would be super nice if people paid attention.
Anyone mining right now, move your miners to http://pool.expanse.tech until your pool confirms they have updated. We notified everyone a month ago and we have noticed there are a few pools still mining the wrong chain. Stragglers are to be expected. For everyone else mining at pool.expanse.tech, youll get extra exp I follow your updates every day (I annunced the fork yesterday on telegram chat), but I installed parity1.8.2....and I did not read anywhere that was incompatible with the new fork. Anyway gexp installed and exp.pool.sexy is on correct chain now.. |
|
|
|
Your expanse pool is on the wrong chain. Please update to gexp.. and pay attention. This fork was announced 28 days ago.
I follow your updates every day (I annunced the fork yesterday on telegram chat), but I use parity1.8.2....and I did not read anywhere that was incompatible with the new fork. Anyway gexp installed and pool is on correct chain now.. |
|
|
|
Just a little bug report, the link to the Ella explorer on an address is incorrect. If you go to: http://ella.pool.sexy/#/account/0x... Currently the explorer link points to: https://explorer.ellaism.org/#/address/0x... Should be: https://explorer.ellaism.org/addr/0x... Fixed, blocks and tx links were also changed, probably explorer has been modified. Thank you man |
|
|
|
nice I sent a request to whattomine for add dbix ....I wonder why it is not yet |
|
|
|
New Bitcoin Gold btg.pool.sexy(will be in the test up to the payment of the first block we will find ) |
|
|
|
ETH pool not working with Nicehash. Difficulty too low. Any chance to get this supported?
You need to use port for nicehash 9019 |
|
|
|
Hi,
I have 0.3 dbix pending on pool 3, is the min payout set correctly?
Regards
Hi, all payments are sent from dbix3, pls send me your address for check I dont think its oki since the morning problem im geting less sheres and payments smthing is not working fine my total gain its less fro about 30% on DBIX culd u explain why or chek?
Hi, i check the pool and all is ok. Almost certainly the difference is given by the bad luck and growing global difficulty. ps: sorry for delay |
|
|
|
|
Show Posts
