-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
packages/jellyfish-api-core
: Add DFI2203 Futures work
#1268
Comments
@surangap: Thanks for opening an issue, it is currently awaiting triage. The triage/accepted label can be added by foundation members by writing /triage accepted in a comment. DetailsI am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository. |
@surangap: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this! You can add area labels by leaving a DetailsI am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository. |
Futures RPC APIsfutureswap: @surangap #1273 dftxfutureswap/withdrawfutureswap: @surangap @jingyi2811 #1329 |
After reading the python code, I believe futureswap and withdrawfutureswap RPCs are harder and you may spend more time on them. Therefore, I pick the rest of the RPCs |
What would you like to be added:
map endpoints related to DeFiCh/ain#1155
Why is this needed:
DeFiCh/dfips#127
The text was updated successfully, but these errors were encountered: