Near: v1.signer users #7597
Draft
Near: v1.signer users #7597
+71
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
WIP
jeff-dude
requested changes
Jan 30, 2025
dbt_subprojects/daily_spellbook/models/near/v1_signer/schema.yml
Outdated
Show resolved
Hide resolved
sources/near/v1_signer.yml
Outdated
There was a problem hiding this comment.
no need for this source file, as it's a new model you're building
in order to read your actual source tables used in model, you'll need to introduce near source file here:
https://github.com/duneanalytics/spellbook/tree/main/sources/_base_sources/other
There was a problem hiding this comment.
Thanks. Is there any particular format for these _base_sources? Or do I just move this file over there?
dbt_subprojects/daily_spellbook/models/near/v1_signer/near_v1_signer_users.sql
Outdated
Show resolved
Hide resolved
Co-authored-by: jeff-dude <102681548+jeff-dude@users.noreply.github.com>
|
Thanks @jeff-dude - I've addressed two. Just not sure about the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).
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.usersv1_signer_near.usersA 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).