Community Update — September 7, 2018

We share some customer feedback from Tabby Pay 2.0. 🔨

Recently, we announced the release of Tabby Pay 2.0 into open beta. For the past two weeks, we’ve been working with both new and existing users to learn more about their experience with our app, squash bugs, and flag potential areas for improvement.

Feedback + Suggestions

Easily Purchase ETH/CAT

One user mentioned that it might be useful to include in-app links to easily purchase ETH/CAT from an exchange. We agree, and we’ve flagged this for improvement in the future.

Easily Purchase Hardware Wallets

Similarly, we show that you can use hardware wallets, but we don’t currently offer any way to purchase them. We’ve flagged this as an area for improvement in the future.

Address Book

Another suggestion was for the integration of an Address Book. This would allow users to associate names with Ethereum addresses for quick access. The main security considerations here are related to preventing errors. It follows then, that the integration of an Address Book would also have to be security conscious (i.e., ensure that a transaction was successfully completed and the address was correct before storage).

This feature was actually already in our road map. There are some logistical pieces that need to be worked out before we can integrate this into our platform.

Improved UX

We are happy to report that several users confirmed that our improved UX is much more approachable, especially for beginners and inexperienced crypto. users.

We are excited about these iterations and have added them to our roadmap, but our next steps will be releasing Pay 2.0 and prioritizing Rewards.

Tabby Rewards

The work done on Tabby Rewards continues to evolve positively with our improved smart contract. If you recall, we talked about some of the challenges presented with the Tabby Rewards contract in our Community Update on July 20th.

After some exhaustive brain-storming sessions, the development team managed to come up with some solutions to the scalability problem we were facing.

However, the implementation of these solutions requires a total reconstruction of the foundational piece of the contract, which of course takes time. We are currently working on the implementation details and hope to have a functional smart contract in the coming weeks. Rewards is our primary focus at the moment.

Dev Notes

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

💻 Feature Development:
+ further development on new gas-tolerant Tabby Rewards contract integration.
+ continued work on security review/testing/requirements for new Tabby Rewards contract.
👉 Internal:
+ conducted focus group test with inexperienced users & integrated minor tweaks to work flow accordingly.
+ final security review/testing/audit of new Tabby Pay contract.
+ reliability and auditability revisions to reusable smart contract components.

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!

Like what you read? Give BlockCAT a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.