No Branch/Tag Specified
arm
asyncnotedecryption
danger
dev
dev-aarch64
dev-mac
dev-old-randomx
divzaddrs
dragonx
duke
freebsd
getfilterednotes
hip39
hushutils
insync
jahway603
master
mvstuff
onryo
p2p_privacy
ramhash
relaytx
rx-largepages
setbestchain
warmup
witness_cache
wolfssl
wolfssl_win
z_createrawtransaction
z_importwallet
z_signmessage
v0.11.2.z0
v0.11.2.z1
v0.11.2.z2
v0.11.2.z3
v0.11.2.z4
v0.11.2.z5
v0.11.2.z6
v0.11.2.z7
v0.11.2.z8
v0.11.2.z9
v1.0.0
v1.0.0-beta1
v1.0.0-beta2
v1.0.0-rc1
v1.0.0-rc2
v1.0.0-rc3
v1.0.0-rc4
v1.0.1
v1.0.10
v1.0.10-1
v1.0.11
v1.0.11-rc1
v1.0.12
v1.0.12-rc1
v1.0.13
v1.0.13-rc1
v1.0.13-rc2
v1.0.14
v1.0.14-rc1
v1.0.15
v1.0.15-rc1
v1.0.2
v1.0.3
v1.0.4
v1.0.5
v1.0.6
v1.0.7-1
v1.0.8
v1.0.8-1
v1.0.9
v1.1.0
v1.1.0-rc1
v1.1.1
v1.1.1-rc1
v1.1.1-rc2
v1.1.2
v1.1.2-rc1
v2.0.0
v2.0.0-rc1
v2.0.1
v3.0.0
v3.1.0
v3.1.1
v3.10.0
v3.10.1
v3.10.2
v3.2.0
v3.2.1
v3.2.1-alpha
v3.2.1-beta
v3.2.2
v3.2.3
v3.3.0
v3.3.1
v3.3.2
v3.4.0
v3.4.1
v3.5.0
v3.5.1
v3.5.2
v3.6.0
v3.6.1
v3.6.2
v3.6.3
v3.7.0
v3.7.1
v3.8.0
v3.9.0
v3.9.1
v3.9.2
v3.9.3
v3.9.4
Labels
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
Apply labels
Clear labels
0-500 bounty
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
No Label
0-500 bounty
2001-5000 bounty
501-2000 bounty
arm
beginners
bug
build
documentation
feature
high priority
i2p
low priority
medium priority
question
release
testing
tor
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
I added a new privacy-focused feature to our stratum code on the
dev
branch that needs testing. There is a new option tohushd
called-stratumaddress
where you can give a "default mining address" for all Stratum clients. When a Stratum client uses a mining address of "x", it will use this "default address".Why does this help privacy?
hushd
on startup@odinzu @jahway603 can you test this? I am still a bit confused on whay @jahway603 got a low hashrate while @odinzu it seems to work at full speed. When reporting results, please say which kind of ASIC you did testing with. I think @odinzu is using a Z9 while @jahway603 has an A9. Maybe there is some differences there.
All you need to do is start hush like
hushd -stratumaddress=R...
and then use a mining address ofx
on the ASIC.As an added feature of convenience, if you have many miners, you no longer need to update them all to change your mining address. You just restart
hushd
with a different-stratumaddress
, which hopefully leads to people changing their mining addresses more frequently. The more frequently miners change their addresses, the less metadata is leaked.Compiled new dev branc and then ran
Then I tried x for the username on the miner, but couldn't get that working.
As soon as I switched back to the same hushd command above w/o "stratumaddress" + re-entering the tAddr on the ASIC, I now see stratum mining as expected.
@oDinZu how long did it take your ASIC to get up there with your own hushd?
Still getting super dumb low speeds
The same miner, with the same amount of time period, can pull 50 KSol/s using coolmine or luckpool. Something isn't acting correctly!
@jahway603 ~2 minutes with 500 default freq.
My network confiuration has my miner connected to a router > fiber modem > www.
On my computer, I host hushd stratum, then I startup my miners.
I had a lot of issues initially because of:
a. firewall was enabled on the computer.
b. my router had a weird AI protection enabled and thought hushd was attacking; maybe because of so many packets being sent.
Maybe it has something to do with sending lots of packets on local router network; it sounds like a throttling issue.
@jahway603 Update: Could it be because of the difficulty algo? My miners are using difficulty 8. I didn't choose that difficulty, nor do I know how to change that difficulty. On the example pool for ZEC, I found its difficulty to be 16.
@duke I compiled fresh hushd and successfully launched hushd with new stratumaddress option.
-stratumaddress=R...
I kept the same T-addr I was using before stratum in the miner config.
I created a new T-addr via
hush-cli getnewaddress
and am using this new address for-stratumaddress=R
.I am mining at the moment and will provide more results after I mint some fresh hush puppies.
The following is the command I used:
On Hush Blockchain Explorer: (Minted with OLD T address in miner config GUI)
On SD Wallet: (Showing mined to OLD T address)
I am unable to verify if stratum is working or not; I thought I would see the stratum address be shown public, while sending to old address or vice versa.
On success of Hush puppy found; all lost hush puppies are protected and generated:
Lots of metadata details if they are useful to you for debugging:
@odinzu
I kept the same T-addr I was using before stratum in the miner config.
is not going to work, you need to set your miner address tox
in your ASIC config, or it will just use whatever address is there.As for debugging,
grep stratum debug.log
is more useful for debugging stratum stuff.@jahway603 can you show me
grep stratum debug.log
? Without that, it's hard to know what is going on with thex
not working. I am not sure why your hashrate is so low, the main difference is you have Innosilicon device and @odinzu has Bitmain.I think @odinzu is onto something, this is related to the "difficulty" or "diff". If diff is too high, miners won't find blocks. If it's too low, they waste hashrate. This is why, for instance, pools have different ports for GPU/ASIC/NiceHash, which all start at a different difficulty level to optimize mining.
Setting my ASIC user to
x
orX
does not work. It shows the pool as offline.I even tested with a zaddr and showed same results.
Only the Taddr works at the moment for me.
@oDinZu please show 'grep stratum debug.log'
In my hush-stratum.log
In my hush3 debug.log
@jahway603 plz send
grep stratum debug.log
so we can debug your low hashrate issue, thanks@duke my log file is almost 9MB and I don't want to share it "publicly". How else should I share it?
@jahway603 make an issue on the private repo: https://git.hush.is/hush/qa
Test -stratumaddressto stratumaddress does not work 1 year ago