A place for developers to talk about building on Farcaster.

/dev

Ⓜ️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.

Continuing with this soundtrack on repeat for today's build

Wanna be the very best. Creator of @moxiescout /miw /buck. ゼニゼニ

Continuing with this soundtrack on repeat for today's build

https://music.youtube.com/watch?v=aqgm9rBjEH4

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.

Indeed, this doesn't look quite right. There are lots of 0s that don't seem like they should be zero.

@yosephks.eth - any insight as to why I'm seeing zeros? This is from the minimal endpoint

working on @moxie.eth | devrel @airstack.eth

But I'm not gonna get blocked by this kind of thing. Let's try using their offchain api to get the clearing price. 

Another API call will slow things down a bit, but I think the performance tradeoff will be worth having the data for individual pages where there's just one call.

But I'm not gonna get blocked by this kind of thing. Let's try using their offchain api to get the clearing price. 

Another API call will slow things down a bit, but I think the performance tradeoff will be worth having the data for individual pages where there's just one call.

https://developer.moxie.xyz/use-cases/fan-token-auctions/get-clearing-price-of-certain-auction

Workaround worked :)

Let's cut off a few decimals and move on.

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