aragonOS icon indicating copy to clipboard operation
aragonOS copied to clipboard

(Aragon 1) Reference implementation for aragonOS: a Solidity framework for building complex dApps and protocols

Results 63 aragonOS issues
Sort by recently updated
recently updated
newest added

See [changes with [email protected]](https://solidity.readthedocs.io/en/v0.6.0/060-breaking-changes.html). It would be nice to support both 0.5.x and 0.6.x versions, but at the moment, it seems non-trivial due to the requirement of `virtual` and `override`...

enhancement

## Preamble Similar to some discussions in https://github.com/aragon/aragonOS/issues/546, but generalized to also work for already deployed organizations who may want to do many permission changes at once (e.g. a permissions...

enhancement
component: acl

A few things: - User input should be restricted, and checked to only be within a certain bounds / certain `OP`s - Potential infinite loops may occur in the ACL...

audit: whg
priority: low

## Option 1 Allow app developers to selfdestruct an app contract (the deployed library that proxies rely on). This would force all organizations using the app to upgrade (`kernel.setAppCode(...)`) to...

research
audit: whg

Following up https://github.com/aragon/aragonOS/pull/579/files#diff-325598653bbd8046a79c33ddabaa86e1L35

enhancement
research
component: acl

At the moment, every time that we forward a call using `DelegateProxy`, 10k gas are not forwarded. When multiple `DelegateProxy.delegatedFwd` are executed in one transaction (in an aragonOS call with...

research

Currently, AppProxies are assigned an `appId` that is assumed to never be changed. While this has so far made it easy to validate an AppProxy's deployment and simplified various points...

enhancement

As solc gets updated, users are increasingly frustrated that they are not able to build upon and integrate with aragonOS contracts which are pinned to 0.4.24. Instead of updating the...

Looks like this was looked over as part of 0.6. We should make sure to revoke the `APP_MANAGER_ROLE` permission that's needed by the factory when creating new aragonPM instances.

bug

A lot of templates use `acl.createPermission()` and `acl.grantPermission()` many, many times. The overhead of each call is quite high, requiring 10-30 duplicate `auth`, `noPermissionManager`, and `onlyPermissionManager` checks, as well as...

enhancement
research