We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In auctions like that one: https://ido-ux.dev.gnosisdev.com/#/auction?auctionId=74&chainId=4#topAnchor
where the intention is to raaise a lot of value, but the first bidders only provide some small funding, the orderbook should better show it.
I see two solution:
Not sure what to chose, but we should introduce one solution
The text was updated successfully, but these errors were encountered:
@Rafanator @cmagan or @gabitoesmiapodo,
do yoou guys have some idea? I think it really important, as this problem will be experienced by all early IDO participants
Sorry, something went wrong.
We can do log scale but I'm not a fan... I think the orderbook will solve this
@cmagan @josojo is the solution provided in the orderbook's ticket #484 enough to solve this? or is the log scale still feasible?
I think the orderbook provides a solution but I'd still like to see how this looks like:
setting the max y-axis value to 2x total bidding volume.
We have now two clear examples (ITGR and MIVA) for why the chart is less informative with low bidding volume
No branches or pull requests
In auctions like that one:
https://ido-ux.dev.gnosisdev.com/#/auction?auctionId=74&chainId=4#topAnchor
where the intention is to raaise a lot of value, but the first bidders only provide some small funding, the orderbook should better show it.
I see two solution:
Not sure what to chose, but we should introduce one solution
The text was updated successfully, but these errors were encountered: