Author Topic: Losing Sign-Ups thanks to a sneak deal between UI Worker and Foundation  (Read 2400 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Reasoning for this deal was the proposal to separated the reference client from open ledger and make a referral reward for the bitshares community instead of subsidizing a 3rd party with the reference wallet. I personally would have preferred to use 100% referral reward, however, account creation costs money - thus the referral reward was set to 60% (that leaves 40% of the reward to the faucet).
The proxy was an error in the settings - I appologize for that - it shouldn't have been set for the reference wallet.

The BBF is now in the making of a formally voted worker that will also fund community owned public API nodes. More on this next week.

Offline Ravid

  • Full Member
  • ***
  • Posts: 84
    • View Profile
So? Did they reach out to you? It's a pretty serious accusation - meddling with settings/code like that without anyone's approval.

Offline fav

  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Nice catch @fav

Is there any way to find out approximately how long this has been happening, and how many referred users were sent?

they reversed it this morning, still waiting for a public statement though.

so it was up for ~24hrs, no way to tell how many users left the sign-up. at least 2 people joined our help channel asking why they can't sign-up (via my ref link)

Offline intelliguy

Nice catch @fav

Is there any way to find out approximately how long this has been happening, and how many referred users were sent?
I'm @intelliguy on steemit. I usually get things right (or so they tell me), follow me there if you want to see more. Tips accepted to bitshares user: intelliguy-bts  (I'm a lifetime member because I trust in the Bitshares ecosystem)

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline fav

  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
additionally.

- only 40% instead of 60% for affiliates

- voter bias, setting default proxy to bisthareseurope

see: http://cryptofresh.com/u/zardo3

Offline fav

  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
yup, this is absolutely inacceptable, here's the story:

by changing to wallet.bitshares.org I decided to test the referral program - did not work so I opened an issue on github.

https://github.com/bitshares/bitshares-ui/issues/677

> https://github.com/bitshares/bitshares-ui/issues/677#issuecomment-341145204

this comment by @svk got me curious, because the default faucet used to be openledger.

so I checked bitshares.org/wallet first if ref is working (no)


Quote
btsfav commented 18 minutes ago
bitshares.org/wallet referral doesn't work either, are you guys kidding me?

@svk31 @wmbutler this is not acceptable, please test this stuff first before you change. ALL ref links are worthless now.

I then went to check the source code, searched for bitshares.eu, and yup. they changed the default registrar to their faucet, it seems.

opened another issue:

Who decided to change the default faucet and why? https://github.com/bitshares/bitshares-ui/issues/683

Quote
btsfav commented 13 minutes ago
Who made the decision to ninja change the default registrar faucet (which is not even working) and why?

Let me remind you that openledger offers tons of access nodes, they fully deserve to be the default faucet.

also, I HOPE whoever made this decision checked with bitshares.eu that they disable the "default proxy" setting, or else you'll commit to voter bias in the reference client.

This all smells like a dirty backhand deal between Worker UI and Bitshares "Foundation".

I expect full transparency and responsibility by @wmbutler and @xeroc