Quote from: UselessGuru on May 05, 2018, 04:05:32 PM

Quote from: realbminer on May 04, 2018, 03:30:37 PM

Quote from: UselessGuru on May 03, 2018, 05:53:58 AM

Quote from: realbminer on May 03, 2018, 02:31:12 AM

Quote from: UselessGuru on May 02, 2018, 10:29:32 AM

How to pass additional parameters in the password field?

Some pools, e.g. zpool allow to define additional mining settings in the password field. See an example below:

BMiner.exe -api 127.0.0.1:1880 -uri stratum://1GSq8txFsg1je6yL8t6S94mYdF8cGqVQJF:BLACKBOX,c=BTC@equihash.mine.zpool.ca:2142 -devices 0

Bminer throws an error:

invalid value "stratum://1GSq8txFsg1je6yL8t6S94mYdF8cGqVQJF:BLACKBOX,c=BTC@equihash.mine.zpool.ca:2142" for flag -uri: Invalid port in the URI
Bminer: When Crypto-mining Made Fast (v7.0.0-9c7291b)

Thanks for your feedback! Please refer to our sample usage page for examples of setting passwords in the command: https://www.bminer.me/examples/.

Here is a concrete example:
bminer -uri stratum://foo.w:pwd@us-east.equihash-hub.miningpoolhub.com:17023
The command above will mine towards the username foo, worker name w and password pwd

Hello

This does not help me Angry

This is what I tried - same error:
BMiner.exe -api 127.0.0.1:1880 -uri stratum://1GSq8txFsg1je6yL8t6S94mYdF8cGqVQJF.BLACKBOX:x,c=BTC@equihash.mine.zpool.ca:2142 -devices 0

Bminer still does not allow me to use ,c=BTC as part of password. Please fix.

Edit: As a workaround I encode the user & password parameters with '[System.Web.HttpUtility]::UrlEncode("StringToEncode")' (Powershell)

Hi, May I ask what is your password exactly? x,c=BTC or ,c=BTC or c=BTC?
The problem is caused by the comma inside the command. We suggest you choose a password without comma.

Some pools (ZergPool, Zpool etc.) require to specify the payout currency by setting it in the password field like this (example taken from http://zergpool.com/):

-o stratum+tcp://neoscrypt.mine.zergpool.com:PORT -u -p c=GUN,mc=GUN

where the required password is c=GUN,mc=GUN

BTW: Yes I am aware the bmnier does NOT do neoscrypt, this is just an example. The same applies however for any other algos like ethash or equihash.

Please refer https://www.bminer.me/examples/#escaping-characters-in-the-uri to solve your problem.
You can always follow RFC 1738 (https://tools.ietf.org/html/rfc1738) to escape special characters.