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

Port latest changes from go-nitro till commit 64c4ee9 on November 15 #138

Merged
merged 4 commits into from
Apr 25, 2024

Conversation

nikugogoi
Copy link
Collaborator

@nikugogoi nikugogoi commented Apr 18, 2024

Part of Port over latest changes from go-nitro

  • Port latest changes from go-nitro till commit 880c8b50 on October 12
    • Remove private key property from p2p message service
    • Add DEVELOPMENT.md file
  • Port latest changes from go-nitro till commit ff84d606 on November 1
    • Use @statechannels/nitro-protocol version 2.0.1-alpha.6 and generate contract bindings
  • Use wrapped errors

@nikugogoi nikugogoi self-assigned this Apr 18, 2024
#3)

* Remove private key property from p2p message service

* Add DEVELOPMENT.md file
#4)

* Upgrade state channel nitro protocol version

* Generate latest contract bindings

* Add steps to generate bindings

* Update DEVELOPMENT.md

* Use wrapped error in handle objective request

* Update README and DEVELOPMENT.md
* Implement wait for payment and ledger channel status meethods

* Add methods to register ledger and payment updates
* Use wrapped error

* Format wrapped error message

* Fix error message
@nikugogoi nikugogoi changed the title [WIP] Port latest changes from go-nitro till commit 64c4ee9 on November 15 Port latest changes from go-nitro till commit 64c4ee9 on November 15 Apr 25, 2024
@ashwinphatak ashwinphatak merged commit 78196f4 into cerc-io:main Apr 25, 2024
4 checks passed
@ashwinphatak ashwinphatak deleted the port-nov-15 branch April 25, 2024 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants