# Peerplays Development FAQs ## Bitcoin-SON ### :question: How can I generate Bitcoin addresses? Command: ``` ./bitcoin-cli -rpcuser=1 -rpcpassword=1 -rpcwallet=default getnewaddress ``` References: {% embed url="" %} {% embed url="" %} ### :question: How to get TEST BTC on the REGTEST network? From developer.bitcoin.org... > For situations where interaction with random peers and blocks is unnecessary or unwanted, Bitcoin Core’s regression test mode (regtest mode) lets you instantly create a brand-new private block chain with the same basic rules as testnet—but one major difference: you choose when to create new blocks, so you have complete control over the environment. > > Many developers consider regtest mode the preferred way to develop new applications. The following example will let you create a regtest environment after you first [configure bitcoind](https://developer.bitcoin.org/examples/index.html). ``` bitcoind -regtest -daemon ``` > Start `bitcoind` in regtest mode to create a private block chain. ``` bitcoin-cli -regtest generatetoaddress 101 $(bitcoin-cli -regtest getnewaddress) ``` > Generate 101 blocks using a special [RPC](https://developer.bitcoin.org/reference/rpc/index.html) which is only available in regtest mode. This takes less than a second on a generic PC. Because this is a new block chain using Bitcoin’s default rules, the first blocks pay a block reward of 50 bitcoins. Unlike mainnet, in regtest mode only the first 150 blocks pay a reward of 50 bitcoins. However, a block must have 100 confirmations before that reward can be spent, so we generate 101 blocks to get access to the coinbase transaction from block #1. ``` bitcoin-cli -regtest getbalance ``` > Verify that we now have 50 bitcoins available to spend. > > You can now use Bitcoin Core [RPCs](https://developer.bitcoin.org/reference/rpc/index.html) prefixed with `bitcoin-cli -regtest`. > > Regtest wallets and block chain state (chainstate) are saved in the `regtest` subdirectory of the Bitcoin Core configuration directory. You can safely delete the `regtest` subdirectory and restart Bitcoin Core to start a new regtest. (See the [Developer Examples Introduction](https://developer.bitcoin.org/examples/index.html) for default configuration directory locations on various operating systems. Always back up mainnet wallets before performing dangerous operations such as deleting.) Reference: {% embed url="" %} ### :question: How can I generate / find the public key for a Bitcoin address? Command: ``` ./bitcoin-cli -rpcuser=1 -rpcpassword=1 -rpcwallet=default getaddressinfo "address" ``` References: {% embed url="" %} {% embed url="" %} ### :question: If funds are deposited to a Bitcoin address, will there be logs? ### :question: What is the cli\_command to generate a Bitcoin deposit address in the Peerplays blockchain? Command Definition: {% code title="return type, namespace, & method" %} ```cpp signed_transaction graphene::wallet::wallet_api::add_sidechain_address( string account, sidechain_type sidechain, string deposit_public_key, string withdraw_public_key, string withdraw_address, bool broadcast); ``` {% endcode %} Command Structure: ``` add_sidechain_address true ``` Command Example: ``` add_sidechain_address myaccount123 bitcoin 03c8d1c33727788ca1f61e13bdeca0127047527a0880c816056b4015d6e2d36c1e 025cee805793fd94ca1933cc28ef9c065addd0e256195f1a541be0cd21867ac1c5 1EToWbQDvEwwie6jYsuM7WkZnh7rCn5Ecu true ``` Reference: {% embed url="" %} ### :question: If a Bitcoin deposit address is created for a Peerplays address (account) what are the logs in the Peerplays blockchain? ### :question: How to run a Peerplays blockchain node with RPC debugging turned on? ## Gamified Proof of Stake (GPOS) ### :question: What are the blockchain logs when a successful GPOS Vesting is done? ## Faucet ### :question: What are the logs in faucet when an account is successfully created? One can use **Curl** command or **POSTMAN** in order to create a new account in the Faucet. With **Curl** you can do the following: ``` curl -X POST http://:/api/v1/accounts -H 'content-type: application/json' -d '{ "account": { "name": "", "owner_key": "TEST5WaszCsqVN9hDkXZPMyiUib3dyrEA4yd5kSMgu28Wz47B3wUqa", "active_key": "TEST5TPTziKkLexhVKsQKtSpo4bAv5RnB8oXcG4sMHEwCcTf3r7dqE", "memo_key": "TEST5TPTziKkLexhVKsQKtSpo4bAv5RnB8oXcG4sMHEwCcTf3r7dqE" } }' ``` {% hint style="info" %} **IP\_ADDRESS** should be **127.0.0.1** or **localhost** when running it directly in a VM or on your local machine. **`owner_key`**, **`active_key`**, **`memo_key`** should start with **TEST** on testnet, and it should be **PPY** on mainnet. {% endhint %} If the result of the above is successful, there should be output like this: ``` { "account": { "active_key": "TEST5TPTziKkLexhVKsQKtSpo4bAv5RnB8oXcG4sMHEwCcTf3r7dqE", "memo_key": "TEST5TPTziKkLexhVKsQKtSpo4bAv5RnB8oXcG4sMHEwCcTf3r7dqE", "name": "account-name4", "owner_key": "TEST5WaszCsqVN9hDkXZPMyiUib3dyrEA4yd5kSMgu28Wz47B3wUqa", "referrer": "nathan" } } ``` And in case of any error, it will be following (i.e. duplicate account): ``` {"error":{"base":["Account exists"]}} ``` You can also track the logs in **Faucet** container, with the following command: ``` docker logs --follow For example: docker logs --follow 47c101add138 ``` And look for logs when receiving **Create Account** requests, with **200** status code as a result. ``` 37.252.95.183 - - [06/Oct/2021 17:55:29] "OPTIONS /api/v1/accounts HTTP/1.1" 200 - 37.252.95.183 - - [06/Oct/2021 17:55:30] "POST /api/v1/accounts HTTP/1.1" 200 - ``` ## Peerplays DEX ### :question: How do I setup a local DEX UI project? This works with a Faucet and a local QA environment (create account & login). First, pull the DEX repository from [here](https://gitlab.com/PBSA/peerplays-dex/-/tree/develop). After setting up the project, update the following variables in .env file: ``` FAUCET_URL='http://:5000/api/v1/accounts' BLOCKCHAIN_ENDPOINTS='ws://:8090/api' ``` {% hint style="info" %} **IP\_ADDRESS** should be **127.0.0.1** or **localhost** when running it directly on your local machine. {% endhint %} ## Peerplays QA Environment ### :question: How do I transfer funds between accounts in a Peerplays QA Environment network? In the QA environment setup by instructions in [here](https://gitlab.com/PBSA/tools-libs/peerplays-utils/-/tree/master/peerplays-qa-environment), execute commands in Peerplays01 container with the following: ``` docker exec -it peerplaysqaenvironment_peerplays01_1 /bin/bash ``` Then running into account’s wallet: ``` ./cli_wallet list_account_balances For example: ./cli_wallet list_account_balances armin ``` Unlock the wallet with the default password (which is "password"): ``` unlock password ``` Get the private key for active key (public key): ``` get_private_key_from_password "" active "" ``` {% hint style="info" %} ACCOUNT\_PASSWORD is the password defined when creating account in DEX UI. {% endhint %} Import the private key returned from previous step: ``` import_key For example: import_key armin 5JckQ6g57P9YyyumHCRj1cNbHTiMEUVA2HjVDJqXDDPYizEaAMu ``` Finally transfer with the following: ``` transfer TEST "" true For example: transfer armin nathan 10 TEST "" true ``` {% hint style="info" %} memo key should be empty string for it to work.\ With list\_core\_accounts command you can check all account’s balances. {% endhint %} ### ❓How to ensure QA environment is healthy ? If you are getting "Generated block..." and "Scheduled SON..." messages, and SON last active timestamps are updated regularly, SON network is working as expected. To get last active timestamp, first use get\_object 1.33.X (ids are 1.33.0, 1.33.1, ... 1.33.6), statistic object id will be there, and then use get\_object statistic\_object\_id (I believe ids are 2.25.0, 2.25.1, ... 2.25.6). All timestamps should be in a last few minutes.