-
Notifications
You must be signed in to change notification settings - Fork 3
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
An 5001/update amm sell #616
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting NULL
sales_amount when I run the test on the full output
recent_date_filter: &recent_date_filter
config:
where: _inserted_timestamp >= '2020-01-01'
16:11:58 Completed with 1 error and 0 warnings:
16:11:58
16:11:58 Failure in test not_null_silver__nft_sales_amm_sell_decoded_SALES_AMOUNT (models/silver/nfts/silver__nft_sales_amm_sell_decoded.yml)
16:11:58 Got 27 results, configured to fail if != 0
16:11:58
16:11:58 compiled Code at target/compiled/solana_models/models/silver/nfts/silver__nft_sales_amm_sell_decoded.yml/not_null_silver__nft_sales_amm_sell_decoded_SALES_AMOUNT.sql
16:11:58
16:11:58 See test failures:
--------------------------------------------------------------------------------
select * from SOLANA_DEV.not_null_silver.nft_sales_amm_sell_decoded_SALES_AMOUNT
--------------------------------------------------------------------------------
16:11:58
16:11:58 Done. PASS=17 WARN=0 ERROR=1 SKIP=0 TOTAL=18
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
depositSell
extDepositSell
mip1DepositSell
ocpDepositSell
solDepositBuy
What do these events do if they are not sales?
They're related to creation of liquidity pools and depositing NFTs into them (or depositing SOL into a buy-side liquidity pool for solDepositBuy). Don't completely understand how it works but those events don't seem to deal with the direct NFT sales. |
Good catch, didn't think about the filter. I added additional event_type in the ME logic, and the test on the complete dataset is passing:
|
'solMip1FulfillSell', | ||
'solOcpFulfillSell' | ||
) THEN silver.udf_get_account_pubkey_by_name( | ||
'pool', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The seller is the NFT pool for coral cube?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vice versa for purchaser comment
decoded_instruction :accounts | ||
) | ||
ELSE silver.udf_get_account_pubkey_by_name( | ||
'pool', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The purchaser is the NFT pool for coral cube?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in these instances the 'pool' address is what recieves the NFT and has ownership, and also what sends payment so we ID that as technically the purchaser.
Use decoded instructions to create new
nft_sales_amm_sell_decoded
modelnft_sales_amm_sell
and create viewfact_nft_sales
because those txs cannot be decoded