Skip to content

Commit c635c2d

Browse files
author
JSKitty
committed
Corrected branding, urls and relevancy
URLs and Branding has been corrected, previous commits were simply 'find and replace' edits. Leading to "zenzocoin.io". Many other similar issues corrected.
1 parent 94e39e9 commit c635c2d

24 files changed

+108
-111
lines changed

CONTRIBUTING.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
Contributing to Zenzo Core
1+
Contributing to ZENZO Core
22
============================
33

4-
The Zenzo Core project operates an open contributor model where anyone is
4+
The ZENZO project operates an open contributor model where anyone is
55
welcome to contribute towards development in the form of peer review, testing
66
and patches. This document explains the practical process and guidelines for
77
contributing.

COPYING

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Copyright (c) 2009-2015 Bitcoin Developers
22
Copyright (c) 2014-2015 Dash Developers
33
Copyright (c) 2015-2017 The PIVX Developers
4-
Copyright (c) 2017 The Zenzo Developers
4+
Copyright (c) 2017-2019 The ZENZO Developers
55

66

77
Permission is hereby granted, free of charge, to any person obtaining a copy

INSTALL

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Building Zenzo
1+
Building ZENZO
22

33
Use the autogen script to prepare the build environment.
44

@@ -10,4 +10,4 @@ Always verify the signatures and checksums.
1010

1111
See doc/build-*.md for instructions on building zenzod,
1212
the intended-for-services, no-graphical-interface, reference
13-
implementation of Zenzo.
13+
implementation of ZENZO.

README.md

+14-11
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,30 @@
1-
### Zenzo is a fork of [PIVX](https://github.com/PIVX-Project/PIVX) that forked [Dash](https://github.com/dashpay/dash) that forked [Bitcoin](https://github.com/bitcoin/bitcoinp)
1+
### ZENZO is a fork of [PIVX](https://github.com/PIVX-Project/PIVX) that forked [Dash](https://github.com/dashpay/dash) that forked [Bitcoin](https://github.com/bitcoin/bitcoinp)
22

33

4-
# Zenzo Core Integration/Staging Repository
4+
# ZENZO Core Integration/Staging Repository
55

66

7-
ZENZO(ZNZ) is an open-source privacy focused digital
7+
ZENZO(ZNZ) is an open-source digital
88
currency based on Bitcoin's blockchain technology, Dash’s Masternodes,
9-
and Zerocoin’s Zerocash Protocol. Each of these elements was combined
10-
to create a powerful and innovative technology. ZENZO is also powered
9+
PIVX’s Zerocoin Protocol and general Codebase. Each of these elements was combined
10+
to create a powerful and innovative technology. ZENZO is also powered
1111
by Blackcoin Proof-of-Stake 3.0 and Bitcoin Core 0.10x code base, using Quark
1212
hashing algorithm with a block time of just 60 seconds.
1313

14-
A peer-to-peer digital currency that provides fast, zero cost
15-
payments to anywhere around the world, without any third-party
16-
intervention. ZENZO is a fully decentralized global payment network
14+
A peer-to-peer digital currency that provides fast, zero cost
15+
payments to anywhere around the world, without any third-party
16+
intervention. ZENZO is a fully decentralized global payment network
1717
allowing individuals to have full control of their finances.
1818

1919
Masternodes require a collateral of 15,000 ZNZ and can be run on the
2020
Tor network for greater privacy. All transactions on the network are fully
2121
verifiable with a built-in blockchain explorer within the software itself. The
2222
block reward ratio of staking to masternodes is 35:65.
2323

24-
**For more information, please visit [zenzo.io](http://www.zenzo.io).**
24+
The ZENZO(ZNZ) digital currency powers the monetary system behind ZENZO’s many
25+
use cases, such as the [ZENZO Arcade](https://arcade.zenzo.io)
26+
27+
**For more information, please visit [zenzo.io](https://www.zenzo.io).**
2528

2629
***
2730

@@ -39,8 +42,8 @@ block reward ratio of staking to masternodes is 35:65.
3942
<tr><td>Block Confirmation</td><td>10</td></tr>
4043
<tr><td>PoS Minimum Age</td><td>3 hours</td></tr>
4144
<tr><td>PoS Maximum Age</td><td>Ø</td></tr>
42-
<tr><td>Block Rewards (Staking)</td><td>35%</td></tr>
43-
<tr><td>Block Rewards (Masternodes)</td><td>65%</td></tr>
45+
<tr><td>Block Rewards (Staking)</td><td>35%</td></tr>
46+
<tr><td>Block Rewards (Masternodes)</td><td>65%</td></tr>
4447
</table>
4548

4649
### Block Rewards (ZNZ)

Zenzo_Install_Instructions.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
1-
# Zenzo
2-
Shell script to install a [Zenzo Masternode](https://zenzocoin.com/) on a Linux server running Ubuntu 16.04. Use it on your own risk.
1+
# ZENZO Masternode Instructions
2+
Shell script to install a [ZENZO Masternode](https://zenzo.io/) on a Linux server running Ubuntu 16.04. Use it on your own risk.
33
***
44

55
## Installation
66
```
7-
wget -q https://raw.githubusercontent.com/zenzocoin/zenzo/master/znz_install.sh
7+
wget -q https://raw.githubusercontent.com/Zenzo-Ecosystem/ZENZO-Core/master/zenzo_install.sh
88
99
bash znz_install.sh
1010
```
1111
***
1212

13-
## Desktop Wallet Setup
13+
## Desktop Wallet Setup
1414

1515
After the MN is up and running, you need to configure the desktop wallet accordingly. Here are the steps:
1616
1. Open the ZENZO(ZNZ) Desktop Wallet.
@@ -36,7 +36,7 @@ Alias Address Privkey TxHash TxIndex
3636
13. Alternatively, open **Debug Console** and type:
3737
```
3838
startmasternode "alias" "0" "my_mn"
39-
```
39+
```
4040
14. Login to your VPS and check your masternode status by running the following command:
4141
```
4242
zenzo-cli masternode status

configure.ac

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ define(_CLIENT_VERSION_REVISION, 0)
66
define(_CLIENT_VERSION_BUILD, 0)
77
define(_CLIENT_VERSION_IS_RELEASE, true)
88
define(_COPYRIGHT_YEAR, 2018)
9-
AC_INIT([Zenzo Core],[_CLIENT_VERSION_MAJOR._CLIENT_VERSION_MINOR._CLIENT_VERSION_REVISION],[www.zenzocoin.com],[zenzo])
9+
AC_INIT([Zenzo Core],[_CLIENT_VERSION_MAJOR._CLIENT_VERSION_MINOR._CLIENT_VERSION_REVISION],[www.zenzo.io],[zenzo])
1010
AC_CONFIG_SRCDIR([src/main.cpp])
1111
AC_CONFIG_HEADERS([src/config/zenzo-config.h])
1212
AC_CONFIG_AUX_DIR([build-aux])

contrib/gitian-descriptors/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Sanity checks:
2020

2121
Once you've got the right hardware and software:
2222

23-
git clone git://github.com/zenzocoin/zenzo.git
23+
git clone git://github.com/Zenzo-Ecosystem/ZENZO-Core.git
2424
git clone git://github.com/devrandom/gitian-builder.git
2525
mkdir gitian-builder/inputs
2626
cd gitian-builder/inputs

contrib/gitian-descriptors/gitian-aarch64.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ packages:
2525
- "python"
2626
reference_datetime: "2015-06-01 00:00:00"
2727
remotes:
28-
- "url": "https://github.com/zenzocoin/zenzo"
28+
- "url": "https://github.com/Zenzo-Ecosystem/ZENZO-Core"
2929
"dir": "zenzo"
3030
files: []
3131
script: |

contrib/gitian-descriptors/gitian-build.sh

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ osx=false
1717
SIGNER=NULL
1818
VERSION=
1919
commit=false
20-
url=https://github.com/zenzocoin/zenzo
20+
url=https://github.com/Zenzo-Ecosystem/ZENZO-Core
2121
proc=2
2222
mem=2000
2323
lxc=true
@@ -39,7 +39,7 @@ version Version number, commit, or branch to build. If building a commit or bra
3939
4040
Options:
4141
-c|--commit Indicate that the version argument is for a commit or branch
42-
-u|--url Specify the URL of the repository. Default is https://github.com/zenzocoin/zenzo
42+
-u|--url Specify the URL of the repository. Default is https://github.com/Zenzo-Ecosystem/ZENZO-Core
4343
-v|--verify Verify the gitian build
4444
-b|--build Do a gitian build
4545
-s|--sign Make signed binaries for Windows and Mac OSX

contrib/gitian-descriptors/gitian-linux.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ packages:
2929
- "python"
3030
reference_datetime: "2015-06-01 00:00:00"
3131
remotes:
32-
- "url": "https://github.com/zenzocoin/zenzo"
32+
- "url": "https://github.com/Zenzo-Ecosystem/ZENZO-Core"
3333
"dir": "zenzo"
3434
files: []
3535
script: |

contrib/gitian-descriptors/gitian-osx.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ packages:
2828
- "python-setuptools"
2929
- "fonts-tuffy"
3030
remotes:
31-
- "url": "https://github.com/zenzocoin/zenzo"
31+
- "url": "https://github.com/Zenzo-Ecosystem/ZENZO-Core"
3232
"dir": "zenzo"
3333
files:
3434
- "MacOSX10.11.sdk.tar.gz"

contrib/gitian-descriptors/gitian-rpi2.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ packages:
2020
- "python"
2121
reference_datetime: "2015-06-01 00:00:00"
2222
remotes:
23-
- "url": "https://github.com/zenzocoin/zenzo"
23+
- "url": "https://github.com/Zenzo-Ecosystem/ZENZO-Core"
2424
"dir": "zenzo"
2525
files:
2626
- "raspberrypi-tools.tar.gz"

contrib/gitian-descriptors/gitian-win.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ packages:
2222
- "ca-certificates"
2323
- "python"
2424
remotes:
25-
- "url": "https://github.com/zenzocoin/zenzo.git"
25+
- "url": "https://github.com/Zenzo-Ecosystem/ZENZO-Core.git"
2626
"dir": "zenzo"
2727
files: []
2828
script: |

doc/README.md

+6-14
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
1-
Zenzo Core
1+
ZENZO Core
22
=====================
33

44
Setup
55
---------------------
6-
[Zenzo Core](http://Zenzocoin.com) is the original Zenzo client and it builds the backbone of the network. However, it downloads and stores the entire history of Zenzo transactions; depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once.
6+
[ZENZO Core](https://zenzo.io) is the original ZENZO client and it builds the backbone of the network. However, it downloads and stores the entire history of ZENZO transactions; depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once.
77

88
Running
99
---------------------
10-
The following are some helpful notes on how to run Zenzo on your native platform.
10+
The following are some helpful notes on how to run ZENZO on your native platform.
1111

1212
### Unix
1313

@@ -26,22 +26,19 @@ Drag Zenzo-Qt to your applications folder, and then run Zenzo-Qt.
2626

2727
### Need Help?
2828

29-
* See the documentation at the [Zenzo Wiki](https://en.bitcoin.it/wiki/Main_Page) ***TODO***
30-
for help and more information.
31-
* Ask for help on [BitcoinTalk](https://bitcointalk.org/index.php) or on the [Zenzo Forum](http://Zenzocoin.com/).
32-
* Join one of our Discord groups [Zenzo Discord Groups](https://discord.gg/YcnvMqt).
29+
* Join our Discord Server [ZENZO Discord](https://discord.gg/nzGapAh).
30+
* Join our Telegram Group [ZENZO Telegram](https://t.me/Zenzo_Telegram).
3331

3432
Building
3533
---------------------
36-
The following are developer notes on how to build Zenzo on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
34+
The following are developer notes on how to build ZENZO Core on your native platform. They are NOT complete guides, but include notes on the necessary libraries, compile flags, etc.
3735

3836
- [OSX Build Notes](build-osx.md)
3937
- [Unix Build Notes](build-unix.md)
4038
- [Gitian Building Guide](gitian-building.md)
4139

4240
Development
4341
---------------------
44-
The Zenzo repo's [root README](https://github.com/eastcoastcrypto/Zenzo/blob/master/README.md) contains relevant information on the development process and automated testing.
4542

4643
- [Developer Notes](developer-notes.md)
4744
- [Multiwallet Qt Development](multiwallet-qt.md)
@@ -53,11 +50,6 @@ The Zenzo repo's [root README](https://github.com/eastcoastcrypto/Zenzo/blob/mas
5350
- [Unauthenticated REST Interface](REST-interface.md)
5451
- [Dnsseed Policy](dnsseed-policy.md)
5552

56-
### Resources
57-
58-
* Discuss on the [BitcoinTalk](https://bitcointalk.org/index.php?topic=1262920.0) .
59-
* Join the [Zenzo-Dev] Discord groups [Zenzo Discord Groups](https://discord.gg/YcnvMqt).
60-
6153
### Miscellaneous
6254
- [Assets Attribution](assets-attribution.md)
6355
- [Files](files.md)

doc/README_windows.txt

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
Zenzo Core
1+
ZENZO Core
22
=====================
33

44
Intro
55
-----
6-
Zenzo is a free open source peer-to-peer electronic cash system that is
6+
ZENZO is a free open source peer-to-peer electronic cash system that is
77
completely decentralized, without the need for a central server or trusted
88
parties. Users hold the crypto keys to their own money and transact directly
99
with each other, with the help of a P2P network to check for double-spending.
@@ -13,7 +13,7 @@ Setup
1313
-----
1414
Unpack the files into a directory and run zenzo-qt.exe.
1515

16-
Zenzo Core is the original Zenzo client and it builds the backbone of the network.
17-
However, it downloads and stores the entire history of Zenzo transactions;
16+
ZENZO Core is the original ZENZO client and it builds the backbone of the network.
17+
However, it downloads and stores the entire history of ZENZO transactions;
1818
depending on the speed of your computer and network connection, the synchronization
1919
process can take anywhere from a few hours to a day or more.

doc/build-osx.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Instructions: Homebrew
4444

4545
1. Clone the github tree to get the source code and go into the directory.
4646

47-
git clone https://github.com/zenzocoin/zenzo.git
47+
git clone https://github.com/Zenzo-Ecosystem/ZENZO-Core.git
4848
cd zenzo
4949

5050
2. Build zenzod:

doc/developer-notes.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -418,7 +418,7 @@ Git and github tips
418418
419419
[remote "upstream-pull"]
420420
fetch = +refs/pull/*:refs/remotes/upstream-pull/*
421-
url = [email protected]:eastcoastcrypto/Zenzo.git
421+
url = [email protected]:Zenzo-Ecosystem/ZENZO-Core.git
422422
423423
This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all`
424424
or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`,

doc/dnsseed-policy.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
Expectations for DNS Seed operators
22
====================================
33

4-
Zenzo Core attempts to minimize the level of trust in DNS seeds,
4+
ZENZO Core attempts to minimize the level of trust in DNS seeds,
55
but DNS seeds still pose a small amount of risk for the network.
66
As such, DNS seeds must be run by entities which have some minimum
7-
level of trust within the Zenzo community.
7+
level of trust within the ZENZO community.
88

9-
Other implementations of Zenzo software may also use the same
9+
Other implementations of ZENZO software may also use the same
1010
seeds and may be more exposed. In light of this exposure this
1111
document establishes some basic expectations for the expectations
1212
for the operation of dnsseeds.
@@ -18,7 +18,7 @@ DNS seed. Any hosting services contracted by the operator are
1818
equally expected to uphold these expectations.
1919

2020
1. The DNS seed results must consist exclusively of fairly selected and
21-
functioning Zenzo nodes from the public network to the best of the
21+
functioning ZENZO nodes from the public network to the best of the
2222
operators understanding and capability.
2323

2424
2. For the avoidance of doubt, the results may be randomized but must not
@@ -28,7 +28,7 @@ urgent technical necessity and disclosed.
2828
3. The results may not be served with a DNS TTL of less than one minute.
2929

3030
4. Any logging of DNS queries should be only that which is necessary
31-
for the operation of the service or urgent health of the Zenzo
31+
for the operation of the service or urgent health of the ZENZO
3232
network and must not be retained longer than necessary or disclosed
3333
to any third party.
3434

@@ -44,9 +44,9 @@ details of their operating practices.
4444
related to the DNS seed operation.
4545

4646
If these expectations cannot be satisfied the operator should
47-
discontinue providing services and contact the active Zenzo
48-
Core development team as well as posting on the
49-
[Zenzo Forum](https://zenzocoin.com).
47+
discontinue providing services and contact the active ZENZO
48+
Core development team as well as visiting the
49+
[ZENZO Website](https://zenzo.io).
5050

5151
Behavior outside of these expectations may be reasonable in some
5252
situations but should be discussed in public in advance.

0 commit comments

Comments
 (0)