--High-level description of what you want to add/change

I'd like to add supply, borrow and potentially other data like flashloans to (Solana) Jupiter schema.

--Which sub-project(s) it affects (dex, nft, etc.)

There are a few candidates for where to place proposed changes.

1
https://github.com/duneanalytics/spellbook/tree/main/dbt_subprojects/solana/models/jupiter

2
https://github.com/duneanalytics/spellbook/tree/main/dbt_subprojects/solana/models/_sector
(new folder: lending like below)

3
https://github.com/duneanalytics/spellbook/tree/main/dbt_subprojects/hourly_spellbook/models/_sector/lending
(then follow schema guides like supply, borrow, flashloan folders)

I chose '1' for all solana jupiter tables are stored in this schema.

However, as Kamino, MarginFi and other lenders on solana are integrated, it might make sense to move to '2' and/or as Dune gauges whether appropriate to move to '3' (per usage, popularity etc.). In any case I thought it would make sense to start at '1' regardless, unless Dune requests elsewhere.

--Why it would benefit the community

Currently it is very hard to analyze any lender on Solana (on Dune).

This table will enable easier analytics for Jupiter Lend, will be a great place to start for Solana Lenders in general (Jupiter Lend recently launched, very popular, likely be easier to run on Dune Cloud compared to others because of time restriction to be applied in code, ie. less data to go through).