Subgraph setup

[rokso]

Available data points in subgraph

• PositionRegistry

  • owner
  • feeCollector
  • positionCount
  • smartAccountCount
  • smartAccounts, list
  • strategies, list

• SmartAccount

  • positionRegistry
  • positionCount
  • positions, a list

• Position

  • owner aka SmartAccount
  • strategyId
  • createdAt
  • openedAt
  • txCount
  • asset
  • totalAllocated
  • pricePerShare
  • isOutdated
  • positionDailyData, a list

• Strategy

  • positionRegistry
  • implementation
  • feePolicy
  • isActive

• PositionDailyData

  • pricePerShare
  • position

[marcelomorgado]

Well done, this isn't a basic subgraph at all! I've just a few comments/questions.

[marcelomorgado]

At this point we're assuming all Odyssey wallets we'll be created through the Entrypoint contract (i.e. without calling kernel Factory directly), is that right?

[rokso]

Correct, I have this setup based few wallets creations that I have observed in Odyssey.

[marcelomorgado]

@mbonfoster could you double check it please?

[marcelomorgado]

I think we could update the isOutdated field here too. A closed position can be reused (as a way to save gas, avoiding deploying another proxy) so with this flag may trigger an update before re-opening it.

[marcelomorgado]

With triggering I mean, bundle [upgrade, open] txs

[rokso]

Good point. I will look into this.

[rokso]

So here is the deal with this flag. Say we fetch latest status of strategy at the time of close and set it in isOutdated. Status can be updated between it is closed and opened and there is no way on subgraph to determine this. Only possible solution would be to check isOutdated() on-chain before reusing position.
We can still set latest at the time of close but it won't be much help IMO.

[rokso]

Done

[marcelomorgado]

So here is the deal with this flag. Say we fetch latest status of strategy at the time of close and set it in isOutdated. Status can be updated between it is closed and opened and there is no way on subgraph to determine this. Only possible solution would be to check isOutdated() on-chain before reusing position. We can still set latest at the time of close but it won't be much help IMO.

Yes, indeed, let's keep it in mind. FYI @mbonfoster

[mbonfoster]

@rokso we expect entry point to change on every new kernel version, and we probably will need to keep support for previous entry points.

[rokso]

Great point. I will think about how we want to handle this.

[rokso]

@patidarmanoj10 cc @marcelomorgado I remember reading somewhere on slack that we can install a module which can emit event at the time of deployment, IMO this can be the best way to handle this. Let me know if this is possible at all.

[rokso]

@mbonfoster when new kernal version is out, which kernel Odyssey will be using for deploying new smart accounts? This setup is only for Odyssey, so we will support whatever version we use on Odyssey side. Can user import smart accounts created outside of Odyssey UI?