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

Sample contract leveraging sendCross for on-chain interaction with IPC #76

Closed
2 tasks
adlrocha opened this issue Jul 5, 2023 · 1 comment
Closed
2 tasks
Assignees

Comments

@adlrocha
Copy link
Contributor

adlrocha commented Jul 5, 2023

SendCross is a method exposed by the gateway for contracts to be able to trigger cross-net messages as a side-effect from their operation. This hasn't yet been tested. Ideally we should:

  • Write a simple contract that when a function is called triggers a cross-net message to some subnet. This can be initially just the sending of funds to the parent or child (for instance).
  • Write a tutorial of how this can be done so developers can start using this feature.

In the process, it would be great if we could deploy two child subnets (/r123/A and /r123/B), and we could also test the propagation of messages through propagate. In the future we will have to improve the IPC agent so with a single command, the IPC agent can orchestrate itself the message propagation until it reaches the destination.

@dnkolegov
Copy link
Contributor

There is an example of such a contract here - https://github.com/consensus-shipyard/ipc-solidity-actors/tree/dev/examples/contracts

@jsoares jsoares transferred this issue from consensus-shipyard/ipc-solidity-actors Dec 19, 2023
@jsoares jsoares closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: No status
Development

No branches or pull requests

4 participants