blend v2.0.0

[DenisCarriere]

To-Do's

• [x] removed global & extra stats data (easier to maintain/migrate without data counters, can be accomplished offchain)
• [x] support for multiple input recipes (template combinations)
• [x] enforce check for end_date
• [x] update test cases
• [x] (not required for initial migration) allow multiple recipes (currently supports 1 recipe)
• [x] ⚠️❓ remove refund mechanism (throws error if does not match perfectly to any recipes)

Scenario:

For Pomelo Season 2, we will have a blend with "base ingredient" + "1 of any grant collectible"

Ex:

• 4x base + 1x grant (Greymass)
• 4x base + 1x grant (EOSNFT)
• 4x base + 1x grant (EOSBees)
• etc...

This would cause us to create unique blends for each combinations (ex: blend1, blend2, blend3)

Instead introducing new concept of "recipes"

This would allow a single blend to have multiple different recipe inputs options, however the output always remains the same.

Tables

TABLE blends

params

• {name} blend_id - (primary key) blend ID (ex: myblend)
• {set<name>} in_recipe_ids - one or many input recipes ID's
• {atomic::nft} out_template - output AtomicAsset NFT template
• {time_point_sec} [start_time=null] - (optional) start time (ex: "2021-07-01T00:00:00")
• {time_point_sec} [end_time=null] - (optional) end time (ex: "2021-08-01T00:00:00")

example

{
    "blend_id": "myblend",
    "in_recipe_ids": ["myrecipe1", "myrecipe2"],
    "out_template": {"collection_name": "mycollection", "template_id": 21883},
    "start_time": "2021-07-01T00:00:00",
    "end_time": "2021-10-01T00:00:00"
}

TABLE recipes

params

• {name} recipe_id - (primary key) recipe ID (ex: myrecipe)
• {vector<atomic::nft>} templates - AtomicAsset NFT templates

example

{
    "recipe_id": "myrecipe",
    "templates": [{"collection_name": "mycollection", "template_id": 21883}]
}

ACTION setblend

Set NFT blend

• authority: get_self()

params

• {name} blend_id - (primary key) blend ID (ex: myblend)
• {set<name>} in_recipe_ids - input recipes ID's
• {atomic::nft} out_template - output AtomicAsset NFT template
• {time_point_sec} [start_time=null] - (optional) start time (ex: "2021-07-01T00:00:00")
• {time_point_sec} [end_time=null] - (optional) end time (ex: "2021-08-01T00:00:00")

Example

$ cleos push action blend.gems setblend '["myblend", ["myrecipe1", "myrecipe2"], ["mycollection", 789], "2021-11-01T00:00:00", "2021-12-01T00:00:00"]' -p blend.gems

ACTION setrecipe

Set NFT recipe

• authority: get_self()

params

• {name} blend_id - blend blend ID (ex: myblend)
• {vector<atomic::nft>} templates - AtomicHub NFT templates

Example

$ cleos push action blend.gems setrecipe '["myrecipe", [["mycollection", 123], ["mycollection", 456]]]' -p blend.gems