# Layer 2 Offline Transaction Updates

**URL:** <https://forum.algorand.co/t/layer-2-offline-transaction-updates/1288>\
**Category:** General\
**Created:** [January 21, 2020, 2:48pm UTC](https://forum.algorand.co/t/layer-2-offline-transaction-updates/1288 "2020-01-21T14:48:21Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ryanRfox](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/ryanrfox/32/364_2.png) [@ryanRfox](https://forum.algorand.co/u/ryanRfox)\
**Post date:** [January 21, 2020, 2:48pm UTC](https://forum.algorand.co/t/layer-2-offline-transaction-updates/1288/1 "2020-01-21T14:48:21Z")

</div>

Are there any discussions, examples or documentation exploring layer two solutions using offline transaction updates? Generally speaking, these would be [payment channels](https://en.bitcoin.it/wiki/Payment_channels) as implemented in the Lightning Network ([PDF](https://lightning.network/lightning-network-summary.pdf)) or specified in the Eltoo white paper ([PDF](https://blockstream.com/eltoo.pdf)). I’m keen to discuss with others designing similar solutions on Algorand using [ACS](https://developer.algorand.org/docs/asc), [multisig accounts](https://developer.algorand.org/docs/creating-multisignature-account), [atomic transfers](https://developer.algorand.org/docs/atomic-transfers), etc.

---

_[View the full topic](https://forum.algorand.co/t/layer-2-offline-transaction-updates/1288)._