There is a lot of content in the Google Doc as well as the private conversation with the senior members of the Kleros team.
Related to #9
Sat 25 Jan 2020 update
Phase 1: User research first so we know exactly what we are doing
Phase 2: Then developing the functionalities
Throughout many discussions, we identified a specific task and genuinely think it is brilliant.
Standardized legal agreements:
web development
mobile app development
video production
podcast production
online marketing services
That’s clever, that can simplify a lot, make it easier to reach an agreement without nitpicking all the clauses.
Note, that working on standardized legal agreements is not working on implementing technical features that have been already identified:
Enhancement 1: no ETH address at hand
Guys meet in real life, shake hands, decided to use Escrow
The receiving person does not have ETH address at hand
That could be for any number of reasons:
Computer / hardware wallet at home, Federico is on 14 hours flight to Argentina
New to crypto, need to create a wallet. Funds are already in escrow, can start working now, it will take 3 days for a business partner who is more into crypto to configure the receiving address.
It’s sizeable money, no longer Metamask, a new Trezor ordered from Amazon
Enhancement 2: Privacy flow IMPORTANT
Encrypting and publishing encrypted?
Publishing hash?
Back-and-worth. What is the exact flow of information?
Similar stuff. I can definitely research and deliver standardized legal agreements!
There is a lot of content in the Google Doc as well as the private conversation with the senior members of the Kleros team.
Related to #9
Throughout many discussions, we identified a specific task and genuinely think it is brilliant.
Standardized legal agreements:
Note, that working on standardized legal agreements is not working on implementing technical features that have been already identified:
Similar stuff. I can definitely research and deliver standardized legal agreements!