Skip to content

Commit 6bb5f58

Browse files
committed
📝 Update CHANGELOG for 0.6.0
Signed-off-by: Matthias Geihs <matthias@perun.network>
1 parent ed8b1f5 commit 6bb5f58

1 file changed

Lines changed: 15 additions & 3 deletions

File tree

CHANGELOG.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
66

77
## [Unreleased]
88

9+
## [0.6.0] Fenrir - 2020-12-18 [:warning:]
10+
Support for on-chain progression of app channels.
11+
12+
### Added
13+
- On-chain progression: The channel watcher is now interactive and informs the client when a channel has been registered on-chain. If the channel has a defined app logic with a valid state transition logic, clients can individually progress the app state on-chain according to the defined state transition logic by calling `ProgressBy` on the channel object.
14+
- Settle with sub-channel disputes: Ledger channels can now be settled with funds locked in disputed sub-channels if the corresponding sub-channels have been registered and the disputes have been resolved on-chain.
15+
916
### Changed
10-
- `ContractBackend.NewTransactor` to set the correct context and also removed
11-
the `value` parameter.
17+
- The channel watcher logic changed. The channel watcher now takes as input an event handler which gets notified about on-chain channel events. Before, the watcher automatically settled a channel in case of a dispute. Now, the watcher will automatically detect if an old state has been registered, refute with the most recent one, and notify the user. If the channel has a defined application logic, the user can further progress the channel on-chain. It is within the responsibility of the framework user to finally settle the channel and withdraw the funds.
18+
- The channel settling logic changed. Before, a call to `Settle` on a channel object automatically registered the channel, concluded it, and withdrew the funds. Now, to accomodate on-chain progression functionality, the user must call `Register` independetly before being able to settle the channel. Afterwards, for app channels, the user has the opportunity to progress the channel state on-chain by calling `ProgressBy`. Finally, the user can settle the channel by calling `Settle`.
19+
- `ContractBackend.NewTransactor` now sets the context on `TransactOpts`. Furthermore, parameter `value` has been removed.
20+
21+
### Fixed
22+
- Persistence: Sub-channels are now persisted and restored properly.
1223

1324
## [0.5.2] European Ecstasy - 2020-11-05 [:warning:]
1425
ERC20 and Funding Agreement support and many test fixes.
@@ -187,7 +198,8 @@ Initial release.
187198

188199
[:warning:]: #:warning:
189200

190-
[Unreleased]: https://github.com/perun-network/go-perun/compare/v0.5.2...HEAD
201+
[Unreleased]: https://github.com/perun-network/go-perun/compare/v0.6.0...HEAD
202+
[0.6.0]: https://github.com/perun-network/go-perun/compare/v0.5.2...v0.6.0
191203
[0.5.2]: https://github.com/perun-network/go-perun/compare/v0.5.0...v0.5.2
192204
[0.5.0]: https://github.com/perun-network/go-perun/compare/v0.4.0...v0.5.0
193205
[0.4.0]: https://github.com/perun-network/go-perun/compare/v0.3.0...v0.4.0

0 commit comments

Comments
 (0)