-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Adds a spell for NEAR blockchain ft_transfer_calls #7900
Conversation
8f1fb0e
to
59733b9
Compare
59733b9
to
2e38584
Compare
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
dbt_subprojects/daily_spellbook/models/near/ft_transfer_calls/schema.yml
Outdated
Show resolved
Hide resolved
3357657
to
aa5eb71
Compare
dbt_subprojects/daily_spellbook/models/near/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
943a6ae
to
532d448
Compare
once you apply all changes and CI workflows complete, plz do test the data output to ensure you are happy with results. you can go into logs here (when complete) |
dbt_subprojects/daily_spellbook/models/near/near_ft_transfer_calls.sql
Outdated
Show resolved
Hide resolved
532d448
to
8ece5ba
Compare
b348bde
to
4f8d7a3
Compare
Adds a spell for NEAR blockchain (resolution of ft_transfer_calls). ft_transfer_call is one of the two ways to send fungible tokens according to the NEP-141 standard. Until now only the other method is covered (ft_transfer through the ft_transfers table). This contribution adds coverage for the ft_transfer_call, which according to the standard: transfer tokens and call a method on a receiver contract. A successful workflow will end in a success execution outcome to the callback on the same contract at the method ft_resolve_transfer. You can think of this as being similar to attaching native NEAR tokens to a function call. It allows you to attach any Fungible Token in a call to a receiver contract.
4f8d7a3
to
2be5d13
Compare
run times look much better & code looking good 🔥 did you get a chance to query |
Hi @jeff-dude that you very much for your reviews! After doing several manual tests, I realised that I had initially misunderstood the problem. The example of undetected transfer: https://nearblocks.io/txns/6a2Pddo4MQgePhj3NLVqhh6HAECrP6xzatp78wKJRoeV# I will close this PR and work on the actual problem. |
all good, hopefully the process still helped you understand spellbook further 🙏 |
Adds a spell for NEAR blockchain ft_transfer_calls.
ft_transfer_call
is one of the two ways to send fungible tokens according to the NEP-141 standard. Until now only the other method is covered (ft_transfer
through theft_transfers
table).This contribution adds coverage for the
ft_transfer_call
, which according to the standard:source: https://github.com/near/NEPs/blob/master/neps/nep-0141.md
TLDR: Without this spell, many Fungible Token transfers are simply not parsed, because they don't appear in the
ft_transfers
.