Community Update — June 22, 2018
We’re releasing a versioning tool via an abstraction layer. ⚙️
This week we’re covering a critical piece of infrastructure for our products; an abstraction layer that will help with continuous contract versioning.
One of the innovative pieces that we’ll be releasing soon is an abstraction layer for our smart contracts.
In order to add new features and fix bugs in our smart contracts, it’s necessary for us to implement a strategy that supports contract versioning.
With this abstraction layer, we can continually release new deployments of our smart contracts, while keeping the old versions still in service.
This means that any newly created payments will exist in the latest version, while any existing payments will remain untouched and active in the older contracts.
Our web interface seamlessly connects you to the appropriate smart contract, allowing the entire process to happen without any additional effort from the user.
This process ensures that we can elegantly phase out older versions of the contract with minimal cost, all while keeping up with the latest techniques in smart contract construction and security.
A few quick notes about what went on behind the scenes this week.
💳 Tabby Pay
+ wrapped up sending tokens functionality
+ integrated all of contract v2's changes
+ integrating pay fees with CAT
🎁 Tabby Rewards
+ finalizing redeem reward
+ optimized contract to allow for more rewards per campaign
+ adding a global blockchain transaction tracking system
+ optimizing event fetching from contracts