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

Issues with Translator and Braiins SV2 pool #1399

Open
jakubtrnka opened this issue Jan 24, 2025 · 2 comments
Open

Issues with Translator and Braiins SV2 pool #1399

jakubtrnka opened this issue Jan 24, 2025 · 2 comments
Assignees
Labels
adopter-feedback translator proxy SV1>SV2 translator proxy issues

Comments

@jakubtrnka
Copy link
Contributor

  1. After the translator is started, it tries to open an extended mining channel with the user "ABC". Such user is not known to the server and rejects the chanel. The translator thereafter terminates.

  2. I didn't find a way to configure the user. Neither do I think it's necessary for the translator to open any channel when there is no downstream mining session active.

  3. If I create the user ABC. the translator connects and then it crashes with the following error:

thread 'tokio-runtime-worker' panicked at translator/src/lib/proxy/next_mining_notify.rs:22:10:
failed to convert extended job to non segwit: InvalidCoinbase
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@pavlenex pavlenex added translator proxy SV1>SV2 translator proxy issues adopter-feedback labels Jan 24, 2025
@Fi3
Copy link
Collaborator

Fi3 commented Jan 28, 2025

is there a braiins public endpoint that I can use to test this?

@plebhash
Copy link
Collaborator

is there a braiins public endpoint that I can use to test this?

a few weeks ago @jakubtrnka asked me to test with this endpoint:

stratum2+tcp://stratum.braiins.com:3336/9avdFUsdssXnmUSaEXEpe5R5mmqTXyxCnXQBBcTVwCGKCYoMkis

unfortunately SRI tProxy cannot resolve URLs, so I had to look up for the IP address and used this one:

164.92.161.229

I just tried again, and actually witnessed a different error:

2025-01-28T12:17:00.727764Z  INFO translator_sv2: Proxy Config: ProxyConfig { upstream_address: "164.92.161.229", upstream_port: 3336, upstream_authority_pubkey: Secp256k1PublicKey(XOnlyPublicKey(7fa233a737ec12d57c0cf02db529cc56bb3bcbfac835811389af870806b3b82630afa46ff95078858a4a9f6cc0879ed27037cfd3024fc2b73edeb27145499583)), downstream_address: "0.0.0.0", downstream_port: 34255, max_supported_version: 2, min_supported_version: 2, min_extranonce2_size: 8, downstream_difficulty_config: DownstreamDifficultyConfig { min_individual_miner_hashrate: 10000000000000.0, shares_per_minute: 6.0, submits_since_last_update: 0, timestamp_of_last_update: 0 }, upstream_difficulty_config: UpstreamDifficultyConfig { channel_diff_update_interval: 60, channel_nominal_hashrate: 10000000000000.0, timestamp_of_last_update: 0, should_aggregate: false } }
2025-01-28T12:17:00.971708Z  INFO translator_sv2::lib::upstream_sv2::upstream: PROXY SERVER - ACCEPTING FROM UPSTREAM: 164.92.161.229:3336
2025-01-28T12:17:01.461018Z  INFO roles_logic_sv2::handlers::common: Received SetupConnectionSuccess: version=2, flags=0
2025-01-28T12:17:01.461190Z  INFO translator_sv2::lib: Connected to Upstream!
2025-01-28T12:17:01.712628Z  INFO roles_logic_sv2::handlers::mining: Received OpenExtendedMiningChannelSuccess with request id: 0 and channel id: 1
thread 'tokio-runtime-worker' panicked at translator/src/lib/utils.rs:8:5:
attempt to subtract with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-01-28T12:17:11.463639Z ERROR translator_sv2::lib::status: Error: PoisonLock
2025-01-28T12:17:11.463773Z ERROR translator_sv2::lib: SHUTDOWN from: Poison Lock error
2025-01-28T12:17:11.463798Z  INFO translator_sv2::lib: Shutting down gracefully...
2025-01-28T12:17:11.464530Z ERROR network_helpers_sv2::noise_connection_async_std: Shutting down noise stream reader! Kind(
    UnexpectedEof,
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adopter-feedback translator proxy SV1>SV2 translator proxy issues
Projects
None yet
Development

No branches or pull requests

5 participants