search

BirthdayResearch / defichain-wallet

DeFiChain Wallet. The DeFi Blockchain Light Wallet for iOS, Android & Web.
MIT License
126 stars 46 forks source link

Next Future Settlement Block is not correctly implemented #4184

Closed Kassius84 closed 2 months ago

Kassius84 commented 2 months ago

What happened:

The DeFiChain Lightwallet shows a different/wrong next Future Settlement Block, then https://defiscan.live/blocks/countdown/NextFutureSwap. So it’s not possible the click „continue“ in Lightwallet to prepare a swap for the next FutureSwap.

What you expected to happen:

Same/correct Next Future Settlement Block in Lightwallet and Blockchain/defiscan.

How to reproduce it (as minimally and precisely as possible):

The bug occurs with Lightwallet version 2.42.0. From my understanding Android and iOS are booth impacted.

Anything else we need to know?:

github-actions[bot] commented 2 months ago

@Kassius84: 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.

Details I am a bot created to help the [BirthdayResearch](https://github.com/BirthdayResearch) developers manage community feedback and contributions. You can check out my [manifest file](https://github.com/BirthdayResearch/defichain-wallet/blob/main/.github/governance.yml) to understand my behavior and what I can do. If you want to use this for your project, you can check out the [BirthdayResearch/oss-governance-bot](https://github.com/BirthdayResearch/oss-governance-bot) repository.
github-actions[bot] commented 2 months ago

@Kassius84: 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 /area comment.

Details I am a bot created to help the [BirthdayResearch](https://github.com/BirthdayResearch) developers manage community feedback and contributions. You can check out my [manifest file](https://github.com/BirthdayResearch/defichain-wallet/blob/main/.github/governance.yml) to understand my behavior and what I can do. If you want to use this for your project, you can check out the [BirthdayResearch/oss-governance-bot](https://github.com/BirthdayResearch/oss-governance-bot) repository.
github-actions[bot] commented 2 months ago

@Kassius84: Thanks for opening an issue, an appropriate priority will be added soon.

The priority labels can be added by foundation members by writing /priority [type] in a comment.

Details I am a bot created to help the [BirthdayResearch](https://github.com/BirthdayResearch) developers manage community feedback and contributions. You can check out my [manifest file](https://github.com/BirthdayResearch/defichain-wallet/blob/main/.github/governance.yml) to understand my behavior and what I can do. If you want to use this for your project, you can check out the [BirthdayResearch/oss-governance-bot](https://github.com/BirthdayResearch/oss-governance-bot) repository.
Kassius84 commented 2 months ago

As a workaround, it’s possible to switch ocean endpoint to alternative provider like https://ocean.mydefichain.com. With mydefichain or with switch back to default provider, the correct Next Future Settlement Block is displayed.

friedriche-br commented 2 months ago

@Kassius84 Could be temporarily be out of sync, is everything working as intended now? I tried replicating it on my LW and future swap works as intended.

Kassius84 commented 2 months ago

Thanks in your reply. I can't repeat the case and there is only one user who has come forward. I would suggest closing the issue. I apologize for the inconvenience.

Kind regards