AtomicAssets Developer (@atomicdevs) — Telegram group messages

3 November 2023

ariefbayu

Caio Tieghihow did you do that? i'm samples on internet shows cleos

1. login using your contract 2. go to "wallet" menu

16:22

ariefbayu

Photo
click to show

3, choose this option inside "wallet" menu

16:22

ariefbayu

Photo
click to show

there, choose "Advanced" and then "Add new+"

16:23

ariefbayu

Photo
click to show

finally, on the new empty fields, fill in "Account" for type and "[email protected]" for the value

16:23

C
Caio Tieghi
it worked, tks for the help mate
16:29

Whole thread · 1 reply →

ariefbayu

save it and sign transaction

16:23

6 November 2023

ariefbayu

Guys a question on mutable/immutable data at burn notification. I noticed that some time, the asset being burn don't carry old_mutable/old_immutable in it. What is the correct flow to read? Should I also have to read this data from the schema?

03:26

C
cc32d9 | EOS Amsterdam
Isn't the old value supposed to be only on changes? On burning, there's just one set of attributes
06:29
1. A
  ariefbayu
  honestly, this is my first ever smart contract development, so any guidance are very much welcomed
  06:37
  1. C
    cc32d9 | EOS Amsterdam
    Link
    click to show
    The sources of AA contract are the best source of knowledge: https://github.com/pinknetworkx/atomicassets-contract
    06:39
    1. A
      ariefbayu
      I'll take a deep look at this, thanks
      06:46

Whole thread · 4 replies →

ariefbayu

so, I guess, based on reply above, I should read immutable from schema and mutable on the old_mutable field?

06:38

C
cc32d9 | EOS Amsterdam
ACTION logburnasset( name asset_owner, uint64_t asset_id, name collection_name, name schema_name, int32_t template_id, vector <asset> backed_tokens, ATTRIBUTE_MAP old_immutable_data, ATTRIBUTE_MAP old_mutable_data, name asset_ram_payer );
06:40

Whole thread · 1 reply →

cc32d9 | EOS Amsterdam

Link
click to show

Also, some generic knowledge here: https://cc32d9.gitbook.io/antelope-smart-contract-developers-handbook/

06:39

cc32d9 | EOS Amsterdam

I forgot the names, and they're indeed old_xxx

06:41

cc32d9 | EOS Amsterdam

So, if one of those maps is empty, it means the asset didn't have them

06:41

A
ariefbayu
therefore, if I need to know what immutable an asset actually have on burn, if those maps is empty, I should read from the schema
06:46
1. C
  cc32d9 | EOS Amsterdam
  No, these maps should deliver you all the data. Also, the tables are already wiped by the time you receive the notification
  06:52
  1. A
    ariefbayu
    Hmm... So, I guess my issue only occurred because I'm testing on testnet? Here's my check step: 1. test collection: testworkshop 2. contract hosted at splltutorial 3. created an asset through AH interface: 1099566958569 4. checked the asset in atomicassets's assets table: https://testnet.waxblock.io/account/atomicassets?code=atomicassets&scope=waxchainuser&table=assets&lower_bound=1099566958569&upper_bound=1099566958569&limit=10#contract-tables << here we can see that immutable and mutable are empty.
    08:32
    1. C
      cc32d9 | EOS Amsterdam
      It doesn't matter if it's test or mainnet. The asset attributes depend on the template and how you create them
      09:03

Whole thread · 4 replies →

ariefbayu

Link
click to show

I see burn action here: https://github.com/pinknetworkx/atomicassets-contract/blob/7991ebfdfe75c32e4ab1e37405c116cda1e76ea5/src/atomicassets.cpp#L839 mutable and immutable are all taken from the assets table. So, make sense if logburnasset got not data