**SafeMath** Eschews SafeMath in favour of considered arithmetic. *Please check all arithmetic*. Internal state only manipulates numbers based on blocktime and Ether quantity burnt from users, neither of which can overflow 1e256-1.
**addExcluded()** There is a special function called addExcluded(), however it costs 1024 Vether to call. It is intended to use this function to exclude future Vether-based smart contracts from charging the transfer fee of 10 basis points. Since anyone can call this function to exlude themselves from paying transfer fees, it is likely that only high-volume addresses that move more than 1m Vether per year will call this function since it makes no sense to burn 1024 Vether to save anything less than that.
**Code brevity** The code is intended to be easily read with trailing comments, but also favours brevity.
**addRegistry** The smart contract has the addRegistry() function commented out since it causes an attack vector. This will be removed in entirety soon. There is reason to instead add a function called removeRegistry() with a fee of 2048 Vether that allows the contract to remove UniSwap and DefSwap in future if they are ever exploited.
## DApp UI The DApp is live on the URL above. Please feel free to interact with the contract. It uses React + AntD. There is room for improvement and further features.
This client allows users to "set-and-forget" mine the contract by sending a small amount of Ether every day into the contract. It is imagined those who mine the contract will be the bidders-of-last-resort establishing a cost-floor for Vether. The mining-client has support for BIP39 derived addresses, and can mine for a "cold-wallet".
The mining client can be run locally or deployed to an online server (Heroku) for un-interrupted mining. Instructions are provided.
## Next steps Please scrutinise the code and help perform more analysis in the implementation. Pull requests are welcome.
If all goes accordingly, Vether will be deployed on mainnet on 12 May 2020.