Skip to content

Issues: sablier-labs/SRFs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10 Open 3 Closed
10 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Rewrite README with sunsetting context effort: medium Default level of effort. priority: 0 Do this first before everything else. This is critical and nothing works without this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#16 opened Oct 3, 2024 by PaulRBerg
@PaulRBerg
The parameters for burn are redundant effort: high Large or difficult task. priority: 1 This is important. It should be dealt with shortly. type: refactor Change that neither fixes a bug nor adds a feature. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#15 opened Jul 24, 2024 by PaulRBerg
Bridged token effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#14 opened May 28, 2024 by PaulRBerg
Study useful ERC-20 extensions and bake them into SRF-20 effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#12 opened May 20, 2024 by PaulRBerg
Explain ERC strategy effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#11 opened May 20, 2024 by PaulRBerg
Integrate Markdown lint tool effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: perf Change that improves performance. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#10 opened May 15, 2024 by PaulRBerg
Contract Administration Standard effort: medium Default level of effort. priority: 3 Nice-to-have. Willing to ship without this. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#6 opened May 11, 2024 by PaulRBerg
Vault Token effort: epic Multi-stage task that may require multiple PRs. priority: 3 Nice-to-have. Willing to ship without this. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#4 opened May 11, 2024 by PaulRBerg
Multi Native Token effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#3 opened May 11, 2024 by PaulRBerg
Mint and Burn effort: medium Default level of effort. priority: 0 Do this first before everything else. This is critical and nothing works without this. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#1 opened May 11, 2024 by PaulRBerg
@PaulRBerg
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.