Create a SEP to allow user to be approved for auth_required asset without leaving their wallet / exchange frontend

Open
#316 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

Start by reviewing SEP-6 and the referenced SEPs 9, 10, and 12 to understand the existing anchor and KYC protocols. Define the client/server flow for submitting KYC information and receiving authorization through a wallet or exchange frontend; done means the new SEP specifies that protocol clearly.

Written by the indexing model from the issue text.

Description

help wanted needs draft SEP

Who: SDEX users who want to hold & trade AUTH_REQUIRED assets
What: Create a new SEP that defines a client / server protocol allowing users to submit KYC info to an anchor and receive authorization to hold an AUTH_REQUIRED asset without leaving their wallet / exchange frontend.
Why: AUTH_REQUIRED assets are becoming more common, and currently the user experience of trying to trade one in an exchange frontend is painful, requiring the user to create an account and manually upload KYC for each new anchor whose assets the user wants to hold.

This SEP would parallel SEP-6 and leverage SEPs 9,10, and 12 to transmit KYC information.

@tomerweller thoughts?

Dominant language
RPC
Stars
632
Forks
399
Avg merge
1d 23h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-protocol

All issues in stellar/stellar-protocol

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.