Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Updated Receipt's logIndexto be index position in the _block_,. #596 #463

Closed
wants to merge 1 commit into from

Conversation

sushilbal
Copy link

Updated the log index to be in sync with the number of logs in the block rather than determined by the number of transactions

@nicholasjpaterno
Copy link
Contributor

@sushilbal nice work! The only thing we would need to merge this is a test case! This is actually a good chance for us to formally test eth_getFilterChanges directly for the first time in our test suite!

  describe("eth_getFilterChanges", function() {
    it("should contain the correct logIndex", function() {
      
    });
  });

Something like this in test/requests.js with just one passing test would be ideal!

@davidmurdoch davidmurdoch changed the title Updated Receipt's logIndexto be index position in the _block_,. #335 Updated Receipt's logIndexto be index position in the _block_,. #596 Jun 23, 2020
@davidmurdoch
Copy link
Member

Closing as this has been fixed in the ts branch.

cometwebdev added a commit to cometwebdev/saddle-contract that referenced this pull request Jan 31, 2022
* Add withdrawal fee that decays over a year

* Fee cannot exceed 1%
* If user adds more liquidity before the decaying is over, it recalculates the fee which gets discounted based on the previous deposit amount & time. Then the decaying period is extended to a year from the second deposit.

* Make withdrawFee a multiplier such that updating the fee applies retroactively as well

* Changes withdrawFee to withdrawFeeMultiplier
* Adds more comments

* Change evm_setNextBlockTimestamp to evm_increaseTime

* Though builder evm supports both calls, coverage uses ganache network
which only supports latter.

* Use evm_mine to specify timestamp

* Due to ganache's design of interpreting evm_increaseTime, there is extra 1 second added to the block depending on Javascript runtime,
* https://ethereum.stackexchange.com/questions/73751/understanding-ganache-timestamps
* trufflesuite/ganache#463

* Use evm_mine during coverage (Ganache) and evm_setNextBlockTimestamp during test (Buidler EVM)

* Rebased and updated function calls to support deadlines

* Change decay period to 4 weeks

* Fix comments

* Fix another typo

* Fix github ci

* Replaces ssh with https

Co-authored-by: Sunil Srivatsa <sunilsrivatsa@gmail.com>
melbesnard85 added a commit to melbesnard85/saddle-contract that referenced this pull request May 7, 2022
* Add withdrawal fee that decays over a year

* Fee cannot exceed 1%
* If user adds more liquidity before the decaying is over, it recalculates the fee which gets discounted based on the previous deposit amount & time. Then the decaying period is extended to a year from the second deposit.

* Make withdrawFee a multiplier such that updating the fee applies retroactively as well

* Changes withdrawFee to withdrawFeeMultiplier
* Adds more comments

* Change evm_setNextBlockTimestamp to evm_increaseTime

* Though builder evm supports both calls, coverage uses ganache network
which only supports latter.

* Use evm_mine to specify timestamp

* Due to ganache's design of interpreting evm_increaseTime, there is extra 1 second added to the block depending on Javascript runtime,
* https://ethereum.stackexchange.com/questions/73751/understanding-ganache-timestamps
* trufflesuite/ganache#463

* Use evm_mine during coverage (Ganache) and evm_setNextBlockTimestamp during test (Buidler EVM)

* Rebased and updated function calls to support deadlines

* Change decay period to 4 weeks

* Fix comments

* Fix another typo

* Fix github ci

* Replaces ssh with https

Co-authored-by: Sunil Srivatsa <sunilsrivatsa@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants