New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for implementing referral program #295

Closed
chiliec opened this Issue Nov 21, 2017 · 39 comments

Comments

Projects
None yet
@chiliec
Copy link

chiliec commented Nov 21, 2017

In our blockchain already exists field "recovery_account" for accounts. It referrer, who invited and registered this account. My proposal is to add some small reward to creator for the actions (supervising and writing posts) of referral. Like in app beneficiaries #285, but for people who registered other people.
Registration of other people will be profitable and there is no need to sponsor registrations anymore.
Referrers will verify referrals and teach them how platform works, because they are interested in the success of their referrals.
What do you think?

@asuleymanov

This comment has been minimized.

Copy link

asuleymanov commented Nov 22, 2017

Идея конечно хороша.
Но зачем это вносить в БЧ в жестком виде. Ведь будет "app beneficiaries" можно будет сделать свой сайт и с него пусть публикуют статьи. Как это делают многие сайты в STEEM.

@chiliec

This comment has been minimized.

Copy link

chiliec commented Nov 22, 2017

Because as an ordinary abstract user, not a developer, I want to invite my friends easily and not force them to go through a strong and paid(?) sms-registration in our official client. And I don't want to do it at my own expense, of course.

@asuleymanov

This comment has been minimized.

Copy link

asuleymanov commented Nov 22, 2017

Ничего не помешает приделать регистрацию на своем сайте.

@chiliec

This comment has been minimized.

Copy link

chiliec commented Nov 22, 2017

I'm an average user, I don't have my own site 👶

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

This issue is a blocker for third-party apps developers on Golos, assuming they want their projects to really scale, and let me explain you why.

Registering let's say 100 000 users is impossible for app developers, because it is simply too expensive in general. You need to pay a user registration fee + pay for a marketing campaign. At the same time, it is unprofitable on per user basis as the conversion rate of active out of registered accounts is too low on Golos. The delegation of power does not solve the problem, as most of the registered accounts are going to be inactive and won't be able to earn back the delegated amount.

Also it's much easier for 10 000 people to market the product to 10 friends each than for one app developer to sell it to 100 000 users, because it's much easier to explain the features of the project to people that you already know.

It does not make sense to implement this feature on the app level, because user can simply change the client after it registered the account in the blockchain for a user, which makes it even more unprofitable for app devs to develop this feature, so it should be implemented on the protocol level.

Personally, I'm a Golos investor and I made my investment decision based on the Golos White Paper https://golos.io/ru--golos/@golos/golos-russkoyazychnaya-socialno-mediinaya-blokchein-platforma, which more than a year ago perfectly described the Motivation of Registrators feature and stated that it is in scope of the development. So I expect this feature to be implemented as I already paid for it.

@asuleymanov

This comment has been minimized.

Copy link

asuleymanov commented Nov 27, 2017

Погодите вы же можете отозвать обратно делегированные голоса.
Тут думаю проблем нет. Просто в своем приложении проверять активность и по каким то условиям отзывать делегированные голоса для зарегистрированных пользователей.

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

Withdrawing delegated power is equal to blocking a user account as if they did something wrong. When users register on Facebook, Twitter or Instagram, they expect to be able to reuse their account a month or a year later without necessarily doing any job for it. If you want users to switch to Golos-based apps you should provide at least the same level of service.

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

Also, not sure if that's the same on Golos, but on Steem you have to borrow 6 times more for the account created with delegated power than for the usual one, which is still another financial burden for app developers.

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

There are still just dozens of app developers on Golos compared to thousands of active users. If you don't let people invite other people for some tip, profit sharing or gift, like on AirBnB and other services, the project won't get viral.

@asuleymanov

This comment has been minimized.

Copy link

asuleymanov commented Nov 27, 2017

Withdrawing delegated power is equal to blocking a user account as if they did something wrong. When users register on Facebook, Twitter or Instagram, they expect to be able to reuse their account a month or a year later without necessarily doing any job for it. If you want users to switch to Golos-based apps you should provide at least the same level of service.

Насколько я понимаю если Вы отзовете делегированные голоса то при этом не происходит блокировка аккаунта. Просто пользователь не сможет голосовать при следующем входе. Я это так понимаю.

Also, not sure if that's the same on Golos, but on Steem you have to borrow 6 times more for the account created with delegated power than for the usual one, which is still another financial burden for app developers.

Ну тут да. Бремя конечно. Но ведь можно регистрировать при условии отзыва делегированных голосов к примеру через 1 неделю.

There are still just dozens of app developers on Golos compared to thousands of active users. If you don't let people invite other people for some tip, profit sharing or gift, like on AirBnB and other services, the project won't get viral.

Так погодите никто не мешает Вам как разработчику давать какие нибудь подарки пользователям которые зарегистрировались из Вашего приложения. Тут никакой механики от системы GOLOS не предусмотрено.

Вообще первоначально разговор шел о том чтобы пользователь или приложение который регистрирует другого пользователя, получал какую нибудь выгоду от этого, а не чтобы зарегистрированный пользователь что то получал.
Просто сейчас если Вы кого нибудь регистрируете, вернуть свои затраты можно только при условии договоренности о возврате потраченных средств. Вот как раз делегирование это может решить.

А товарищ @chiliec предлагал сделать автоматическое бенефициарство для пользователей которых регистрируют. Я понял его вопрос именно так.

@chiliec

This comment has been minimized.

Copy link

chiliec commented Nov 27, 2017

There are still just dozens of app developers on Golos compared to thousands of active users. If you don't let people invite other people for some tip, profit sharing or gift, like on AirBnB and other services, the project won't get viral.

Exactly! If people will be able to invite other people for some benefits, they become bellman and themselves will explain and take care of invite only active users. People will be the drivers of blockchain growth, not only developers.

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

Насколько я понимаю если Вы отзовете делегированные голоса то при этом не происходит блокировка аккаунта. Просто пользователь не сможет голосовать при следующем входе. Я это так понимаю.

User won't be able to use the most part of the functionality of the app, which is equal to enforced account blocking.

Ну тут да. Бремя конечно. Но ведь можно регистрировать при условии отзыва делегированных голосов к примеру через 1 неделю.

I'm not saying it is technically impossible to withdraw the power in 1 week, I'm saying that delegation feature is meaningless for me as an app developer as it does NOT solve my problems with user registration and project scaling. 95% of social network users won't accept those 1 week "conditions" and will just stay on Facebook or Instagram. Unless you implement this feature #295, of course.

Так погодите никто не мешает Вам как разработчику давать какие нибудь подарки пользователям которые зарегистрировались из Вашего приложения. Тут никакой механики от системы GOLOS не предусмотрено.

I don't want to reward users for the registrations. I want protocol to be able to reward registrators (users that registered other users). As I've mentioned earlier, that mechanics IS stipulated as it is written in Golos Whitepaper, which I believe you carefully follow during your daily development routine.

Вообще первоначально разговор шел о том чтобы пользователь или приложение который регистрирует другого пользователя, получал какую нибудь выгоду от этого, а не чтобы зарегистрированный пользователь что то получал.

Registrators should be beneficiaries of registered users actions at least for some period of time. That's exactly what I mean.

Просто сейчас если Вы кого нибудь регистрируете, вернуть свои затраты можно только при условии договоренности о возврате потраченных средств. Вот как раз делегирование это может решить.

А товарищ @chiliec предлагал сделать автоматическое бенефициарство для пользователей которых регистрируют. Я понял его вопрос именно так.

Exactly! The user that was registered by other user (registrator) should share some reward with the registrator, and that should be implemented on the protocol level, so that no matter what client the registered user is using, the registrator gets beneficiary reward.

@chiliec

This comment has been minimized.

Copy link

chiliec commented Nov 27, 2017

it is written in Golos Whitepaper, which I believe you carefully follow during your daily development routine.

Unfortunately, @asuleymanov not a member of "Golos team" and not develop chain core.
We must call @nemo1369 @AKorpusenko @kotbegemot @jevgenika @alex-firsov @dankinescop @pavelit
and other decision-makers @serejandmyself @21xhipster @litvintech
and just active users @vikxx @On1x @gropox @primusd @vadbars @vista7 @VIM-Arcange @tomarcafe @b1acksun @litrbooh for discussion.

@nemo1369 nemo1369 added this to the 0.2.0 milestone Nov 27, 2017

@nemo1369 nemo1369 self-assigned this Nov 27, 2017

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 27, 2017

@asuleymanov Sorry for misunderstanding. I thought you're a Golos core team member.

@asuleymanov

This comment has been minimized.

Copy link

asuleymanov commented Nov 28, 2017

Ну я вообщем то скажем так не до участник. Так делегат среднего пошиба.
Я все таки понял вашу идею и поддержу её. Но думаю если будут делать как Вы предложили.
А именно чтобы было принудительное бенефициарство для зарегистрированных пользователей.
То стоит все таки как нибудь это ограничить.

Как предложение:

  1. Сделать чтобы такое принудительное бенефициарство было только на 1-2 месяца.
  2. Сделать чтобы такое принудительное бенефициарство было до того момента пока вложенные в регистрацию пользователя затраты либо удвоились либо утроились.

Просто на постоянной основе не вижу смысла. Хотя это всего лишь мое мнение.

@pmartynov

This comment has been minimized.

Copy link

pmartynov commented Nov 28, 2017

@asuleymanov, totally agree.

It should be either limited in time for let's say 3-6 months, or should be limited with the amount of earnings proportional to the registration fee x3-x5, or both.

The case with some insignificant amount like 0.1%-0.5% of rewards for the lifetime might also be considered.

@gropox

This comment has been minimized.

Copy link

gropox commented Nov 28, 2017

It should be possible to ransom self free after some period of time. At costs paid by referrer

@kotbegemot kotbegemot modified the milestones: 0.2.0, 0.2.2 Dec 1, 2017

@kotbegemot kotbegemot added this to BackLog in GolosCoreOLD Dec 4, 2017

@chiliec

This comment has been minimized.

Copy link

chiliec commented Dec 4, 2017

Сan limited with reference to the value of karma.

@alex-firsov

This comment has been minimized.

Copy link

alex-firsov commented Dec 6, 2017

Запущен конкурс идей для реферальной программы — https://golos.io/golosio/@golosio/konkurs-idei-dlya-referalnoi-programm.

@AntonBliznets

This comment has been minimized.

Copy link

AntonBliznets commented Mar 4, 2018

@kotbegemot kotbegemot removed the enhancement label Mar 11, 2018

@kotbegemot kotbegemot removed this from the 0.2.2 milestone Mar 12, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

maslenitsa93 added a commit that referenced this issue Aug 24, 2018

afalaleev added a commit that referenced this issue Aug 24, 2018

Merge pull request #939 from GolosChain/295-chain-propertie
Fix naming in chain_properties_19 #295

maslenitsa93 added a commit that referenced this issue Aug 26, 2018

maslenitsa93 added a commit that referenced this issue Aug 27, 2018

maslenitsa93 added a commit that referenced this issue Aug 27, 2018

maslenitsa93 added a commit that referenced this issue Aug 28, 2018

maslenitsa93 added a commit that referenced this issue Aug 28, 2018

maslenitsa93 added a commit that referenced this issue Aug 28, 2018

maslenitsa93 added a commit that referenced this issue Aug 29, 2018

maslenitsa93 added a commit that referenced this issue Aug 29, 2018

maslenitsa93 added a commit that referenced this issue Aug 31, 2018

maslenitsa93 added a commit that referenced this issue Aug 31, 2018

maslenitsa93 added a commit that referenced this issue Sep 3, 2018

maslenitsa93 added a commit that referenced this issue Sep 4, 2018

maslenitsa93 added a commit that referenced this issue Sep 4, 2018

maslenitsa93 added a commit that referenced this issue Sep 5, 2018

maslenitsa93 added a commit that referenced this issue Sep 11, 2018

maslenitsa93 added a commit that referenced this issue Sep 11, 2018

afalaleev added a commit that referenced this issue Sep 11, 2018

AKorpusenko added a commit that referenced this issue Sep 18, 2018

Added votable auction window. Added returning of auction rewards to r…
…eward poll. #898

Merge pull request #937 from GolosChain/golos-v0.18.4

Golos v0.18.4
Add chain_properties_19 #295

Merge pull request #938 from GolosChain/295-referral-program

chain_properties_19 #295
Made auction window votable. Fixed rewards calculations. #898

Merge branch 'master' into golos-v0.19.0

Fix naming in chain_properties_19 #295

Merge pull request #939 from GolosChain/295-chain-propertie

Fix naming in chain_properties_19 #295
Updated with current 19.0

Added auction_window_size to wallet update_chain_properties. #898

Fixed some codestyle errors. Changed auction_window_weight to uint128_t. #898

Added HF19 checks. Fixed auction_window_size in update_chain_properties. #898

Added auction_window_max_size constant to config. Added HF19 checks in steem_evaluator. #898

Fixed some comment reward logic in tests. #898

Referral program, ASSERT_REQ_HF improved, HF 19 #295

Merge pull request #942 from GolosChain/295-referral-program-impl2

Referral program implemented #295
Update with current 19.0. #898

Fixed auction window tokens return to reward fund. #898

Renamed modify reward fund function. #898

@afalaleev afalaleev closed this Nov 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment