This time, let’s look at how to differentiate between locality keys and non-locality keys.
– Locality key
With getkeyentangle, SORA addresses are entangled with Ethereum-style addresses, and these entangled addresses become hidden addresses. This means that using these hidden addresses, SORA addresses and Ethereum-style addresses are “strongly correlated.” This is why it’s called entanglement. Due to the nature of locality, its effective range is limited to one’s own wallet. However, the hash values recorded on the blockchain remain valid across the network. Therefore, if you are executing atomic swaps or bridges with your own assets, this key is sufficient.
– Non-locality key
When you need to use Ethereum-style addresses with other SORA wallets besides your own, a non-locality key is necessary. To convert a locality key into a non-locality key, a certain amount of SORA needs to be permanently locked.
A similar concept for easy understanding is like when you generate and use a new Ripple address, which requires a certain amount of lock-up, right? That’s the idea.
Converting to a non-locality key allows for sending and receiving funds just like with SORA addresses, while maintaining the same properties as a locality key.
Thus, if you can accept a certain amount of SORA’s permanent lock, it becomes possible to use an Ethereum-style address with a convenient non-locality key, treating it the same as a SORA address. In this way, we are considering how to facilitate interactions between different blockchains.
