Revamping IPC Xnet messages howto and demo

vukolic commented 2 months ago

Feature Request

No

n/a

No

No response

We need a howto - recorded demo is a bonus - which would demonstrate L2-to-L2 IPC communication akin to https://youtu.be/qPDYOa8Tnp0?list=PLxN6L-h3wFfse7XdcdH9dDuhQwe-W6zWt&t=281 with our current stack.

Seamless Ln-Ln (n>1) subnet-to-subnet addressing and value (message) transfers as in https://youtu.be/qPDYOa8Tnp0?list=PLxN6L-h3wFfse7XdcdH9dDuhQwe-W6zWt&t=281 with routing along the IPC tree. L2-(L1)-L2 suffices, or L3-(L2)-L3.

No response

linear[bot] commented 2 months ago

jsoares commented 2 months ago

Some raw thoughts from elsewhere:

At a basic, demoable level, this isn't much more than chaining a sequence of those calls with a simple blocking state machine.
Should be doable, with or without adding an explicit CLI for multi-hop transfer. The caveat, of course, is that whoever's sending the transfer needs access to an RPC on every intermediate subnet (though not the terminal subnet, though for demo purposes they would need it to show the balance), i.e. it's not general in the "hands-off, arbitrary depth" sense.
- ⬆️ is actually in line with Guy's Lisbon presentation and the regional subnets (Schweiz) where the transfer should happen in a subnet where both parties had an account, rather than someone's "home" subnet.
That said, following the disabling of L3+ support, the RPC issue is hardly an issue (everyone already has access to L1 RPC). I think the question really hinges on what the hierarchy will look like.
- If we're focusing on application-specific L2s (with a hierarchy below them or not), then it doesn't matter much. Having the L1 RPC is enough to do cross-application transfers and what happens inside each application is its own microcosm.
- This doesn't really work for the banking system scenario, which also doesn't require heavy L2 customisation.

consensus-shipyard / ipc