Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rif token on rsk mainnet #305

Merged
merged 3 commits into from
Apr 21, 2020
Merged

rif token on rsk mainnet #305

merged 3 commits into from
Apr 21, 2020

Conversation

alebanzas
Copy link
Contributor

Implements EIP-1191 for checksum, extending EIP-55

Copy link
Member

@ligi ligi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! But to merge it the address must be in ERC-55 (filename and address field)

via CI: The address is not valid with ERC-55 checksum 0x2aCc95758f8b5F583470bA265Eb685a8f45fC9D5 expected: 0x2AcC95758f8b5F583470ba265EB685a8F45fC9D5

@ligi
Copy link
Member

ligi commented Jan 26, 2020

seems related: komputing/KEthereum#80

@jonathansmirnoff
Copy link
Contributor

@ligi because of the PR: komputing/KEthereum#85 was merged, I wanted to know how we can forward with this PR. Do I have to add the chainId? Thanks!

@ligi
Copy link
Member

ligi commented Apr 14, 2020

we have the chainId here: https://github.com/ethereum-lists/tokens/blob/master/src/main/kotlin/org/ethereum/lists/tokens/Main.kt#L13 no need to put it in the json.
What needs to happen: add a new field address_eip1191 in the CI scripts / README. We cannot directly change the behavior of the address field as upstream projects might stumble over it.
I will merge PRs implementing this - but I will not do them as I think EIP1191 is a horrible idea actualy.

@jonathansmirnoff
Copy link
Contributor

jonathansmirnoff commented Apr 14, 2020

Thanks for your response and I understand that you don't like the EIP1191.
I need more clarification about the steps that I should do:

@ligi
Copy link
Member

ligi commented Apr 14, 2020

as far as I see it is already there

yes

@jonathansmirnoff
Copy link
Contributor

@ligi because the PR #339 has been merged, do you think this PR can be merged? Thanks!

@ligi
Copy link
Member

ligi commented Apr 21, 2020

sure - can you rebase to master?

@jonathansmirnoff
Copy link
Contributor

sure - can you rebase to master?

Sure, I'll try to do it. If I can't do it because I didn't make this PR, I'll make another PR and ask to close this.

@jonathansmirnoff
Copy link
Contributor

Done! :)

@ligi ligi merged commit d916f1d into ethereum-lists:master Apr 21, 2020
@ligi
Copy link
Member

ligi commented Apr 21, 2020

merged ;-)

@jonathansmirnoff
Copy link
Contributor

Thanks so much for your help in this process!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants