Author Topic: Emergency Measure - Temporary Shutdown of MineBitShares  (Read 32260 times)

0 Members and 1 Guest are viewing this topic.

Offline hybridd

  • Full Member
  • ***
  • Posts: 164
    • View Profile
  • BitShares: hybr1d
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)
http://sharebits.io - #sharebits "person" amount asset - Start tipping on bitsharestalk today!
Developer @ Freebie

Offline BunkerChainLabs-DataSecurityNode

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!
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline BunkerChainLabs-DataSecurityNode

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!
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline hybridd

  • Full Member
  • ***
  • Posts: 164
    • View Profile
  • BitShares: hybr1d
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.
« Last Edit: December 10, 2015, 12:12:42 am by hybridd »
http://sharebits.io - #sharebits "person" amount asset - Start tipping on bitsharestalk today!
Developer @ Freebie

Offline CalabiYau

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.

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
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.

Offline BunkerChainLabs-DataSecurityNode

What's up with X11?

Sorry can you be more specific? What kind of issue are you having with x11?
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile

Offline BunkerChainLabs-DataSecurityNode

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.
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline hybridd

  • Full Member
  • ***
  • Posts: 164
    • View Profile
  • BitShares: hybr1d
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
http://sharebits.io - #sharebits "person" amount asset - Start tipping on bitsharestalk today!
Developer @ Freebie

Offline proctologic

  • Full Member
  • ***
  • Posts: 58
    • View Profile
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

Offline abad812

  • Newbie
  • *
  • Posts: 11
    • View Profile
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.

Offline Brekyrself

  • Hero Member
  • *****
  • Posts: 511
    • View Profile
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?

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
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"...

Offline proctologic

  • Full Member
  • ***
  • Posts: 58
    • View Profile
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
« Last Edit: December 08, 2015, 02:56:54 am by proctologic »