Skip to content
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

Developer Call - 2019.05.28 at 17:00 CET #132

Closed
m52go opened this issue May 23, 2019 · 2 comments
Closed

Developer Call - 2019.05.28 at 17:00 CET #132

m52go opened this issue May 23, 2019 · 2 comments

Comments

@m52go
Copy link
Contributor

m52go commented May 23, 2019

It's important that we talk through the proposed protection mechanisms and determine a way forward.

This call is scheduled at the same time as past calls, so hopefully most folks can join...a critical part of determining how to best proceed will require developer input.

Day/Time

  • Tuesday May 28 2019, 17 CET

Agenda

Feel free to suggest other topics you'd like to cover (preferably as they relate to protection mechanisms).

YouTube

Hangout

  • TBD
@m52go m52go changed the title 2019.05.28 Dev Call at 17:00 CET Developer Call - 2019.05.28 at 17:00 CET May 23, 2019
@mpolavieja
Copy link

mpolavieja commented May 23, 2019

Within this bullet point, I would add a discussion about the pre-trade step (as this would enable the possibility of any 2FA method the traders agree without having to end the trade in a dispute wasting mining fees in case they don´t come to an agreement).

The optional (soft-fork like) approach for this proposal is also an important discussion.

@m52go
Copy link
Contributor Author

m52go commented May 28, 2019

Outcome: ripcurlx and other developers will evaluate the technical requirements for the proposed measures and convey findings this week. Next week, we'll work toward crafting a technical specification and wire-frames to implement soon after.

@m52go m52go closed this as completed May 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants