interfacerproject / interfacerproject/zenflows
Resctrict economic events base to ownership
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 18
- Forks
- 4
- Avg merge
- 7m
- Merged PRs (30d)
- 2
Description
An authenticated user is able to perform an economic event, including transfer, on any economic resource, whether it belongs to him or not. This should be restricted in some way.
- Some economics event could be proposal until they were accept by both two agents involved?
- The right to execute economic events on a resource could be limited to the agent who has accountability over that resource?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the authenticated economic-event handling path and reviewing how resource ownership or accountability is represented; clarify whether proposals, dual acceptance, or accountability should govern authorization. Done means the policy is agreed, implemented, and tested for both owned and unowned resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100