BitShares Forum

Main => General Discussion => Topic started by: BunkerChainLabs-DataSecurityNode on November 30, 2015, 02:44:19 pm

Title: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on November 30, 2015, 02:44:19 pm
Emergency Measures

Today we have shut down the mining pool until such time as @kuro112 with @Freebieservers delivers the new pool they were suppose to have completed back in September of this year. We do not have access to the migration data that was collected at this time, so I am calling on everyone to please PM me to match up the BTS1 address below with your current BTS2 address. These will be cross referenced with our historical payout data for verification.

With help from @nethyb we have gone through all the current balances and have the following records for payout that have been maintained Since Oct 12. They are as follows:

Scrypt Paytouts:

BTS1Address                                                                                                  Shares                  Percent            BTC
BTSX6LntkCfDLvwPrr13az5kYmivVYnJrSA7pmNF9kxNFFjeMqDgE7   18137595904   40.457%   1.2302752828
BTS6hUKzaE5LsebYWo9nxXU3f9oz4q82uahhDmkzGox1a5xMMbTQD   15887193199   35.437%   1.0776302002
BTS6KFYwMFodzumAd58zBkqUfzBVqE9Wbq9daofRSTtCV1he5BpWg   3457748291   7.713%   0.2345394769
BTS718HWwtV7MSdSid9iJDeGfNYDw9DoVXG4UJFmn8b7ixYPJu8vs   2085200083   4.651%   0.1414393691
BTS6hMGqB7L8VPrfV9QrUCEjthtE4PT58HNMLXSJvjdwGVpxBDPE3   1089955274   2.431%   0.0739317956
BTS8NAAuWpVTBtR41UNSPqXtnmUAUqP7HaLFsyDCqpz9T5QCFb5ci   731896712.4   1.633%   0.0496446409
BTSX77DEm1ek1RUzgwXrzfVa7SoKVmJNMKPGXry2ZbB9mGsVLEfkdj   730249085.5   1.629%   0.0495328821
BTS5JT3ErQizmLdrsPgux7hjmnBD5jMS17PQkVgre8LdiQ4LRvisR   630658672.1   1.407%   0.0427776526
BTS7gQqipVy69Civ55u2T3es8y7LjaiikegV36UjNMWYYbVfnB1Wi   589912063.2   1.316%   0.0400138053
BTS5bSRsHDLVUVKhLAD625SdUT8TGhdKFHUQP2q7KJZMFusZVTQ9s   313096553   0.698%   0.0212373763
BTS59yyNvg16PomdeZmvghXvm1vBLrFJyz8kVXazUrgUVScbcHEA8   308959821.9   0.689%   0.0209567814
BTS7jdG65fzKANubcPbPGLF7u66ZUdfbVs1gZiqFZsAWGHKBx2jjW   178657326.5   0.399%   0.0121183477
BTS7pKUDo5Ea7PHogv7RD6vLKKKqGhrok19GE2w3MKFreZ4DavEpz   135370752   0.302%   0.0091822142
BTS6vkX1rTvzMEZscUpgJioiWDkWyzWpVuL6WnmmPPd8ia6K8vi9s   117833728   0.263%   0.0079926758
BTS7m2BgRBEreEr6AiDqh1nX7pK2Qnu45wafDbuoWXD48u84MkEhT   90720718.45   0.202%   0.0061535971
BTS7wgVpQ1JFC5quNGnjPgQTfvNopLDEfniQesK3jaxAqHtUQkxPb   90656011.53   0.202%   0.0061492080
BTS6zGSmKugeW23iDefXTmr2NS3bYXQetpqowYnbU2WY4bejsWD8H   70072584.26   0.156%   0.0047530317
BTS7m6M3piLNVH97NwvMzUV8upsBBr5kheFBR2oF1zCXghvvwjFMG   58810103   0.131%   0.0039890963
BTS7MmaFRCTUbGJEXTbAZuuxeR9wtXuKVak4mvjSLpmXtr8adMv5H   17101948.14   0.038%   0.0011600272
BTS6h3zey2jFop7UXoU8Psgd23mKR5wt3BqxR73d9Kxfjnm78kotb   16225706.49   0.036%   0.0011005916


X11 Payouts:

BTS1Address                                                                                                  Shares                  Percent            BTC
BTSX7xK4aawrQ2mgteoHmDNTRLT5MN7E7zn84cjzMZKbGeviCZEyV7   25110.22733   29.125%   0.1515059475
BTSX8McjC24ViaAJP558pVdUAfifZpV3bBYmouNrcPk34o3pfx8YAQ   17770.74462   20.612%   0.1072221874
BTS6ivx4gAuW7mfjr799vX1AuMTuxssSbsEL2Je9iV19MCNV7Nn74   8060.92636   9.350%   0.0486366877
BTSX8cMZ3Was5orWHpkkjDnEjvVmcj16Ekpj4Decb164hY3hrw44Qm   7212.264975   8.365%   0.0435161747
BTS6fCKf3nL7MqMV94ipCTpzH6wRVnm4HYPhZFNbQocJ9jVpEDqKG   5906.939868   6.851%   0.0356403194
BTSX5j6qS7fVAjyyD7snxtvZEpt5nrxRTcY1ayzvZv9ugPJoLfuxE1   5488.07499   6.365%   0.0331130416
BTS63zvVbpiFwsTbewCa1ueysb5wS7S6TFxbuQfedW95gqn7FtnpS   5314.555367   6.164%   0.0320660875
BTSX8SweUepGQvDPAYoAKM4Pthys8pN71aZyGasWWgdMXVxzJw9XFv   3212.047886   3.726%   0.0193803247
BTS6LDzy3asT7YsVUrP6FBYpsfXZsRUpq5uKiSumTLsSTnnFo1yEu   2660.046727   3.085%   0.0160497511
BTS7ZgRGFeNMEszj7UBK3jj3ESwv9S7ctDAtGq8oYFKahBKYppiYY   1249.442154   1.449%   0.0075386780
BTS7GW6MKyLCrtd6thqTyexsxbvK6xXtPgcTaJUvVB8oQgcS1XqUJ   1032.490454   1.198%   0.0062296706
BTS6P1GcvamCFm5nEBCyQrqDvZ2hdFGLhUYPhCRejLe3Zdgnx1A7h   865.5043155   1.004%   0.0052221372
BTS6njHmvdqK5hV8kjnMKhTHfxUhpE3rvRB1MRfr8dijkYBmfG4sD   430.4476552   0.499%   0.0025971641
BTS6RhfW4b4Jvc4LAnjjDCiqxfYTmwfwqPzbxTgHR9ubAcY91qLU7   367.8784181   0.427%   0.0022196441
BTS8CgpR5Pg1RDtyKrPzbeUYLfYDnyvhi1YVnUkyYGwQdNS3AFaFq   280.9869697   0.326%   0.0016953728
BTS8fTwBh5Sd5UesH1wTGivHE5se656BKSP9jzahDWFTWZcTo7PEd   182.1595873   0.211%   0.0010990845
BTS6KhF2VeGPPGD6knH1nszS4XZkMcC5YoE5uUQDwExDJwF9AdpVu   170.0125012   0.197%   0.0010257934

As of this posting.. mining has halted until the new pool can be brought online. We will resume mining at that time.

I am saddened that it has come to this point, but there is no indication that the trend of delayed delivery is going to break anytime soon despite the numerous promises I have received to the contrary.

For this payout, you may specify how you wish to be paid. I will be happy to make the payouts in BTC, BTS, or any other BitAssets you wish to have sent for your payout. Please send me a PM with this information here.

I hope that we can sooner than later get the mining pool back up and running. At that time all payouts will be starting from zero once the pool comes back online, since this payout is the final balance outstanding as of today.

I again appreciate everyone's support and patience through this. I will continue to press for delivery and launch of the new pool which the community has paid to be completed.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: xeroc on November 30, 2015, 02:48:19 pm
That's unfortunate .. not that I mine .. but to see that you picked a contractor that does deliver :(
Title: Re: Emergency Measure - Temporary Shutdown
Post by: nethyb on November 30, 2015, 02:52:56 pm
Thanks @BunkerChainLabs,  appreciate the detail and clarity, keep pressing for the devs to finish / launch the new pool!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on November 30, 2015, 02:55:02 pm
That's unfortunate .. not that I mine .. but to see that you picked a contractor that does deliver :(

his pool has been delivered for the better part of 2 months, he simply chose not to use the software.

ill let freebie handle this one...
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on November 30, 2015, 03:07:44 pm
That's unfortunate .. not that I mine .. but to see that you picked a contractor that does deliver :(

his pool has been delivered for the better part of 2 months, he simply chose not to use the software.

ill let freebie handle this one...

That makes perfect sense.  ::)

I don't have time for forum shenanigans.

I messaged you 14 hours ago regarding migration and you have not responded, but you have time to post here.  ::) Over the past months this happened in stretches of days and weeks.. which is why we have a 2 week project now on its 3 months anniversary.

Get it done.

I will not be having discussions in public about this. It only wastes time that should be spent getting this delivered. Communicate directly like an adult. Rather sure the community wants results, not shenanigans. I said the same thing to you a month ago, yet here we are.

Get it done.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: CalabiYau on November 30, 2015, 03:35:45 pm
I like the pool so far. Thank you for the pragmatic solution. Hope that you find a reliable contractor !  PM sent.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Xypher on November 30, 2015, 04:02:37 pm
Hey Jonathan.

Glad that you decided to post about this.
We were discussing things internally too and this is the best way we could permit the community to know what's going on (although I need to point out, you just defaulted your own NDA here, but whatever)

Okay, now down to the issues at hand here.

1. You believe, we do not contribute sufficient time to the project and expect more from us (justified)
2. You believe this should have been wrapped up 2 months back


I'd like to bring to your notice a few things

1. We just sent the migration data via skype.
2.  You know this as well as anyone else that you haven't found the time to sit down with us and help us with the transition. Anyone that's worked with us on sharebits would know that we're available 24/7 on skype when we're on projects and we do give it our best but am all open to post chat logs and show you - how you have been busy with your other projects and haven't given us your time in regards to helping us with the transit. We are currently integrating with an exchange and we do take time in advance and schedule with coders from the other side so we have individuals with the technical expertise working with us, as and when we need them. Have we been able to schedule time with you and do the same ? There have been innumerous cases where you said "BRB" and went to be with your son, or had an emergency and left off to the bunker in the middle of tests and transition. How can an external enterprise help you with the transition with behaviour like that?

3. You've been sitting on the core software for a month or so now with basic transition issues going on. Some things mentioned are not even in the scope of the contract, but we have personall helped you set up your daemons and boxes and you come here..talking this of us.

4. We are not YOUR company. We are contractors. This means, while we will take time to figure your system out, you need to be present to assist us when we need you. You not being available doesn't help us in any way.

5. We did create a front end and a back end - went beyond the scope of the contract to be of service to you and ..this is what we get in return.

To end with, for the users here - you would have had your pool up a month back if Jonathan wasn't busy handling so many things at once. Unlike him, I understand business and I have to point out he is handling too many things together and due to the same its possible he couldn't commit the time required to spend with us to assist with the transition. But to come out and put the blame on us like this.. it hurts.

You have had the software for over a month with a minor setback on the transition aspect pending. To come out and have the audacity to tell people that we are at fault for your lack of commitment is admirable. Please message me when you decide to invest the time and energy to commit to this project and we'd be glad to cover this.

When you say the community wants results : we have delivered on other projects here, and are all set to launch 3 more in the weeks to come.
We understand results, but usually it doens't involve the counterparty being off so often.
Personally, I am obliged to admit, we are not perfect. Hell we're far from there. But pointless attacks like these..
Not sure, how I should react to them.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: TheLostBoy on November 30, 2015, 11:21:25 pm
Not the first complaint here

"Beware of FreebieServers LLC and their developer Michael": https://bitsharestalk.org/index.php/topic,20034.0.html
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Akado on November 30, 2015, 11:34:15 pm
Why not talked via cellphone and/or skype calls? There seems to be lack of communication and organization.. form both parts, or this wouldn't happen.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: liondani on November 30, 2015, 11:37:59 pm
https://youtu.be/AHWLVxg8MxA
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on November 30, 2015, 11:57:27 pm
Not the first complaint here

"Beware of FreebieServers LLC and their developer Michael": https://bitsharestalk.org/index.php/topic,20034.0.html

I'm just saying, the new pool has been ready for people to mine on for over a month, I mean Bunker himself has been mining on it for over a month now (screenshot of payouts db):
(http://i.imgur.com/gRLRmDr.png)

As kuro put it, I'm just going to let @Freebieservers handle this in terms of discussion, I just felt obligated to point out this skewed mentality of "it's entirely our fault."
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 01, 2015, 03:46:53 am
Why not talked via cellphone and/or skype calls? There seems to be lack of communication and organization.. form both parts, or this wouldn't happen.

That would be great... but they are more intend on wasting time on here than doing anything about finishing this project.

Other than sending me the db of the migration after I requested it in skype.. they have said nothing and done nothing all day to proceed with finishing the job. It's how what they said would be delivered in two weeks has gone on for three months. I held out and gave more chances than I care to talk about.

It's in their hands to deliver on this project, always has been. They have taken Bitshares communities money, and have yet to deliver on the project. The past week was more delays over the migration. Now I have removed this.

Lets see them in action now!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 01, 2015, 04:11:51 am
Thanks to everyone that PMed me with your information as requested.

Everyone who has PMed me with their info were verified and paid out today. Gave me a little nostalgia over the past half year what I did every single day for payouts to miners.

There is still many more to be paid out, so please PM me asap so we can get your paid up!

I am heartened by our miners that when given the choice between BTC BTS or other assets, we had only one choose BTC, one BitUSD, and the rest all wanted BTS! Bravo!

@kuro112 @Freebieservers have yet to take any actions to complete delivery.

@nethyb has offered to actually do a 3rd party arbitration audit regarding the work they have claimed to have been 'completed', and what was supposed to have been delivered. (sound familiar @killakem ?).

I had no plans to pursue something like this, but given the surprising polemic amateurish rantings that followed attempting to assign blame, instead of some kind of effort to deliver, I may consider it if I continue to see nothing but these shenanigans and continued lack of results and communication.

I repeat again I am not going to engage in public forum about this, and urge again to contact me directly like adults.

Get it done.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 01, 2015, 04:14:17 am
Not the first complaint here

"Beware of FreebieServers LLC and their developer Michael": https://bitsharestalk.org/index.php/topic,20034.0.html

I'm just saying, the new pool has been ready for people to mine on for over a month, I mean Bunker himself has been mining on it for over a month now (screenshot of payouts db):
(http://i.imgur.com/gRLRmDr.png)

As kuro put it, I'm just going to let @Freebieservers handle this in terms of discussion, I just felt obligated to point out this skewed mentality of "it's entirely our fault."

were more than willing to go through any arbitration, you can keep saying get it done and claiming its not done all you want, doesnt make it true, to anyone who wants to mine on his new pool:

http://216.146.143.200/dashboard

as you can see from the stats its been up and been mined on for a month or so.


i will note that we had an NDA agreement, breaching it like this makes the contract null-in-void and we will not be continuing to work on this product for the time being, we may be convinced to do otherwise though depending on how this plays out, we wish no ill will to bunker, were just confused as to why he has done nothing with the software we delivered and is now pointing the finger at us for it...?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: donkeypong on December 01, 2015, 06:09:48 am
I thought I was reading the NXT thread for a moment. You guys have exactly the same defense. Ouch.
Here's hoping BCL gets what he needs.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 01, 2015, 06:18:09 am
I thought I was reading the NXT thread for a moment. You guys have exactly the same defense. Ouch.
Here's hoping BCL gets what he needs.

it happens to be true, he has his product, hes even mining on it... what exactly do you call that pal?



I'm just saying, the new pool has been ready for people to mine on for over a month, I mean Bunker himself has been mining on it for over a month now (screenshot of payouts db):
(http://i.imgur.com/gRLRmDr.png)

As kuro put it, I'm just going to let @Freebieservers handle this in terms of discussion, I just felt obligated to point out this skewed mentality of "it's entirely our fault."

were more than willing to go through any arbitration, you can keep saying get it done and claiming its not done all you want, doesnt make it true, to anyone who wants to mine on his new pool:

http://216.146.143.200/dashboard

as you can see from the stats its been up and been mined on for a month or so.


the BTS community should be asking bunker why he wont put the software online for them
Title: Re: Emergency Measure - Temporary Shutdown
Post by: tonyk on December 01, 2015, 06:28:47 am
I as a total tech idiot know one thing. One of those parties is not  right.

And I will be completely honest  here - I have no clue which one!

The link seems to show a mining pool, indeed.

Bunker was this or wasn't this their job?

On a semi related note - Do you plan to do all those projects you have listed on your website [more or less whatever the whole crypto industry has ever come up with and then some] by contracting independent outside devs?  :-\
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Brekyrself on December 01, 2015, 10:03:16 pm
Just curious, why shut down the old pool until the new one is 100% up and running?  I don't care if payouts are manual and once a week etc... just want my cards earning bts!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 02, 2015, 12:29:07 am
Just curious, why shut down the old pool until the new one is 100% up and running?  I don't care if payouts are manual and once a week etc... just want my cards earning bts!

hey pal dont worry the new pool has been up for over a month, why dont you just try it out for yourself

http://216.146.143.200/dashboard/getstarted
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 01:50:51 am
Just curious, why shut down the old pool until the new one is 100% up and running?  I don't care if payouts are manual and once a week etc... just want my cards earning bts!

hey pal dont worry the new pool has been up for over a month, why dont you just try it out for yourself

http://216.146.143.200/dashboard/getstarted
I tried to connect to stratum+tcp://216.146.143.177:4447 two different miners said the pool dead did u put a wrong number for stratum thanks
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 01:55:26 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 03:00:30 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 02, 2015, 03:31:09 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 03:32:25 am
awesome sha up to that's great thank you
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 02, 2015, 04:08:47 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x
Are there higher difficulty ports?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: fuzzy on December 02, 2015, 04:26:17 am
Just curious, why shut down the old pool until the new one is 100% up and running?  I don't care if payouts are manual and once a week etc... just want my cards earning bts!

hey pal dont worry the new pool has been up for over a month, why dont you just try it out for yourself

http://216.146.143.200/dashboard/getstarted

Starting next week, ill gladly run some open beta testing if we need to in a similar fashion to how we did for the ShareBot if this will help resolve this stuff.  It seems to have made a huge difference for Sharebits to have gotten so much help testing by the community...

offer is on the table if interested.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 05:24:23 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x
Are there higher difficulty ports?

Will have to talk to kuro about this (seem's he's been off for the night) I'm sure he'll reply in the morning, cheers. @kuro112
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 02, 2015, 05:40:46 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x
Are there higher difficulty ports?

Will have to talk to kuro about this (seem's he's been off for the night) I'm sure he'll reply in the morning, cheers. @kuro112

yeah i was taking a nap sorry, right now theres only one port for var diff, as explained in in geting started page:

Quote
A second VarDiff stratum port (4445) suitable for large GPU rigs and scrypt ASICs allows a range of 4096 to 32768.

however, I will update the getting started page tonight with much more clear info, thanks for the feedback!


update: edited the getting started page to reflect the correct info, will probably add more info about how the pool works later, thanks for the feedback!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 02, 2015, 07:25:03 am
Status Update

More of you have PMed me with your details and more payouts were processed today. 100% BTS and BitUSD!

We still have more remaining, so please PM me and we will get your payment out to you once your data is verified the same day.

Warning

The information regarding the DEVELOPMENT POOL was not authorized to be made public. (This is the only *real* violation of the NDA they are under that has been mentioned in this thread.)

What you have been getting are screen captures of the dev pool where multiple issues and features even today still have not been resolved or completed.

IT IS NOT PRODUCTION READY!

Today for the first time I got some documentation on where to access certain elements. More bug fixes were made, and security issues I discovered after getting the documentation are now also being addressed.

ANYBODY MINING THIS POOL IS DOING SO AT YOUR OWN RISK!

This is a dev space. It is not secure. It is not production. You may continue to point your miners with the understanding that it is TESTING ONLY and we will not be accountable for the potential of funds going missing while it has not been properly secured.

Proxy Pool mining has not been installed or setup yet as per the contract. Many of you in the community were part of the initial plans we made to update the pool, so you might remember that configuration for proxy pooling (for places like Nicehash and Antpool) was part of the scope.

As of today, the only information I received regarding this was the following:

Code: [Select]
Proxy Pool:
https://github.com/dogestreet/proxypool

Install and configure the software provided and link it to the modified UNOMP via the provided instructions, and plug in the pools you want to switch to via their instructions.

For the last month, we have been waiting for them to find or build a solution for the multi pool mining, as per the scope of the contract. Rather than delivering on this, they returned the link we provided (as a suggestion for a possible solution) with a note attached telling us to install and configure it ourselves. They are claiming that this is done, by telling us to do it ourselves. We disagree.

Nevertheless, I am glad however to finally see some progress being made towards getting the pool to production standard so that it can eventually be launched. @hybridd has been proactive in communicating and fixing outstanding issues today. It was @kuro112 that sent the documentation at my request.

Looking forward to seeing more progress tomorrow!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 02, 2015, 08:02:04 am
Heres an actual quote of the scope of work:

Quote
Enable capability to mine multipools like NiceHash
Implement upstream pool proxy mining to smooth profitability for high-difficulty coins (litecoin, doge, dash, bitcoin) (https://github.com/Stratehm/stratum-proxy, https://github.com/dogestreet/proxypool)
Ready to implement stratum port DDoS protection - ie. Incapsula (https://www.incapsula.com/ddos/)
Have the website translated to other languages to attract miners from other countries (Manderin, Hindi, Spanish, Russian)
Nice Charts (highcharts) of Pool Hash Algo
Miner Payout Lookups
Miner Real Time Hash Rate stats along with estimated daily payouts
Establish a high and stable history of payouts on multipool.us and coinking.io
Enable BTS address mining using username or public_key
Automated Payouts - Payouts are done once a day now manually in bitUSD. All funds now are mined and automatically sent to exchanges where they are auto traded to BTC. From BTC we then go to metaexchange.info or blocktrades.us to get the price for BTC/bitUSD at current market price, and then send that amount out from our delegate balance.

all of the features requested are available and have been delivered for over a month, the delay has been that the client (bunker) is unwilling to learn and configure the system and expects us (the developers) to put this system online, pay all his users etc, hes still shifting the blame for everything to us saying this dev pool is not authorized...


Quote
[11/23/2015 11:01:57 AM]
 Kuro: hey reactivating this group as its realvent to all of us
[11/23/2015 11:01:59 AM] Kuro: anoncoin    cannabiscoin  digitalcoin  litecoin  myriadcoin  potcoin  saffroncoin  startcoin  uro      worldcoin
auroracoin  dash          fractalcoin  megacoin  novacoin    quatloo  smartcoin    syscoin    viacoin
[11/23/2015 11:02:06 AM] Kuro: please make sure you have wallets for each of these ready
[11/23/2015 11:02:14 AM] Kuro: and if you didnt before, give us the new wallet addy
[11/23/2015 11:02:19 AM] Kuro: (cryptsy)
[11/23/2015 11:02:41 AM] Kuro: from one glance i can tell you were for sure missing a few
[11/23/2015 11:03:56 AM] Kuro: once we have the payout system configured for the new coins ill swap unomp for the current install
[11/23/2015 11:04:10 AM] Kuro: then all thats left is to point your dns to the new front end
[11/23/2015 11:04:14 AM] Kuro: and run the payouts
[11/23/2015 11:06:10 AM] Kuro: let us know when you have the new wallets ready please and thanks
[11/23/2015 5:58:13 PM] Jonathan Bunker: I will have all the wallets verified tomorrow
[11/24/2015 9:14:53 PM] hybridd: Cryptsy is/has been being DDoSed for the last little while, so there might be some down time / delay on the payments occuring.
[11/25/2015 2:17:09 PM] Jonathan Bunker: ok
[11/25/2015 2:17:12 PM] Jonathan Bunker: so we are not going to move the wallets
[11/25/2015 2:17:15 PM] Jonathan Bunker: we are going to leave them where the yare
[11/25/2015 2:17:23 PM] Jonathan Bunker: all the wallets have been worked on
[11/25/2015 2:17:27 PM] Jonathan Bunker: and are working
[11/25/2015 2:17:56 PM] Jonathan Bunker: lets see if we can get this working tonight

this was on the 25th that he explained the pool wouldn't be changing, ever since we have been waiting for him to configure the software and put it online for his users.

its obvious this system is completely production ready and his attempts to divert attention away from the live stats showing him mining for a month are pretty stupid...

To make one thing clear regarding the 'security flaws' bunker found,

Quote
[12/1/2015 7:00:03 PM] Jonathan Bunker: Seriously great way for us to get hacked
[12/1/2015 7:00:05 PM] hybridd: all your rpcs are localhost bound they reject external connection
[12/1/2015 7:00:13 PM] hybridd: there's no way to get hacked lol
[12/1/2015 7:00:36 PM] hybridd: not to mention funds are constantly being moved off the RPCs to cryptsty, if there is a breach of security the loss is inisignificant
[12/1/2015 7:01:14 PM] hybridd: If you want added security, I can add basic http auth to that page so it requires a user/pw to see.
[12/1/2015 7:01:22 PM] hybridd: but it's not nessesary.
[12/1/2015 7:01:42 PM] Jonathan Bunker: What if wallets take a public address to be on remote systems
[12/1/2015 7:02:03 PM] hybridd: what do you mean?
[12/1/2015 7:02:12 PM] hybridd: do you want to jump on a call, I think it'd be easier to discuss verbably
[12/1/2015 7:02:41 PM] Jonathan Bunker: We want wallets to not be on the same physical machine as the mining pool
[12/1/2015 7:03:12 PM] hybridd: that's fine, the way Bunker.Transfer moves the funds is by SSHing to the machine that the wallets are on
[12/1/2015 7:03:28 PM] hybridd: So even if it's on a different machine, that's no problem and doesnt' change the way our system works
[12/1/2015 7:04:15 PM] Jonathan Bunker: Pass protect that page is necessary  at least to satisfy perceptions of security of the pool
[12/1/2015 7:04:27 PM] hybridd: Alright, no problem I will get that added tonight.
[12/1/2015 7:05:11 PM] hybridd: That page isn't mentioned anywhere publicly, so only with fusking would the url be found, so it is fine for now, but I will get a password added asap.

that being said, as of now that page is also password protected despite not needing to be.

for the record, week ago i offered to come on and post on his behalf explaining the delays... he decided to keep you in the dark:

Quote
[11/22/2015 9:26:38 PM] Kuro: i was thinking we could give an update on your behalf and take the blame, we have been doing family stuff over the weekend but intend to launch first thing in the morning, we just need to sit down with you tomorrow morning and handle the small details during the launch
[11/22/2015 9:26:55 PM] Kuro: what time is good for you
[11/22/2015 9:27:25 PM] Jonathan Bunker: ok.. I will be at the bunker 9:30am my time.. I have a LOT going on tomorrow though.. so I will only have some inbetween time
[11/22/2015 9:27:49 PM] Kuro: okay we will be on and launching around then
[11/22/2015 9:28:56 PM] Jonathan Bunker: ok.. see u then
[11/22/2015 9:29:23 PM] Kuro: do you want us to post the update?
[11/22/2015 9:31:22 PM] Jonathan Bunker: no.. at this point there is nothing else other than getting it done that is going to be satisfying... lets get the payouts out and get the mining pool updated and get going.. then see what needs to be said at that point.

he keeps saying 'get it done'

its obvious that he is unwilling to do so, as all the features in the scope are met and users here want there pool its now up to us to launch the product for him...
this is an unreasonable position as we are contractors and should not be providing this support nor be held responsible for these delays,

please look to bunker to get you guys set up... tell the guy to come on and spend 2-3 hours working with this community instead of making big posts about how things need to get done...

the only reason you didnt get paid and havent been mining for over 2~ months is bunker himself.

Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 08:13:42 am
The information regarding the DEVELOPMENT POOL was not authorized to be made public. (This is the only *real* violation of the NDA they are under that has been mentioned in this thread.)

Please, you practically staged a witch hunt wanting people to go back and refer to the non-sense killakem posted because he didn't even understand his product making it seem as if we did no work on your project or it was unfunctional. Views have drastically changed now that people see that there's a pool, you can mine it, it's compatible with BTS 2.0, and it's paying out.

I've addressed the security concerns you brought up, but in all actuality there wasn't one to begin with. In the very unlikely scenario of a breach, at most because of how often the Transfer module moves coins, you'd be looking at a maximum loss of like ~0.001 BTC (probably less). Tbh, when more people start mining the min-move should be upped for the transfer module to reduce loss to tx-fee, but the loss as it stands is minimal.

While these are only my own views (I don't speak for the "Freebie" group), I'm not only talking about this particular incident but my own personal experiences: I'm really tired of the witch hunting that happens in the crypto world and how nobody ever takes the times to investigate both sides. The crypto community's contractors quite literally just shits on developers and treat them very unfairly. You want to do things professionally? We should be developing work flow diagrams before even starting on the work, and in the real world these aren't free. But in the crypto world, who's going to pay for diagrams? People just want to pay for the work done, so you end up getting some half-wit developer who'll make you think it's working get paid and then when you try putting your product into production it breaks (a lot of the clients we've worked for had broken systems due to this, and we were the one's who came in and eventually fixed them and gave them a working solution) so it's no wonder there's a lack of professional developers and talent in the crypto world these days. If it wasn't for the fact my work was mediated through kuro, I'd probably have said fuck working on crypto projects half a year ago, it's cancer.

Just to clarify, when I say "you" above, I'm not talking to you Bunker, this is nothing personal, I just wrote this as a rant to all contractors in crypto. I hope this rant hits home with any other developers who may read it who've tried freelancing within crypto.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: iHashFury on December 02, 2015, 10:03:25 am
I am willing to test Script and SHA on the new pool.

How often are payouts and will BitShares users get paid using:

 http://216.146.143.200/dashboard (http://216.146.143.200/dashboard)
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 10:48:22 am
I am willing to test Script and SHA on the new pool.

How often are payouts and will BitShares users get paid using:

 http://216.146.143.200/dashboard (http://216.146.143.200/dashboard)

It's best to infer this from looking payouts that've occured to bunker himself:
http://216.146.143.200/Dashboard/User?address=www.minebitshares-com

The pool payout roughly every 0.02 BTC. Looking at the data for his address, that's typically around every 20-24 hours given the (current) mining power invested in the pool (this will be adjusted in the future).

You're paid to whatever address you choose to mine with. If you would like to receive an asset instead of BTS instead of using your BTS account for your user name, put your BTS account with a space and then the asset, i.e. "hybr1d USD"

To qualify for being paid in the form of an asset you must have mined atleast 60 BTS worth in value (this is because ~15 BTS is eaten in buying the asset as a tx fee, and ~45 is eaten as a tx fee for sending). If say for example, you've only mined 59 BTS worth in value and asked to be paid in USD. You would not receive USD but instead receive (14) BTS (59-45=14).

A payout occured about 5 hours ago, and there's about 0.005 BTC on the pool right now, so if we assume perfect linear progression the next payout should theoretically occur around 9pm EST 12/2/2015 (m/d/y)

If anyone's familiar with mining pools and/or mines often, please PM me I have a few technical questions you may be able to assist me with.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 12:11:53 pm
I have one more question when I put quotes in the username my miner won't connect in the getting started on the pool it states specifically to put quotes is this right as as I take those quotes out the pool says alive with quotes the pool say dead thanks
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 02, 2015, 09:30:45 pm
I have one more question when I put quotes in the username my miner won't connect in the getting started on the pool it states specifically to put quotes is this right as as I take those quotes out the pool says alive with quotes the pool say dead thanks

That part seems not working for me as well. I rather see username.USD or password USD . Is it possible to fix devs?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 09:49:46 pm
I believe that's poorly worded, you don't need quotes in your username, but you do need quotes when specifying your username on the command line. Look at the pool, and look at Bunker's username with USD for an example. Say I was using sgminer and wanted to mine USD:

sgminer.exe -o stratum+tcp://mining.bunkermining.com:4449 -u "hybr1d USD" -p ANYTHING_YOU_LIKE --no-submit-stale

Is what I would use. There's quotes around the username here because if there weren't the command line wouldn't realize that the space is part of the username. Likewise, with cgminer:

Quote
"pools" : [
{
            "name" : "hybrid",
            "url":"stratum+tcp://mining.bunkermining.com:4449",
            "user": "hybr1d USD",
            "pass": "x"
        }
],

--

I have one more question when I put quotes in the username my miner won't connect in the getting started on the pool it states specifically to put quotes is this right as as I take those quotes out the pool says alive with quotes the pool say dead thanks

That part seems not working for me as well. I rather see username.USD or password USD . Is it possible to fix devs?

username.USD is not possible since "." is allowed in bitshares 2.0 characters, but we can use another character instead of spaces (or I should say "as well as spaces"). What other characters aren't allowed in BTS 2.0 names?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 10:02:48 pm
got u so that's  for s configuration file for cgminer but not a bat file cause when I tried to set my miner in minera it said the pool was dead also multiminer and my other rigs where on miningrigrentals they told me the pool was dead as soon as I took those quotes out it was good now I also believe when I left those quotes out and put oakmaster USD my mining programs didn't recognize it I don't use conf. files with anyb of my miners and I don't think a lot of other ppl do so if it's the case it's going to cause ppl not to be able to mine a bit asset
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 02, 2015, 10:09:15 pm
got u so that's  for s configuration file for cgminer but not a bat file cause when I tried to set my miner in minera it said the pool was dead also multiminer and my other rigs where on miningrigrentals they told me the pool was dead as soon as I took those quotes out it was good now I also believe when I left those quotes out and put oakmaster USD my mining programs didn't recognize it I don't use conf. files with anyb of my miners and I don't think a lot of other ppl do so if it's the case it's going to cause ppl not to be able to mine a bit asset

If the space is causing that much of a problem, I propose we use a different character then since we are unable to use the password field for this. What other characters are not allowed in BTS 2.0 usernames? Is the pound symbol (#) allowed? If it is not, then we could do something like hybr1d#USD
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 02, 2015, 11:42:45 pm
I'm not sure I no most pool u put . in between to keep track of ur miners so I have oakmaster.worker1 and so on but I don't no if bitshares names have . I no I use - in a few but I do no the standard at most pool use the . so I no none of the mining software will give a problem
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 03, 2015, 12:39:00 am
got u so that's  for s configuration file for cgminer but not a bat file cause when I tried to set my miner in minera it said the pool was dead also multiminer and my other rigs where on miningrigrentals they told me the pool was dead as soon as I took those quotes out it was good now I also believe when I left those quotes out and put oakmaster USD my mining programs didn't recognize it I don't use conf. files with anyb of my miners and I don't think a lot of other ppl do so if it's the case it's going to cause ppl not to be able to mine a bit asset

If the space is causing that much of a problem, I propose we use a different character then since we are unable to use the password field for this. What other characters are not allowed in BTS 2.0 usernames? Is the pound symbol (#) allowed? If it is not, then we could do something like hybr1d#USD
Why not?
sgminer.exe -k x11mod -o stratum+tcp://216.146.143.177:5559 -u proctologic -p USD -I d -g 1 -w 128

      "name" : "Bitshares pool X11",
      "url" : "stratum+tcp://216.146.143.177:5559",
      "user" : "proctologic",
      "pass" : "USD"
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 03, 2015, 12:42:59 am
got u so that's  for s configuration file for cgminer but not a bat file cause when I tried to set my miner in minera it said the pool was dead also multiminer and my other rigs where on miningrigrentals they told me the pool was dead as soon as I took those quotes out it was good now I also believe when I left those quotes out and put oakmaster USD my mining programs didn't recognize it I don't use conf. files with anyb of my miners and I don't think a lot of other ppl do so if it's the case it's going to cause ppl not to be able to mine a bit asset

If the space is causing that much of a problem, I propose we use a different character then since we are unable to use the password field for this. What other characters are not allowed in BTS 2.0 usernames? Is the pound symbol (#) allowed? If it is not, then we could do something like hybr1d#USD
Why not?
sgminer.exe -k x11mod -o stratum+tcp://216.146.143.177:5559 -u proctologic -p USD -I d -g 1 -w 128

      "name" : "Bitshares pool X11",
      "url" : "stratum+tcp://216.146.143.177:5559",
      "user" : "proctologic",
      "pass" : "USD"

The issue is the modifications required to specify the asset as the password are far more complicated then passing it as part of the username by some delimiter character, I'm not saying this isn't possible just to do, just that it's (far) more of a hassle then passing it via the username.

I'm not sure I no most pool u put . in between to keep track of ur miners so I have oakmaster.worker1 and so on but I don't no if bitshares names have . I no I use - in a few but I do no the standard at most pool use the . so I no none of the mining software will give a problem

Unfortunately "." is a valid character in BTS 2.0 account names.

Edit:
I'll look into figuring out how to do the password change, but no guarantees on this one.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 12:43:32 am
password for the asset u want to mine if u just want bts we can use the simple x that will work
 edit didn't see it would be more of a problem to change the pass so there no other $ ! # / \ & * we can use I don't no what bts don't allow in their username or I'd throw one out there
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 03, 2015, 02:34:43 am
password for the asset u want to mine if u just want bts we can use the simple x that will work
 edit didn't see it would be more of a problem to change the pass so there no other $ ! # / \ & * we can use I don't no what bts don't allow in their username or I'd throw one out there

I've added "|" as a delimiter for an asset, so try mining with the name for example: hybr1d|USD and that should work as well (instead of a space). For the record, the pool is at ~0.019 BTC so payout should be soon... (need to mine 0.01 BTC more b/c its moved in 0.01 chunks, so could be a few more hours).
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 03:03:42 am
awesome thanks for getting this figured out
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 03:15:24 am
password for the asset u want to mine if u just want bts we can use the simple x that will work
 edit didn't see it would be more of a problem to change the pass so there no other $ ! # / \ & * we can use I don't no what bts don't allow in their username or I'd throw one out there

I've added "|" as a delimiter for an asset, so try mining with the name for example: hybr1d|USD and that should work as well (instead of a space). For the record, the pool is at ~0.019 BTC so payout should be soon... (need to mine 0.01 BTC more b/c its moved in 0.01 chunks, so could be a few more hours).
k it seams to be good my miner wasnt connecting so even for BTS you have to put | in so I just changed to oakmaster|BTS and it's all good now I was checking out the pool I see CNY in there so we can mine any bitasset we want even BITBTC and so on that's freaking awesome
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Brekyrself on December 03, 2015, 03:18:50 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x

Are these the correct addresses and ports to use?  Info is all over the place and I would like to help test the new pool!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 03:19:55 am
ya those are correct
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 03, 2015, 04:30:34 am
password for the asset u want to mine if u just want bts we can use the simple x that will work
 edit didn't see it would be more of a problem to change the pass so there no other $ ! # / \ & * we can use I don't no what bts don't allow in their username or I'd throw one out there

I've added "|" as a delimiter for an asset, so try mining with the name for example: hybr1d|USD and that should work as well (instead of a space). For the record, the pool is at ~0.019 BTC so payout should be soon... (need to mine 0.01 BTC more b/c its moved in 0.01 chunks, so could be a few more hours).
k it seams to be good my miner wasnt connecting so even for BTS you have to put | in so I just changed to oakmaster|BTS and it's all good now I was checking out the pool I see CNY in there so we can mine any bitasset we want even BITBTC and so on that's freaking awesome

I am mining for BROWNIES right now along with CNY testing.

When the pool becomes production ready more details on this will be provided.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 05:02:02 am
password for the asset u want to mine if u just want bts we can use the simple x that will work
 edit didn't see it would be more of a problem to change the pass so there no other $ ! # / \ & * we can use I don't no what bts don't allow in their username or I'd throw one out there

I've added "|" as a delimiter for an asset, so try mining with the name for example: hybr1d|USD and that should work as well (instead of a space). For the record, the pool is at ~0.019 BTC so payout should be soon... (need to mine 0.01 BTC more b/c its moved in 0.01 chunks, so could be a few more hours).
k it seams to be good my miner wasnt connecting so even for BTS you have to put | in so I just changed to oakmaster|BTS and it's all good now I was checking out the pool I see CNY in there so we can mine any bitasset we want even BITBTC and so on that's freaking awesome

I am mining for BROWNIES right now along with CNY testing.

When the pool becomes production ready more details on this will be provided.
thanks can't wait till everything gets figured out and is 100% operational
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 03, 2015, 05:58:47 am
Status Update

Today more PMs were sent and we processed more payments. 100% BTS this time.

I reported on more issues with the pool and they have been fixed. If you look at the dashboard display now, you can make sense of the hash data now that it is separated by protocol.

Community here has been finding issues with the development pool and fixes are being done. Awesome.

Proxy pool implementation has been refused to be delivered now despite my inquiries on it's completion.

Now beginning to test other asset payout methods.

We setup several more coins. All the coins we plan to support in X11, and sha256 are now setup. There are just a handful more of scrypt coin we are planning to add initially. Others like Antpool and Nicehash will not be possible without the proxy pool implementation being completed. This will greatly diminish our profitability prospects.

Ports for mining have been optimized to include switching ports only.

We are slowly but surely getting closer to production readiness.

Looking forward to seeing more progress tomorrow!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Brekyrself on December 03, 2015, 06:25:37 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x

Are these the correct addresses and ports to use?  Info is all over the place and I would like to help test the new pool!

Tried x11 with these and difficulty is set to 8.  I do not see any shares being accepted.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: nethyb on December 03, 2015, 07:55:19 am
So is upstream proxy mining actually implemented?

If not - having v high diff coins like Dash on the pool will just  be wasting miners hash and pulling the overall pools algo's mining profitability down.

Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 03, 2015, 08:00:30 am
Just mine LTC+DOGE+VIA @ Coinotron and sell them for BTS. You'll end up with more BTS that way. ;)
Title: Re: Emergency Measure - Temporary Shutdown
Post by: CalabiYau on December 03, 2015, 08:22:47 am
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x

Are these the correct addresses and ports to use?  Info is all over the place and I would like to help test the new pool!

Tried x11 with these and difficulty is set to 8.  I do not see any shares being accepted.

x11 seems broken atm.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: fuzzy on December 03, 2015, 08:35:57 am
Good to see the community is jumping onboard to help :)
Title: Re: Emergency Measure - Temporary Shutdown
Post by: iHashFury on December 03, 2015, 09:36:42 am
Testing the pool today using SHA256 and Script.

Would love to see the proxy to NiceHash working (pool I usually use)

Please send my funds from the old pool in BTS to iperky

BTS5JT3ErQizmLdrsPgux7hjmnBD5jMS17PQkVgre8LdiQ4LRvisR 630658672.1 1.407% 0.0427776526
Title: Re: Emergency Measure - Temporary Shutdown
Post by: iHashFury on December 03, 2015, 10:39:59 am
SHA256 seems to be working well but high diff Script ports are dead

stratum+tcp://mining.bunkermining.com:4445
stratum+tcp://216.146.143.177:4445

Only showing 1.54 MH on stratum+tcp://mining.bunkermining.com:4449 - should be 24-25 MH
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 11:11:42 am
SHA256 seems to be working well but high diff Script ports are dead

stratum+tcp://mining.bunkermining.com:4445
stratum+tcp://216.146.143.177:4445

Only showing 1.54 MH on stratum+tcp://mining.bunkermining.com:4449 - should be 24-25 MH
I have the same problem with scrypt showing 5mh and I should be at 20-24mh when I had my rig routed through miningrigrentals as soon as I took it off and it was fine the thing is I use them cause I rent some rigs but the main thing is I'm never home so monitoring my rigs are easier this way
Title: Re: Emergency Measure - Temporary Shutdown
Post by: iHashFury on December 03, 2015, 11:34:10 am
@BunkerChain Labs - www.minebitshares-com

What ports/settings are you using to mine?

I cannot replicate your speed.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 03, 2015, 11:59:48 am
@BunkerChain Labs - www.minebitshares-com

What ports/settings are you using to mine?

I cannot replicate your speed.
stratum+tcp://mining.bunkermining.com:4449 Im using minera I have a zeus thunder X2 it seems once in awhile minera switches to a backup pool maybe because their making changes to the pool as we mine
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 12:13:29 pm
Quote
I reported on more issues with the pool and they have been fixed. If you look at the dashboard display now, you can make sense of the hash data now that it is separated by protocol.

Community here has been finding issues with the development pool and fixes are being done. Awesome.

Proxy pool implementation has been refused to be delivered now despite my inquiries on it's completion.


sorry let me just give the community an HONEST update as bunker has a serious problem with honesty:

The miners have suggested various visual changes that have nothing to do with the actual functionality,
and despite the breach of our contract we are continuing to support this service out of our good will.

other than visual changes, the pool software has not been modified since its delivery and no bugs found / fixed

the proxypool software is ready to be installed and configured however bunker refuses to do it himself and is preventing its delivery for the community.
as we are software development contractors and not responsible for such things, i would look to bunker to solve these problems.

we will be making some visual changes tomorrow at bunkers request, but otherwise the pool is production ready any time.

note: to those of you noticing a slowdown in hashing power, this may have to do with us testing the password field for bitassets, we will update.

Title: Re: Emergency Measure - Temporary Shutdown
Post by: xeroc on December 03, 2015, 12:42:16 pm
sorry let me just give the community an HONEST update as bunker has a serious problem with honesty:

As of now .. Bunker has gain way more trust and reputation than you.
So I'd recommend to revise you strategy with strangers, community members and
your clients.

Quote
we will be making some visual changes tomorrow at bunkers request, but otherwise
the pool is production ready any time.

note: to those of you noticing a slowdown in hashing power, this may have to do
with us testing the password field for bitassets, we will update.
Do you see how those two statements contradict each other?
What has happend with proxy mining?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 01:04:52 pm
sorry let me just give the community an HONEST update as bunker has a serious problem with honesty:

As of now .. Bunker has gain way more trust and reputation than you.
So I'd recommend to revise you strategy with strangers, community members and
your clients.

Quote
we will be making some visual changes tomorrow at bunkers request, but otherwise
the pool is production ready any time.

note: to those of you noticing a slowdown in hashing power, this may have to do
with us testing the password field for bitassets, we will update.
Do you see how those two statements contradict each other?
What has happend with proxy mining?

the pool is production ready, the bitasset change was at the request of users here or did you not read the thread?

as for the proxy mining situation, the contract specified we implement a software called proxypool,
the software is completely compatable and just waiting for bunker to set up an instance on his servers and plug in the pool.

as for our strategy, the trust we have is not in question, our work speaks for its self, we have not failed to deliver one product to date... including this one.

if you want to discuss bunker's trust in this community however, that could be its own thread, the guy is KNOWN for his lack of honesty and talking behind peoples backs...

I was only trying to give an honest update because so far none of the ones bunker is giving tells the truth or gives any real details to his miners,
 its a bunch of useless doubletalk... he broke his own nda, continually lies about his product, refuses to put any time or energy into its release...

but i digress, theres no point in throwing around mud, the point of this thread is to get the miners up and running xeroc with honest information, not to assault peoples trust and reputation.

I will add that we have no reason to even be here posting on this topic, we are trying to provide support because bunker is too busy to do so, in addition to the many things we have done for bunker including but not limited to making his new website and front end for the pool, we still have no ill will for bunker, this endeavor or any of the users, i hope that much is obvious, but what should also be obvious by now to anyone is that if you attempt to BS, obfuscate the truth or tell users anything BUT the actual truth, you had better expect us to call you on it very publicly...

no we are not perfect either, we fuck up timelines, sometimes our software has bugs... we have blame here too, but were here supporting every product we launch.

sorry if my derailing offends anyone but we have gone far beyond the call to help this product launch already and to be accused like this despite many offers to take the blame and provide this support months ago, we really wanted to help you all but the NDA stoped us from doing so... we apologize, that much is completely our fault.

Quote
[11/22/2015 9:26:38 PM] Kuro: i was thinking we could give an update on your behalf and take the blame, we have been doing family stuff over the weekend but intend to launch first thing in the morning, we just need to sit down with you tomorrow morning and handle the small details during the launch
[11/22/2015 9:26:55 PM] Kuro: what time is good for you
[11/22/2015 9:27:25 PM] Jonathan Bunker: ok.. I will be at the bunker 9:30am my time.. I have a LOT going on tomorrow though.. so I will only have some in between time
[11/22/2015 9:27:49 PM] Kuro: okay we will be on and launching around then
[11/22/2015 9:28:56 PM] Jonathan Bunker: ok.. see u then
[11/22/2015 9:29:23 PM] Kuro: do you want us to post the update?
[11/22/2015 9:31:22 PM] Jonathan Bunker: no.. at this point there is nothing else other than getting it done that is going to be satisfying... lets get the payouts out and get the mining pool updated and get going.. then see what needs to be said at that point.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 03, 2015, 02:43:21 pm
@BunkerChain Labs - www.minebitshares-com

What ports/settings are you using to mine?

I cannot replicate your speed.

4449 as @oakmaster mentioned afterwards is the same setting I am using now for scrypt mining.

Title: Re: Emergency Measure - Temporary Shutdown
Post by: JWF on December 03, 2015, 02:47:21 pm
Forwarded your post to @kuro112 on Skype, it's possible he put the wrong details on the site I'm not sure of them myself, so will get back to you.

Edit: Talked to Bunker, and this is the stratum he's mining on:
stratum+tcp://mining.bunkermining.com:4449
k thanks I have one more question if I want to mine bts I put just my name if I want bitusd I put USD after my name
Sha256 stratum+tcp://mining.bunkermining.com:3339
Scrypt   stratum+tcp://mining.bunkermining.com:4449
X11        stratum+tcp://mining.bunkermining.com:5559
username oakmaster USD password x

Are these the correct addresses and ports to use?  Info is all over the place and I would like to help test the new pool!

Tried x11 with these and difficulty is set to 8.  I do not see any shares being accepted.

x11 seems broken atm.

I'm finding the same issue with the X11. Going to try and get my miner on the 256 and test it out today.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 03, 2015, 03:38:33 pm
the proxypool software is ready to be installed and configured however bunker refuses to do it himself and is preventing its delivery for the community.
as we are software development contractors and not responsible for such things, i would look to bunker to solve these problems.

Item #5 on the terms of the contract which you have (committing another NDA infraction adding to the list) posted earlier, states that this feature would be implemented. That means to be put into effect and functioning. Only now have you started this narative of it being something we are responsible for installing and configuring despite over a month of chat logs and phone conversations that are contrary to this position. As well, the bottom line fact that the contract from the very beginning called on you (freebieserver) to complete this.

Actually, this narrative of it being something we have to do ourselves only began Tuesday (December 1st) where you restated everything was delivered a month ago that you claimed to "have proven that fact". I then took the positive approach and apologized, not knowing you had completed the proxy pool mining portion which had been the hold up previously, and asked if you could please send all the documentation necessary so we could input account info and start testing. It was only when I received the documentation that included this feature, did this story of 'setup yourself' start. This was shared at this update:  https://bitsharestalk.org/index.php/topic,20350.msg262715.html#msg262715

We are here now in this public forum @kuro112 because whatever collateral I extended to you through my reputation and good faith despite the numerous excuses you have made over the past three months that spanned blaming everything including your own team members @hybridd and @Freebieservers , has been spent.

I am not in the business of posting personal chat logs to forums. It is a serious breach of confidentiality and trust, particularly under a signed NDA agreement. So while you think you are manipulating public opinion by using edited snippets of chat logs, all you have really accomplished is destroying any trust anyone might put in ever talking to you again about anything. You have demonstrated through your own actions you cannot handle data responsibly. Regardless, what's done is done, and the consequences of such will continue for you.

I knew taking this measure would result in the monkey poop throwing palooza you seem to relish in when your contracts go undelivered. What matters most though is what I told you on December 1st.. execution. So if I had to get a little monkey poopie thrown at me so we can get you executing on the contract, sobeit. (cue an epic @Tuck Fheman meme) :)

I just want delivery for what the community paid for, and I am only excited about how much closer to that we have come in a few days. You would do well to be equally excited, and dig in to getting everything completed and in production. It would only help you.

Looking forward to seeing more progress today!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 03:47:41 pm
the proxypool software is ready to be installed and configured however bunker refuses to do it himself and is preventing its delivery for the community.
as we are software development contractors and not responsible for such things, i would look to bunker to solve these problems.

Item #5 on the terms of the contract which you have (committing another NDA infraction adding to the list) posted earlier, states that this feature would be implemented. That means to be put into effect and functioning. Only now have you started this narative of it being something we are responsible for installing and configuring despite over a month of chat logs and phone conversations that are contrary to this position. As well, the bottom line fact that the contract from the very beginning called on you (freebieserver) to complete this.

Actually, this narrative of it being something we have to do ourselves only began Tuesday (December 1st) where you restated everything was delivered a month ago that you claimed to "have proven that fact". I then took the positive approach and apologized, not knowing you had completed the proxy pool mining portion which had been the hold up previously, and asked if you could please send all the documentation necessary so we could input account info and start testing. It was only when I received the documentation that included this feature, did this story of 'setup yourself' start. This was shared at this update:  https://bitsharestalk.org/index.php/topic,20350.msg262715.html#msg262715

We are here now in this public forum @kuro112 because whatever collateral I extended to you through my reputation and good faith despite the numerous excuses over the past three months that spanned blaming everything including your own team members @hybridd and @Freebieservers , has been spent.

I am not in the business of posting personal chat logs to forums. It is a serious breach of confidentiality and trust, particularly under a signed NDA agreement. So while you think you are manipulating public opinion by using edited snippets of chat logs, all you have really accomplished is destroying any trust anyone might put in ever talking to you again about anything. You have demonstrated through your own actions you cannot handle data responsibly. Regardless, what's done is done, and the consequences of such will continue for you.

I knew taking this measure would result in the monkey poop throwing palooza you seem to relish in when your contracts go undelivered. What matters most though is what I told you on December 1st.. execution. So if I had to get a little monkey poopie thrown at me so we can get you executing on the contract, sobeit. (cue an epic @Tuck Fheman meme) :)

I just want delivery for what the community paid for, and I am only excited about how much closer to that we have come in a few days. You would do well to be equally excited, and dig in to getting everything completed and in production. It would only help you.

Looking forward to seeing more progress today!

you can twist it however you want, but were only posting proof in response to your own violation of the NDA and breech of a contract we we handled professionally.

in the end, were the ones delivering this software and your just making excuses and lieing even more...

Quote
am not in the business of posting personal chat logs to forums. It is a serious breach of confidentiality and trust, particularly under a signed NDA agreement. So while you think you are manipulating public opinion by using edited snippets of chat logs, all you have really accomplished is destroying any trust anyone might put in ever talking to you again about anything. You have demonstrated through your own actions you cannot handle data responsibly. Regardless, what's done is done, and the consequences of such will continue for you.

I encourage any third party auditor to come check out the chat records on my (or his) skype so you can see nothing has been edited, this matter has escalated purely due to bunker breaching the NDA, lieing to his clients about us, and attempting to shift all blame for the failure here to us... its pathetic, step up and take responsibility for your lack of delivery!

we are here supporting and launching this software because for months now you keep refusing to and blaming us...

stop redirecting the blame and take responsibility, these miners are asking for your help to launch a product and your just pointing fingers! grow up and spend some time supporting them.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 03, 2015, 04:35:42 pm
I knew taking this measure would result in the monkey poop throwing palooza you seem to relish in when your contracts go undelivered. What matters most though is what I told you on December 1st.. execution. So if I had to get a little monkey poopie thrown at me so we can get you executing on the contract, sobeit. (cue an epic @Tuck Fheman meme) :)

I think you just violated our NDA brah.

It explicitly states, and I quote, "my monkey poop meme making is to be kept between you and I".

 :P
Title: Re: Emergency Measure - Temporary Shutdown
Post by: fuzzy on December 03, 2015, 05:49:23 pm
ive been sitting on the sidelines here but feel it is important to recognize when there is an issue it is almost always BOTH SIDES at fault in some manner.  And I take myself into account on this because i have to remind myself the same things when i have conflicts. it is one of the beautiful...yet complex aspects of being human.  Still we all have to admit what is being done here in bitshares is code based...which takes time, user feedback and iterations...

please everyone lets just get back to working on this so this production seems less like lord of the flies..  :/

to those testing....THANK YOU for being productive and moving this forward while largely dodging the "monkey poo" ♡
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 05:54:41 pm
ive been sitting on the sidelines here but feel it is important to recognize when there is an issue it is almost always BOTH SIDES at fault in some manner.  And I take myself into account on this because i have to remind myself the same things when i have conflicts. it is one of the beautiful...yet complex aspects of being human.  Still we all have to admit what is being done here in bitshares is code based...which takes time, user feedback and iterations...

please everyone lets just get back to working on this so this production seems less like lord of the flies..  :/

to those testing....THANK YOU for being productive and moving this forward while largely dodging the "monkey poo" ♡

well put man, for my part i apologize for derailing things, i commend the people ignoring it and testing the pool, giving feedback and allowing us to proceed with a much overdue launch.

thanks fuzzster
Title: Re: Emergency Measure - Temporary Shutdown
Post by: CalabiYau on December 03, 2015, 06:24:05 pm
x11 still in the woods.....
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 03, 2015, 08:53:22 pm
Is this ready for production pool? nonworking X11 and nonworking stats? http://216.146.143.200/Dashboard/User?address=proctologic
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 09:28:57 pm
Is this ready for production pool? nonworking X11 and nonworking stats? http://216.146.143.200/Dashboard/User?address=proctologic

the stats work perfectly fine? as for x11 id ask data anout that its not up to us to configure his unomp software
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 03, 2015, 10:01:11 pm
Is this ready for production pool? nonworking X11 and nonworking stats? http://216.146.143.200/Dashboard/User?address=proctologic

the stats work perfectly fine? as for x11 id ask data anout that its not up to us to configure his unomp software
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Title: Re: Emergency Measure - Temporary Shutdown
Post by: cass on December 03, 2015, 10:05:28 pm
same here …
Title: Re: Emergency Measure - Temporary Shutdown
Post by: kuro112 on December 03, 2015, 10:22:30 pm
Is this ready for production pool? nonworking X11 and nonworking stats? http://216.146.143.200/Dashboard/User?address=proctologic

the stats work perfectly fine? as for x11 id ask data anout that its not up to us to configure his unomp software
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

oh looking into that right now, my bad didnt notice that, it worked perfectly for me :P

will be fixed shortly.

fixed
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 03, 2015, 10:38:57 pm
don't mind me guys, just on an on topic post coming through..
Quote
[12/3/2015 10:26:56 PM] Begin Cycle...
        [Cryptsy] BTC: 0.00734649
        [Poloniex] BTC: 0.01932096
        [Poloniex] BTS: 0.00000000

Once that # hits 0.01 it'll get moved, and poloniex will be > 0.02, so a payout will exec shortly after. Also that down time on the user stats was because I renamed some stuff in the DB (and forgot to re-publish the website)... oops.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 04, 2015, 01:25:19 am
don't mind me guys, just on an on topic post coming through..
Quote
[12/3/2015 10:26:56 PM] Begin Cycle...
        [Cryptsy] BTC: 0.00734649
        [Poloniex] BTC: 0.01932096
        [Poloniex] BTS: 0.00000000

Once that # hits 0.01 it'll get moved, and poloniex will be > 0.02, so a payout will exec shortly after. Also that down time on the user stats was because I renamed some stuff in the DB (and forgot to re-publish the website)... oops.

 +5% +5% +5% +5% +5% +5% +5% +5%
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Brekyrself on December 04, 2015, 03:21:58 am
x11 looks to be working again.  How will payout amounts work with 2.0's higher fee's?  Still daily or will the miner be able to decide?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 04, 2015, 03:24:11 am
x11 looks to be working again.  How will payout amounts work with 2.0's higher fee's?  Still daily or will the miner be able to decide?

As of right now the way the payout works is when the pool has mined 0.02 BTC worth in coins (realistically its more like 0.029 BTC due to transfer loss), this is converted to BTS and then paid out to the miners. Thus, it's not on a timed schedule but on an ASAP schedule. I'm sure this will be adjusted as more people start mining. I will link Bunker to this to get you an official response of how he wants the end-result to be.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 04, 2015, 05:04:45 am
there is some port and diffchanges so please look at this list and choose correct port and restart miners

SHA256

Normal Vardiff
Port 3339
minDiff:128
maxDiff:8192

High Vardiff
Port 3338
minDiff:8192,
maxDiff:16384

Low Vardiff
Port 3337
minDiff:8
maxDiff:128

Scrypt

Low Vardiff
Port 4449
minDiff:128
maxDiff:4096

Normal Vardiff
Port 4448
minDiff:4096,
maxDiff:8192


High Vardiff
Port 4444
minDiff:8192,
maxDiff:16284

Fixed Diff 2048 for TITAN
Port 4447
Diff:2048

Fixed Diff 512
Port 4446
diff:512

Fixed Diff 1024
Port 4445
diff:1024


X11

Normal Vardiff
Port 5559
minDiff:0.0001
maxDiff:1

Fixed Diff 0.2
Port 5558
Diff:0.2


Some recommendations
SCRYPT

Below 500KH: 32
500+: 64
1000+: 128
2000+: 256
3000+: 384
5000+: 512
10000+: 1024
25000+: 2048
50000+: 4096
100000+: 8192
250000+: 16284
SHA-256 coins:

1-100GH: 8
100GH-500GH: 256
500GH-1TH: 512
1TH+: 1024
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 04, 2015, 06:01:41 am
x11 looks to be working again.  How will payout amounts work with 2.0's higher fee's?  Still daily or will the miner be able to decide?

Good question. In the future we might be able to make updates that enable miners to determine when their payouts occur. However with the current system that was not planned.

During the testing period we are going to continue to payout every 0.02BTC balance, however, once we go into production, we will adjust this rate based on the amount of mining taking place to approximate something close to a daily payout. So for example when we go into production, we might get more miners going then, and so we might increase the payout rate to every 0.1 BTC. Later we may increase it to every 1 BTC and so on to be distributed to all miners.

The reason for the variation is to ensure we are not getting gamed during payouts with someone setting sell orders at certain times knowing we are paying out then.

Let me know if you have any other questions.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 04, 2015, 06:01:54 am
HERE YE, HERE YE, payments have occured. This would not have been realized without the help of the community, but I realized there is an error in terms of payments which is if a person mines less than 45 BTS, they're entirely ignored. I will make changes to the system so if you mine less than 45 BTS, you're assigned a "credit" for the next payout cycle (so that if credit + pay for that cycle > 45, then you get paid, otherwise your pay for that cycle gets added onto your credit).
 
Quote
        [BTS Daemon] BTS: 3066.36918
        [BTS Daemon] proctologic was paid 31.00000 1.3.0
        [BTS Daemon] oakmaster was paid 440.00000 1.3.0
        [BTS Daemon] www.minebitshares-com was paid 140.2857 1.3.535
        [BTS Daemon] www.minebitshares-com was paid 3.1632 1.3.121
        [BTS Daemon] www.minebitshares-com was paid 652.00000 1.3.0
        [BTS Daemon] ihashfury was paid 17.00000 1.3.0

1.3.0 is BTS, 1.3.121 is USD, 1.3.535 is BROWNIE.PTS

Apologies to those who mined less than 45 BTS, will have the system corrected for the next payout.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 04, 2015, 06:23:22 am
What is the proper format for X11 to mine BROWNIE.PTS?

In looking at users there appears to be a "|" separating the username and asset, but that's not what the instructions say.

So I'm looking for some clarification. Thanks!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 04, 2015, 06:43:27 am
What is the proper format for X11 to mine BROWNIE.PTS?

In looking at users there appears to be a "|" separating the username and asset, but that's not what the instructions say.

So I'm looking for some clarification. Thanks!

You can use either a space or a "|", both are acceptable.

Code: [Select]
        public static char[] AddressDelimiter = new[] { ' ', '|' };
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 04, 2015, 06:51:20 am
What is the proper format for X11 to mine BROWNIE.PTS?

In looking at users there appears to be a "|" separating the username and asset, but that's not what the instructions say.

So I'm looking for some clarification. Thanks!

You can use either a space or a "|", both are acceptable.

Code: [Select]
        public static char[] AddressDelimiter = new[] { ' ', '|' };

ty!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 04, 2015, 06:59:27 am
Any plans to merge mine LTC/DOGE/VIA?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 04, 2015, 08:01:00 am
Status Update

We manually paid out more miners today. 100% BTS once again!

More bugs were fixed.

We got X11 working. This was related to difficulty settings that were too high.

Pool total hash rates were added to the Dashboard.

We found issues in the pool difficulty that have been resolved and have also set some more ports for various difficulty levels for miners to specify depending on their gear.

Payouts took place today. An issue with assets was discovered and fixed. Will verify it was solved in the next payout.

Some coins that have been shown to have issues were removed.

We will continue to wait on features to be completed and continue to test until we can move to production.

Thanks to everyone who is pointing their miners at the various algos now so we can continue to test.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 04, 2015, 08:09:29 am
Any plans to merge mine LTC/DOGE/VIA?

Unfortunately at present the merge mining in the pool is not supported as of yet. However, we are reviewing to see if it is something we can do sooner rather than later.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: CalabiYau on December 04, 2015, 08:16:34 am
x11 is working fine now - thank you for the fix !
Title: Re: Emergency Measure - Temporary Shutdown
Post by: fuzzy on December 04, 2015, 09:20:58 am
Thank you to who is participating in debugging and testing the pool!  You have all given a well-deserved HIGHFIVE for your achievement.  Pat yourselves on the back kids---cause you are special! :D

#sharebits "cass" 1 HIGHFIVE
#sharebits "Tuck Fheman" 1 HIGHFIVE
#sharebits "Brekyrself" 1 HIGHFIVE
#sharebits "kuro112" 1 HIGHFIVE   
#sharebits "oakmaster" 1 HIGHFIVE
#sharebits "hybridd" 1 HIGHFIVE
#sharebits "proctologic" 1 HIGHFIVE
#sharebits "abad812" 1 HIGHFIVE
#sharebits "BunkerChain Labs" 1 HIGHFIVE
#sharebits "Tuck Fheman" 1 HIGHFIVE
#sharebits "iHashFury" 1 HIGHFIVE
#sharebits "nethyb" 1 HIGHFIVE   
#sharebits "CalabiYau" 1 HIGHFIVE
#sharebits "JWF" 1 HIGHFIVE
Title: Re: Emergency Measure - Temporary Shutdown
Post by: btstip on December 04, 2015, 09:22:01 am
Hey fuzzy, here are the results of your tips...
Curious about BtsTip? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20350.msg263392/topicseen.html#msg263392
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
Title: Re: Emergency Measure - Temporary Shutdown
Post by: iHashFury on December 04, 2015, 11:01:27 am
All mining ports I'm using are working well:

Scrypt - A2 mini 24MH:
stratum+tcp://mining.bunkermining.com:4445
stratum+tcp://mining.bunkermining.com:4449

SHA256 - Antminer 500GH:
stratum+tcp://mining.bunkermining.com:3339

I have also received my first Bunker Mining Payout from minebts1.bunkermining-com and my funds from the old setup.

Thanks
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 04, 2015, 12:57:38 pm
Alright, I've implemented a credit system. Let me explain how it works since it will apply to some of you on the next payout cycle.

Joe is mining, but doesn't have the most hashing power in the world. For sake of simplicity, let's assume Joe wants to be paid in BTS (and not another asset). Our pool requires you to have mined a minimum of 45 BTS, since we assume transferring could cost upto 45 BTS, thus if you mine 50 BTS in a cycle, you're paid 5 BTS (50-45=5).

Joe mines a humble amount of 20 BTS per cycle.

cycle 1:
Joe mines 20 BTS.
Since Joe doesn't get paid on cycle 1, he's awarded a credit of 20 BTS.

cycle 2:
Joe mines 20 BTS
Joe has a credit of 20 BTS, so he's owed 40 BTS.
Since 40 BTS is still not a sufficient amount, Joe's credit is updated to 40 BTS.

cycle 3:
Joe mines 20 BTS.
Joe has a credit of 40 BTS, so he's owed 60 BTS.
Since 60 BTS is a sufficient amount Joe gets paid 15 BTS (60-45=15).

Fee's hurt miners with weak hashing power the most, and for this I have a possible solution to mitigate the fee-cost that I will discuss with my associates, as well as BCL.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: Tuck Fheman on December 04, 2015, 02:39:02 pm
Any plans to merge mine LTC/DOGE/VIA?

Unfortunately at present the merge mining in the pool is not supported as of yet. However, we are reviewing to see if it is something we can do sooner rather than later.

coo
Title: Re: Emergency Measure - Temporary Shutdown
Post by: JWF on December 04, 2015, 02:55:47 pm
Alright, I've implemented a credit system. Let me explain how it works since it will apply to some of you on the next payout cycle.

Joe is mining, but doesn't have the most hashing power in the world. For sake of simplicity, let's assume Joe wants to be paid in BTS (and not another asset). Our pool requires you to have mined a minimum of 45 BTS, since we assume transferring could cost upto 45 BTS, thus if you mine 50 BTS in a cycle, you're paid 5 BTS (50-45=5).

Joe mines a humble amount of 20 BTS per cycle.

cycle 1:
Joe mines 20 BTS.
Since Joe doesn't get paid on cycle 1, he's awarded a credit of 20 BTS.

cycle 2:
Joe mines 20 BTS
Joe has a credit of 20 BTS, so he's owed 40 BTS.
Since 40 BTS is still not a sufficient amount, Joe's credit is updated to 40 BTS.

cycle 3:
Joe mines 20 BTS.
Joe has a credit of 40 BTS, so he's owed 60 BTS.
Since 60 BTS is a sufficient amount Joe gets paid 15 BTS (60-45=15).

Fee's hurt miners with weak hashing power the most, and for this I have a possible solution to mitigate the fee-cost that I will discuss with my associates, as well as BCL.


Thank you. Without logging of the prior rounds mining, there would be zero point for anyone with lower hashing power to mine.

Also is there a plan to have stats like the old site with the payout profitability and details on the site?

Things are working good on my side for x11 and sha256.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: hybridd on December 04, 2015, 03:04:06 pm
Alright, I've implemented a credit system. Let me explain how it works since it will apply to some of you on the next payout cycle.

Joe is mining, but doesn't have the most hashing power in the world. For sake of simplicity, let's assume Joe wants to be paid in BTS (and not another asset). Our pool requires you to have mined a minimum of 45 BTS, since we assume transferring could cost upto 45 BTS, thus if you mine 50 BTS in a cycle, you're paid 5 BTS (50-45=5).

Joe mines a humble amount of 20 BTS per cycle.

cycle 1:
Joe mines 20 BTS.
Since Joe doesn't get paid on cycle 1, he's awarded a credit of 20 BTS.

cycle 2:
Joe mines 20 BTS
Joe has a credit of 20 BTS, so he's owed 40 BTS.
Since 40 BTS is still not a sufficient amount, Joe's credit is updated to 40 BTS.

cycle 3:
Joe mines 20 BTS.
Joe has a credit of 40 BTS, so he's owed 60 BTS.
Since 60 BTS is a sufficient amount Joe gets paid 15 BTS (60-45=15).

Fee's hurt miners with weak hashing power the most, and for this I have a possible solution to mitigate the fee-cost that I will discuss with my associates, as well as BCL.


Thank you. Without logging of the prior rounds mining, there would be zero point for anyone with lower hashing power to mine.

Also is there a plan to have stats like the old site with the payout profitability and details on the site?

Things are working good on my side for x11 and sha256.

http://216.146.143.200/Dashboard/User?address=www.minebitshares-com

if you see 0 for a prediction it doesn't necessarily mean 0, but more so indeterminate -- keep in mind these are estimates so they're not necessarily super accurate.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 04, 2015, 06:02:56 pm
Alright, I've implemented a credit system. Let me explain how it works since it will apply to some of you on the next payout cycle.

Joe is mining, but doesn't have the most hashing power in the world. For sake of simplicity, let's assume Joe wants to be paid in BTS (and not another asset). Our pool requires you to have mined a minimum of 45 BTS, since we assume transferring could cost upto 45 BTS, thus if you mine 50 BTS in a cycle, you're paid 5 BTS (50-45=5).

Joe mines a humble amount of 20 BTS per cycle.

cycle 1:
Joe mines 20 BTS.
Since Joe doesn't get paid on cycle 1, he's awarded a credit of 20 BTS.

cycle 2:
Joe mines 20 BTS
Joe has a credit of 20 BTS, so he's owed 40 BTS.
Since 40 BTS is still not a sufficient amount, Joe's credit is updated to 40 BTS.

cycle 3:
Joe mines 20 BTS.
Joe has a credit of 40 BTS, so he's owed 60 BTS.
Since 60 BTS is a sufficient amount Joe gets paid 15 BTS (60-45=15).

Fee's hurt miners with weak hashing power the most, and for this I have a possible solution to mitigate the fee-cost that I will discuss with my associates, as well as BCL.


Thank you. Without logging of the prior rounds mining, there would be zero point for anyone with lower hashing power to mine.

Also is there a plan to have stats like the old site with the payout profitability and details on the site?

Things are working good on my side for x11 and sha256.

http://216.146.143.200/Dashboard/User?address=www.minebitshares-com

if you see 0 for a prediction it doesn't necessarily mean 0, but more so indeterminate -- keep in mind these are estimates so they're not necessarily super accurate.
the credit system is a great idea just received the first new pool payout thanks coming along good
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 04, 2015, 06:10:08 pm
Great work guys!

Will the new pool be listed on http://poolpicker.eu/table (http://poolpicker.eu/table) again? Thanks.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 04, 2015, 09:57:10 pm
How long do you need to be mining until you see stats? When I click my miner http://216.146.143.200/Dashboard/User?address=pba2%20BTS (http://216.146.143.200/Dashboard/User?address=pba2%20BTS) i'm not seeing anything.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 04, 2015, 11:00:43 pm
How long do you need to be mining until you see stats? When I click my miner http://216.146.143.200/Dashboard/User?address=pba2%20BTS (http://216.146.143.200/Dashboard/User?address=pba2%20BTS) i'm not seeing anything.

Just use http://216.146.143.200/Dashboard/User?address=pba2

You don't need to specify the currency.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 04, 2015, 11:08:08 pm
How long do you need to be mining until you see stats? When I click my miner http://216.146.143.200/Dashboard/User?address=pba2%20BTS (http://216.146.143.200/Dashboard/User?address=pba2%20BTS) i'm not seeing anything.

Just use http://216.146.143.200/Dashboard/User?address=pba2

You don't need to specify the currency.
Thanks!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 04, 2015, 11:21:11 pm
One more question... is there a higher difficulty port available for X11? I'm not able to mine properly at port 5559.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 05, 2015, 12:55:21 am
One more question... is there a higher difficulty port available for X11? I'm not able to mine properly at port 5559.

Can you post log whats happening?
Title: Re: Emergency Measure - Temporary Shutdown
Post by: abad812 on December 05, 2015, 01:34:32 am
One more question... is there a higher difficulty port available for X11? I'm not able to mine properly at port 5559.

Can you post log whats happening?
I'm not sure how to post the log; i'm using Nicehash to mine. According to their pool verificatior the pool was showing as incompatible because the difficulty was too low. But I just checked again and now it seems ok.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 05, 2015, 03:25:58 am
One more question... is there a higher difficulty port available for X11? I'm not able to mine properly at port 5559.

Can you post log whats happening?
I'm not sure how to post the log; i'm using Nicehash to mine. According to their pool verificatior the pool was showing as incompatible because the difficulty was too low. But I just checked again and now it seems ok.

Yea diff have been changed tonight
Title: Re: Emergency Measure - Temporary Shutdown
Post by: BunkerChainLabs-DataSecurityNode on December 05, 2015, 04:59:53 am
Status Update

No more payouts from the previous pool today were requested.

Our first automated payouts got processed today and in that discovered a bug that prevents the proper payout in some circumstances. A fix was applied and we wait to see in the next payout if it worked.

We had #10 item on the list of things that needed to be completed delivered. If you login to your User stats page, you can now get an estimate of how much you will be paid during the next payout in your respective currency. Will continue to test it.

We got merge mining setup and are exploring possibilities of somehow including it as part of the payouts.

Much more to come!

Keep on mining and giving us feedback on everything. If you have any issues let us know!

Thanks to everyone!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: donkeypong on December 05, 2015, 06:08:55 am
May I suggest you close this thread? "Emergency Measures: Temporary Shutdown" is not what everyone wants to see on top of the BitShares discussion board.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: 38PTSWarrior on December 05, 2015, 06:14:51 am
Status Update

No more payouts from the previous pool today were requested.

Our first automated payouts got processed today and in that discovered a bug that prevents the proper payout in some circumstances. A fix was applied and we wait to see in the next payout if it worked.

We had #10 item on the list of things that needed to be completed delivered. If you login to your User stats page, you can now get an estimate of how much you will be paid during the next payout in your respective currency. Will continue to test it.

We got merge mining setup and are exploring possibilities of somehow including it as part of the payouts.

Much more to come!

Keep on mining and giving us feedback on everything. If you have any issues let us know!

Thanks to everyone!

Congrats for automization!

#sharebits "BunkerChain Labs" 1 CHATEAUX
Title: Re: Emergency Measure - Temporary Shutdown
Post by: btstip on December 05, 2015, 06:16:33 am
Hey 38PTSWarrior, here are the results of your tips...
Curious about ShareBits? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20350.msg263647/topicseen.html#msg263647
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
Title: Re: Emergency Measure - Temporary Shutdown
Post by: tonyk on December 05, 2015, 07:47:18 am
May I suggest you close this thread? "Emergency Measures: Temporary Shutdown" is not what everyone wants to see on top of the BitShares discussion board.

Yes, obit for BTS is far more appropriate.
Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 06, 2015, 07:31:17 pm
Can we please get more testing in SHA256 it would be great.

there is some port and diffchanges so please look at this list and choose correct port and restart miners

SHA256

Normal Vardiff
Port 3339
minDiff:128
maxDiff:8192

High Vardiff
Port 3338
minDiff:8192,
maxDiff:16384

Low Vardiff
Port 3337
minDiff:8
maxDiff:128

Scrypt

Low Vardiff
Port 4449
minDiff:128
maxDiff:4096

Normal Vardiff
Port 4448
minDiff:4096,
maxDiff:8192


High Vardiff
Port 4444
minDiff:8192,
maxDiff:16284

Fixed Diff 2048 for TITAN
Port 4447
Diff:2048

Fixed Diff 512
Port 4446
diff:512

Fixed Diff 1024
Port 4445
diff:1024


X11

Normal Vardiff
Port 5559
minDiff:0.0001
maxDiff:1

Some recommendations
SCRYPT

Below 500KH: 32
500+: 64
1000+: 128
2000+: 256
3000+: 384
5000+: 512
10000+: 1024
25000+: 2048
50000+: 4096
100000+: 8192
250000+: 16284
SHA-256 coins:

1-100GH: 8
100GH-500GH: 256
500GH-1TH: 512
1TH+: 1024
Title: Re: Emergency Measure - Temporary Shutdown
Post by: oakmaster on December 06, 2015, 09:10:42 pm
Can we please get more testing in SHA256 it would be great.

there is some port and diffchanges so please look at this list and choose correct port and restart miners

SHA256

Normal Vardiff
Port 3339
minDiff:128
maxDiff:8192

High Vardiff
Port 3338
minDiff:8192,
maxDiff:16384

Low Vardiff
Port 3337
minDiff:8
maxDiff:128

Scrypt

Low Vardiff
Port 4449
minDiff:128
maxDiff:4096

Normal Vardiff
Port 4448
minDiff:4096,
maxDiff:8192


High Vardiff
Port 4444
minDiff:8192,
maxDiff:16284

Fixed Diff 2048 for TITAN
Port 4447
Diff:2048

Fixed Diff 512
Port 4446
diff:512

Fixed Diff 1024
Port 4445
diff:1024


X11

Normal Vardiff
Port 5559
minDiff:0.0001
maxDiff:1

Some recommendations
SCRYPT

Below 500KH: 32
500+: 64
1000+: 128
2000+: 256
3000+: 384
5000+: 512
10000+: 1024
25000+: 2048
50000+: 4096
100000+: 8192
250000+: 16284
SHA-256 coins:

1-100GH: 8
100GH-500GH: 256
500GH-1TH: 512
1TH+: 1024
my sha256 rig is rented once it done all through back on the only thing right now I'm seeing is the estimated payouts is all over the place one minute it says 400 bts than a hr later 13 bts than it'll jump to 1400 bts does it reset it self everytime the coin switches other than that I didn't have any other issues good work thanks
Title: Re: Emergency Measure - Temporary Shutdown
Post by: liondani on December 07, 2015, 12:59:44 pm
May I suggest you close this thread? "Emergency Measures: Temporary Shutdown" is not what everyone wants to see on top of the BitShares discussion board.

 +5%

or at least rename it!

(https://s3-eu5.ixquick.com/cgi-bin/serveimage?url=http%3A%2F%2Falissajean.files.wordpress.com%2F2012%2F01%2Ffoot.jpg&sp=cab434a02a0eb84103c8246302c66c52)


Title: Re: Emergency Measure - Temporary Shutdown
Post by: proctologic on December 07, 2015, 01:27:53 pm
 +5% +5% +5% +5% +5% +5% :o
Title: Re: Emergency Measure - Temporary Shutdown
Post by: CalabiYau on December 07, 2015, 01:54:14 pm
May I suggest you close this thread? "Emergency Measures: Temporary Shutdown" is not what everyone wants to see on top of the BitShares discussion board.

 +5%

or at least rename it!


+5%
Title: Re: Emergency Measure - Temporary Shutdown of MinerBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 07, 2015, 07:08:56 pm
Renamed too  "Emergency Measure - Temporary Shutdown of MinerBitShares"

That is more specific.

There are a few reasons this thread has to remain going.

1. We are still not up with a production pool yet.
2. People still need to get paid out and need to see this thread for instructions.

Until the pool is back in production we will continue to post updates here.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on December 08, 2015, 02:53:47 am
New fixed ports added for NiceHash. Please try them.
SHA256

Low Vardiff
Port 3337
minDiff:8
maxDiff:128

Normal Vardiff
Port 3339
minDiff:128
maxDiff:8192

High Vardiff
Port 3338
minDiff:8192,
maxDiff:16384

Nicehash Fixed Diff
Port 4443
Diff:16384


Scrypt

Low Vardiff
Port 4449
minDiff:128
maxDiff:4096

Normal Vardiff
Port 4448
minDiff:4096,
maxDiff:8192


High Vardiff
Port 4444
minDiff:8192,
maxDiff:16284

NiceHash Fixed Diff
Port 4443
diff:16284

Fixed Diff 2048 for TITAN
Port 4447
Diff:2048

Fixed Diff 512
Port 4446
diff:512

Fixed Diff 1024
Port 4445
diff:1024


X11

Normal Vardiff
Port 5559
minDiff:0.001
maxDiff:1

NiceHash Fixed Diff
Port 5558
diff:0.2
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Troglodactyl on December 08, 2015, 04:29:21 am
What's the status on X11?  I've been mining at ~8MH for a few days and I'm showing "Est. Value Payout: 0.00015 BTS"...
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on December 08, 2015, 04:33:26 am
New fixed ports added for NiceHash. Please try them.

X11

Normal Vardiff
Port 5559
minDiff:0.001
maxDiff:1

NiceHash Fixed Diff
Port 5558
diff:0.2

What's the reason to choose one or the other for x11?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: abad812 on December 08, 2015, 04:44:37 am
New fixed ports added for NiceHash. Please try them.

X11

Normal Vardiff
Port 5559
minDiff:0.001
maxDiff:1

NiceHash Fixed Diff
Port 5558
diff:0.2

What's the reason to choose one or the other for x11?
Using port 5559 for Nicehash's X11 algo has been working fine for me and port 4448 for scrypt.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on December 08, 2015, 04:48:53 am
New fixed ports added for NiceHash. Please try them.

X11

Normal Vardiff
Port 5559
minDiff:0.001
maxDiff:1

NiceHash Fixed Diff
Port 5558
diff:0.2

What's the reason to choose one or the other for x11?
Using port 5559 for Nicehash's X11 algo has been working fine for me and port 4448 for scrypt.


It may depend on hashrate then. with high hashrate fixed ports is recommended for NiceHash
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 08, 2015, 05:54:58 pm
We've changed the way users stats is displayed. It will show you all of the shares you own since the last payout, and tell you how much of the shares you own %-wise.

Payouts have been adjusted to now occur at 0.04 BTC.

An estimate can be calculated like this:
BTS = 0.04 BTC / RATE_BTC_BTS * %-Holding

i.e. if you hold 10% of all shares since the last payout, and suppose the current market value of BTS is 0.00000920,
BTS = 0.04 /  0.00000920 * 0.10 = 434.7826

http://216.146.143.200/Dashboard/User?address=www.minebitshares-com
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 09, 2015, 05:48:09 am
Status Update

More miners from the old pool were paid out over the past few days. Some in BTS and some BTC.

Testing the pool has continued and over the past few days we have had some improvements.

Just recently a payout log area was added but it is not in the navigation yet:

http://216.146.143.200/dashboard/payments

Also you will notice we optimized some mining ports for nicehash and other rig rental places.

Improvements were made to the reporting area for users.

If there is any additional feedback regarding all these things now is the time to share it!

Thanks for everyone who is helping to test the pool.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Troglodactyl on December 09, 2015, 01:20:59 pm
What's up with X11?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 09, 2015, 06:03:00 pm
What's up with X11?

Sorry can you be more specific? What kind of issue are you having with x11?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Troglodactyl on December 09, 2015, 07:07:21 pm
What's up with X11?

Sorry can you be more specific? What kind of issue are you having with x11?
No one is getting payouts, and the payout estimates are all at almost nothing.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: CalabiYau on December 09, 2015, 07:50:02 pm
What's up with X11?

Sorry can you be more specific? What kind of issue are you having with x11?
No one is getting payouts, and the payout estimates are all at almost nothing.
+5% +5%

Completely broken, no fix for days now.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 09, 2015, 09:11:29 pm
Payouts have been occuring, however Bunker has made the decision that the shares  your miner has acquired will only be grouped against miners mining the same algorithm. We'll be implementing this change soon.

To walk you through this, suppose theres are 3 miners and these are their respective shares (hypothetical numbers to make calculations easy):

algo coin name shares
x11 startcoin joe 10
x11 startcoin sam 5
scrypt casinocoin joe 100

Suppose the 0.04 BTC threshold is hit

Current Way
joe = (0.04 * (100+10)/115) / BTC_PER_BTS
sam = (0.04 * 5/115) / BTC_PER_BTS

Changes to be made
suppose theoretically of the 0.04, 0.02 BTC is from x11 coins, and 0.02 BTC is from scrypt coins.

joe = ((0.02 * 100/100) + (0.02 * 10/15)) / BTC_PER_BTS
sam = ((0.02 * 0/100) + (0.02 5/15)) / BTC_PER_BTS

tl;dr for those of you since math is apparently hard and don't understand the phrase "hypothetical numbers":
x11 miners get paid based on x11 coins mined
scrypt miners get paid based on scrypt coins mined
sha256 miners get paid based on sha256 coins mined

this change has not been made live yet.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 10, 2015, 12:22:54 am
Payouts have been occuring, however Bunker has made the decision that the shares  your miner has acquired will only be grouped against miners mining the same algorithm. We'll be implementing this change soon.

To walk you through this, suppose theres are 3 miners and these are their respective shares (hypothetical numbers to make calculations easy):

algo coin name shares
x11 startcoin joe 10
x11 startcoin sam 5
scrypt casinocoin joe 100

Suppose the 0.04 BTC threshold is hit

Current Way
joe = (0.04 * (100+10)/115) / BTC_PER_BTS
sam = (0.04 * 5/115) / BTC_PER_BTS

Changes to be made
0.02 BTC of which is from x11, and 0.02 BTC of which is from scrypt.

joe = ((0.02 * 100/100) + (0.02 * 10/15)) / BTC_PER_BTS
sam = ((0.02 * 0/100) + (0.02 5/15)) / BTC_PER_BTS

tl;dr for those of you since math is apparently hard and don't understand the phrase "hypothetical numbers":
x11 miners get paid based on x11 coins mined
scrypt miners get paid based on scrypt coins mined
sha256 miners get paid based on sha256 coins mined

this change has not been made live yet.

To further clarify on this change, what this means is that each algo balance that is mined will be kept separate from eachother, and the shares paid out according to each algo share holder.

So if x11 only mined 0.01 and scrypt mined 0.01, and sha256 mined 0.02, then the payout to x11s would be a total of 0.01, script would be paid out 0.01, and sha256 would get 0.02 and that will be distributed to each miners respective shares in those algos.

This is how the previous pool used to work and how we want to proceed forward, fair share.

Hope this helps clarify the fix that will be done.

This will solve the issue x11 miners had not getting paid out.

This fix should be completed within 48 hours.

Thanks for the feedback that helped us identify this issue before we went into production!
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 10, 2015, 02:37:08 pm
I was given confirmation that this fix has been completed.

However, it has been untested. Therefore, we all have to wait until the next payout cycle to see if it was done properly.

Everyone please report back to us if the payouts appear to be more in the normal payout space, or if they were absent all together, or any other irregularities.

Thanks!
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 11, 2015, 04:25:34 am
http://216.146.143.200/dashboard/index
Index page updated to reflect the current BTC totals of each algorithm (resets after a payout).

Predictability shown in user-panel reflects the current worth of  your miner(s), this resets every time a payout completes. -- Should be way more accurate than before!
http://216.146.143.200/Dashboard/User?address=www.minebitshares-com
http://216.146.143.200/Dashboard/User?address=generator (x11 miner)
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on December 11, 2015, 09:54:09 pm
http://216.146.143.200/dashboard/index
Index page updated to reflect the current BTC totals of each algorithm (resets after a payout).

Predictability shown in user-panel reflects the current worth of  your miner(s), this resets every time a payout completes. -- Should be way more accurate than before!
http://216.146.143.200/Dashboard/User?address=www.minebitshares-com
http://216.146.143.200/Dashboard/User?address=generator (x11 miner)


Nice improvement.  Any other plans to share on the future of the pool?  The previous one was interesting because you ran the delegates to provide a bonus, what's the plan to make this one extra profitable?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on December 12, 2015, 02:33:18 am
We've changed the way users stats is displayed. It will show you all of the shares you own since the last payout, and tell you how much of the shares you own %-wise.

Payouts have been adjusted to now occur at 0.04 BTC.

An estimate can be calculated like this:
BTS = 0.04 BTC / RATE_BTC_BTS * %-Holding

i.e. if you hold 10% of all shares since the last payout, and suppose the current market value of BTS is 0.00000920,
BTS = 0.04 /  0.00000920 * 0.10 = 434.7826

http://216.146.143.200/Dashboard/User?address=www.minebitshares-com
It appears that the .04btc payout limit is per algo?  Was thinking it would be total for pool…  Though i am unsure what is the most fair.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 12, 2015, 03:01:36 am
It is 0.04 for the entire pool, unfortunately, cryptsy is being very slow with withdrawals =/
We liquidate alts at Cryptsy move the BTC to Poloniex and then buy the BTS.

Quote
        [Cryptsy] BTC: 0.00968221
        [Unomp] scrypt BTC: 0.0345651
        [Unomp] x11 BTC: 0.01591743
        [Unomp] sha256 BTC: 0.0026986
        [Poloniex] BTC: 0.03645680
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on December 12, 2015, 03:05:11 am
It is 0.04 for the entire pool, unfortunately, cryptsy is being very slow with withdrawals =/
We liquidate alts at Cryptsy, and buy the BTS over at Poloniex.

Quote
        [Cryptsy] BTC: 0.00968221
        [Unomp] scrypt BTC: 0.0345651
        [Unomp] x11 BTC: 0.01591743
        [Unomp] sha256 BTC: 0.0026986
        [Poloniex] BTC: 0.03645680

There's a pending withdrawal for 0.01 from C->P still currently.
Ok.  Cool.  No problem.  Just so long as i know.  Thank you.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: abad812 on December 12, 2015, 03:48:27 am
It is 0.04 for the entire pool, unfortunately, cryptsy is being very slow with withdrawals =/
We liquidate alts at Cryptsy move the BTC to Poloniex and then buy the BTS.

Quote
        [Cryptsy] BTC: 0.00968221
        [Unomp] scrypt BTC: 0.0345651
        [Unomp] x11 BTC: 0.01591743
        [Unomp] sha256 BTC: 0.0026986
        [Poloniex] BTC: 0.03645680
Is it possible to use a different exchange other than Cryptsy? https://www.cryptocoinsnews.com/cryptsys-bitcoin-withdrawal-troubles-continue/ (https://www.cryptocoinsnews.com/cryptsys-bitcoin-withdrawal-troubles-continue/)
Perhaps Bittrex?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 12, 2015, 03:50:07 am
It is 0.04 for the entire pool, unfortunately, cryptsy is being very slow with withdrawals =/
We liquidate alts at Cryptsy, and buy the BTS over at Poloniex.

Quote
        [Cryptsy] BTC: 0.00968221
        [Unomp] scrypt BTC: 0.0345651
        [Unomp] x11 BTC: 0.01591743
        [Unomp] sha256 BTC: 0.0026986
        [Poloniex] BTC: 0.03645680

There's a pending withdrawal for 0.01 from C->P still currently.
Ok.  Cool.  No problem.  Just so long as i know.  Thank you.

Keep in mind that the rate is also a moving rate that will change as the pool volume changes. We will attempt to keep it in line closer to a once per day payout. The decision to move it up actually happened when we were getting 1GH script mining, and then it stopped. So it might make sense for us to dial it back to 0.2 again.

We are still testing though.. this payout will help us determine if the recent fix in share distribution has worked also.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 12, 2015, 03:53:44 am
It is 0.04 for the entire pool, unfortunately, cryptsy is being very slow with withdrawals =/
We liquidate alts at Cryptsy move the BTC to Poloniex and then buy the BTS.

Quote
        [Cryptsy] BTC: 0.00968221
        [Unomp] scrypt BTC: 0.0345651
        [Unomp] x11 BTC: 0.01591743
        [Unomp] sha256 BTC: 0.0026986
        [Poloniex] BTC: 0.03645680
Is it possible to use a different exchange other than Cryptsy? https://www.cryptocoinsnews.com/cryptsys-bitcoin-withdrawal-troubles-continue/ (https://www.cryptocoinsnews.com/cryptsys-bitcoin-withdrawal-troubles-continue/)
Perhaps Bittrex?

The current choice in exchange is largely determined by who supports the coins we are mining for the most profitability. I realize it is not ideal, and frankly wish there was more competition with volume to consider, but there isn't at present. This however is not meant to be permanent.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 12, 2015, 03:56:32 am
http://216.146.143.200/dashboard/index
Index page updated to reflect the current BTC totals of each algorithm (resets after a payout).

Predictability shown in user-panel reflects the current worth of  your miner(s), this resets every time a payout completes. -- Should be way more accurate than before!
http://216.146.143.200/Dashboard/User?address=www.minebitshares-com
http://216.146.143.200/Dashboard/User?address=generator (x11 miner)


Nice improvement.  Any other plans to share on the future of the pool?  The previous one was interesting because you ran the delegates to provide a bonus, what's the plan to make this one extra profitable?

There are plans to incorporate bonus payouts. More on that will come out on the production launch.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 14, 2015, 05:02:01 pm
Status Update

Those of you mining may have noticed that payouts have gone past the threshold that we set for the pool. This is due to cryptsy delaying the transfer of BTC out of their exchange. There have been a whirlwind of other accusations related to cryptsy payouts including class actions.

Some of our more profitable coins were only on cryptsy, but there isn't more profit when you simply are not getting paid out.

I decided that we would cut our losses, and use what coins we can, and a few new ones that we can exchange at Poloniex, and Bittrex.

Between these two exchanges, we currently have about 17 coins between all three algos that the pool currently supports. In addition to this, we also have enabled merge mining with DOGE. We are working out a way to make this part of the bonus payout.

The migration has not been completed yet. As you can see, after we had updated all the wallets and the config for the pool it appears all our charts suddenly stopped working. This has been reported to @Freebieservers along with the updated deposit addresses to start being directed at the other exchanges. If you ignore the charts you can see from the workers below on the Dashboard the current coins that are being mined.

Hopefully we will see the payout make its way out of crytpsy, but we aren't holding out a lot of hope given all the accusations and the shrinking volume happening there.

Please continue to test the pool and report any other issues you are finding, or things missing that you think should be there in regards to features and/or reporting. If you have been mining elsewhere while we are still in development and have seen some good success with other coins, also feel free to share and we can consider adding those to the pool if they are available for exchange on Polo/Bittrex.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Xypher on December 14, 2015, 05:06:04 pm
Status Update

Those of you mining may have noticed that payouts have gone past the threshold that we set for the pool. This is due to cryptsy delaying the transfer of BTC out of their exchange. There have been a whirlwind of other accusations related to cryptsy payouts including class actions.

Some of our more profitable coins were only on cryptsy, but there isn't more profit when you simply are not getting paid out.

I decided that we would cut our losses, and use what coins we can, and a few new ones that we can exchange at Poloniex, and Bittrex.

Between these two exchanges, we currently have about 17 coins between all three algos that the pool currently supports. In addition to this, we also have enabled merge mining with DOGE. We are working out a way to make this part of the bonus payout.

The migration has not been completed yet. As you can see, after we had updated all the wallets and the config for the pool it appears all our charts suddenly stopped working. This has been reported to @Freebieservers along with the updated deposit addresses to start being directed at the other exchanges. If you ignore the charts you can see from the workers below on the Dashboard the current coins that are being mined.

Hopefully we will see the payout make its way out of crytpsy, but we aren't holding out a lot of hope given all the accusations and the shrinking volume happening there.

Please continue to test the pool and report any other issues you are finding, or things missing that you think should be there in regards to features and/or reporting. If you have been mining elsewhere while we are still in development and have seen some good success with other coins, also feel free to share and we can consider adding those to the pool if they are available for exchange on Polo/Bittrex.

I can confirm he's shared the required information in the group chat.
That said, its sad to see these delays - thanks to external factors.
Hybridd might be off until later today (exams) but am sure he'll update as soon as he's on.

As BCL mentioned - do share inputs as it would help come out with a far better product.

Regards
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: CalabiYau on December 14, 2015, 06:56:18 pm
Code: [Select]
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Actually getting this error msg on the payout page.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on December 14, 2015, 07:14:28 pm
Still need to update the "getting started" page with x11 and sha256 instructions.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 14, 2015, 10:46:15 pm
Code: [Select]
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Actually getting this error msg on the payout page.

Currently, the BTS daemon is offline, I've notified BCL, once its back online, that page should resume working. We've also undergone various changes over the last day to move away from using Cryptsy as they've proven incredibly unreliable in being able to process withdrawals in the last 2 days.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 15, 2015, 07:49:47 am
k so that's why I only received a small payout after mining for 5 days without one is because craptsy is holding up withdrawals it not your fault thanks for the updates it sucks cause it just seemed everything was going well that the exchange had to get us outside of that the ports I'm running on seem to be good
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 15, 2015, 08:40:08 am
k so that's why I only received a small payout after mining for 5 days without one is because craptsy is holding up withdrawals it not your fault thanks for the updates it sucks cause it just seemed everything was going well that the exchange had to get us outside of that the ports I'm running on seem to be good

Yeah that's correct. We have really around 0.1 BTC to be distributed, but about 0.06-0.07 BTC of that is being held by Cryptsy. The distribution that happened today was only worth around 0.036 BTC.

It looks like the modified payment model is indeed working... it's just unfortunate that Cryptsy is in the position it's currently in. We've eliminated using them entirely from out system now.

Still need to update the "getting started" page with x11 and sha256 instructions.
Seems I overlooked this, I'll look into this in the morning, thx.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 15, 2015, 09:14:26 pm
Status Update

Cryptsy withdraws are still pending. I have submitted a ticket in an attempt to get them confirmed. There are a total of 16 withdraws that never made it out of there.

We got new coins setup with Polo/Bittrex now and just waiting on the first payouts again.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Troglodactyl on December 16, 2015, 12:04:56 am
Status Update

Those of you mining may have noticed that payouts have gone past the threshold that we set for the pool. This is due to cryptsy delaying the transfer of BTC out of their exchange. There have been a whirlwind of other accusations related to cryptsy payouts including class actions.

Some of our more profitable coins were only on cryptsy, but there isn't more profit when you simply are not getting paid out.

I decided that we would cut our losses, and use what coins we can, and a few new ones that we can exchange at Poloniex, and Bittrex.

Between these two exchanges, we currently have about 17 coins between all three algos that the pool currently supports. In addition to this, we also have enabled merge mining with DOGE. We are working out a way to make this part of the bonus payout.

The migration has not been completed yet. As you can see, after we had updated all the wallets and the config for the pool it appears all our charts suddenly stopped working. This has been reported to @Freebieservers along with the updated deposit addresses to start being directed at the other exchanges. If you ignore the charts you can see from the workers below on the Dashboard the current coins that are being mined.

Hopefully we will see the payout make its way out of crytpsy, but we aren't holding out a lot of hope given all the accusations and the shrinking volume happening there.

Please continue to test the pool and report any other issues you are finding, or things missing that you think should be there in regards to features and/or reporting. If you have been mining elsewhere while we are still in development and have seen some good success with other coins, also feel free to share and we can consider adding those to the pool if they are available for exchange on Polo/Bittrex.

Isn't this on opportunity, if several of the most profitable (demanded) coins now have no exchange?  Why not hang on to them and issue corresponding UIAs to set up a gateway?  You could reach out to their communities and let them know, since I'm sure they're looking for a new exchange.

EDIT: Perhaps @monsterer, @dannotestein, or @ccedk could help out with that...
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 16, 2015, 02:42:29 am
k so that's why I only received a small payout after mining for 5 days without one is because craptsy is holding up withdrawals it not your fault thanks for the updates it sucks cause it just seemed everything was going well that the exchange had to get us outside of that the ports I'm running on seem to be good

Yeah that's correct. We have really around 0.1 BTC to be distributed, but about 0.06-0.07 BTC of that is being held by Cryptsy. The distribution that happened today was only worth around 0.036 BTC.

It looks like the modified payment model is indeed working... it's just unfortunate that Cryptsy is in the position it's currently in. We've eliminated using them entirely from out system now.

Still need to update the "getting started" page with x11 and sha256 instructions.
Seems I overlooked this, I'll look into this in the morning, thx.
that's what I thought it sucks that this is happening with cryptsy they support a large amount of alts and have been around for awhile makes you wonder what's going to happen with all the coins that rely on them for being their only exchange if cryptsy goes under
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 16, 2015, 02:48:51 am
just one more thing I noticed on the getting started page there's a typo under sha for normal diff there 8192 for the port it's 3339
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on December 16, 2015, 02:51:48 am
Seems if Cryptsy does go under,  @ccedk would do well to try and absorb as many as possible and add them into the exchange. Short notice and all, but no time like the present to try and up the ante with volume on the exchange.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 16, 2015, 03:00:15 am
k so that's why I only received a small payout after mining for 5 days without one is because craptsy is holding up withdrawals it not your fault thanks for the updates it sucks cause it just seemed everything was going well that the exchange had to get us outside of that the ports I'm running on seem to be good

Yeah that's correct. We have really around 0.1 BTC to be distributed, but about 0.06-0.07 BTC of that is being held by Cryptsy. The distribution that happened today was only worth around 0.036 BTC.

It looks like the modified payment model is indeed working... it's just unfortunate that Cryptsy is in the position it's currently in. We've eliminated using them entirely from out system now.

Still need to update the "getting started" page with x11 and sha256 instructions.
Seems I overlooked this, I'll look into this in the morning, thx.
that's what I thought it sucks that this is happening with cryptsy they support a large amount of alts and have been around for awhile makes you wonder what's going to happen with all the coins that rely on them for being their only exchange if cryptsy goes under

Many of those alts are very low volume, which is why they only have Cyrptsy left.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 16, 2015, 03:17:16 am
k so that's why I only received a small payout after mining for 5 days without one is because craptsy is holding up withdrawals it not your fault thanks for the updates it sucks cause it just seemed everything was going well that the exchange had to get us outside of that the ports I'm running on seem to be good

Yeah that's correct. We have really around 0.1 BTC to be distributed, but about 0.06-0.07 BTC of that is being held by Cryptsy. The distribution that happened today was only worth around 0.036 BTC.

It looks like the modified payment model is indeed working... it's just unfortunate that Cryptsy is in the position it's currently in. We've eliminated using them entirely from out system now.

Still need to update the "getting started" page with x11 and sha256 instructions.
Seems I overlooked this, I'll look into this in the morning, thx.
that's what I thought it sucks that this is happening with cryptsy they support a large amount of alts and have been around for awhile makes you wonder what's going to happen with all the coins that rely on them for being their only exchange if cryptsy goes under

Many of those alts are very low volume, which is why they only have Cyrptsy left.
that's a good point I guess this is a way to clean up a little there's no reason why there's 200 to 300 different alts when most of them are copy and paste code with nothing different to offer
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on December 17, 2015, 08:52:10 am
just one more thing I noticed on the getting started page there's a typo under sha for normal diff there 8192 for the port it's 3339

where do you see that?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 17, 2015, 12:21:50 pm
just one more thing I noticed on the getting started page there's a typo under sha for normal diff there 8192 for the port it's 3339

where do you see that?
k either I'm going crazy or it's been changed the other day when I was looking at the getting started for the different ports the norm diff for sha256 said 8192 but anyway I think the pool running great I haven't had no issues connecting or with hashrate outside of the issue with cryptsy seems payments are running good you guys did a good job getting it up and running seems any little glitches that where found was fixed petty quick
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 17, 2015, 02:16:45 pm
just one more thing I noticed on the getting started page there's a typo under sha for normal diff there 8192 for the port it's 3339

where do you see that?
k either I'm going crazy or it's been changed the other day when I was looking at the getting started for the different ports the norm diff for sha256 said 8192 but anyway I think the pool running great I haven't had no issues connecting or with hashrate outside of the issue with cryptsy seems payments are running good you guys did a good job getting it up and running seems any little glitches that where found was fixed petty quick

You're not, I did indeed change it :P and thanks for the positive feed back! If only we had started open-testing sooner, I think we could've resolved a lot of the issues more early on, but regardless we're on the right track.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 17, 2015, 06:22:57 pm
Status Update

Reply from Cryptsy regarding payouts:

Quote
Thank you for getting in touch with us.

Most BTC LTC and BTCD withdrawals are currently extremely slow moving due to tech issues. This progressively got worse over the past week and were trying to find the reason they are not going out. Please understand that due to extremely high security this a very complex system and the problem is still being resolved.

We appreciate your patience and understanding on this matter. Should you wish to cancel your pending withdraw, please let us know.

A few more of the withdraw requests have been processed, but the bulk are still outstanding. At this rate expect the rest of it to be withdrawn within about a week.

Few more minor updates are being waited on and we are continuing to test out the payout system. Please be sure to let us know if you find anything unusual.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 18, 2015, 09:55:19 pm
Fixed, sorry for the down time.. a payout should be occurring fairly soon with a hefty amount since some of the cryptsy btc that was held up has been flowing in.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on December 19, 2015, 02:40:32 am
What's left on the to do list before launching officially?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 19, 2015, 01:18:21 pm
we need a little more hash on sha256 I don't think I'm doing anything by myself it sucks cause I sold my antminers s1's and my s2 cause the power to profit was worth it if I still had them they all would be at bunkermining
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 19, 2015, 11:25:38 pm
Status Update

IMPORTANT UPDATE - If you are mining the test pool, access to the IP address will be disabled as of 12pm EST on Sunday December 20th 2015.

If your mining configuration is pointing to 216.146.143.177 please change it to mining.bunkermining.com.

We just added three new coins to the pool that will become active at the same time.

This will bring our total coin count for the pool up to 25 coins.

We are still working on merge mining payouts.

More of the cryptsy deposits have been making their way into our payouts which is good news.

We are getting much close to finally getting to production.

I anticipate we maybe ready for the beginning of 2016!

Keep on hashing and testing and giving us feedback!
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on December 20, 2015, 03:28:49 pm
we need a little more hash on sha256 I don't think I'm doing anything by myself it sucks cause I sold my antminers s1's and my s2 cause the power to profit was worth it if I still had them they all would be at bunkermining

Feel free to recommend low diff sha256 coins to add to pool as its not producing any blocks with this low hashrate.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 20, 2015, 05:59:10 pm
we need a little more hash on sha256 I don't think I'm doing anything by myself it sucks cause I sold my antminers s1's and my s2 cause the power to profit was worth it if I still had them they all would be at bunkermining

Feel free to recommend low diff sha256 coins to add to pool as its not producing any blocks with this low hashrate.
is there anyway to forward the hash to nicehash at least this way even if there's only a few ppl hashing on sha but altogether it's still a low hashrate there can still be a payment cause nicehash pays for every accepted share just I thought I'm not a programmer so I don't no if it's a lot of work but if it isn't than even the guys with USB sticks can collect a few bts than when our rate goes up it'll swith to regular coins
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 20, 2015, 06:12:51 pm
Status Update

All the mining has now moved to mining.bunkermining.com and is no longer functional on the IP address that was posted here.

The operation caused some downtime due to DNS propagation issues, but it was done within about 30 minutes total.

If you haven't updated your configurations please do so now to resume your testing.

We had some challenges in the switch over. We will continue to monitor the situation and make fixes as needed.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on December 20, 2015, 06:21:43 pm
we need a little more hash on sha256 I don't think I'm doing anything by myself it sucks cause I sold my antminers s1's and my s2 cause the power to profit was worth it if I still had them they all would be at bunkermining

Feel free to recommend low diff sha256 coins to add to pool as its not producing any blocks with this low hashrate.
is there anyway to forward the hash to nicehash at least this way even if there's only a few ppl hashing on sha but altogether it's still a low hashrate there can still be a payment cause nicehash pays for every accepted share just I thought I'm not a programmer so I don't no if it's a lot of work but if it isn't than even the guys with USB sticks can collect a few bts than when our rate goes up it'll swith to regular coins

Unfortunately this was one of our feature parameters of the contract for the mining pool that will not be fulfilled by freebieserver.

Keep in mind though that we are ONLY TESTING right now. We have not gone into production. We are also only in an early version for the pool that will have many more things to come in the near future.

Once we go into production, we can start to publicly invite anyone to mine the pool and we should have our hash rates increase. I know that there are many with sha256 who are just waiting for us to be finished.

I also plan to buy some hashing power from these rig leasing places when we get started to help prop up the hash of the pool for a little while until we get word spreading.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on December 20, 2015, 06:48:45 pm
Status Update

All the mining has now moved to mining.bunkermining.com and is no longer functional on the IP address that was posted here.

The operation caused some downtime due to DNS propagation issues, but it was done within about 30 minutes total.

If you haven't updated your configurations please do so now to resume your testing.

We had some challenges in the switch over. We will continue to monitor the situation and make fixes as needed.


Link http://www.bunkermining.com/dashboard/getstarted
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on December 21, 2015, 01:14:25 am
Fixed an issue with case-sensitivity with miners' BTS 2.0 addresses
Removed the color white from the charts
Added txid to payments log / database
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on December 21, 2015, 12:33:19 pm
we need a little more hash on sha256 I don't think I'm doing anything by myself it sucks cause I sold my antminers s1's and my s2 cause the power to profit was worth it if I still had them they all would be at bunkermining

Feel free to recommend low diff sha256 coins to add to pool as its not producing any blocks with this low hashrate.
is there anyway to forward the hash to nicehash at least this way even if there's only a few ppl hashing on sha but altogether it's still a low hashrate there can still be a payment cause nicehash pays for every accepted share just I thought I'm not a programmer so I don't no if it's a lot of work but if it isn't than even the guys with USB sticks can collect a few bts than when our rate goes up it'll swith to regular coins

Unfortunately this was one of our feature parameters of the contract for the mining pool that will not be fulfilled by freebieserver.

Keep in mind though that we are ONLY TESTING right now. We have not gone into production. We are also only in an early version for the pool that will have many more things to come in the near future.

Once we go into production, we can start to publicly invite anyone to mine the pool and we should have our hash rates increase. I know that there are many with sha256 who are just waiting for us to be finished.

I also plan to buy some hashing power from these rig leasing places when we get started to help prop up the hash of the pool for a little while until we get word spreading.
sounds good I figured that being the pool not really be advertised so there's really not a lot of hash right now once it's ready I'm sure some more ppl with sha rigs will be on I'm just waiting till after the holidays are over than I have plans to retire my rig I have now and get a s7 that I'll run here thanks for the update I'm sure this pool will be a success
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: hybridd on January 05, 2016, 08:14:48 pm
Just a follow up here, while the chart may no longer displaying hashing power, please continue mining as funds are being converted to BTS and everyone is being actively credited. Right now there is a hold up at Poloniex for BTS withdrawals, once that's resolved everything will continue as normal.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on January 10, 2016, 06:38:26 am
Any update on payouts?  Still issues with Poloniex updating their wallet?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: CalabiYau on January 10, 2016, 06:42:05 pm
Any update on payouts?  Still issues with Poloniex updating their wallet?

Last payout received 7 days ago. Meanwhile: 
https://bitshares.openledger.info/?r=cryptofresh#/account/minebts1.bunkermining-com/overview/ (https://bitshares.openledger.info/?r=cryptofresh#/account/minebts1.bunkermining-com/overview/)

Code: [Select]
OPERATION INFO DATE
TRANSFER poloniexwallet sent 1,447.73856 BTS to minebts1.bunkermining-com  16 hours ago
TRANSFER bittrex-deposit sent 1,558.82471 BTS to minebts1.bunkermining-com  20 hours ago
TRANSFER poloniexwallet sent 1,377.22542 BTS to minebts1.bunkermining-com  yesterday
TRANSFER bittrex-deposit sent 1,468.4435 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER bittrex-deposit sent 1,429.97206 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER poloniexwallet sent 1,405.02365 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER poloniexwallet sent 1,619.05827 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 1,562.14475 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER poloniexwallet sent 1,540.8454 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 2,000.88592 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER poloniexwallet sent 1,782.39623 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 1,289.66 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,275.77144 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER bittrex-deposit sent 1,314.46869 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,355.5806 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,314.33094 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,281.04836 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER bittrex-deposit sent 1,466.11368 BTS to minebts1.bunkermining-com  5 days ago
TRANSFER poloniexwallet sent 1,367.57474 BTS to minebts1.bunkermining-com  7 days ago
TRANSFER

Interested in update also.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on January 10, 2016, 06:49:38 pm
Also a website issue.  On the main page the "get started today" link in the center of the screen does nothing.  Link in the upper right works.  Using Firefox 43.0.4.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: kuro112 on January 10, 2016, 07:02:06 pm
Any update on payouts?  Still issues with Poloniex updating their wallet?

Last payout received 7 days ago. Meanwhile: 
https://bitshares.openledger.info/?r=cryptofresh#/account/minebts1.bunkermining-com/overview/ (https://bitshares.openledger.info/?r=cryptofresh#/account/minebts1.bunkermining-com/overview/)

Code: [Select]
OPERATION INFO DATE
TRANSFER poloniexwallet sent 1,447.73856 BTS to minebts1.bunkermining-com  16 hours ago
TRANSFER bittrex-deposit sent 1,558.82471 BTS to minebts1.bunkermining-com  20 hours ago
TRANSFER poloniexwallet sent 1,377.22542 BTS to minebts1.bunkermining-com  yesterday
TRANSFER bittrex-deposit sent 1,468.4435 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER bittrex-deposit sent 1,429.97206 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER poloniexwallet sent 1,405.02365 BTS to minebts1.bunkermining-com  2 days ago
TRANSFER poloniexwallet sent 1,619.05827 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 1,562.14475 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER poloniexwallet sent 1,540.8454 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 2,000.88592 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER poloniexwallet sent 1,782.39623 BTS to minebts1.bunkermining-com  3 days ago
TRANSFER bittrex-deposit sent 1,289.66 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,275.77144 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER bittrex-deposit sent 1,314.46869 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,355.5806 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,314.33094 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER poloniexwallet sent 1,281.04836 BTS to minebts1.bunkermining-com  4 days ago
TRANSFER bittrex-deposit sent 1,466.11368 BTS to minebts1.bunkermining-com  5 days ago
TRANSFER poloniexwallet sent 1,367.57474 BTS to minebts1.bunkermining-com  7 days ago
TRANSFER

Interested in update also.


Polo had disabled the account we used due to the frequency and size of transactions (uwotm8)
we are seeking a solution to this right now and bunker will update when he has a chance.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on January 11, 2016, 02:40:43 pm
Just to update everyone on where things are at.

Our node went out of sync last week and caused some of the payouts over the past 4 days to get backed up. When we got the node back online it was long enough for a payout from what was in the wallet got processed but it was forked. So last night we finally got the node back in sync with the network to be able to access the funds. However, the next payout that occurs would be based on shares mined in the last day instead of the last 4 days. So those that stopped for some reason then would lose their payouts. Not good.

To make matters worse our account was frozen by Poloniex as well at one point for what they called excessive depositing. We are lowering the frequency as they requested and they unfrozen the account.

Given this situation I contacted the developers to get the logs for the payout from the previous day so that we can get the shares at that time and then do a manual payout according to that. I haven't gotten a response to my request yet, so I ask for everyone to be patient as we sort it out. Until then I moved the funds (about 35k bts) out of the payout account to the bunkermining account temporarily.

This event has revealed some parts to the workings of the pool still needs a little more done.

In regards to other development things slowed down during the holidays and things are just starting to ramp up again. Still welcome more feedback on any bugs or issues you may find.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: CalabiYau on January 11, 2016, 03:53:23 pm
Thank you !
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on January 15, 2016, 03:04:11 pm
Any kind of time frame available for when this will be fixed? no payouts this week and no clue if any of the work performed is logged correctly is not making this look good, again. I know there are only a few of us now, but if it doesn't get working for us, then who in their right mind would join up?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on January 17, 2016, 04:33:07 am
Update on the missed half week payout.

I looked into how we could properly assign the payouts only to find out that logging in the custom payout system that was created was not enabled. This means at the end of every payout the shares are reset and there were no logs being kept.

So my hope to payout fairly were dashed at that point. I requested that logs be enabled and they have been, but that doesn't do much for the past.

The only other option I have for some fair distribution would be to have all miners continue to mine as you were and we will add the balance to the bonus payouts. During the course of the week a portion of the balance will then go out according to the shares of the day daily.

I recommend any previous miners who stopped mining to start again over the course of this week to receive that missing balance.

Also in the news, luckily for us, we had already moved away from Cryptsy who now have gone completely bust.

We had some issues with wallets a few days ago due to some versioning issues with dependencies that caused them to crash. We got them back up and running now but we will need to look at how we can better handle that situation efficiently so that it doesn't happen again.

That's all for now. Get your miners going!
Title: Re: Emergency Measure - Temporary Shutdown
Post by: rayday111 on January 28, 2016, 05:56:09 pm
What is the proper format for X11 to mine BROWNIE.PTS?

In looking at users there appears to be a "|" separating the username and asset, but that's not what the instructions say.

So I'm looking for some clarification. Thanks!

You can use either a space or a "|", both are acceptable.

Code: [Select]
        public static char[] AddressDelimiter = new[] { ' ', '|' };

ty!
neither of those delimeter's work for me. Is a "period" acceptable?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on February 15, 2016, 08:52:04 pm
Any updates on the progress of the pool?  I have not seen payouts in a few days.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on February 16, 2016, 03:21:51 am
Any updates on the progress of the pool?  I have not seen payouts in a few days.

Thanks for the inquiry.

Polo disabled markets on one of the coins we were mining and it caused the pool payout system to get locked up.

It's not reinitialized and we are moving trades for that coin (URO) from polo to bittrex.

Things should be running smoothly again and payouts have already been processed.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on March 12, 2016, 02:25:08 am
Can i get som help on mining SHA256 here  :-*
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on March 12, 2016, 03:35:41 pm
Can i get som help on mining SHA256 here  :-*

I put my little machine back on. not much but at least it can do something here since it hasn't been anywhere else.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on March 28, 2016, 08:36:20 pm
New low-diff coin added to SHA256 so come on help mining

http://coinmarketcap.com/currencies/universal-currency/

SHA256
Stratum Address (low var diff): stratum+tcp://mining.bunkermining.com:3337

Stratum Address (norm diff): stratum+tcp://mining.bunkermining.com:3339

Stratum Address (high diff): stratum+tcp://mining.bunkermining.com:3338

Low Vardiff of 8 to 128.

Normal VarDiff of 128 to 8192.

High Vardiff of 8192 to 16394.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: JWF on March 31, 2016, 02:24:42 pm
We are getting blocks, but no payouts yet for the SHA256. Bittrex is showing more than enough volume to have gotten the conversions/sales done.  Is there a certain number of blocks needed to make it worth payout?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: proctologic on April 01, 2016, 10:45:06 pm
We are getting blocks, but no payouts yet for the SHA256. Bittrex is showing more than enough volume to have gotten the conversions/sales done.  Is there a certain number of blocks needed to make it worth payout?

Payout is 100 so wee need to have more hashrate to get pay every day

The volume is fine http://coinmarketcap.com/currencies/universal-currency/
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on April 11, 2016, 12:55:06 am
Everything ok with the payouts?  According to the website, a few payouts are not showing up in the wallet even though they are indicated on the website.

These seem to be skipped:
BTS    brekyrse1f3    1174.62592118    4/6/2016 9:21:35 PM
BTS    brekyrse1f3    312.92976694    4/6/2016 6:47:31 AM
BTS    brekyrse1f3    289.77028151    2/24/2016 10:37:29 AM
BTS    brekyrse1f3    177.43976024    1/10/2016 11:09:19 PM
BTS    brekyrse1f3    77.08215620    1/6/2016 4:21:26 PM
BTS    brekyrse1f3    118.85506832    1/6/2016 6:16:54 AM
BTS    brekyrse1f3    74.32134320    1/4/2016 12:36:19 AM

I need to check the following when I get home, not sure if the "recent history" includes these or not since they are old.  They also do not show up on CryptoFresh.
BTS    brekyrse1f3    137.41309900    12/23/2015 10:57:38 AM
BTS    brekyrse1f3    1064.18212841    12/22/2015 1:04:47 AM
BTS    brekyrse1f3    233.54878255    12/20/2015 6:36:02 PM
BTS    brekyrse1f3    488.44238237    12/19/2015 1:19:23 AM
BTS    brekyrse1f3    765.26706888    12/17/2015 12:41:03 PM
BTS    brekyrse1f3    766.43377861    12/16/2015 10:31:40 AM
BTS    brekyrse1f3    403.46890751    12/15/2015 12:40:40 AM
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on April 11, 2016, 01:09:46 am
Everything ok with the payouts?  According to the website, a few payouts are not showing up in the wallet even though they are indicated on the website.

These seem to be skipped:
BTS    brekyrse1f3    1174.62592118    4/6/2016 9:21:35 PM
BTS    brekyrse1f3    312.92976694    4/6/2016 6:47:31 AM
BTS    brekyrse1f3    289.77028151    2/24/2016 10:37:29 AM
BTS    brekyrse1f3    177.43976024    1/10/2016 11:09:19 PM
BTS    brekyrse1f3    77.08215620    1/6/2016 4:21:26 PM
BTS    brekyrse1f3    118.85506832    1/6/2016 6:16:54 AM
BTS    brekyrse1f3    74.32134320    1/4/2016 12:36:19 AM

I need to check the following when I get home, not sure if the "recent history" includes these or not since they are old.  They also do not show up on CryptoFresh.
BTS    brekyrse1f3    137.41309900    12/23/2015 10:57:38 AM
BTS    brekyrse1f3    1064.18212841    12/22/2015 1:04:47 AM
BTS    brekyrse1f3    233.54878255    12/20/2015 6:36:02 PM
BTS    brekyrse1f3    488.44238237    12/19/2015 1:19:23 AM
BTS    brekyrse1f3    765.26706888    12/17/2015 12:41:03 PM
BTS    brekyrse1f3    766.43377861    12/16/2015 10:31:40 AM
BTS    brekyrse1f3    403.46890751    12/15/2015 12:40:40 AM

This issue has been brought to the attention of the devs.
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: Brekyrself on April 22, 2016, 02:23:29 am
Everything ok with the payouts?  According to the website, a few payouts are not showing up in the wallet even though they are indicated on the website.

These seem to be skipped:
BTS    brekyrse1f3    1174.62592118    4/6/2016 9:21:35 PM
BTS    brekyrse1f3    312.92976694    4/6/2016 6:47:31 AM
BTS    brekyrse1f3    289.77028151    2/24/2016 10:37:29 AM
BTS    brekyrse1f3    177.43976024    1/10/2016 11:09:19 PM
BTS    brekyrse1f3    77.08215620    1/6/2016 4:21:26 PM
BTS    brekyrse1f3    118.85506832    1/6/2016 6:16:54 AM
BTS    brekyrse1f3    74.32134320    1/4/2016 12:36:19 AM

I need to check the following when I get home, not sure if the "recent history" includes these or not since they are old.  They also do not show up on CryptoFresh.
BTS    brekyrse1f3    137.41309900    12/23/2015 10:57:38 AM
BTS    brekyrse1f3    1064.18212841    12/22/2015 1:04:47 AM
BTS    brekyrse1f3    233.54878255    12/20/2015 6:36:02 PM
BTS    brekyrse1f3    488.44238237    12/19/2015 1:19:23 AM
BTS    brekyrse1f3    765.26706888    12/17/2015 12:41:03 PM
BTS    brekyrse1f3    766.43377861    12/16/2015 10:31:40 AM
BTS    brekyrse1f3    403.46890751    12/15/2015 12:40:40 AM

This issue has been brought to the attention of the devs.

Any insight into this?
Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on April 22, 2016, 03:03:55 am
Everything ok with the payouts?  According to the website, a few payouts are not showing up in the wallet even though they are indicated on the website.

These seem to be skipped:
BTS    brekyrse1f3    1174.62592118    4/6/2016 9:21:35 PM
BTS    brekyrse1f3    312.92976694    4/6/2016 6:47:31 AM
BTS    brekyrse1f3    289.77028151    2/24/2016 10:37:29 AM
BTS    brekyrse1f3    177.43976024    1/10/2016 11:09:19 PM
BTS    brekyrse1f3    77.08215620    1/6/2016 4:21:26 PM
BTS    brekyrse1f3    118.85506832    1/6/2016 6:16:54 AM
BTS    brekyrse1f3    74.32134320    1/4/2016 12:36:19 AM

I need to check the following when I get home, not sure if the "recent history" includes these or not since they are old.  They also do not show up on CryptoFresh.
BTS    brekyrse1f3    137.41309900    12/23/2015 10:57:38 AM
BTS    brekyrse1f3    1064.18212841    12/22/2015 1:04:47 AM
BTS    brekyrse1f3    233.54878255    12/20/2015 6:36:02 PM
BTS    brekyrse1f3    488.44238237    12/19/2015 1:19:23 AM
BTS    brekyrse1f3    765.26706888    12/17/2015 12:41:03 PM
BTS    brekyrse1f3    766.43377861    12/16/2015 10:31:40 AM
BTS    brekyrse1f3    403.46890751    12/15/2015 12:40:40 AM

This issue has been brought to the attention of the devs.

Any insight into this?

None yet.. I got acknowledgement from the devs about receiving the issue, but they said they were busy with other things right now. I will press on them again about this.

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: oakmaster on May 02, 2016, 12:19:20 am
I've been buried in work and just realized the pool is down just wondering what's going on

Sent from my SAMSUNG-SM-N900A using Tapatalk

Title: Re: Emergency Measure - Temporary Shutdown of MineBitShares
Post by: BunkerChainLabs-DataSecurityNode on May 02, 2016, 12:56:10 am
I've been buried in work and just realized the pool is down just wondering what's going on

Sent from my SAMSUNG-SM-N900A using Tapatalk

https://bitsharestalk.org/index.php/topic,22299.0.html