Update REP Token Contract Address -- First Week of July about tokens

[tayvano]

@ligi Thanks for letting me know. Definitely doable on my end. I created this issue just as much for me as for you. 😉

cc @409H so you can follow this too

[ligi]

hey @tayvano - be aware I will be offline the first week of juli (festival) - but you should be able to merge - but perhaps give it a try before so there is no problem in the pipeline then ..-)

[ligi]

@tayvano Great! Was just wondering if we should do one test-merge before as I will not have the ability to login to github in this 2 weeks if there is some setting wrong here to do this ..-)

[ligi]

I just returned - is this still a thing?

[tayvano]

Hey hey! Hope your vacay was great and relaxing!

Just waiting on the address from Augur right now

Latest info:

a) New augur.net website launched today - check it out for an overview of Augur, the Forecast Foundation, bug bounties, and frequently asked questions.

b) REP migration is planned to begin at 11:01AM PT tomorrow, July 9th. At that time, the current REP contract will be frozen indefinitely. The migration will take place over the rest of the day. We do not have an exact estimation of how long the migration will take, this channel & Twitter will be updated during the process tomorrow.

c) Prior Augur App releases have been removed, the final release will be published tomorrow once the REP migration is complete. Blog posts coming in the morning.

[tayvano]

Hello,

We are writing to let you know that the REP token migration is confirmed to begin at 11:01AM PT. At this time, the current REP contract will be frozen indefinitely.

Current REP contract that will be frozen: 0xe94327d07fc17907b4db788e5adf2ed424addff6

https://medium.com/@AugurProject/rep-migration-deployment-122e7189779d

We will be conducting the automatic migration immediately after. We expect this process to take around 8 to 10 hours (higher end of the spectrum estimate) assuming all goes smoothly. The previous REP migration took about 3.5 hours, and there are now about double the amount of unique accounts that hold REP this time around.

I will follow up to let you know the new REP token contract address as soon as we have confirmed that the migration is complete and successful. Feel free to reach out to us at the @AugurProject twitter (DM), or join our Discord and DM (@tk) for any real-time communications or questions, or just reply to this email thread.

Thanks,

Tom

Forecast Foundation OU
[email protected]

[tayvano]

Hello,

The migration is complete, and Augur is deployed.

New REP token contract address: 0x1985365e9f78359a9B6AD760e32412f4a445E862

Announcement: https://medium.com/@AugurProject/augur-launches-794fa7f88c6a

Thank you for the cooperation during the migration. You can now update to the new REP token contract address above.

Please let me know if you have any questions.

Cheers,

The Forecast Foundation OU

Will open a PR to update in the AM. In bed atm.

[ligi]

cool - thanks for all the detailed info - will make the PR now - just not sure what to do with the old address - perhaps do a REPOLD token?
This seems to be something that happens often - perhaps we should even make a new field in the model - e.g. a boolean deprecated. So that we can better show in the UI that a token is deprecated.

[ligi]

cc @409H @gamalielhere @vikmeup - what do you think about a deprecated field in the token lists? Perhaps this should even have a field that links it to the new token? and perhaps a date field when the migration happened

[tayvano]

Agreed.

Digix (#102) now has two tokens as well due to contract upgrade. It should be noted that updating or changing an existing token like in these cases is not the same as duplicate symbols by different projects (which is another issue entirely)

I think there are actually three REP tokens now:

• First one that was used 2015/2016/2017? Locked a few months back due to Serpent bug

• Second one that was used until today

• This third one that was just deployed