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

add rpc service usage instructions #1236

Merged
merged 29 commits into from
Apr 28, 2023
Merged

add rpc service usage instructions #1236

merged 29 commits into from
Apr 28, 2023

Conversation

NiloCK
Copy link
Contributor

@NiloCK NiloCK commented Apr 25, 2023

PR adds documentation on requirements for running main.go.

geoknee and others added 3 commits April 24, 2023 18:06
…jectives

nil pointers represent channels that are undefined in the protocol (i.e. a channel left of Alice)
These remain untouched / unpopulated throughout.
@netlify
Copy link

netlify bot commented Apr 25, 2023

Deploy Preview for nitrodocs canceled.

Name Link
🔨 Latest commit 0d72e0d
🔍 Latest deploy log https://app.netlify.com/sites/nitrodocs/deploys/644bd5fb1831810008cf53d6

only store id of consensus channels when marshalling virtualdefund objectives
lalexgap and others added 17 commits April 25, 2023 14:36
The receiver can have AppData = nil. If that's the case, we shouldn't set the AppData = [] on the returned clone.
rather than duplicating that information. This means that things like finalization proofs can be read from the store by other tasks/objectives. This will be important when it comes to handling challenges.

Other changes follow from this one, generally reading / writing to V, ensuring V is "related" to the objective (so it is stored alongside). We can reuse many helpers on V so quite a bit of code can be ripped out.
As in the other protocols, when serializing we only retain the channel Id.
This is enabled by the greater harmony of virtualdefund (it now puts more information in an obvious place in the store)
given changes to underlying data structure
@lalexgap
Copy link
Contributor

Just a heads up that hardhat-docker is no longer required, due to #1235

readme.md Outdated
After the hardhat docker node is running, go-nitro can be started from the root directory with

```
go run ./...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this meaningfully different to go run .?

  • be good to give a sense of the arguments which may be passed in, or at least point to where that information is (go run . -help).
  • let's also point to the go build way of doing it, too?

@NiloCK NiloCK merged commit f6d69c4 into main Apr 28, 2023
@NiloCK NiloCK deleted the cmk.hh-readme branch April 28, 2023 14:31
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