urdt/ussd
5
0
Fork 0
Code Issues 32 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Implement phone number registry #12

New Issue
Open
opened 2024-08-29 16:38:21 +02:00 by lash · 2 comments
lash commented 2024-08-29 16:38:21 +02:00
Owner
Copy Link

A registry must exist to resolve phone numbers to accounts when accounts want to interact with each other.

A registry must exist to resolve phone numbers to accounts when accounts want to interact with each other.
lash added the
Kind/Feature
 label 2024-08-29 16:38:21 +02:00
lash added a new dependency 2024-08-29 16:50:54 +02:00
#11 Check whether phone number is registered
kamikazechaser commented 2024-08-29 17:17:45 +02:00
Owner
Copy Link

Additionally, accounts should also be able to send to VPA (virtual payment identifiers)/usernames. The resolution service can be provided by either hooking directly into the graph db with read-only creds or through an HTTP API.

The following account identifiers should work:

  • 0700123177 (registered Ugandan phone)
  • sohail@urdt (registered and approved VPA on sarafu.network)
  • 0x00....0000 (valid Ethereum address)

Not sure if this is the scope of the issue. But we can move this comment onto a new issue.

Additionally, accounts should also be able to send to VPA (virtual payment identifiers)/usernames. The resolution service can be provided by either hooking directly into the graph db with read-only creds or through an HTTP API. The following account identifiers should work: * 0700123177 (registered Ugandan phone) * sohail@urdt (registered and approved VPA on sarafu.network) * 0x00....0000 (valid Ethereum address) Not sure if this is the scope of the issue. But we can move this comment onto a new issue.
lash commented 2024-08-29 18:22:21 +02:00
Author
Owner
Copy Link

@kamikazechaser do we have all the docs we need for the graphql part?

@kamikazechaser do we have all the docs we need for the graphql part?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Runner
AT

  
Runner
CLI

  
Runner
HTTP

  
cleanup

   
easy

A task that can be completed with little effort

  
optimization

   
refactor

   
smell

Code smell

No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Runner
AT
Runner
CLI
Runner
HTTP
cleanup
easy
optimization
refactor
smell
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Blocks
#11 Check whether phone number is registered
urdt/ussd
Reference: urdt/ussd#12
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?