Develop processes for different device usage #6

Open
opened 2024-11-20 22:54:05 +00:00 by anton · 2 comments
Owner
  • Create individual playbooks for each asset and cold storage method
  • Specify steps for both offline and semi-cold operations
  • Cover on-site and off-site (travel) operations
  • Each playbook has defined roles
  • Each playbook has defined prerequisites
- [ ] Create individual playbooks for each asset and cold storage method - [ ] Specify steps for both offline and semi-cold operations - [ ] Cover on-site and off-site (travel) operations * Each playbook has defined roles * Each playbook has defined prerequisites
Author
Owner

Start by documenting the end to end flow for Ronin.

Start by documenting the end to end flow for Ronin.
lrvick added this to the Custody Framework project 2024-11-21 04:51:25 +00:00
Author
Owner

There is a challenge with SOL transactions because they are only valid for 250 blocks from the hash which was used to generate the tx. Solana processes 2.5 blocks a second, which means we have a 100 second window to get a tx to the SCIF for signing, and bringing it back to broadcast.

There are two paths:

  • Derive SOL key in SCIF and transfer it to hot room for transaction hosting

  • Have a way to generate a tx in the hot room, get it into the SCIF on an SD card, sign it, get the signed tx out of the SCIF and back to the hot room, and broadcast it (while maintaining SCIF frequency protection in tact)

There is a challenge with SOL transactions because they are only valid for 250 blocks from the hash which was used to generate the tx. Solana processes 2.5 blocks a second, which means we have a 100 second window to get a tx to the SCIF for signing, and bringing it back to broadcast. There are two paths: * Derive SOL key in SCIF and transfer it to hot room for transaction hosting * Have a way to generate a tx in the hot room, get it into the SCIF on an SD card, sign it, get the signed tx out of the SCIF and back to the hot room, and broadcast it (while maintaining SCIF frequency protection in tact)
anton changed title from Develop Playbooks for Each Token and Storage Type to Develop processes for different device usage 2024-12-05 22:55:36 +00:00
anton started working 2024-12-05 22:57:54 +00:00
anton stopped working 2024-12-05 23:11:38 +00:00
13 minutes 44 seconds
anton added this to the Vaulting Framework Documentation milestone 2024-12-06 01:32:59 +00:00
Sign in to join this conversation.
No Label
No Assignees
1 Participants
Notifications
Total Time Spent: 13 minutes 44 seconds
anton
13 minutes 44 seconds
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/docs#6
No description provided.