Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / daostack/access_control issues and pull requests
#44 - new release + docs + publish on ci
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
#43 - Publish to NPM
Issue -
State: closed - Opened by tarrencev over 6 years ago
- 2 comments
#42 - rm ANYTHING and lockId
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
#41 - Prepare for EIP submission
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
#40 - Changed uint80 to uint
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
#39 - uint80 is more expansive on read(unlock) and cheaper in write(lock) re uint256
Issue -
State: closed - Opened by orenyodfat over 6 years ago
- 3 comments
#38 - Groups
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
- 9 comments
Labels: enhancement
#37 - House keeping
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
Labels: enhancement
#36 - should `isValidExpiration` be public?
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: question
#35 - Start time
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
- 3 comments
Labels: enhancement
#34 - Usage example + convenience methods
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
- 1 comment
Labels: documentation
#33 - In addition to `expiration`, have a `startTime`
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: enhancement
#32 - ANYTHING is unnecessary
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 8 comments
#31 - Add test for the ANYTHING property
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 2 comments
#30 - Formalize a language and interpreter for defining the lock criterion
Issue -
State: open - Opened by ben-kaufman over 6 years ago
- 7 comments
Labels: enhancement
#29 - Non revoke-able keys
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 5 comments
#28 - Making an EIP
Issue -
State: closed - Opened by tsuberim over 6 years ago
Labels: documentation
#27 - Blog post
Issue -
State: closed - Opened by tsuberim over 6 years ago
Labels: documentation
#26 - Documentation
Issue -
State: open - Opened by tsuberim over 6 years ago
Labels: documentation
#25 - Examples
Issue -
State: open - Opened by tsuberim over 6 years ago
Labels: documentation
#24 - Fixed mistake in test case
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
- 1 comment
#23 - Modularized the Interface
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
- 7 comments
#22 - Cleanup
Pull Request -
State: closed - Opened by tsuberim over 6 years ago
- 9 comments
Labels: enhancement
#21 - Added tests
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
- 1 comment
#20 - Moved ProtectedController to test directory
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
#19 - ANYTHING constant should be changed
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 2 comments
#18 - Merge Travis from development to master
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
- 2 comments
#17 - Why toBytes function is needed at protected.sol ?
Issue -
State: closed - Opened by orenyodfat over 6 years ago
- 3 comments
#16 - Remove import math.sol from Protected.sol
Issue -
State: closed - Opened by orenyodfat over 6 years ago
- 3 comments
#15 - Added Travis CI
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
#14 - Make `expiration` and `uses` each 127 bit so that the entire key can fit in a single 256 bit word
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 9 comments
Labels: enhancement
#13 - Think more about the `Use` event
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: question
#12 - Allow revoking a lock id
Issue -
State: open - Opened by tsuberim over 6 years ago
- 1 comment
Labels: enhancement
#11 - Solve capability escalation problem
Pull Request -
State: closed - Opened by ben-kaufman over 6 years ago
- 9 comments
#10 - Multiple Keys Management
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 5 comments
#9 - `expiration` should be a block number instead of timestamp
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 1 comment
Labels: enhancement
#8 - key can be used twice if specified in more than one `only`
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 1 comment
Labels: bug
#7 - `only` with array literal won't compile
Issue -
State: closed - Opened by ben-kaufman over 6 years ago
- 2 comments
#6 - Import code from Arc and make it compile
Issue -
State: closed - Opened by tsuberim over 6 years ago
Labels: task
#5 - Use the contract as a service pattern
Issue -
State: open - Opened by tsuberim over 6 years ago
- 3 comments
Labels: enhancement
#4 - Implement EIP165
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 1 comment
Labels: enhancement
#3 - Solve capability escalation issue
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: enhancement
#2 - How to allow users to specify the key?
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: question
#1 - Research on similar ideas
Issue -
State: closed - Opened by tsuberim over 6 years ago
- 2 comments
Labels: research