Today we could not be more excited to be shipping Deliverable 3.2 to the community and @ZcashGrants. With this delivery, we complete Milestone 3 for the project.
“Implementation of security best practices to protect ZavaX Oracle subnet, and a report posted to the forum describing our penetration tester’s attempt to stop the ZavaX Oracle subnet from operating.”
This was a cumbersome but necessary deliverable in preparation for deploying a bridge that is both secure and robust. We split the three node ZavaX Oracle network across eight different servers, each with its own role and its own layers of protection. We then performed penetration testing on all servers and adjusted their configuration accordingly until all tests passed. Please see these notes which describe the new platform configuration in detail, and please see this report for the results of our penetration testing.
In other news, we are transitioning away from the name ZavaX to red·bridge. We had wanted to retain ZavaX in addition to red·bridge, but this has proved to be confusing to just about everyone we’ve talked to about the project outside of the Zcash community. Launching a new product is challenging enough without added confusion. We are also changing the staking token ticker from ZAX to RBR. Amazingly, no project has ever used those three letters before!
So the last time you will see “ZavaX” used is with this ZavaX Oracle testnet. Thank you for your service, ZavaX! 
As Josh says, onwards!
Kit