status-im/swarms
2
0
Fork 0
mirror of https://github.com/status-im/swarms.git synced 2025-02-12 18:06:24 +00:00
Code Issues Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Nabil N 2019-02-04 08:09:05 -05:00 committed by GitHub
parent 40d5df51e1
commit 99679270c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
ideas/314-tribute-to-talk/README.md
View File

@ -11,9 +11,9 @@ contributors:
- Richard - Richard
- Rachel - Rachel
budget: budget:
- actual: xxx - actual: $32k
- estimate: yyy - estimate: yyy
- currency: ETH - currency: USD
--- ---
@ -88,12 +88,27 @@ Changes to the smart contract may be required in order to meet specs defined in
- First version of UI is complete and design reviewed - First version of UI is complete and design reviewed
- Changes required here: https://github.com/status-im/status-react/pull/7304#issuecomment-459337181 - Changes required here: https://github.com/status-im/status-react/pull/7304#issuecomment-459337181
**Update 7/1/19**<br> **7/1/19**
*Top line: The Tribute to Talk MVP will deliver 1:1 spam prevention. The contract will manage tribute settings only. There will be no escrow; payment will be handled through a normal SNT transaction. There are constraints that force this decision, but it's also the simplest possible implementation.* *Top line: The Tribute to Talk MVP will deliver 1:1 spam prevention. The contract will manage tribute settings only. There will be no escrow; payment will be handled through a normal SNT transaction. There are constraints that force this decision, but it's also the simplest possible implementation.*
User A = Person sending tribute<br> User A = Person sending tribute<br>
User B = Person accepting/rejecting chat request User B = Person accepting/rejecting chat request
**21/1/19**
- Design review complete
- Product spec complete
- Includes contract functional requirements, migration strategy & risk assessment
- UI implementation in progress
- Tangential—contact list w/ “remove contact” WIP
**4/2/19**
- Settings UI design reviewed
- Changes required
[Eric] [Eric]
So far we have discussed 2 different options: So far we have discussed 2 different options:
- contract 1 is a very simple contract that is only used as a index of tributes required to contact users. The tribute is payed with a regular transaction which is slightly better for privacy but requires A to pay before talking to B without an escrow. I don't think there would be a need for a security audit for this one because the contract itself doesn't handle any value. - contract 1 is a very simple contract that is only used as a index of tributes required to contact users. The tribute is payed with a regular transaction which is slightly better for privacy but requires A to pay before talking to B without an escrow. I don't think there would be a need for a security audit for this one because the contract itself doesn't handle any value.