Session Date/Time: 09 Nov 2023 12:00

satp

Summary

The Session on Asset Transfer Protocol (SATP) covered updates on the architecture draft, crash recovery, and a Rust implementation of SATP. A demo on NF use cases and a report from the network identification design team were presented. Dennis discussed asset profile definitions. Discussions included charter scope, GitHub usage, use case inclusion, and the design of network identification.

Key Discussion Points

Architecture Draft: Thomas requested feedback on the architecture draft, aiming for working group last call. Wes emphasized that the document should align with the chartered scope, avoiding prescriptions for internal network APIs.
GitHub Usage: It was clarified that comments and questions can be raised on GitHub, with the recommendation to announce the creation of issues on the mailing list for visibility.
Crash Recovery Draft: Thomas provided an update on the crash recovery draft, noting it's not a formal working group item but relevant to implementations.
Rust Implementation of SATP: Rama presented on a Rust implementation of SATP within the Hyperledger Cacti project, enabling cross-chain asset transfers. Discussions focused on DLT version compatibility, the scope beyond DLTs, and verification mechanisms.
NFT Use Cases: Victor demoed the use of NFTs for domain ownership and the need for protocols like SATP to coordinate complexities.
Network Identification Design Team: Thomas reported on the team's progress, addressing network forks and legal ownership declaration. Key considerations included TLV usage, default address format (32 bytes), and extended address format for additional network identification.
Asset Profile Definition: Dennis discussed the context of SATP operation including defining asset profiles to ensure a precise description of assets being transferred. This is considered outside the current scope but may be added in the future.

Decisions and Action Items

Architecture Draft Review: The chairs will review the architecture draft within two weeks to assess its readiness for working group last call.
NFT Use Case Inclusion: The working group will vote on including Victor's NFT use case in the official use case document.
Mailing List Usage: Encourage the working group to reference important GitHub issues in the mailing list to ensure visibility.
Interim Meeting Scheduling: A Doodle poll will be sent out to find the most suitable time for all participants for the recurring monthly interim meeting.

Next Steps

Chairs to provide comments to the architecture draft authors within two weeks.
Gather working group consensus on including the NFT use case in the document.
Distribute a Doodle poll to determine optimal time/day for interim meetings.
Send proposed text for use cases to mailing list.