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

Breaking roller changes #11

Open
pkova opened this issue Jun 17, 2022 · 0 comments
Open

Breaking roller changes #11

pkova opened this issue Jun 17, 2022 · 0 comments

Comments

@pkova
Copy link

pkova commented Jun 17, 2022

There have been breaking roller rpc changes since the development of azimuth-cli started. When trying to spawn L2 planets with azimuth-cli, I ran into this problem:

curl --location --request POST 'https://roller.urbit.org/v1/roller' --header 'Content-Type: application/json' --data-raw '{
    "jsonrpc": "2.0",
    "method": "getNonce",
    "params": {
        "from": "~lapdeg"
    },
    "id": "1234"
}'
{"id":"1234","error":{"code":-32700,"message":"Failed to parse"},"jsonrpc":"2.0"}

The properly formed getNonce call is this nowadays:

curl --location --request POST 'https://roller.urbit.org/v1/roller' --header 'Content-Type: application/json' --data-raw '{
    "jsonrpc": "2.0",
    "method": "getNonce",
    "params": {
        "from": {"ship": "~lapdeg", "proxy": "spawn"}
    },
    "id": "1234"
}'
{"id":"1234","jsonrpc":"2.0","result":4253}

You could use the roller client (npm, github) instead of raw json rpc calls to fix this.

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

No branches or pull requests

1 participant