You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
I think I found an issue with counterwallet betting and the bet resolution date parsing.
I created a broadcast/feed which expired in 1 hour, and then tried to bet on that feed in counterwallet. The betting information came up, so counterwallet is correctly detecting that the feed can still accept bets. However, the resolution date that is displayed is actually in the past, and trying to place bets on the feed results in errors about the deadline already being passed.
I think I found an issue with counterwallet betting and the bet resolution date parsing.
I created a broadcast/feed which expired in 1 hour, and then tried to bet on that feed in counterwallet. The betting information came up, so counterwallet is correctly detecting that the feed can still accept bets. However, the resolution date that is displayed is actually in the past, and trying to place bets on the feed results in errors about the deadline already being passed.
Tx shows broadcast date/deadline of 1539889200 (2018-10-18T19:00:00Z)... in the future
https://testnet.xchain.io/tx/21866
Counterwallet shows deadline of 2018/10/17 09:00:00 PM -07:00... which is in the past.
Trying to bet on the feed passes a deadline of 1539835200 to create_bet.. resulting in an API error
The text was updated successfully, but these errors were encountered: