Open van-orton opened 3 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 1.0432 ETH (400.51 USD @ $383.93/ETH) 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 266 years, 1 month from now. Please review their action plans below:
1) hhio618 has been approved to start work.
I'll fix the data for this test case and make sure BOOST_AUTO_TEST_CASE(txvalid) runs properly. **2) atiwat31 has applied to start work (Funders only: approve worker | reject worker)_.**
ไว้เพื่อหาข้อมูลศึกษาค้นคว่า และนำไปลงทุนความเสื่ยงในเกม 3) efrainleuck has applied to start work _(Funders only: approve worker | reject worker)_.
I will generate numerous test cases in the defined Tx_valid.json file and ensure transaction_test.cpp is running BOOST_AUTO_TEST_CASE(tx_valid)properly.
Learn more on the Gitcoin Issue Details page.
@hhio618 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
@hhio618 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
@hhio618 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
Hi, I've been a little busy. I'll submit a pr ASAP.
@hhio618 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
@hhio618 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
@hhio618 Hi, how're you doing? Can we expect the PR to be created soon? Please make an update.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@hhio618 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
@wu-emma I apologize and really sorry for being too late. It’s been a rough two week for me and my family duo infection with covid-19, so that’s the reason for me to progress very slowly within these two weeks. In exchange for that I’m willing to this even without any payment if you still want me to do it?
@hhio618 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
@hhio618 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
@hhio618 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
@hhio618 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
The funding of 1.0432 ETH (1259.69 USD @ $1211.24/ETH) attached to this issue has been cancelled by the bounty submitter
Issue Status: 1. Open 2. Cancelled
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) hhio618 has been approved to start work.
I'll fix the data for this test case and make sure BOOST_AUTO_TEST_CASE(tx_valid) runs properly.
Learn more on the Gitcoin Issue Details page.
Description
src/test/data/tx_valid.json
contains data for various transactions that are simulated during the unit test execution. Because of the different hashing algorithm used (keccak instead of double sha256) in BGL, this file has to be regenerated for tests section to pass. The test section is commented out and located insrc/test/transaction_tests.cpp
Solution direction
The only differences should be only hashing algorithm used for txs (keccak) and that transactions are required to be segwit ('new' type).
Acceptance criteria