likwid 2nd layer beneficiary for dapps

We are excited to announce a new likwid feature targeted at dApps.

Intro

Vested reward (SteemPower) is often a liability for businesses. The option of inmediate liquid rewards has many potential applications. There is however a limitation in how the beneficiary STEEM-native feature can be exploited.

This new feature is an application-based beneficiary abstraction layer that allows dApps to keep their beneficiary scheme while using likwid.

Under normal circumstances, likwid needs to be set as beneficiary for a given dApp-powered post. However, a problem arises for dApps which operate on a "traditional beneficiary monetisation model"; likwid utilisation would clash with it.

Now with the implementation of a custom_json operation during post signing likwid will follow the beneficiary pattern specified at this very json document.

Traditional monetisation model with beneficiaries diagram

New likwid proposal diagram

Benefits

Startups sometimes struggle in competitive enviroments rewarding their customers in a timely manner. We help professionals reward their customers at a more appealing pace.

Basically, dApps can now pay their customers in cash (100% liquid) instantly at payout time while keeping their usual beneficiary distribution.

Setup and configuration

The beneficiary proxy will be read from a custom_json container.

Official STEEM custom_json documentation

All you need to do is appending a custom_json operation within the same transaction where the comment operation is included

[ "custom_json", { "required_auths": [], "required_posting_auths": ["example_account"], "id": "likwid-beneficiary", "json": "{ "id": "likwid-beneficiary", "beneficiaries":[["customerA", 9000], ["example_account",1000]] }" } ]

idand beneficiariesfields are mandatory

Credits

Contact & help

Find us on Steemium Discord under #likwid channel.

For more information on Hive account@likwid check out our announcement post.

likwid 2nd layer beneficiary for dapps