• one additonal, special, parameter-less method must be added to the contract to set the contract owner to 0 address
• this method will be callable by anyone
• the only condition to be verified is that the transition_period has passed

we want to support both on-ramping and off-ramping. Does ERC-20 compliance suffice or do additional features need to be added to the contract (or one of the cooperating contracts in case of the modular approach) to support them?

UI should refresh upon changing network or account in Metamask.

NGNT should be able be set as MigrationAgent in the GNT.

This issue is done when:

• NGNT smart contract implements the MigrationAgent interface
• Automate tests show that it's possible to migrate funds to the new token

• Add GNT Deposit contract to deployment
• Show status of deposits in UI

Change in balance of NGNT, GNT, GNTB should trigger UI update.
Also changes on deposit should update UI.

• Simple UI, not according to designs yet
• Happy path only, so do not handle failed transactions yet
• No progress monitoring, just trigger the transaction and (optionally) update balances when transaction complete

Simple feature, but let's include app setup here.

Support deploy via Golem's multisig.

• When kill switch is activated, it's not possible to perform any operations on the token
• Kill switch can be activated only by owner
• Kill switch can be activated only in transition period

When transaction is started user sees modal with "Transaction in progress".

• spinner
• link to transaction on etherscan

Upon completing migration user should see a summary with:

• amount migrated
• link to transaction on etherscan
• link to main migration page (X)

After pressing Convert or Unwrap if the user has a balance in GNTb or locked tokens we will display a warning that he will need to convert them at a later date.

Configure CI build, including running tests.

Deployment of the frontend app should be done automatically to some cryptic URL.

Deploy development version of the app to netlify when master is changed.

Possible approaches:

• Maker (https://etherscan.io/address/0x6b175474e89094c44da98b954eedeac495271d0f#code)
• GSN
• a'la UL/gnosis safe (execution function that takes a user-signed transaction + possibly refund)
• ERC777

HTML/CSS, UI flow.

• User cancelled transaction in Metamask
• Not enough balance
• Other reasons
• Page reload

Feedback welcome:

https://www.figma.com/proto/iB182qTF2rXwZGAEZQCOW7/golem-wireframes?node-id=46%3A85&viewport=2343%2C582%2C0.6194624900817871&scaling=min-zoom

Deploy current version of GNTB token in scripts which prepare dev environment.

If window.ethereum is not available or window.ethereum.isMetaMask is false, ask the user to install MetaMask extension.

We want to have an environment for testing the migration app which is similar to Ethereum mainnet.

Open questions:

• which testnet to use? Ropsten because it's PoW?
• does Golem have contracts and accounts available for testing or do we deploy our own contract set?

As stated in migration scope doc:

We'd like to explore two main approaches:

1. modular - the new GNT contract is purely ERC-20 (plus kill switch feature described below) and any additional features are implemented using sister contracts that supplement the main one (similar to how currently GNTB supplements the original GNT with batching transactions)
2. monolithic - all the features described here are implemented in one, monolithic contract
3. hybrid - potentially, the final token contract can be a combination of the above - where some features beside the kill-switch are implemented in the base contract and some features are added in the add-on contracts

Ethworks should prepare an implementation proposal for both of those approaches alongside the main pros and cons for each one - or - if the hybrid solution is chosen - reasoning behind such decision.

Research output:

• Recommendation of approach with reasoning

Include contract addresses for MainNet in app configuration.

If we are connected to a wrong network then we show a message to the user, but disallow any other interactions.