0lt and 0x addresses (New upcoming Frankenstein update with OLVM)

In order to make OLVM compatible with such instruments as truffle, remix, hardhat etc. and with wallets like Metamask, MyEtherWallet etc. (or briefly web3 wallets), 0x will be used in parallel with 0lt prefix. Technically the main important part of an address is the last 20 bytes (of 40 last strings).

Let's take a look example scenario below:

Some OneLedgerian user (Alice) with the address 0ltc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 (created via OneWallet) and wants to send his friend (Bob) 10 OLT tokens, but Bob has a wallet in the MetaMask. Bob has an address in his wallet 0xdac17f958d2ee523a2206206994597c13d831ec7. So in order to send OLT tokens to Bob, Alice will change prefix from 0x to 0lt (0ltdac17f958d2ee523a2206206994597c13d831ec7 instead of 0xdac17f958d2ee523a2206206994597c13d831ec7) and she could make this transfer. So the main important part is this - dac17f958d2ee523a2206206994597c13d831ec7 (last 40 strings).

Bob imagined that 10 OLT for him was too much and he want to send it back to Alice 7 OLT. So Bob could do send back to Alice with several ways:

1. Take a look in MetaMask history the Alice address, copy it and send;
2. Bob could ask Alice address from OneWallet and she could provide her address - 0ltc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2, so Bob could take it, remove 0lt prefix and provide recipient as c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 (or 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2). When transaction will be mined, Alice will receive her 7 OLT on OneWallet address 0ltc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2.