19 lines
887 B
Markdown
19 lines
887 B
Markdown
|
# Future Work (Channels)
|
|||
|
|
|
|||
|
|
Possible extensions beyond the current payment and generic state channel managers.
|
|||
|
|
|
|||
|
|
## Virtual channels
|
|||
|
|
|
|||
|
|
Virtual channels (hub, ledger channels, guarantees) allow many parties to interact without each pair opening a separate on-chain channel. For design and references:
|
|||
|
|
|
|||
|
|
- [State Channels blog – Virtual channels](https://blog.statechannels.org/virtual-channels/)
|
|||
|
|
- Nitro / Statechannels.org protocols
|
|||
|
|
|
|||
|
|
Current codebase does not implement virtual channels; this is listed as future work.
|
|||
|
|
|
|||
|
|
## Other directions
|
|||
|
|
|
|||
|
|
- **ERC20 payment channels**: Separate manager or token parameter with safe transfers (see PRE_DEPLOYMENT_RECOMMENDATIONS.md).
|
|||
|
|
- **Connext / Raiden / Statechannels SDK**: Optional in-app flows or embedded guides (see EXTERNAL_PROTOCOL_INTEGRATION.md).
|
|||
|
|
- **Upgradeability**: Deploy behind a transparent proxy if contract upgrades are required later.
|