Open jackygu2006 opened 3 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 4.0 BNB (1662.24 USD @ $415.56/BNB) attached to it.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 264 years, 4 months from now. Please review their action plans below:
1) joshtharakan has been approved to start work.
I have set it up locally and works fine. I can now able to
chain_extrinsics
with extrinsics and then fetch the transfers and reward slashes from the table with sql. Learn more on the Gitcoin Issue Details page.
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
I have started the basic implementation of the transfer endpoint and started writing test cases. Will provide a WIP PR soon
Sorting out the challenges in testing this locally. This could have been much easier if sqlite("gorm.io/driver/sqlite") is used for testing locally but the testing relies on a running sql instance now which doesnt enable individual testing. TBH it doesnt follow FIRST principles of unit testing
I will be modifying the gorm version from v1.9
to v1.21.4
first and will raise a PR first
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@joshtharakan due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@joshtharakan due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
There is a blocker to progress further in implementing this because of some type registry changes required. This is being agreed with @jackygu2006 .
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@joshtharakan Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@joshtharakan due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@jackygu2006 pls snooze the warnings as this bounty is under hold from your side
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@joshtharakan due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Subscan-essential is a framework for developing chain-browser for the polkadot/substrate based blockchain, here we need to develop 2 APIs interfaces which are not opensourced yet.
Ref: https://docs.api.subscan.io/#transfers
Ref: https://docs.api.subscan.io/#reward-slash
Technical Stack: Golang