Near: v1.signer users

[bh2smith]

As far as I can tell this is the first spell for near blockchain data so the standards aren't yet well defined.

This query extracts the near accountId and derivation path used for the signing contract v1.signer. It takes too long to run and should probably become an incremental strategy (although I am seeking some pointers on how best to achieve that).

Sample PoC Query: https://dune.com/queries/4642523 (also referenced comments on SQL file).

⚠️ It takes 18 minutes to run on a large cluster and should become an incremental strategy based on block_height (since historical data is fixed).

I think that the source naming may not be defined appropriately.

Ideally the resulting source winds up being something like

or maybe:

near_v1_signer.users
v1_signer_near.users

A possible alternative project name might be

mpc_near.users.

seeking some clarification and corrections on syntax declarations (its been a while since I made a new spell cc @jeff-dude).

[bh2smith]

Thanks @jeff-dude - I've addressed two. Just not sure about the _base_sources since the near domain already exists but the file isn't here.

[bh2smith]

@jeff-dude - So this is now failing with

  Model 'model.daily_spellbook.near_v1_signer_users' (models/near/v1_signer/near_v1_signer_users.sql) depends on a source named 'near.actions' which was not found

Here is the working sample query:

https://dune.com/queries/4642523

Wondering if Maybe I should replace

FROM {{ source('near', 'actions') }} action
JOIN {{ source('near', 'logs') }} log

with

FROM {{ ref('near', 'actions') }} action
JOIN {{ ref('near', 'logs') }} log

Don't wanna blast your CI with any more test commits. Will await your suggestion.

[Hosuke]

We need to add near.actions in the sources first.

[Hosuke]

Updated several known base sources.