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

Implement POC for supporting drafts #3116

Open
RafaelAPB opened this issue Mar 15, 2024 · 1 comment
Open

Implement POC for supporting drafts #3116

RafaelAPB opened this issue Mar 15, 2024 · 1 comment
Assignees
Labels
IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force.

Comments

@RafaelAPB
Copy link
Contributor

There are drafts that will need to be implemented for our solution to work properly. Those are 1) draft-zhang-satp-network-identification-00 and draft-avrilionis-satp-asset-schema-architecture-00. The first provides a way to identify different networks such that gateways can reason about the same locations. Akin to chainlist, but also for private blockchains and even centralized systems. The second draft concerns itself with the identification and characterization of an asset, so gateways can refer to exactly the same asset prior to the transfer process.

Requirements:
1 - Create simple POC for network identification. Support Ethereum mainnet, private Hyperledger Besu networks, and private Hyperledger Fabric networks (the ones used in our work for testing purposes).

2 - Create simple POC for asset schema / asset profiles. Define asset profiles for a test token in Fabric, a test token in Ethereum, Bitcoin, and support for most popular ERC20 tokens (ETH, USDC, USDT)

@RafaelAPB RafaelAPB added the IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force. label Mar 15, 2024
@LordKubaya
Copy link

hi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force.
Development

No branches or pull requests

2 participants