From 76d26f64585b975710ea3847db03cdbb79646d86 Mon Sep 17 00:00:00 2001 From: ca333 Date: Tue, 9 May 2017 04:31:02 +0200 Subject: [PATCH 1/4] add libcurl build recipe for static linking --- depends/packages/libcurl.mk | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 depends/packages/libcurl.mk diff --git a/depends/packages/libcurl.mk b/depends/packages/libcurl.mk new file mode 100644 index 000000000..9e8577bb5 --- /dev/null +++ b/depends/packages/libcurl.mk @@ -0,0 +1,23 @@ +package=libcurl +$(package)_version=7.54.0 +$(package)_download_path=https://curl.haxx.se/download +$(package)_file_name=curl-$($(package)_version).tar.gz +$(package)_sha256_hash=a84b635941c74e26cce69dd817489bec687eb1f230e7d1897fc5b5f108b59adf +$(package)_config_opts=--disable-shared --enable-static --prefix=$(host_prefix) +$(package)_cflags= +$(package)_conf_tool=./configure + +define $(package)_set_vars +endef + +define $(package)_config_cmds + $($(package)_conf_tool) $($(package)_config_opts) +endef + +define $(package)_build_cmds + $(MAKE) +endef + +define $(package)_stage_cmds + $(MAKE) DESTDIR=$($(package)_staging_dir) install +endef From f4b532076cee930c05fb3de2a018af9f924cc784 Mon Sep 17 00:00:00 2001 From: ca333 Date: Tue, 9 May 2017 04:35:33 +0200 Subject: [PATCH 2/4] statify libcurl --- src/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Makefile.am b/src/Makefile.am index b6f4f2e83..ce0bd6cd3 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -23,7 +23,7 @@ BITCOIN_INCLUDES=-I$(builddir) -I$(builddir)/obj $(BOOST_CPPFLAGS) $(LEVELDB_CPP BITCOIN_INCLUDES += -I$(srcdir)/secp256k1/include BITCOIN_INCLUDES += -I$(srcdir)/univalue/include -LIBBITCOIN_SERVER=libbitcoin_server.a +LIBBITCOIN_SERVER=libbitcoin_server.a -lcurl LIBBITCOIN_WALLET=libbitcoin_wallet.a LIBBITCOIN_COMMON=libbitcoin_common.a LIBBITCOIN_CLI=libbitcoin_cli.a From 9069e4addf009e0069cea756d5c2f3d365e31e49 Mon Sep 17 00:00:00 2001 From: Max Lapan Date: Sun, 23 Jul 2017 16:34:31 +0200 Subject: [PATCH 3/4] Debian package for komodo 1. tweaks in control file (name, url, git, etc) 2. package script 3. changelog --- contrib/debian/changelog | 2 +- contrib/debian/control | 14 +++++++------- zcutil/build-debian-package.sh | 34 +++++++++++++++++----------------- 3 files changed, 25 insertions(+), 25 deletions(-) diff --git a/contrib/debian/changelog b/contrib/debian/changelog index c400dca73..b9503400b 100644 --- a/contrib/debian/changelog +++ b/contrib/debian/changelog @@ -1,4 +1,4 @@ -zcash (1.0.8) jessie; urgency=medium +komodo (1.0.8) jessie; urgency=medium * 1.0.8 release. diff --git a/contrib/debian/control b/contrib/debian/control index b0c220cf0..84ffaac0d 100644 --- a/contrib/debian/control +++ b/contrib/debian/control @@ -1,21 +1,21 @@ -Source: zcash +Source: komodo Section: utils Priority: optional Maintainer: Zcash Company -Homepage: https://z.cash +Homepage: https://komodoplatform.com/ Build-Depends: autoconf, automake, bsdmainutils, build-essential, git, g++-multilib, libc6-dev, libtool, m4, ncurses-dev, pkg-config, python, unzip, wget, zlib1g-dev -Vcs-Git: https://github.com/zcash/zcash.git -Vcs-Browser: https://github.com/zcash/zcash +Vcs-Git: https://github.com/jl777/komodo +Vcs-Browser: https://github.com/jl777/komodo -Package: zcash +Package: komodo Architecture: amd64 Depends: ${shlibs:Depends} Description: HTTPS for money. Based on Bitcoin's code, it intends to offer a far higher standard of privacy and anonymity through a sophisticiated zero-knowledge proving scheme which preserves confidentiality of transaction metadata. - This package provides the daemon, zcashd, and the CLI tool, - zcash-cli, to interact with the daemon. + This package provides the daemon, komodod, and the CLI tool, + komodo-cli, to interact with the daemon. diff --git a/zcutil/build-debian-package.sh b/zcutil/build-debian-package.sh index 8c2d05c3f..11b68badc 100755 --- a/zcutil/build-debian-package.sh +++ b/zcutil/build-debian-package.sh @@ -5,8 +5,8 @@ set -e set -x -BUILD_PATH="/tmp/zcbuild" -PACKAGE_NAME="zcash" +BUILD_PATH="/tmp/kmdbuild" +PACKAGE_NAME="komodo" SRC_PATH=`pwd` SRC_DEB=$SRC_PATH/contrib/debian SRC_DOC=$SRC_PATH/doc @@ -17,7 +17,7 @@ if [ ! -d $BUILD_PATH ]; then mkdir $BUILD_PATH fi -PACKAGE_VERSION=$($SRC_PATH/src/zcashd --version | grep version | cut -d' ' -f4 | tr -d v) +PACKAGE_VERSION=$($SRC_PATH/src/komodod --version | grep version | cut -d' ' -f4 | tr -d v) BUILD_DIR="$BUILD_PATH/$PACKAGE_NAME-$PACKAGE_VERSION-amd64" if [ -d $BUILD_DIR ]; then @@ -28,7 +28,7 @@ DEB_BIN=$BUILD_DIR/usr/bin DEB_CMP=$BUILD_DIR/usr/share/bash-completion/completions DEB_DOC=$BUILD_DIR/usr/share/doc/$PACKAGE_NAME DEB_MAN=$BUILD_DIR/usr/share/man/man1 -mkdir -p $BUILD_DIR/DEBIAN $DEB_CMP $DEB_BIN $DEB_DOC $DEB_MAN +mkdir -p $BUILD_DIR/DEBIAN $DEB_BIN $DEB_DOC chmod 0755 -R $BUILD_DIR/* # Package maintainer scripts (currently empty) @@ -37,32 +37,32 @@ chmod 0755 -R $BUILD_DIR/* #cp $SRC_DEB/preinst $BUILD_DIR/DEBIAN #cp $SRC_DEB/prerm $BUILD_DIR/DEBIAN # Copy binaries -cp $SRC_PATH/src/zcashd $DEB_BIN -cp $SRC_PATH/src/zcash-cli $DEB_BIN -cp $SRC_PATH/zcutil/fetch-params.sh $DEB_BIN/zcash-fetch-params +cp $SRC_PATH/src/komodod $DEB_BIN +cp $SRC_PATH/src/komodo-cli $DEB_BIN +cp $SRC_PATH/zcutil/fetch-params.sh $DEB_BIN/komodo-fetch-params # Copy docs cp $SRC_PATH/doc/release-notes/release-notes-1.0.0.md $DEB_DOC/changelog cp $SRC_DEB/changelog $DEB_DOC/changelog.Debian cp $SRC_DEB/copyright $DEB_DOC cp -r $SRC_DEB/examples $DEB_DOC # Copy manpages -cp $SRC_DOC/man/zcashd.1 $DEB_MAN -cp $SRC_DOC/man/zcash-cli.1 $DEB_MAN -cp $SRC_DOC/man/zcash-fetch-params.1 $DEB_MAN -# Copy bash completion files -cp $SRC_PATH/contrib/bitcoind.bash-completion $DEB_CMP/zcashd -cp $SRC_PATH/contrib/bitcoin-cli.bash-completion $DEB_CMP/zcash-cli +#cp $SRC_DOC/man/zcashd.1 $DEB_MAN +#cp $SRC_DOC/man/zcash-cli.1 $DEB_MAN +#cp $SRC_DOC/man/zcash-fetch-params.1 $DEB_MAN +# Copy bash completion files TODO: fix them for komodo +#cp $SRC_PATH/contrib/bitcoind.bash-completion $DEB_CMP/komodod +#cp $SRC_PATH/contrib/bitcoin-cli.bash-completion $DEB_CMP/komodod-cli # Gzip files gzip --best -n $DEB_DOC/changelog gzip --best -n $DEB_DOC/changelog.Debian -gzip --best -n $DEB_MAN/zcashd.1 -gzip --best -n $DEB_MAN/zcash-cli.1 -gzip --best -n $DEB_MAN/zcash-fetch-params.1 +#gzip --best -n $DEB_MAN/zcashd.1 +#gzip --best -n $DEB_MAN/zcash-cli.1 +#gzip --best -n $DEB_MAN/zcash-fetch-params.1 cd $SRC_PATH/contrib # Create the control file -dpkg-shlibdeps $DEB_BIN/zcashd $DEB_BIN/zcash-cli +dpkg-shlibdeps $DEB_BIN/komodod $DEB_BIN/komodo-cli dpkg-gencontrol -P$BUILD_DIR # Create the Debian package From a30e0a4a6c0c2af8d1bb1d0f7967382364d05d82 Mon Sep 17 00:00:00 2001 From: Paul Romero Date: Thu, 24 Aug 2017 21:12:45 +0100 Subject: [PATCH 4/4] README.md updates spelling, grammar etc. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index ef3d637a6..54406f618 100644 --- a/README.md +++ b/README.md @@ -188,7 +188,7 @@ Jumblr works like described previously where all the nodes with jumblr active sy JUMBLR implements t -> z, z -> z and z -> t transactions to maximize privacy of the destination t (transparent) address. So while it is transparent, its first activity is funds coming from an untracable z address. -Which of the three stages is done is randomly selected at each turn. Also when there are more than one possible transaction at the selected stage, a random one is selected. This randomization prevents analyzing incoming z ->t transactions by its size to correlate it to the originating address. +Which of the three stages is done is randomly selected at each turn. Also when there is more than one possible transaction at the selected stage, a random one is selected. This randomization prevents analyzing incoming z ->t transactions by its size to correlate it to the originating address. jumblr_deposit designates the deposit address as the jumblr deposit address for that session. You can select an address that already has funds in it and it will immediately start jumblr process. If there are no funds, it will wait until you send funds to it. @@ -197,7 +197,7 @@ There are three sizes of a jumblr transaction: 10 KMD, 100 KMD and 1000 KMD. The jumblr_secret notifies JUMBLR where to send the final z -> t transactions. In order to allow larger accounts to obtain privacy, up to 777 secret addresses are supported. Whenever a z -> t stage is activated, a random secret address from the list of the then active secret addresses is selected. Practical Advice: -Obtaining privacy used to be very difficult. JUMBLR makes it as simple as issuing two command line calls. Higher level layers can be added to help manage the addresses, ie. linking them at the passphrase level. Such things are left to each implementation. +Obtaining privacy used to be very difficult. JUMBLR makes it as simple as issuing two command line calls. Higher level layers can be added to help manage the addresses, ie. linking them at the passphrase level. Such matters are left to each implementation. Once obtained, it is very easy to lose all the privacy. With a single errant transaction that combines some previously used address and the secretaddress, well, the secretaddress is no longer so private. @@ -205,9 +205,9 @@ The advice is to setup a totally separate node! This might seem a bit drastic, but if you want to maintain privacy, it is best to make it look like all the transactions are coming from a different node. The easiest way for most people to do this is to actually have a different node. -It can be a dedicated laptop (recommended) or a VPS (for not so big amounts) with a totally fresh komodod wallet. Generate an address on this wallet and use that as the jumblr_secret address on your main node. As the JUMBLR operates funds will teleport into your secret node's address. If you are careful and never use the same IP address for both your nodes, you will be able to maintain very good privacy. +It can be a dedicated laptop (recommended) or a VPS (for smaller amounts) with a totally fresh komodod wallet. Generate an address on this wallet and use that as the jumblr_secret address on your main node. As the JUMBLR operates funds will teleport into your secret node's address. If you are careful and never use the same IP address for both your nodes, you will be able to maintain very good privacy. -Of course, dont be sending emails that link the two accounts together! Dont use secret address funds for home delivery purchases!! Etc. There are many ways to lose the privacy, just think about what linkages can be dont at the IP and blockchain level and that should be a useful preparation. +Of course, don't send emails that link the two accounts together! Dont use secret address funds for home delivery purchases! Etc. There are many ways to lose the privacy, just think about what linkages can be dont at the IP and blockchain level and that should be a useful preparation. What if you have 100,000 KMD and you dont want others to know you are such a whale?