myhush / hush Goto Github PK
View Code? Open in Web Editor NEWHush is a fork of Zcash focused on secure communications
Home Page: https://myhush.org
License: Other
Hush is a fork of Zcash focused on secure communications
Home Page: https://myhush.org
License: Other
We do not have a testnet for core devs to develop new features on and use as a testing ground.
This is worth 500 Hush
Yes.
A testnet should exist.
To close this issue, we must have a new Genesis block created and mined. Then, the IP of the origin testnet node needs to be added to the code and then other nodes can begin to connect to the testnet.
This issue is only for getting the origin node up and running and the genesis block created and mined.
All
Docs need to be generated and decision needs to be made about how long to wait before deprecation.
Hush has not had a valid regtest genesis block. So, that should be generated as well otherwise there is no real qa.
400 Hush to be paid by @Acidut
miner.myhush.org does not support SSL. To fully support SSL, we must support Secure WebSockets (WSS), which requires opening up new server ports, and new nginx configs and updating HTML/JS with relevant URL and code changes.
Additionally, the Perl code that is the dynamic part of the codebase needs to be made into a CPAN module, to be testable and trivially distributable via-known-trusted channels like package managers.
Additionally, we need to be able to payout to N addresses with arbitrary ratios, to enable many use cases.
Yes
250 Hush
miner.myhush.org has modern TLS security deployed and is able to ask people to input a taddr and then send a certain percentage of that browser tab's mining to their custom address.
Additionally, it is a CPAN module which reads in a custom config file, and is trivially installable on every server Perl exists (just about every one).
We use HTTP currently which can be re-written by evil network operators, and leaks metadata.
All
When trying to compile the latest hush.git from source:
g++: error: unrecognized command line option "-m64"
hush should build correctly
When boost is being compiled, it seems to compile for x86_64 when this is an ARM7vl system.
hush.git master 875183b360f4
https://bitcoin.org/en/full-node#maximum-upload-targets
since 4 days (4 february) I cannot sync anymore to network
I also try to port forward 8888 with no succes. any idea ?
in ~/.hush/debug.log
2018-02-08 19:31:31 socket recv error Connection reset by peer (104)
2018-02-08 19:31:31 connect() to [2001:0:9d38:953c:1ca7:e871:a472:fde9]:8888 failed: Network is unreachable (101)
2018-02-08 19:31:32 socket recv error Connection reset by peer (104)
2018-02-08 19:31:33 connect() to [2001:0:9d38:90d7:c8f:3875:b635:d6a8]:8888 failed: Network is unreachable (101)
2018-02-08 19:31:39 socket recv error Connection reset by peer (104)
2018-02-08 19:31:40 connect() to 46.147.23.0:8888 failed after select(): Connection refused (111)
2018-02-08 19:31:41 socket recv error Connection reset by peer (104)
2018-02-08 19:31:48 socket recv error Connection reset by peer (104)
2018-02-08 19:31:50 socket recv error Connection reset by peer (104)
2018-02-08 19:31:55 connect() to [2001:0:4137:9e76:c60:6ad2:2ac8:4f36]:8888 failed: Network is unreachable (101)
2018-02-08 19:31:56 socket recv error Connection reset by peer (104)
2018-02-08 19:31:57 socket recv error Connection reset by peer (104)
2018-02-08 19:31:58 socket recv error Connection reset by peer (104)
2018-02-08 19:31:59 socket recv error Connection reset by peer (104)
2018-02-08 19:32:05 connect() to [2a01:cb08:5c:300:35e9:622f:2ab0:29f4]:8888 failed: Network is unreachable (101)
2018-02-08 19:32:11 connect() to [2001:0:4137:9e76:4de:3453:b992:c6b9]:8888 failed: Network is unreachable (101)
2018-02-08 19:32:12 connect() to [2001:0:9d38:6abd:c5d:c204:a88b:4f82]:8888 failed: Network is unreachable (101)
2018-02-08 19:32:14 socket recv error Connection reset by peer (104)
2018-02-08 19:32:14 socket recv error Connection reset by peer (104)
2018-02-08 19:32:15 socket recv error Connection reset by peer (104)
Build a deb for 1.0.12 and put in the correct apt repo
Why I'm unable to open my hush web wallet. I stored my hush coins in web wallet but the link for web wallet doesn't work.
This issue tracker is only for technical issues related to hushd, the Hush node daemon.
General Hush questions and/or support requests and are best directed to the Hush Forums or Slack Chat.
For reporting security vulnerabilities or for sensitive discussions with our security team, please contact your local nasal demon via ICMP.
Please provide a general summary of the issue you're experiencing
Tell us what should happen
Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
Run hushd --version
to find out
This includes the relevant contents of ~/.hush/debug.log
. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
~/.hush
directory and/or take a VM snapshot?~/.hush
directory might help make the problem reproducible. Please redact appropriately.The Hush Messenger Protocol needs a reference implementation, hopefully written in a language that does not hate humans.
= 1000Hush
Yes
Hush messages shall fly freely, like birds in the wind.
Hush messages dream of the day they will be let from their coops.
All
We need a miner in JS, prior art:
https://forum.z.cash/t/zcash-javascript-miner/17496/21
100 Hush
Yes
Mining Hush in the browser!
Doesn't exist
All
No regtest genblock
100 Hush
Devs should be able to run RPC tests/other in regtest mode.
Doesn't exist, can't run the tests
All
The createrawtransaction
RPC method in Hush does not support a data
key to embed data into a raw transaction via OP_RETURN.
This makes it hard/impossible to port a tool such as https://github.com/coinspark/python-OP_RETURN to Hush, since there is no RPC access to raw transactions that gives us what we need.
Yes
A hush developer should be able to create custom raw transactions with data keys, so as to enable embedding data via OP_RETURN, like http://coinsecrets.org/
No way to create custom OP_RETURN data
All
Hey guys, would you please add my pool to the hush readme? Thanks https://hush.deltapool.net
Wallet encryption on Linux is not working
error code: -16
error message:
Error: wallet encryption is disabled.
Wallets should be able to be encrypted.
Error above.
“version”: 1000950,
When running "hush-cli help" command it references "zcashaddress" which could lead to confusion. For example, one line of the returned text shows:
sendtoaddress "zcashaddress" amount ( "comment" "comment-to" subtractfeefromamount )
To avoid confusions, it should return something like:
sendtoaddress "hushaddress" amount ( "comment" "comment-to" subtractfeefromamount )
I saw this on hushd version v1.0.9-9b5ced9
Optional argument should turn on decoding of memo field, from binary hex to a Unicode string, which is vastly more friendly to Hush application developers. This will make HushList implementations much easier to write + maintain as well.
We need to adjust the hard-coded nodes to account for removal of myhush.network.
Merge latest bitcore
1000 Hush
xxx
The repository 'https://dl.bintray.com/myhush/hush hush Release' does not exist anymore.
The repository should exist
The repository does not exist
Hush only supports HTTP and therefore connecting to an RPC backend is only "safe" over localhost, otherwise it would leak lots of metadata and rpc user/pass. Hush should support TLS like Bitcoin and other coins like Zen. Encrypted p2p connections will additionally greatly reduce network metadata available to snoopy people.
TBD
Yup
Support TLS connections,
No TLS
All
See ZEN's TLS_integration branch: https://github.com/zencashio/zen/compare/master...ZencashOfficial:TLS_integration?expand=1
and the corresponding issue: HorizenOfficial/zen#26
No one likes building stuff that takes 10 minutes - 1 hour constantly. Including .debs and .zips of prebuilt binaries is always useful
There's a script to automatically package binaries into a deb in zcutil
https://github.com/MyHush/hush/blob/master/zcutil/build-debian-package.sh
Getting an error when trying to send HUSH from my wallet to another address
Error 16: bad-txns-oversize
Should send 300 Hush.
Fails to send 300, gives error.
All
All
Hi Hust team,
I was transferring my hush from the web wallet to Cryptopia exchange. (last week)
Hush never arrived.
My friends having a same problem as well.
Help please to solve this problem.
Thanks,
Zsolt
The discord invite in the github doc has expired
Please can you update the discord invite / make it a perm invite
We have a testnet, but no explorer! It would make it easier on devs if they could look at explorer pages for testnet xtns and stuff like that.
Yes
TBD
Awesome testnet explorer exists
No testnet explorer
Currently we are using a self-signed cert which has scary warnings.
Yes
Proper cert
Scary warnings to average people 😢
All
No easy way to restart hushd
$ ./src/hush-cli restart
error code: -32601
error message:
Method not found
The hushd
daemon should restart.
Silly error message that is confusing to new users.
$ ./src/hushd --version
Zcash Daemon version v1.0.9-c54a837
Running ./zcutil/build.sh -j$(nproc) fails on Manjaro 64bit
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system-mt... no
configure: error: Could not link against boost_system-mt !
The zCash solution is to run build.sh w/ --disable-proton
, but even though this is present in the configuration file, the script doesn't accept it, "invalid argument --disable-proton"
edit: I see that disable-proton is default on the build file.
I'm currently attempting to change PREFIX="/usr/"
to see if that works
update: somehow didn't pick up on the db headers.
Tried now with setting --with-boost-libdir=/usr/lib64
still getting same error.
Not easy to spin up a Hush server on ec2.
All the time.
No deterministic builds
Yes
500HUSH
Since Bitcoin Core and Zcash have reproducible builds, we should as well. It increases the security of our entire ecosystem.
We do not have Gitian setup
All
I like tuhtles
This issue tracker is only for technical issues related to hushd, the Hush node daemon.
General Hush questions and/or support requests and are best directed to the Hush Forums or Slack Chat.
For reporting security vulnerabilities or for sensitive discussions with our security team, please contact your local nasal demon via ICMP.
Automatic deprecation shutdown feature. How do I get rid of it? If there is no upgrade? Is there a quick upgrade ?
Messages:
It's just a temporary README right now
Yup
Super snazzy developer-oriented website to be an "easy onramp" for Hush devs/miners/pool ops/etc..
Ain't nothin' there
The current difficulty algorithm appears to have an averaging window of N=50 which is pretty long and 3x more than Zcash. This allows big miners to come on and off, "stealing" blocks before the diff algo is able to rise, leaving small miners with a higher-than-necessary difficulty. There appears to be 5 to 10 "attacks" like this per day of miners with ~2x the network hashrate, getting 10 to 20 blocks at 1/3 the correct difficulty setting.
An argument can be made for just copying Zcash, but N=17 still invites attacks. Also, Daira has said they should have gone to < 3600 +/- timestamp limit. I think +/- 1000 is good.
N=10 is better and if it is used I recommend using my zawy v1b. Karbowanek coin has spent a lot of time with me testing it and looking for something better. N=10 in the Zcash algo may be pretty much the same but I distrust trying to use median like they do, especially with smaller N, at least without tweaking it again to make sure the average comes out correct. Str4d said it was to deal with bad timestamps, but now I know the average immediately corrects the bad timestamp's effect in the next block (if it is allowed to go negative) and it should be better due to accuracy.
But I would like to see N=8 used and call it "Gandalf's difficulty algorithm" (see below). No attacker could profit from it, assuming it's not worth getting only 2 to 4 free blocks before having to change coins again. The "free blocks" obtainable from diff algo's is 1/4 the N averaging window, but up to 1/2 N if they begin the attack when D is accidentally low, and then mine for 3/4 N with > 3x hash rate.
The following looks simple, but the link above shows how much work I've done in advanced techniques like a variable averaging window, hash-attack detection using statistics, least-squares slope prediction, significant-slope-change detection, mixtures of avg and median, recent-blocks-more-heavily-weighted, and "discrete D/T averaging" as a hashrate measurement. I was able to get all of them only as good as simple averaging, and none of them better than simply going to a smaller N for averaging.
# Gandalf's difficulty algorithm v1. "Hash attacks shall not pass!"
# This is Zawy v1b with low N=8 (and X=5)
# Timestamp manipulation protection is not needed due to limits on next_D.
# Negative timestamps must be allowed.
# 0.92 keeps avg solvetime on track but makes median come out 8% low. I can't find a fix.
# Increase N to 30 if you want correct avg & median, but expect 10% of blocks in small
# coins to be stolen. Median mixed in w/ avg will not help.
# Do not use sum(D's) * T / [max(timestamp)-min(timestamp)] method.
# 5% block solvetimes are > 5x target solvetime under constant HEAVY attack.
# 1.3% block solvetimes > 5x target solvetime when hashrate is constant.
# 3% of blocks will be < 0.5x or > 2x the correct difficulty on accident.
# When N=15 these numbers are 5%,, 1%, and 0.5%.
https://github.com/seredat/karbowanec/commit/231db5270acb2e673a641a1800be910ce345668a
avg(last 8 solvetimes) = 1 if avg(last 8 solvetimes) < 1; # prevent divide by zero
next_D = avg(last 8 Ds) * TargetInterval / avg(last 8 solvetimes] *0.92;
next_D = 1.6*previous_D if next_D/previous_D > 1.6;
next_D = 0.63*previous_D if next_D/previous_D < 0.63;
The only potential problem I see is that the D will swing below 0.5 the correct D a lot, attracting an attack. But they can only get ~4 blocks at low difficulty. A question I need an answer to is this: How short of a "hash attack" can a big miner with 2x network hashrate accept before it is not worth switching coins to go work on a coin that is going to know his difficulty in X blocks? What is the upper bound on X for 90% of miners? What is the time cost in switching coins? I can go to N=5 which will result in a lot of D < 0.33 correct D, which is really attractive, but is worth 3 blocks for them to switch coins?
We are now in ElectrumX 1.2.1, so we can run the backend of a light wallet, a huge piece, but we lack the frontend part. This bounty is to implement the frontend Electrum starting from another forks implementation. For example Bitcoin Cash has https://www.electroncash.org/
100HUSH
We need an HMP spec on Github
Yes
TBD
A publicly viewable spec which we can point people at and take Github Pull Requests on.
Hi,
My hush daemon throws error when I restart.
any help?
Thanks
Running "sudo echo 'deb https://dl.bintray.com/myhush/hush/ hush main' >> /etc/apt/sources.list" errors with "permission denied: /etc/apt/sources.list". Using "echo 'deb https://dl.bintray.com/myhush/hush/ hush main' | sudo tee --append /etc/apt/sources.list.d/hush.list" works as expected.
Also "apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61" should be executed with sudo otherwise it fails to install the key.
Yes
The repository should be added to sources and the key should install correctly.
In my Hush pool i have tryed to change diff setting from 0.1 upto 128 and still same errors
could anyone tell me where i messed up ?
[Pool] [hush] (Thread 4) Share rejected: {"job":"cccd","ip":"::ffff:31.24.216.135","worker":"t1aPXQqsm9fFZzhFotsYeJyvve3SNgURCQH.Rig18","difficulty":2.4,"error":"incorrect size of solution"}
List of known issues / TODOs for 1.0.12
We need docs on how to run a testnet node, or else nobody will know how.
Yes
To be able to RTFM
No RTFMing possible
ALL
No list of default nodes
This:
addnode=us.madmining.club
addnode=183.89.226.141
addnode=163.172.70.26
addnode=76.188.211.191
addnode=173.212.196.148
addnode=78.94.32.197
addnode=77.78.12.89
addnode=78.46.88.113
addnode=163.172.70.26
addnode=192.99.3.29
addnode=144.76.62.229
addnode=163.172.64.208
addnode=37.187.167.145
addnode=[2607:5300:60:341d::1]
addnode=[2001:41d0:d:691::]
addnode=[2a02:c207:2008:8708::1]
addnode=[2001:470:1f09:3b6:7285:c2ff:fe0e:1664]
addnode=[2a02:908:162:67dc:225:90ff:fe50:2b9b]
Nothing
All
This file lists Zcash contributors and commit counts. We need to decide if we want to start fresh with a list of Hush contributors or keep this list and add to it in some way.
Yes, erryday
A nice list of Hush contributors should be seen.
Old list of Zcash contributors is currently there.
All
This issue tracker is only for technical issues related to hushd, the Hush node daemon.
General Hush questions and/or support requests and are best directed to the Hush Forums or Slack Chat.
For reporting security vulnerabilities or for sensitive discussions with our security team, please contact your local nasal demon via ICMP.
Please provide a general summary of the issue you're experiencing
Tell us what should happen
Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
Run hushd --version
to find out
This includes the relevant contents of ~/.hush/debug.log
. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
~/.hush
directory and/or take a VM snapshot?~/.hush
directory might help make the problem reproducible. Please redact appropriately.sorry i need orientation on how to edit the chainparams to make my own chain and have my own coin
i was using different sources but i was success with the litecoin source but i'm searching for the equihash algo
please can anyone help me or give me some link where i can read what to do?
thanks
We need to redefine the hush release process and update related documentation accordingly. This re-write is needed due to team changes and to fully sync devs.
We need to very clearly explain privacy and anonymity on our homepage and how they relate to Hush.
But our homepage confuses them.
Privacy is not the same as anonymity, and we need to explain that to our potential users.
Teach people good stuff instead of spreading FUD
Hush does not have CI.
Yup
Continuously integrated goodness
No way to tell if a commit breaks the build!!!
All
Since merging 1.0.9 updates from upstream, nodes have an auto-senescence feature that causes versions more than roughly 18 weeks old to not run without a flag to override this.
We need to adjust parameters to match HUSH block heights, and possibly make for a longer deprecation period or consider not enabling by default.
Original upstream issue is zcash/zcash#2274 and was implemented in zcash/zcash#2297
I generated a diff between the radis42/zcash
v1.0.8-1-mac-gcc
branch and the zcash v1.0.8
branch to pick up the mac specific differences for a build.
I've generated a v1.0.9-mac branch from the hush v1.0.9-lin branch in my hush fork here:
https://github.com/ianblenke/hush
The only real difference in my patched branch is that I don't have any of the client name changes from MagicBean to AppleSeed as with zcash4mac. There is a README-mac.md that should help building and using this branch.
As this is a new branch, I can't really generate a proper github PR for this.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.