2018-06-26 Meeting note: RHOC/REV - contract findings

Date

26 Jun 2018

Attendees

Goals

The purpose of this meeting is to discuss Dave's findings of RHOC held in contracts and consider next steps to help assure people are successful with the swap. David's findings are at https://gist.github.com/desaperados/98e4cf3d8c2fcefd4b6d7a5a3cb856a6

Discussion items

Item	Notes
Resources	David's findings are at https://gist.github.com/desaperados/98e4cf3d8c2fcefd4b6d7a5a3cb856a6
Review of findings	Amounts are incorrect in the gist in the balances. This is less important than having the number of contracts holding RHOC. https://github.com/makerdao/vulcan0x
How the software works	https://github.com/makerdao/vulcan0x Its a generic ERC20 cache Schema Collection of transaction data Collection of account state It's a docker stack that is easy to stand up and operate It is a full Ethereum node
Discusion about selecting the block height for swap (timestamp project)	We need a way to estimate the block height leading up to the freeze before the swap This needs to be communicated to exchanges to encourage them to freeze trading Needs to be somewhat ambiguous to protect from phishing scams Metaphor - like a count down clock Concern - long strings of zeros may cause confusion We need to leave enough room so that if things roll over, we're not committing to a bit that could roll over We want to avoid deploying software as a service to mitigate liability risks We need a script that given a date, picks a block height that we can publish bit by bit The cache solution has a few layers between script and truth of the Ethereum blockchain This may not support the solution to this need Can we do a fuzzy countdown clock? Count down each time an Ethereum block passes? It should suffice to publish a range "after this block, and before that block" A shrinking bullseye
Next steps	Idea to stand up the code on a machine owned by the Coop or share via API Recommendation to provide the code for people to use if they want to explore the blockchain in a similar way. We want to avoid standing up infrastructure that others might misconstrue Reduces liability to the Coop Idea - consider language for the RHOC/REV page to encourage exchanges to do right by their customers and tips for RHOC holders who use exchanges

Action items

Nash Foster by July 2 to review the software to better understand if and how it could be used
David to review the software to assure usability