Gotta a few hours to spare and added support for the [Open Standard for a HIVE Account Referral System](https://peakd.com/hive/@hiveonboard/open-standard-for-a-hive-account-referral-system) to the Condenser frontend which is currently used on https://hive.blog as many of you know.

![badge_developingonhive_dark_240.png](https://files.peakd.com/file/peakd-hive/roomservice/ZzYoHWaX-badge_developing-on-hive_dark_240.png)

Since these changes are not live yet and the repository owner has to decide if to accept the merge request or not - I would love to give you an overview about the changes.

Link to Merge Request: https://gitlab.syncad.com/hive/condenser/-/merge_requests/70

---
#### Default Beneficiaries For Referred Accounts
When a new account, which was referred before creates a post, the suggested beneficiaries will be default settings now. For all other accounts, nothing will change.

![image.png](https://files.peakd.com/file/peakd-hive/roomservice/O4tVd282-image.png)

In this sample the following `json_metadata` where set for the new referred account:
````
{
   "beneficiaries": [
      {
         "name":"roomservice",
         "weight":300,
         "label":"referrer"
      },
      {
         "name":"tipu",
         "weight":100,
         "label":"creator"
      },
      {
         "name":"hiveonboard",
         "weight":100,
         "label":"provider"
      }
   ]
}
````
These values are now set as default when creating a post.
![image.png](https://files.peakd.com/file/peakd-hive/roomservice/5ADgTlmh-image.png)

#### Abuse Prevention

I've added some additional rules for the beneficiaries in order to be accepted on condenser:
* Maximum `weight` for `referrer` = 300
* Maximum `weight` for `creator` = 100
* Maximum `weight` for `provider` = 100

If anyone creates an account with higher fees than this, it won't be accepted and not set as a beneficiary.

#### Opt-Out Option
As a requirement of the Open Standard everyone who was referred by this system, has a choice to opt-out.
I've added such an option to the Preferences where it can be changed at any time.

![image.png](https://files.peakd.com/file/peakd-hive/roomservice/74ySAgBC-image.png)

#### Test Run
In order to test everything out, I've created a new account @referral-tester where you can inspect all the stuff, which has happened on the chain.

**Reference User:** https://hiveblocks.com/@referral-tester

**Post with *Referral System* enabled:**
https://hive.blog/testing/@referral-tester/test-post-for-open-standard-for-a-hive-account-referral-system
![image.png](https://files.peakd.com/file/peakd-hive/roomservice/7piqMIXq-image.png)

**Post with *Referral System* disabled:**
http://localhost:8080/testing/@referral-tester/45keom-test-post-for-open-standard-for-a-hive-account-referral-system
![image.png](https://files.peakd.com/file/peakd-hive/roomservice/t2CMIgp7-image.png)

#### 200 HIVE Bounty for the first dApp Adoption still available
As mentioned in my [last post](https://peakd.com/hive/@hiveonboard/feature-update-hive-referral-tracker) I put a 200 HIVE bounty up to the first dApp which integrates the *Open Standard for a HIVE Account Referral System*. Since it makes no sense to send funds to myself, the bounty is still in place, even if this merge request will be accepted.

#### Looking Forward
If the Merge Request would be accepted it would be a great success for evolving the Referral System and will create incentives for everybody to onboard new people to HIVE!


---
**This is @roomservice and when you like my work, I would be glad to be your witness: [Vote here](https://vote.hive.uno/@roomservice)**