menu
Channels
# All channels
view-forward
# Announcements
view-forward
# App development
view-forward
# Aragon Agent
view-forward
# Aragon Client
view-forward
# Aragon Connect
view-forward
# aragonOS
view-forward
# aragonUI
view-forward
# Feature requests
view-forward
Team

Do I need to change the app address?

April 1, 2020 at 5:16pm

Do I need to change the app address?

April 1, 2020 at 5:16pm
I've deployed my app reward.open.aragonpm.eth on Rinkeby from the default Rinkeby account 0xb4124cEB3451635DAcedd11767f004d8a28c6eE7. Now I suspect that anybody can overwrite it and I cannot change the account associated with reward.open.aragonpm.eth. So I need to allocate a new *.open.aragonpm.eth address. Right?

April 1, 2020 at 5:59pm
Hi Victor. Yes using your own private account is always a good idea. However, you don't need to publish your app to a new subdomain to fix that. You can simply use the aragon apm grant command to grant the permission to another account. After this, you can manually call your repository's ACL to set a new permission manager and remove the permission from 0xb4124cEB3451635DAcedd11767f004d8a28c6eE7.
  • reply
  • like
"manually call your repository's ACL" How?
  • reply
  • like
Actually there should probably be a command for that in the CLI. Let me see what I can do.
  • reply
  • like
$ npx aragon apm grant 0xC62ce5310E175fcE50589550AF3e1a4bEDe34077 --env rinkeby
ℹ Fetching repository
ℹ Granting permission to publish on reward.open.aragonpm.eth for 0xC62ce5310E175fcE50589550AF3e1a4bEDe34077
(node:2292086) UnhandledPromiseRejectionWarning: Error: gas required exceeds allowance (9990236) or always failing transaction
at /home/porton/Projects/courts/node_modules/@truffle/hdwallet-provider/node_modules/web3-provider-engine/subproviders/provider.js:18:36
at XMLHttpRequest.request.onreadystatechange (/home/porton/Projects/courts/node_modules/web3-providers-http/src/index.js:96:13)
at XMLHttpRequestEventTarget.dispatchEvent (/home/porton/Projects/courts/node_modules/xhr2-cookies/xml-http-request-event-target.ts:44:13)
at XMLHttpRequest._setReadyState (/home/porton/Projects/courts/node_modules/xhr2-cookies/xml-http-request.ts:219:8)
at XMLHttpRequest._onHttpResponseEnd (/home/porton/Projects/courts/node_modules/xhr2-cookies/xml-http-request.ts:345:8)
at IncomingMessage.<anonymous> (/home/porton/Projects/courts/node_modules/xhr2-cookies/xml-http-request.ts:311:39)
at IncomingMessage.emit (events.js:194:15)
at endReadableNT (_stream_readable.js:1103:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:2292086) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
(node:2292086) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  • reply
  • like
I have this ^^^ error even despite much ETH on the 0xb4124cEB3451635DAcedd11767f004d8a28c6eE7 Rinkeby account I tried to use to grant the permission to another account
  • reply
  • like
Thanks for reporting this. Here is the Github issue if you would like to track its progress: https://github.com/aragon/aragon-cli/issues/1596
Edited
  • reply
  • like