teamforus / research

Shared learning of decentralized development.

https://forus.io

The Unlicense

27 stars 5 forks source link

POC-001: Updates of smart contracts #15

Closed jamalv closed 5 years ago

jamalv commented 7 years ago

moved to poc folder

jamalv commented 7 years ago

@jakkodejong I heard trough the grapevine that you are planning to take on this one?

jakkodejong commented 7 years ago

Yes, I will pick this up.

jakkodejong commented 7 years ago

Filled in template at 2017-nov-14 16:22h

jamalv commented 7 years ago

Great! This will be POC2, please create a new feature branch with a folder named poc2_update_smart_contracts and add the contents of this issue to the readme.

jamalv commented 6 years ago

@maxvisser @martijndoornik is this achieved by using embark?

maxvisser commented 6 years ago

for development Embark automatically deploys changes to your local geth instance. Issue still stands for when deploying update to mainnet. Somehow your front end should communicate through a proxy contract to your smart contracts, when you deploy changes, you can edit the proxy to point to the newly deployed contracts.

maxvisser commented 6 years ago

https://gist.github.com/GNSPS/ba7b88565c947cfd781d44cf469c2ddb maybe this can be of use

jamalv commented 6 years ago

https://github.com/ethereum/EIPs/issues/121

maxvisser commented 6 years ago

maybe we should try making an ENS address for a smart contract. Let the front-end point towards ENS and ENS points to the current smartcontract.

martijndoornik commented 5 years ago

Is this still relevant? If so, reopen