One of the biggest benefits of Tabby Rewards is the ability to mass distribute your tokens in unique and exciting ways. Similar to coupon codes, there are dozens of effective ways to incentivize users.

However, as we’ve talked about before , there are a number of hurdles that we need to overcome before we can deliver a product that will perform at scale.

Over the course of the next few weeks we’ll dive into some of these challenges in a bit more detail, as well as solicit feedback from our community that could help us prioritize which problems we tackle first.

It should be noted that we’re also exploring potential partnerships that may result in a collaborative development effort, in order to build more innovative products that reach a wider audience.

We’ve been particularly quiet on this front, as things are still in the exploratory phase and nothing has been confirmed yet, but we’re hoping to have more info that we can share publicly in the months ahead.

Dev Notes

A few quick notes about what went on behind the scenes this week.

🐞 Bug Fixes:

+ race condition where fee would be used before fetched

+ token balance/allowance fetching fixed for subsequent payments

+ loading indicator when changing accounts

+ form state properly resets between submissions

+ token authorization + send payment modals race condition 💻 App Tweaks:

+ prevent wrapping of statuses in payment list

+ reduced font size for payment list

+ padding has been made consistent in several places

+ amounts are now truncated to a fixed number of decimal places

+ background image on account bar

+ only show scrollbar on tx data when it's required 👉 Internal:

+ async derived field calculations

+ demo environment setup and deployed

That’s it for this week! If you have any questions, be sure to join our Discord channel, tweet to us on Twitter or chime in on the /r/BlockCAT subreddit!