Skip to content

[FEATURE] Compliance Need to Finish KYC to Claim Transfer #37

Description

@codingshot

Problem

  • DAOs don't currenly have KYC checks

Description

  • KYC enabled checks on a DAO level or proposal basis, where can specify the SBT or KYC check

User Story(s):

As a DAO compliance officer, I want to make sure we cannot send funds to people who are not complaint, so that I can verify all vendors in a systemized ways

Acceptance Criteria

  • show expiry if kyc needed
  • maybe kYC on contract level for DAO level compliance
  • Must be on transfer and function call requests. Someone could inherently go around the way
    KYC threshold, time until the transfer of functional call request (cool-down period) if receiver doesn’t meet KYC requirements, then the approved proposal will be nullified.

Limitations

  • need designs for this
  • need a KYC standard / sbt / cross contract call to specify (which isn't currently satisfied)

Resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Ideating

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions