Basically having a trusted Decentralized Password Manager AND Password Generator is important.........




INTRODUCTION:

This is a 2-Factor NEXUS Wallet Login Password and Tidecoin PRE-Quantum Wallet.dat OpenSSL ENC Fri-Manual




Tidecoin OpenSSL Command Line Encryption Instructions for Cloud Storage (Non-Post Quantum Encryption)  Also make sure Whole wallet Encryption is Enabled also!




PART:1


Encryption Command using ChaCha20 Encryption


openssl enc -e -pbkdf2 -chacha20 -md sha512 -in /home/COMPUTER-NAME-HERE/TIDE.dat -out /home/COMPUTER-NAME-HERE/TIDE.dat.enc



Decryption Command using ChaCha20 Encryption


openssl enc -d -pbkdf2 -chacha20 -md sha512 -in /home/COMPUTER-NAME-HERE/TIDE.dat.enc -out /home/COMPUTER-NAME-HERE/TIDE.dat



Hopefully Son the OpenSSL and PQ-Clean Github will support Post-Quantum Encryption Algo for the OpenSSL .ENC function for files!


For Full list of Variables type in Command Line Terminal using CTRL T to start Terminal


openssl enc --help






PART:2




For OpenSSL ENC function Passwords it is encouraged to use a generated Address from Tidecoin Wallet using the RipMd180 Encryption cypher to autogenerate the RANDOM Hash PASSWORD FOR US

Tidcoin Address

TNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATs



This TDC address is going to be the Base for our OpenSSL Encryption PassW*RD






PART:3



JUst run it through a RANDOM amount of Times AND Combine


 
Combine with other RIPMD180 generated Tidecoin ADDRESSES or other Crypto-Currency Wallet addresses you use for MULTI-FACTOR Authentication





This is the MINIMUM Amount of Encryption to use for Encrypting and then uploading a Wallet.dat file into the Cloud Storage or Decentralized Storage Platforms like FileCoin ect...........Chia..........




So if we used Our Tidecoin Generated Wallet with A Message Label it will become a lot easier to manage...............the Password for our Wallet.Dat file



TNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQ h5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyx csWhBWsMaATs



So we just created a RANDOM 5 repeat Password for our OpenSSL ENC function


PASSWORD=


TNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQ h5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyxcsWhBWsMaATsTNzm7L9YhMQh5zaP3TRRyx csWhBWsMaATs



This is What is used to Set-Up 2 Facotor Nexus Password AND Pin Also


The NEXUS Wallet Username MUST be easy to remember as it's CaSe sEnSiTivE


However Remember this will TIE Permentantly your NEXUS wallet to a 2-Factor Authentication using your Tidecoin Generated Address if we used the same TDC coin Password for our NEXUS Login Password AND Pin


The only way to break the Tidecoin Wallet.dat file providing the Nexus Password is to Create a New Nexus Wallet and send the NEXUS to a Fresh Wallet this will break the Permenent Tidecoin Wallet.dat file from your NEXUS Login Password AND Pin

If you add MULTI-Factor using Tidecoin And BTC/NMC than it would be something like



NEXUS Wallet LOGIN


Username:

Nexus


Password:

TDC Address Random Amount of Times RIPMD180 x 5



Pin:

BTC/NMC Address Random Amount of Times RIPMD180 x 5



Conversely



Password:

BTC/NMC Address Random Amount of Times RIPMD180 x 5



Pin:

TDC Address Random Amount of Times RIPMD180 x 5




MD180 x  5 =  900 Bit Long Password






After Encryption for 2-or More Onion Layers using Multi-TDC or BTC/NMC RIPMD180 Addresses for MULTI-FACTOR encryption


If your worried about torture to unfold your pass key, using MULTI-Facotor is the only way to not divulge the Key Pass.........

As once The Torture begins it's simple not possible for the Mind to Even Process it anymore as it is a matter of Stress level which cannot be achieved under torture conditions to produce the password Sequence.................................




thanks to Vlad2Vlad


Maybe someone or other noticed that the "Entry" or Tidecoin Wallet.dat requires unique way to access it...............


Vlad2Vlad sparked the idea of using Namecoin..........Basically Namecoin allows using easy to REMEMBER .bit human readable names for our First Hop Onion Encryption


Basically the idea is Namecoin Explorer https://www.namebrow.se/ and search our Human Readable .Bit domains.....


These domains don't even need to be ours to use it can be a combination of some others

Doing a search for Army

https://www.namebrow.se/name/d/Army/

This lists all the record updates for this entry.........

The Name_New Transaction is all encoded into the Blockchain............


Here it shows the RipMD180 Address that we can use for our Password Base for our OpenSSL ENC Password

Basically we can choose from 3 different RipMD180 addresses from 2 different d/Army Namecoin .Bit entries



We could basically use the Transaction ID or Input Scripts or RipMD180 Name Coin Addresses


Obviously it can be as simple or complex as desired!


It's not hard to throw in !!!!!!!!!!!!!!!!!!!!!!!! into passwords also or ?   

It's all a personal preference