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.

Sign up for GitHub

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

Jump to bottom

Investigate spending credentials from the main API (coconut enabled to a gateway) from feature/ephemera branch #3741

Closed
tommyv1987 opened this issue Aug 4, 2023 · 3 comments · Fixed by #3755
Closed

Investigate spending credentials from the main API (coconut enabled to a gateway) from feature/ephemera branch #3741

tommyv1987 opened this issue Aug 4, 2023 · 3 comments · Fixed by #3755
Assignees
@neacsu
Milestone
Toblerone

Comments

@tommyv1987
Copy link
Contributor

No description provided.

@tommyv1987
Copy link
Contributor Author

Deploying the main nym-api in coconut enabled mode (with vouchers in the creds db) returns an error from the gateways once the API is trying to spend the voucher against it: error message:


 2023-08-04T10:49:34.780Z WARN  nym_api::network_monitor::monitor::sender     > failed to authenticate with new gateway (BBtXZ2whW6VAuUdTKGqaZgTUXHpqxbuax3DCQ37ibfZ8) - Gateway returned an error response - Validator API error - nym api request failed - Request failed with error message - <!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title>404 Not Found</title>
</head>
<body align="center">
    <div role="main" align="center">
        <h1>404: Not Found</h1>
        <p>The requested resource could not be found.</p>
        <hr />
    </div>
    <div role="contentinfo" align="center">
        <small>Rocket</small>
    </div>
</body>
</html>

@tommyv1987
Copy link
Contributor Author

When running the API in non creds mode it works fine, the gateway has been set up with the following configuration:

./nym-gateway --config-env-file .env init --id "${ID}" --output json --host "$(curl ifconfig.me)" --mnemonic "${GATEWAY_DOUBLE_SPEND_MNEMONIC}" >>/home/nym/output/gateway-"${ID}"-node-details.json

and the double spend mnemonic has funds associated with it

@neacsu neacsu mentioned this issue Aug 9, 2023
Merged
@neacsu
Copy link
Contributor

neacsu commented Aug 9, 2023

One of the coconut signers is not run in coconut enabled mode, making both the coconut sign and coconut verify fail with a 404 error. The sign operation is correctly disregarded initially, as there is still a threshold achieved (2/3), but the verification flow stops on the error, and returns the error to the client (network monitor) via the gateway that initiated the process.
I've put up a PR to make use of the threshold on the verification flow and have a soft failure, but this is an adjacent problem. In this case, the main problem is that one of the nym-api signers is not properly run in coconut mode, and is also built from a different git version, according to what I found in the docker containers

@tommyv1987 tommyv1987 added this to the Toblerone milestone Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neacsu neacsu

Labels
None yet
Projects
None yet
Milestone
Toblerone
Development

Successfully merging a pull request may close this issue.

Print warning when coconut verif endpoint doesn't work nymtech/nym
2 participants
@neacsu @tommyv1987