Buy One Get One Weekend 🎉 - Dark Emblem

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    img: "img",
    h3: "h3"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "We did a stealth production launch this last week, with some of the members on our discord participating. I decided not to publicly announce the launch since there was still a lot of testing to do, and lo-and-behold we found quite a few issues that needed to be addressed."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-03-19-state-of-play-update/splash.png",
        alt: "Splash"
      })
    }), "\n", _jsx(_components.h3, {
      children: "Working with AtomicHub"
    }), "\n", _jsx(_components.p, {
      children: "I have been in contact with the AtomicHub team to get our NFT whitelisted on AtomicHub’s site."
    }), "\n", _jsx(_components.p, {
      children: "In addition, I’m working with their team to determine the best way to use their AtomicAssets API to power the Dark Emblem dApp."
    }), "\n", _jsx(_components.h3, {
      children: "Stability"
    }), "\n", _jsx(_components.p, {
      children: "When we deployed to production, we noticed a lot of stability issues in the UI and the server thanks to our community testing the dApp out. It turns out the production nodes for WAX and for AtomicAssets aren’t as nice to work with as the testnet versions. I released a new version of the app that fixes a lot of these issues."
    }), "\n", _jsx(_components.p, {
      children: "With the help of the WAX community, I have been looking into ways to add more resiliency to our application. I am using different WAX nodes now to keep our UI and Server in-sync with new blocks on the WAX blockchain. We were running into rate limiting issues with the official WAX API node, but have seen a huge increase in successful requests since changes nodes."
    }), "\n", _jsx(_components.p, {
      children: "As for the AtomicAsssets API, we are still seeing a lot of 520 responses coming from their API and I am working with them to resolve this issue. Until then, I have updated the dApp to let users retry requests that commonly fail."
    }), "\n", _jsx(_components.p, {
      children: "If all that wasn’t enough, I added a tool called Bugsnag to the dApp and server so that we can track any errors in the future. This will help us debug the application and take note of which WAX nodes need to be replaced in our code."
    }), "\n", _jsx(_components.h3, {
      children: "Chaos Testing"
    }), "\n", _jsx(_components.p, {
      children: "In order to better prepare the dApp for what can go wrong on production, I created a chaos module that will randomly fail requests when testing with common failures. This will force us to write a better app experience since we will commonly encounter errors on testing versions of the app, instead of just in production."
    }), "\n", _jsx(_components.h3, {
      children: "New Status Page"
    }), "\n", _jsx(_components.p, {
      children: "To help users understand what may be going wrong on the site if features aren’t working correctly, we released a new Status Page at the top of the application."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-03-19-state-of-play-update/health.png",
        alt: "Health"
      })
    }), "\n", _jsx(_components.p, {
      children: "If an endpoint appears unhealthy, we will show an alert at the top of the page. We use a combination of 3 APIs to create a rich UI: WAX, AtomicAssets, and Dark Emblem. This page will let you monitor their current status."
    }), "\n", _jsx(_components.h3, {
      children: "Looking Forward"
    }), "\n", _jsx(_components.p, {
      children: "There is still more work to do to get the UI to have a seamless experience. We will start looking at proxying requests to our server for AtomicAssets and WAX API calls that we can cache."
    }), "\n", _jsx(_components.p, {
      children: "More importantly though, I am confident on our fixes and I am moving forward with a full launch of Dark Emblem!"
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, Object.assign({}, props, {
    children: _jsx(_createMdxContent, props)
  })) : _createMdxContent(props);
}
return {
  default: MDXContent
};


<div class="text-base text-gray-50">We did a stealth production launch this last week, with some of the members on our discord participating. I decided not to publicly announce the launch since there was still a lot of testing to do, and lo-and-behold we found quite a few issues that needed to be addressed.</div>
<div class="text-base text-gray-50"><img alt="Splash" src="media/2022-03-19-state-of-play-update/splash.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Working with AtomicHub</h3>
<div class="text-base text-gray-50">I have been in contact with the AtomicHub team to get our NFT whitelisted on AtomicHub’s site.</div>
<div class="text-base text-gray-50">In addition, I’m working with their team to determine the best way to use their AtomicAssets API to power the Dark Emblem dApp.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Stability</h3>
<div class="text-base text-gray-50">When we deployed to production, we noticed a lot of stability issues in the UI and the server thanks to our community testing the dApp out. It turns out the production nodes for WAX and for AtomicAssets aren’t as nice to work with as the testnet versions. I released a new version of the app that fixes a lot of these issues.</div>
<div class="text-base text-gray-50">With the help of the WAX community, I have been looking into ways to add more resiliency to our application. I am using different WAX nodes now to keep our UI and Server in-sync with new blocks on the WAX blockchain. We were running into rate limiting issues with the official WAX API node, but have seen a huge increase in successful requests since changes nodes.</div>
<div class="text-base text-gray-50">As for the AtomicAsssets API, we are still seeing a lot of 520 responses coming from their API and I am working with them to resolve this issue. Until then, I have updated the dApp to let users retry requests that commonly fail.</div>
<div class="text-base text-gray-50">If all that wasn’t enough, I added a tool called Bugsnag to the dApp and server so that we can track any errors in the future. This will help us debug the application and take note of which WAX nodes need to be replaced in our code.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Chaos Testing</h3>
<div class="text-base text-gray-50">In order to better prepare the dApp for what can go wrong on production, I created a chaos module that will randomly fail requests when testing with common failures. This will force us to write a better app experience since we will commonly encounter errors on testing versions of the app, instead of just in production.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">New Status Page</h3>
<div class="text-base text-gray-50">To help users understand what may be going wrong on the site if features aren’t working correctly, we released a new Status Page at the top of the application.</div>
<div class="text-base text-gray-50"><img alt="Health" src="media/2022-03-19-state-of-play-update/health.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<div class="text-base text-gray-50">If an endpoint appears unhealthy, we will show an alert at the top of the page. We use a combination of 3 APIs to create a rich UI: WAX, AtomicAssets, and Dark Emblem. This page will let you monitor their current status.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Looking Forward</h3>
<div class="text-base text-gray-50">There is still more work to do to get the UI to have a seamless experience. We will start looking at proxying requests to our server for AtomicAssets and WAX API calls that we can cache.</div>
<div class="text-base text-gray-50">More importantly though, I am confident on our fixes and I am moving forward with a full launch of Dark Emblem!</div>

We did a stealth production launch this last week, with some of the members on our discord participating. I decided not to publicly announce the launch since there was still a lot of testing to do, and lo-and-behold we found quite a few issues that needed to be addressed.

![Splash](media/2022-03-19-state-of-play-update/splash.png)



### Working with AtomicHub

I have been in contact with the AtomicHub team to get our NFT whitelisted on AtomicHub’s site.

In addition, I’m working with their team to determine the best way to use their AtomicAssets API to power the Dark Emblem dApp.

### Stability

When we deployed to production, we noticed a lot of stability issues in the UI and the server thanks to our community testing the dApp out. It turns out the production nodes for WAX and for AtomicAssets aren’t as nice to work with as the testnet versions. I released a new version of the app that fixes a lot of these issues.

With the help of the WAX community, I have been looking into ways to add more resiliency to our application. I am using different WAX nodes now to keep our UI and Server in-sync with new blocks on the WAX blockchain. We were running into rate limiting issues with the official WAX API node, but have seen a huge increase in successful requests since changes nodes.

As for the AtomicAsssets API, we are still seeing a lot of 520 responses coming from their API and I am working with them to resolve this issue. Until then, I have updated the dApp to let users retry requests that commonly fail.

If all that wasn’t enough, I added a tool called Bugsnag to the dApp and server so that we can track any errors in the future. This will help us debug the application and take note of which WAX nodes need to be replaced in our code.

### Chaos Testing

In order to better prepare the dApp for what can go wrong on production, I created a chaos module that will randomly fail requests when testing with common failures. This will force us to write a better app experience since we will commonly encounter errors on testing versions of the app, instead of just in production.

### New Status Page

To help users understand what may be going wrong on the site if features aren’t working correctly, we released a new Status Page at the top of the application.

![Health](media/2022-03-19-state-of-play-update/health.png)

If an endpoint appears unhealthy, we will show an alert at the top of the page. We use a combination of 3 APIs to create a rich UI: WAX, AtomicAssets, and Dark Emblem. This page will let you monitor their current status.

### Looking Forward

There is still more work to do to get the UI to have a seamless experience. We will start looking at proxying requests to our server for AtomicAssets and WAX API calls that we can cache.

More importantly though, I am confident on our fixes and I am moving forward with a full launch of Dark Emblem!

State of Play Update March 19

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    img: "img",
    h2: "h2",
    a: "a",
    strong: "strong",
    code: "code",
    h3: "h3"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "It's that time! To celebrate deploying to production and give everyone a little\nsomething before we get whitelisted by AtomicHub, we are hosting a Buy One\nGet One event!"
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-03-28-bogo/bogo-splash.jpg",
        alt: "Splash"
      })
    }), "\n", _jsx(_components.h2, {
      children: "BOGO Weekend"
    }), "\n", _jsx(_components.p, {
      children: "This weekend, from April 1, 9:00 PM PT to April 3, 11:59 PM PT, we are hosting\na BOGO event: buy ANY Dark Emblem Pack, and we will air drop you a FREE legendary\npack after the event ends."
    }), "\n", _jsx(_components.h2, {
      children: "How it works"
    }), "\n", _jsx(_components.p, {
      children: "During this weekend, if you buy any Dark Emblem pack, we will air drop you one\nlegendary pack. Max 1 free pack per account."
    }), "\n", _jsxs(_components.p, {
      children: ["We will check ", _jsx(_components.a, {
        href: "https://wax.bloks.io/account/darkemblems1",
        children: "WAX on Bloks"
      }), " for transactions.\nOnly accounts where there is a ", _jsx(_components.strong, {
        children: "Recieve Token"
      }), " Action with memo ", _jsx(_components.code, {
        children: "purchase_pack:XYZ"
      }), " during\nthe above time frame will be eligible for a free pack."]
    }), "\n", _jsx(_components.h2, {
      children: "LFG 🚀"
    }), "\n", _jsxs(_components.p, {
      children: ["Get ready for a free pack this weekend! Make sure you have a WAX account with some WAXP in it,\nget signed into Dark Emblem, and read up on ", _jsx(_components.a, {
        href: "/docs/buying-packs",
        children: "our docs on how to buy your first pack"
      }), "!"]
    }), "\n", _jsxs(_components.p, {
      children: ["Read more about the promotion on ", _jsx(_components.a, {
        href: "https://www.darkemblem.com/promotions/2022-04-02-Bogo",
        children: "our official site"
      }), "."]
    }), "\n", _jsx(_components.h2, {
      children: "FAQ"
    }), "\n", _jsx(_components.h3, {
      children: "Q: I missed the deadline due to the time it took my pack purchase to get accepted by the WAX network. Can I still get a free pack?"
    }), "\n", _jsx(_components.p, {
      children: "No. I would suggest not waiting until the last minute purchase a pack."
    }), "\n", _jsx(_components.h3, {
      children: "Q: I purchased two packs during the event, will I get 2 free packs?"
    }), "\n", _jsx(_components.p, {
      children: "No. Each account will only be eligible to receive a single free pack when the promotion ends."
    }), "\n", _jsx(_components.h3, {
      children: "Q: How long will it take for us to receive our free packs?"
    }), "\n", _jsx(_components.p, {
      children: "You will receive your free pack up to 24 hours after the event ends. If there is\nany expected delay, we will let you know via our Discord community."
    }), "\n", _jsx(_components.h3, {
      children: "Q: I purchased a pack before the event, can I still get a free pack?"
    }), "\n", _jsx(_components.p, {
      children: "No, however we will be reaching out to some of our early pack purchasers for\nother cool Dark Emblem goodies."
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, Object.assign({}, props, {
    children: _jsx(_createMdxContent, props)
  })) : _createMdxContent(props);
}
return {
  default: MDXContent
};


<div class="text-base text-gray-50">It&#x27;s that time! To celebrate deploying to production and give everyone a little
something before we get whitelisted by AtomicHub, we are hosting a Buy One
Get One event!</div>
<div class="text-base text-gray-50"><img alt="Splash" src="media/2022-03-28-bogo/bogo-splash.jpg" style="max-height:500px;margin:auto;text-align:center"/></div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">BOGO Weekend</h2>
<div class="text-base text-gray-50">This weekend, from April 1, 9:00 PM PT to April 3, 11:59 PM PT, we are hosting
a BOGO event: buy ANY Dark Emblem Pack, and we will air drop you a FREE legendary
pack after the event ends.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">How it works</h2>
<div class="text-base text-gray-50">During this weekend, if you buy any Dark Emblem pack, we will air drop you one
legendary pack. Max 1 free pack per account.</div>
<div class="text-base text-gray-50">We will check <a href="https://wax.bloks.io/account/darkemblems1">WAX on Bloks</a> for transactions.
Only accounts where there is a <strong>Recieve Token</strong> Action with memo <code>purchase_pack:XYZ</code> during
the above time frame will be eligible for a free pack.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">LFG 🚀</h2>
<div class="text-base text-gray-50">Get ready for a free pack this weekend! Make sure you have a WAX account with some WAXP in it,
get signed into Dark Emblem, and read up on <a href="/docs/buying-packs">our docs on how to buy your first pack</a>!</div>
<div class="text-base text-gray-50">Read more about the promotion on <a href="https://www.darkemblem.com/promotions/2022-04-02-Bogo">our official site</a>.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">FAQ</h2>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Q: I missed the deadline due to the time it took my pack purchase to get accepted by the WAX network. Can I still get a free pack?</h3>
<div class="text-base text-gray-50">No. I would suggest not waiting until the last minute purchase a pack.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Q: I purchased two packs during the event, will I get 2 free packs?</h3>
<div class="text-base text-gray-50">No. Each account will only be eligible to receive a single free pack when the promotion ends.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Q: How long will it take for us to receive our free packs?</h3>
<div class="text-base text-gray-50">You will receive your free pack up to 24 hours after the event ends. If there is
any expected delay, we will let you know via our Discord community.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">Q: I purchased a pack before the event, can I still get a free pack?</h3>
<div class="text-base text-gray-50">No, however we will be reaching out to some of our early pack purchasers for
other cool Dark Emblem goodies.</div>

It's that time! To celebrate deploying to production and give everyone a little
something before we get whitelisted by AtomicHub, we are hosting a Buy One
Get One event!

![Splash](media/2022-03-28-bogo/bogo-splash.jpg)



## BOGO Weekend

This weekend, from April 1, 9:00 PM PT to April 3, 11:59 PM PT, we are hosting
a BOGO event: buy ANY Dark Emblem Pack, and we will air drop you a FREE legendary
pack after the event ends.

## How it works

During this weekend, if you buy any Dark Emblem pack, we will air drop you one
legendary pack. Max 1 free pack per account.

We will check [WAX on Bloks](https://wax.bloks.io/account/darkemblems1) for transactions.
Only accounts where there is a **Recieve Token** Action with memo `purchase_pack:XYZ` during
the above time frame will be eligible for a free pack.

## LFG 🚀

Get ready for a free pack this weekend! Make sure you have a WAX account with some WAXP in it,
get signed into Dark Emblem, and read up on [our docs on how to buy your first pack](/docs/buying-packs)!

Read more about the promotion on [our official site](https://www.darkemblem.com/promotions/2022-04-02-Bogo).

## FAQ

### Q: I missed the deadline due to the time it took my pack purchase to get accepted by the WAX network. Can I still get a free pack?

No. I would suggest not waiting until the last minute purchase a pack.

### Q: I purchased two packs during the event, will I get 2 free packs?

No. Each account will only be eligible to receive a single free pack when the promotion ends.

### Q: How long will it take for us to receive our free packs?

You will receive your free pack up to 24 hours after the event ends. If there is
any expected delay, we will let you know via our Discord community.

### Q: I purchased a pack before the event, can I still get a free pack?

No, however we will be reaching out to some of our early pack purchasers for
other cool Dark Emblem goodies.

Buy One Get One Weekend 🎉

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    code: "code",
    h2: "h2",
    h3: "h3",
    img: "img"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsxs(_components.p, {
      children: ["We are working on our Whitelisting process with AtomicHub. This takes some time and may cause some changes along the way. If you have already opened some packs at this point, you will want to migrate your cards from the old ", _jsx(_components.code, {
        children: "cards"
      }), " schema to our new card schema. This is a one time migration that will update the image url and make sure all the cards show up in the correct schema."]
    }), "\n", _jsx(_components.p, {
      children: "To do this, you just need to transfer the card assets to our contract with a specific memo, then the contract will burn the old card and mint a new version of the NFT with the exact same traits."
    }), "\n", _jsx(_components.h2, {
      children: "Detailed Steps"
    }), "\n", _jsx(_components.p, {
      children: "How to migrate your cards:"
    }), "\n", _jsx(_components.h3, {
      children: "1. Go to your collection"
    }), "\n", _jsxs(_components.p, {
      children: ["Go to your AtomicHub collection and filter by the Dark Emblem collection (", _jsx(_components.code, {
        children: "darkemblemc1"
      }), ") and look for cards in the ", _jsx(_components.code, {
        children: "cards"
      }), " schema:"]
    }), "\n", _jsxs(_components.p, {
      children: ["Example link: ", _jsx(_components.code, {
        children: "https://wax.atomichub.io/profile/<YOUR_WAX_NAME>?collection_name=darkemblemc1&order=desc&schema_name=cards&sort=transferred#inventory"
      })]
    }), "\n", _jsx(_components.p, {
      children: "Make sure to unselect \"Only Whitelisted NFTs\"."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-04-12-card-migrate/1-filter.png",
        alt: "View your cards"
      })
    }), "\n", _jsx(_components.h3, {
      children: "2. Select all your Dark Emblem NFTs"
    }), "\n", _jsx(_components.p, {
      children: "Select all your Dark Emblem card NFTs. There is a little checkbox next to each card."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-04-12-card-migrate/2-select.png",
        alt: "Select your cards"
      })
    }), "\n", _jsx(_components.h3, {
      children: "3. Start a transfer"
    }), "\n", _jsx(_components.p, {
      children: "Click Actions -> Transfer."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-04-12-card-migrate/3-actions.png",
        alt: "Actions Transfer"
      })
    }), "\n", _jsx(_components.h3, {
      children: "4. Set up the transfer"
    }), "\n", _jsxs(_components.p, {
      children: ["Set the ", _jsx(_components.code, {
        children: "To"
      }), " field to \"darkemblems1\". It may say \"No results found\"."]
    }), "\n", _jsxs(_components.p, {
      children: ["Set the memo to ", _jsx(_components.code, {
        children: "migrate"
      }), ". This is very important. Without this memo, the contract will not mint your NFTs."]
    }), "\n", _jsx(_components.p, {
      children: "Double check the above inputs, they are case sensitive."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2022-04-12-card-migrate/4-migrate.png",
        alt: "Run the migration"
      })
    }), "\n", _jsx(_components.h3, {
      children: "5. Send the transfer"
    }), "\n", _jsx(_components.p, {
      children: "Sign your transfer. Once the contract receives your NFTs, it will burn them and remint them in the new schema."
    }), "\n", _jsx(_components.p, {
      children: "Thanks for working with us while we are going through the whitelisting process."
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, Object.assign({}, props, {
    children: _jsx(_createMdxContent, props)
  })) : _createMdxContent(props);
}
return {
  default: MDXContent
};


<div class="text-base text-gray-50">We are working on our Whitelisting process with AtomicHub. This takes some time and may cause some changes along the way. If you have already opened some packs at this point, you will want to migrate your cards from the old <code>cards</code> schema to our new card schema. This is a one time migration that will update the image url and make sure all the cards show up in the correct schema.</div>
<div class="text-base text-gray-50">To do this, you just need to transfer the card assets to our contract with a specific memo, then the contract will burn the old card and mint a new version of the NFT with the exact same traits.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Detailed Steps</h2>
<div class="text-base text-gray-50">How to migrate your cards:</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">1. Go to your collection</h3>
<div class="text-base text-gray-50">Go to your AtomicHub collection and filter by the Dark Emblem collection (<code>darkemblemc1</code>) and look for cards in the <code>cards</code> schema:</div>
<div class="text-base text-gray-50">Example link: <code>https://wax.atomichub.io/profile/&lt;YOUR_WAX_NAME&gt;?collection_name=darkemblemc1&amp;order=desc&amp;schema_name=cards&amp;sort=transferred#inventory</code></div>
<div class="text-base text-gray-50">Make sure to unselect &quot;Only Whitelisted NFTs&quot;.</div>
<div class="text-base text-gray-50"><img alt="View your cards" src="media/2022-04-12-card-migrate/1-filter.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">2. Select all your Dark Emblem NFTs</h3>
<div class="text-base text-gray-50">Select all your Dark Emblem card NFTs. There is a little checkbox next to each card.</div>
<div class="text-base text-gray-50"><img alt="Select your cards" src="media/2022-04-12-card-migrate/2-select.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">3. Start a transfer</h3>
<div class="text-base text-gray-50">Click Actions -&gt; Transfer.</div>
<div class="text-base text-gray-50"><img alt="Actions Transfer" src="media/2022-04-12-card-migrate/3-actions.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">4. Set up the transfer</h3>
<div class="text-base text-gray-50">Set the <code>To</code> field to &quot;darkemblems1&quot;. It may say &quot;No results found&quot;.</div>
<div class="text-base text-gray-50">Set the memo to <code>migrate</code>. This is very important. Without this memo, the contract will not mint your NFTs.</div>
<div class="text-base text-gray-50">Double check the above inputs, they are case sensitive.</div>
<div class="text-base text-gray-50"><img alt="Run the migration" src="media/2022-04-12-card-migrate/4-migrate.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">5. Send the transfer</h3>
<div class="text-base text-gray-50">Sign your transfer. Once the contract receives your NFTs, it will burn them and remint them in the new schema.</div>
<div class="text-base text-gray-50">Thanks for working with us while we are going through the whitelisting process.</div>


We are working on our Whitelisting process with AtomicHub. This takes some time and may cause some changes along the way. If you have already opened some packs at this point, you will want to migrate your cards from the old `cards` schema to our new card schema. This is a one time migration that will update the image url and make sure all the cards show up in the correct schema.

To do this, you just need to transfer the card assets to our contract with a specific memo, then the contract will burn the old card and mint a new version of the NFT with the exact same traits.

## Detailed Steps

How to migrate your cards:

### 1. Go to your collection

Go to your AtomicHub collection and filter by the Dark Emblem collection (`darkemblemc1`) and look for cards in the `cards` schema:

Example link: `https://wax.atomichub.io/profile/<YOUR_WAX_NAME>?collection_name=darkemblemc1&order=desc&schema_name=cards&sort=transferred#inventory`

Make sure to unselect "Only Whitelisted NFTs".

![View your cards](media/2022-04-12-card-migrate/1-filter.png)

### 2. Select all your Dark Emblem NFTs

Select all your Dark Emblem card NFTs. There is a little checkbox next to each card.

![Select your cards](media/2022-04-12-card-migrate/2-select.png)

### 3. Start a transfer

Click Actions -> Transfer.

![Actions Transfer](media/2022-04-12-card-migrate/3-actions.png)

### 4. Set up the transfer

Set the `To` field to "darkemblems1". It may say "No results found".

Set the memo to `migrate`. This is very important. Without this memo, the contract will not mint your NFTs.

Double check the above inputs, they are case sensitive.

![Run the migration](media/2022-04-12-card-migrate/4-migrate.png)

### 5. Send the transfer

Sign your transfer. Once the contract receives your NFTs, it will burn them and remint them in the new schema.

Thanks for working with us while we are going through the whitelisting process.
