Aaron Craelius

Ref #101. Let's stick with Postgres/postgis for now please. It's what the registry is using no need to spend innovation tokens here.

The core thing I think we need to get clear on is whether a bond token can simply be an `x/bank` token or not, in which case `x/bond` just needs...

The fundamental thing needed here is alignment on design. I don't think it's worth spending a lot of time on details until that's decided. The proto files IMHO are mostly...

So one thing I’m wanting to understand better in terms of credit metadata is the size of the data, specifically polygons Can you comment on the size of polygons for...

My original designs for `x/data` included an URL field and I still think it makes sense to support that somehow. But it needs some design. Specifically, if polygons are stored...

I agree integration tests should mostly be focused on the server level using `MsgClient`/`MsgServer` directly - basically the level just above unit tests rather than all the way out to...

With the ORM, the stored object is effectively the presented object because the ORM will expose its own direct query layer to clients. So we will need to figure out...

Moving my comments from #1022 here > > This makes me want to spend a bit of time on the query infrastructure in the SDK using Cosmos scalars so we...

> > What do you think @ryanchristo ? > > I think we should consider jumping straight to graphql given we need more than just addresses converted from bytes to...

I think (1) is fine for now. I think we could get more granular in the future for the DEX if needed, but (1) seems sufficient and simplest. It's basically...