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

Multi-wallet M2S and S2S transfers with faster speeds #1567

Closed
sergiy-skalelabs opened this issue Aug 28, 2023 · 0 comments · Fixed by #1570
Closed

Multi-wallet M2S and S2S transfers with faster speeds #1567

sergiy-skalelabs opened this issue Aug 28, 2023 · 0 comments · Fixed by #1570
Assignees
Labels

Comments

@sergiy-skalelabs
Copy link
Contributor

This is feature request ticket for future release(es). We do have M2S and S2S transfer directions in IMA Agent pumping messages from other chains into this one particular S-Chain. So all M2S and S2S transfers use same wallet/private key, This make them mutually dependent and unable to work fully parallel even if M2S and S2S run on different time frames inside different IMA Agents. Transfer delays may still happen when some IMA Agent is restarted and its PWA/busy state was lost and stuck as busy in other agents. Using different wallets in M2S and S2S transfers can resolve all mutual dependency issues.

@sergiy-skalelabs sergiy-skalelabs self-assigned this Aug 28, 2023
@sergiy-skalelabs sergiy-skalelabs changed the title Multi-walled M2S and S2S transfers with faster speeds Multi-wallet M2S and S2S transfers with faster speeds Aug 28, 2023
@sergiy-skalelabs sergiy-skalelabs linked a pull request Aug 30, 2023 that will close this issue
@sergiy-skalelabs sergiy-skalelabs linked a pull request Oct 10, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants