BitCanna $BCNA Presentation & Invitational Tesnet tips — Imperator.co

🌿What is BitCanna?

BitCanna is an initiative supported by a strategic alliance of European cannabis market leaders under the moniker Bitcanna Alliance. This network brings together Europe’s most reputable seed banks and companies that serve over ten million visitors per month. With a common interest, they are committed to providing the best possible solutions to these challenges. Through shared expertise, they have succeeded in finding it.

⛓️What about Cosmos ?

They are now making the strong choice to switch to the Cosmos blockchain, commonly known as the internet of blockchains.
Cosmos apps and services connect using IBC, the Inter-Blockchain Communication protocol. This innovation enables you to freely exchange assets and data across sovereign, decentralized blockchains. In this case, BitCanna blockchain will be able to communicate with giants like Ethereum, Binance Chain, Polkadot, Cardano, and many more

However, to make this transition they need to do some testing and so they have launched the BitCanna Invitational Testnet in which Imperator.co is honored to participate! In the next part, we will reveal some tips to make this one go as smoothly as possible

🧪BitCanna Invitational Testnet tips

And here we are, since unaccustomed people also participate in the testnet, we thought it would be appropriate to share our experience via a small series of tips

✍Add your logo to your validator

Register on Keybase.io, add your logo, register a PGP key, and you are done! Your account should look like this:

Go back to your terminal, where you launched the validator creation command and run:

bcnad tx staking edit-validator - - identiy <your PGP key>  -- chain-id bitcanna-testnet-2 - - from <your wallet name> - - gas-price 0.01ubcna   -- gas-adjustement 1.5 -- gas auto
[Unit]

This will refer to an existing Keybase account and use its associated information (e.g. avatar image) as metadata for your validator. And this is it:

⚙️Relaunch automatically your node

# /etc/systemd/system/bitcanna.service
[Unit]
Description=Bitcanna Node
After=network.target

[Service]
Type=simple
User=<your user>
WorkingDirectory=<your working directory>
ExecStart=<bcnad binary location>/bcnad start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096

[Install]
WantedBy=multi-user.target

Save this file into /etc/systemd/system as “bitcanna.service”. And run “systemctl start bitcanna.service” and you are done!

🔐Security tips

  • Vote on governance proposals
  • Create governance proposals from your validator’s identity
  • Transfer tokens from your validator’s balance
  • Modify validator details (moniker, commission, details)
  • Sign any transaction from this account
  • And many mores

A lost key is considered a serious and irreparable flaw as the holder can act on behalf of your validator. Here is now a little guide on how to enable the two authentication factor on your node: this will add another layer of security to your machine.

Note: this is just a basic security tutorial, it is highly recommended to use a KSM to protect your key

Multi-factor authentication is a method of confirming your identity using at least two different ways of authentication. The most common and easiest to implement is via a one-time-passcode generated by a special mobile app.

We will use the Google Authenticator app available for Android (in the Play Store) and iOS (in iTunes) to generate authentication codes.

#Start with: 
sudo apt install libpam-google-authenticator
#To make SSH use the Google Authenticator PAM module, add the following line to the /etc/pam.d/sshd file:auth required pam_google_authenticator.so------------------------------------------------------#restart the sshd daemon:sudo systemctl restart sshd.service------------------------------------------------------#Modify /etc/ssh/sshd_config – change ChallengeResponseAuthentication from no to yes, so this part of the file looks like this:

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no # CHANGE THIS TO YES

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes
------------------------------------------------------#In a terminal, run the google-authenticator command.It will ask you a series of questions, answer yes on each of them------------------------------------------------------You may have noticed the giant QR code that appeared during the process, underneath are your emergency scratch codes to be used if you don’t have access to your phone: write them down on paper and keep them in a safe place.------------------------------------------------------On your Google Authenticator: Touch the Add icon (+) and select “Scan a barcode”. Use phone camera to scan QR code.

Now, when you will try to log in to your SSH shell, you will be asked for an authentication key in addition to a traditional password.

We provide reliable infrastructure for next generation technologies $XKI $XPRT