Jump to content

Claim address ALL CAP question?


KarmaCoverage
 Share

Recommended Posts

How does the cryptography work when we put the claim address in the message field as ALL CAP, but the actual address recieving the FLR has lower case letters?

How does the Flare network know which letters are lower case? 

Link to comment
Share on other sites

10 minutes ago, KarmaCoverage said:

How does the cryptography work when we put the claim address in the message field as ALL CAP, but the actual address recieving the FLR has lower case letters?

How does the Flare network know which letters are lower case? 

Ethereum addresses are not case sensitive:

https://www.quora.com/Is-an-Ethereum-Wallet-address-case-sensitive#:~:text=addresses case sensitive%3F-,Ethereum addresses are displayed in HEX%2C so they are not,are the same in HEX.

Link to comment
Share on other sites

11 minutes ago, KarmaCoverage said:

How does the cryptography work when we put the claim address in the message field as ALL CAP, but the actual address recieving the FLR has lower case letters?

How does the Flare network know which letters are lower case? 

It's hexaecimal so 0123456789abcdef. A library can simply call, string.toLowerCase(key);

Link to comment
Share on other sites

I blinked several times at the supposed case-sensitivity of their addressing scheme, as well, initially.  Read some explanations that didn't make much sense.  I put everything in upper case, as it's supposed to be... we shall see!

These kids and their shift keys...

They probably use monitors that are in color, too.  They'll never know the warm, green glow... :)

Also, not sure why everyone is up in arms over Cathode Ray Tubes, lately... or why suddenly everyone in crypto seem to be going to S&M clubs and need to remember their "safe words."

Edited by NightJanitor
I'm so old, I remember when "theory" didn't mean "opinion." Damn "soft sciences." Get off my lawn!
Link to comment
Share on other sites

28 minutes ago, KarmaCoverage said:

Why was that design decision made?

Is there an advantage?

It's not a design decision really. The addresses are not strings. They are numbers in the hexadecimal system. 

  1. We use the decimal system everyday (i.e. base 10). That means, our numbers go from 0-9. Any numeric value is represented by digits between 0-9.
  2. The binary system (i.e. base 2) has only two numbers. 0 and 1. This is how computers operate at the lowest level. Either there is a signal, or there isn't.
  3. The hexadecimal system is base 16. It goes from 0-9 followed by a-f, where a to f letters are used as hexadecimal representation of the decimal numbers 10 ,11, 12, 13, 14 and 15.

For example, 0xD in hexadecimal is 13 in the decimal system or 1101 in the binary system.

Another example. 30 in the decimal system is 11110 in the binary system and 1E in the hexadecimal system (or more formally, 0x1E or 0x1e). The case sensitiveness of "e" has no value because it's not used as a letter here. It's just a representation of the decimal number 14, in the hexadecimal system. 

You'll notice that there are no alphabets beyond F in any Ethereum address.

And that's why a sample Ethereum address like 0xc0ffee254729296a45a3885639AC7E10F9d54979 is the same as 0xC0FFEE254729296A45A3885639AC7E10F9D54979. 

The address is not a string. It's a number. Hope this helps.

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.