FrogCoin is a blockchain project aimed at helping save our world's rainforests and other important environmental features.
The FrogCoin [FROG] Blockchain is an experimental smart contract platform that enables instant payments to anyone, anywhere in the world in a private, secure manner. FrogCoin [FROG] uses peer-to-peer blockchain technology developed by CryptoCoderz and SaltineChips to operate with no central authority: managing transactions, execution of contracts, and issuing money are carried out collectively by the network.
BVAC is a unique system that we developed and created in house just for Espers [ESP] and associated projects. This offers us the ability to store ANY data as a PNG or JPG, similarly to a QR code, with only three files being required as apposed to three entire libraries that QR codes require and the data storage is denser. If you would like to learn more about this feature feel free to reach out to CryptoCoderz or SaltineChips. The current proof of concept implementation is the ability to store and read a public receiving address as a 16x16 BVAC image. Users can share their public keys this way by simply sending each other the BVAC image of the pubkey created from the wallet and then the receiving part is able to load the image using the wallet and decode it into the pubkey once again.
VRX is designed from the ground up to integrate properly with the Velocity parameter enforcement system to ensure users no longer receive orphan blocks.
Ensuring FrogCoin stays as secure and robust as possible, we have implemented what's known as the Velocity block constraint system (developed by CryptoCoderz & SaltineChips). This system acts as a third and final check for both mined and peer-accepted blocks, ensuring that all parameters are strictly enforced.
Our network now operates by using "Demi-nodes" to help the wallet make informed decisions on how to treat a peer in the network or even other nodes that aren't trusted. Demi-nodes are a list of trusted nodes a user can define inside of the wallet. These user-defined trusted nodes then can be queried for specific data such as asking the Demi-node network wether or not a reorganization request from another peer is a valid one or something that should be rejected and then banned off the network to protect other peers. An adaptive self cleaning network as this continiously defends itself from any possible intrusion or attack while still keeping decentralization as the underlying focus by allowing users to define their own lists. This feature compliments the Velocity security system which goes beyond other blockchain's security methods to ensure no possibility of malformed blocks making it onto the chain even with something like a 51% attack.
Wish or bmw512 hashing algorithm is utilized for the Proof-of-Work function and also replaces much of the underlying codebase hashing functions as well that normally are SHA256. By doing so this codebase is able to be both exponentially lighter and more secure in comparison to reference implementations.
FrogCoin uses
libsecp256k1
libgmp
Boost1.74, OR Boost1.6+
Openssl1.02u, OR OpenSSL1.1.1q, OR OpenSSL3.0.5
Berkeley DB 6.2.32
QT5.15.2 (for GUI)
General Specs
Coin Name: Frog Coin
Ticker: FROG
Block Spacing: 2 Minutes
Stake Minimum Age: 60 Confirmations (PoS-v3) | 2 Hours (PoS-v2)
Block Reward: 225 FROG
PoW/PoS Reward: 150 FROG
MasterNode Reward: 70 FROG
Dev/donation: 5 FROG
MasterNode Collateral: 75,000 (500 blocks of 150 pow/pos)
Maximum Coin Count: 1 billion FROG
Premine Coin Count: 15 Million (used for - Discord Airdrop, Compititions, Coding, and operating costs)
Mineable/Mintable Coin Count: 985,000,000 FROG (16.9 year coin)
Port: 20995
RPC Port: 20925
sudo -i
cd ~; sudo fallocate -l 3G /swapfile; ls -lh /swapfile; sudo chmod 600 /swapfile; ls -lh /swapfile; sudo mkswap /swapfile; sudo swapon /swapfile; sudo swapon --show; sudo cp /etc/fstab /etc/fstab.bak; echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
cd ~; sudo apt-get install -y ntp git build-essential libssl-dev libdb-dev libdb++-dev libboost-all-dev libqrencode-dev libcurl4-openssl-dev curl libzip-dev; apt-get update -y; apt-get install -y git make automake build-essential libboost-all-dev; apt-get install -y yasm binutils libcurl4-openssl-dev openssl libssl-dev; sudo apt-get install -y libgmp-dev; sudo apt-get install -y libtool;
cd ~; wget http://download.oracle.com/berkeley-db/db-6.2.32.NC.tar.gz; tar zxf db-6.2.32.NC.tar.gz; cd db-6.2.32.NC/build_unix; ../dist/configure --enable-cxx --disable-shared; make; sudo make install; sudo ln -s /usr/local/BerkeleyDB.6.2/lib/libdb-6.2.so /usr/lib/libdb-6.2.so; sudo ln -s /usr/local/BerkeleyDB.6.2/lib/libdb_cxx-6.2.so /usr/lib/libdb_cxx-6.2.so; export BDB_INCLUDE_PATH="/usr/local/BerkeleyDB.6.2/include"; export BDB_LIB_PATH="/usr/local/BerkeleyDB.6.2/lib"
cd ~; git clone https://github.com/Frog-Coin/Frog-Coin-Core FrogCoin
cd ~; cd ~/FrogCoin/src; chmod a+x obj; chmod a+x leveldb/build_detect_platform; chmod a+x secp256k1; chmod a+x leveldb; chmod a+x ~/FrogCoin/src; chmod a+x ~/FrogCoin; make -f makefile.unix USE_UPNP=-; cd ~; cp -r ~/FrogCoin/src/FrogCoind /usr/local/bin/FrogCoind;
cd ~; sudo ufw allow 20995/tcp; sudo ufw allow 20925/tcp; sudo ufw allow 22/tcp; sudo mkdir ~/.FROG; cat << "CONFIG" >> ~/.FROG/FrogCoin.conf
listen=1
server=1
daemon=1
deminodes=1
demimaxdepth=200
testnet=0
rpcuser=FROGrpcuser
rpcpassword=SomeCrazyVeryVerySecurePasswordHere
rpcport=20925
port=20995
rpcconnect=127.0.0.1
rpcallowip=127.0.0.1
addnode=172.105.121.51:20995
addnode=173.230.156.35:20995
addnode=45.56.105.176:20995
addnode=86.48.24.194:20995
addnode=209.126.82.242:20995
CONFIG
chmod 700 ~/.FROG/FrogCoin.conf; chmod 700 ~/.FROG; ls -la ~/.FROG
cd ~; FrogCoind; FrogCoind getinfo
All previous steps must be completed first. (If you recompiling some other time you don't have to repeat previous steps.)
Install Qt dependencies:
sudo apt-get install -y qtcreator qtbase5-dev qttools5-dev qttools5-dev-tools qt5-qmake cmake
Install extended dependencies:
sudo apt-get install -y autoconf autotools-dev pkg-config zlib1g-dev
Qt Dependencies build and link (1 of 2):
wget https://ppa.launchpadcontent.net/linuxuprising/libpng12/ubuntu/pool/main/libp/libpng/libpng_1.2.54.orig.tar.xz; tar Jxfv libpng_1.2.54.orig.tar.xz; cd ~/libpng-1.2.54; ./configure; make; sudo make install; cd ~; sudo ln -s /usr/local/lib/libpng12.so.0.54.0 /usr/lib/libpng12.so; sudo ln -s /usr/local/lib/libpng12.so.0.54.0 /usr/lib/libpng12.so.0
Qt Dependencies build and link (2 of 2):
wget https://fukuchi.org/works/qrencode/qrencode-4.0.2.tar.gz; tar zxfv qrencode-4.0.2.tar.gz; cd ~/qrencode-4.0.2; ./configure; make; sudo make install; sudo ldconfig
Ubuntu Legacy Patch (Ubuntu 18.04 and older)
sudo apt-get install -y libevent-dev
cp -r ~/FrogCoin/src/qt/forms/signverifymessagedialog.ui.legacy_qt ~/FrogCoin/src/qt/forms/signverifymessagedialog.ui
cp -r ~/FrogCoin/src/qt/forms/rpcconsolesettings.ui.legacy_qt ~/FrogCoin/src/qt/forms/rpcconsolesettings.ui
cp -r ~/FrogCoin/src/qt/forms/rpcconsole.ui.legacy_qt ~/FrogCoin/src/qt/forms/rpcconsole.ui
Build FrogCoin Qt
cd ~/FrogCoin; qmake -qt=qt5 USE_UPNP=-; make
make clean -f makefile.unix USE_UPNP=-
make -f makefile.unix USE_UPNP=-
cd ~; cp -r ~/FrogCoin/src/FrogCoind /usr/local/bin
FrogCoin [FROG] is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
The master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of FrogCoin [FROG].
The contribution workflow is described in CONTRIBUTING.md.
The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.
Developer Discord can be found at https://discord.gg/MTJWM9eHVQ .
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check
There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
