Content
@
0 reply
0 recast
2 reactions
Zenigame
@zeni.eth
Ⓜ️oxie Build-In-Public Round 8 Moxie Auctions launched yesterday and I launched MoxieScout 0.4 along with it. Time to fill in some of the features I left on the cutting room floor. Without infinite time, I often have to cut scope or leave things unpolished. Hence the hefty loading time and UI dissonance. The north star is always Creating Value. Is shipping faster more valuable than polish? It depends. Yesterday night, shipping for the community to use was better than waiting for perfect data...so I cut scope and shipped. Today, I'll fill in more of the pieces. Clearing price is first on the list.
1 reply
0 recast
10 reactions
Zenigame
@zeni.eth
Continuing with this soundtrack on repeat for today's build https://music.youtube.com/watch?v=aqgm9rBjEH4
1 reply
0 recast
0 reaction
Zenigame
@zeni.eth
First up is getting that Clearing Price data. Yesterday it was coming up as 0 from the auction API. I'm not sure if this is as intended or a bug, will look into the docs and then hit up the team if necessary.
1 reply
0 recast
0 reaction
Zenigame
@zeni.eth
Indeed, this doesn't look quite right. There are lots of 0s that don't seem like they should be zero. @yosephks - any insight as to why I'm seeing zeros? This is from the minimal endpoint
2 replies
0 recast
0 reaction
Yoseph Ⓜ️
@yosephks
Hi @zeni.eth happy to see from the thread you have it figured out! But yeah the subgraph is a bit slow in processing, so getting the clearing price is not ideal during auction from the subgraph, only after the auction is cleared or finalized That is why we have the offchain API here for this, which will be much faster and help you calculate the clearing price real time Let me know if you have any questions 🙏
1 reply
0 recast
0 reaction
Zenigame
@zeni.eth
got it, that makes sense! "current" in currentClearingPrice threw me a bit since it was out of date, but will go with the offchain api for now
0 reply
0 recast
1 reaction
