-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Appeal key" #65
Comments
The appeal key is one, the client sets it while creating the deal. |
A variation to this would be having an admin key see #66, which doesn’t affect the idea of the appeal key |
@turinglabsorg should we call this keys or addresses? And what’s the difference in your opinion? |
@0xjona for me it's an appeal address, addresses are hashed version of keys. They're comparable but not exactly the same. In any case it's an address allowed to make transactions. |
Ok to call it a appeal address. The appeal addresses should be a list of keys and it should contain all keys that the client picks at deal creation. We don't have to force the deal creator key to be in the appeal address. Imagine preparers that resell this product to other people which do not want to include themselves. |
So it's a list? In our first iteration we said it should be just one address, it's pretty the same for me, just need to understand if it's an array of addresses or a single address. We must be sure there's at least one appeal address or not? |
(hackMD updated) |
We want to allow others to be able to create appeal for a deal created by the client X.
We decided that we can implement this by modifying the "create proposal" function.
In the new version the client can specify another address (different form the default that is the client address) that can send an on-chain message to create an appeal.
The text was updated successfully, but these errors were encountered: