Why WAX? - Dark Emblem

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    h2: "h2",
    img: "img",
    a: "a",
    ol: "ol",
    li: "li",
    h3: "h3"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "Hope everyone isn't sick of weekly updates yet! We are rolling out v2 of the testnet, we've announced the final $DREM rewards, and we are gearing up for mainnet."
    }), "\n", _jsx(_components.h2, {
      children: "Testnet v2"
    }), "\n", _jsx(_components.p, {
      children: "We are rolling v2 of the Testnet."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2021-12-05-state-of-play-update/dj-khaled-another-one.gif",
        alt: "Another one"
      })
    }), "\n", _jsxs(_components.p, {
      children: ["The old contracts still exist on the blockchain, but we have deployed a new set of contracts and the ", _jsx(_components.a, {
        href: "https://darkemblem.com",
        children: "dapp"
      }), " now points to the new contracts. All of the old card assets that were cached have been deleted as well."]
    }), "\n", _jsx(_components.p, {
      children: "As part of this deployment, we also fixed how the contract code was verified. You can now see the verified contract code when inspecting our contracts, NFT, and ERC20 token on Etherscan."
    }), "\n", _jsx(_components.h2, {
      children: "Early Supporter Role"
    }), "\n", _jsx(_components.p, {
      children: "We have announced the final $DREM rewards for being an Early Supporter and Testnet user."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "media/2021-12-05-state-of-play-update/rewards.png",
        alt: "Rewards"
      })
    }), "\n", _jsxs(_components.ol, {
      children: ["\n", _jsx(_components.li, {
        children: "Early Supporters will get 10 $DREM on release"
      }), "\n", _jsx(_components.li, {
        children: "Testnet users will get 5 $DREM on release"
      }), "\n"]
    }), "\n", _jsxs(_components.p, {
      children: ["Our ", _jsx(_components.a, {
        href: "https://www.darkemblem.com",
        children: "main site"
      }), " also has a countdown timer for the Early Supporter role. We will be closing that role at the end of the month (December 31, 2021)."]
    }), "\n", _jsx(_components.h2, {
      children: "Documentation"
    }), "\n", _jsxs(_components.p, {
      children: ["We rolled out additional documentation on how Pack IDs, traits, and rarities work. You can read more on our ", _jsx(_components.a, {
        href: "https://blog.darkemblem.com/docs",
        children: "docs"
      }), "."]
    }), "\n", _jsx(_components.h2, {
      children: "Card Improvements"
    }), "\n", _jsx(_components.p, {
      children: "Generally, this last week, the team has been focusing on card art, getting new cards implemented, and improving the way cards are generated."
    }), "\n", _jsx(_components.p, {
      children: "There are now improved color palettes for cards, a few more variants of our existing cards, and we've scaled backgrounds so rarer cards have nicer backgrounds."
    }), "\n", _jsx(_components.h2, {
      children: "Going Live"
    }), "\n", _jsx(_components.p, {
      children: "On top of the improvements above, we are also prepping for production. And the best way to prep is to run through different scenarios to see how we can respond."
    }), "\n", _jsx(_components.h3, {
      children: "How it Works"
    }), "\n", _jsxs(_components.ol, {
      children: ["\n", _jsx(_components.li, {
        children: "We come up with a catastrophic scenario that can happen in production."
      }), "\n", _jsx(_components.li, {
        children: "We determine what steps we need to mitigate the issue."
      }), "\n", _jsx(_components.li, {
        children: "We walk through the steps on local or testnet environments."
      }), "\n", _jsx(_components.li, {
        children: "We formalize these steps into what we call a \"Runbook\" – these are specific instructions that any of the devs can take in the event of a security issue, server crash, and more."
      }), "\n", _jsx(_components.li, {
        children: "Finally, we determine if there was anything missing from our contracts or infrastructure that could have helped us mitigate the issue."
      }), "\n"]
    }), "\n", _jsx(_components.p, {
      children: "Some positive outcomes from these runbooks:"
    }), "\n", _jsxs(_components.ol, {
      children: ["\n", _jsx(_components.li, {
        children: "We found some issues in the contracts that we have patched for the testnet."
      }), "\n", _jsx(_components.li, {
        children: "We formalized some of the mitigation patterns as tests against the contracts."
      }), "\n", _jsx(_components.li, {
        children: "We have a few more plans to help mitigate issues once the contracts are on mainnet."
      }), "\n"]
    }), "\n", _jsx(_components.h2, {
      children: "Looking Forward"
    }), "\n", _jsx(_components.p, {
      children: "We are excited for the coming months as we finalize our GEN0 artwork and start building our community in anticipation for mainnet!"
    })]
  });
}
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">Hope everyone isn&#x27;t sick of weekly updates yet! We are rolling out v2 of the testnet, we&#x27;ve announced the final $DREM rewards, and we are gearing up for mainnet.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Testnet v2</h2>
<div class="text-base text-gray-50">We are rolling v2 of the Testnet.</div>
<div class="text-base text-gray-50"><img alt="Another one" src="media/2021-12-05-state-of-play-update/dj-khaled-another-one.gif" style="max-height:500px;margin:auto;text-align:center"/></div>
<div class="text-base text-gray-50">The old contracts still exist on the blockchain, but we have deployed a new set of contracts and the <a href="https://darkemblem.com">dapp</a> now points to the new contracts. All of the old card assets that were cached have been deleted as well.</div>
<div class="text-base text-gray-50">As part of this deployment, we also fixed how the contract code was verified. You can now see the verified contract code when inspecting our contracts, NFT, and ERC20 token on Etherscan.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Early Supporter Role</h2>
<div class="text-base text-gray-50">We have announced the final $DREM rewards for being an Early Supporter and Testnet user.</div>
<div class="text-base text-gray-50"><img alt="Rewards" src="media/2021-12-05-state-of-play-update/rewards.png" style="max-height:500px;margin:auto;text-align:center"/></div>
<ol class="ml-4 list-decimal p-0">
<li>Early Supporters will get 10 $DREM on release</li>
<li>Testnet users will get 5 $DREM on release</li>
</ol>
<div class="text-base text-gray-50">Our <a href="https://www.darkemblem.com">main site</a> also has a countdown timer for the Early Supporter role. We will be closing that role at the end of the month (December 31, 2021).</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Documentation</h2>
<div class="text-base text-gray-50">We rolled out additional documentation on how Pack IDs, traits, and rarities work. You can read more on our <a href="https://blog.darkemblem.com/docs">docs</a>.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Card Improvements</h2>
<div class="text-base text-gray-50">Generally, this last week, the team has been focusing on card art, getting new cards implemented, and improving the way cards are generated.</div>
<div class="text-base text-gray-50">There are now improved color palettes for cards, a few more variants of our existing cards, and we&#x27;ve scaled backgrounds so rarer cards have nicer backgrounds.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Going Live</h2>
<div class="text-base text-gray-50">On top of the improvements above, we are also prepping for production. And the best way to prep is to run through different scenarios to see how we can respond.</div>
<h3 class="text-gray-50 text-xl font-bold text-gray-50">How it Works</h3>
<ol class="ml-4 list-decimal p-0">
<li>We come up with a catastrophic scenario that can happen in production.</li>
<li>We determine what steps we need to mitigate the issue.</li>
<li>We walk through the steps on local or testnet environments.</li>
<li>We formalize these steps into what we call a &quot;Runbook&quot; – these are specific instructions that any of the devs can take in the event of a security issue, server crash, and more.</li>
<li>Finally, we determine if there was anything missing from our contracts or infrastructure that could have helped us mitigate the issue.</li>
</ol>
<div class="text-base text-gray-50">Some positive outcomes from these runbooks:</div>
<ol class="ml-4 list-decimal p-0">
<li>We found some issues in the contracts that we have patched for the testnet.</li>
<li>We formalized some of the mitigation patterns as tests against the contracts.</li>
<li>We have a few more plans to help mitigate issues once the contracts are on mainnet.</li>
</ol>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Looking Forward</h2>
<div class="text-base text-gray-50">We are excited for the coming months as we finalize our GEN0 artwork and start building our community in anticipation for mainnet!</div>

Hope everyone isn't sick of weekly updates yet! We are rolling out v2 of the testnet, we've announced the final $DREM rewards, and we are gearing up for mainnet.



## Testnet v2

We are rolling v2 of the Testnet.

![Another one](media/2021-12-05-state-of-play-update/dj-khaled-another-one.gif)

The old contracts still exist on the blockchain, but we have deployed a new set of contracts and the [dapp](https://darkemblem.com) now points to the new contracts. All of the old card assets that were cached have been deleted as well.

As part of this deployment, we also fixed how the contract code was verified. You can now see the verified contract code when inspecting our contracts, NFT, and ERC20 token on Etherscan.

## Early Supporter Role

We have announced the final $DREM rewards for being an Early Supporter and Testnet user.

![Rewards](media/2021-12-05-state-of-play-update/rewards.png)

1. Early Supporters will get 10 $DREM on release
2. Testnet users will get 5 $DREM on release

Our [main site](https://www.darkemblem.com) also has a countdown timer for the Early Supporter role. We will be closing that role at the end of the month (December 31, 2021).

## Documentation

We rolled out additional documentation on how Pack IDs, traits, and rarities work. You can read more on our [docs](https://blog.darkemblem.com/docs).

## Card Improvements

Generally, this last week, the team has been focusing on card art, getting new cards implemented, and improving the way cards are generated.

There are now improved color palettes for cards, a few more variants of our existing cards, and we've scaled backgrounds so rarer cards have nicer backgrounds.

## Going Live

On top of the improvements above, we are also prepping for production. And the best way to prep is to run through different scenarios to see how we can respond.

### How it Works

1. We come up with a catastrophic scenario that can happen in production.
2. We determine what steps we need to mitigate the issue.
3. We walk through the steps on local or testnet environments.
4. We formalize these steps into what we call a "Runbook" – these are specific instructions that any of the devs can take in the event of a security issue, server crash, and more.
5. Finally, we determine if there was anything missing from our contracts or infrastructure that could have helped us mitigate the issue.

Some positive outcomes from these runbooks:

1. We found some issues in the contracts that we have patched for the testnet.
2. We formalized some of the mitigation patterns as tests against the contracts.
3. We have a few more plans to help mitigate issues once the contracts are on mainnet.

## Looking Forward

We are excited for the coming months as we finalize our GEN0 artwork and start building our community in anticipation for mainnet!

State of Play Update December 5

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    h2: "h2",
    ul: "ul",
    li: "li"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "Dark Emblem is ditching ETH and Web3 and moving to WAX and WAXJS. This is a major change and was quite an overhaul of our system, but it's also a big step forward."
    }), "\n", _jsx(_components.h2, {
      children: "Why WAX"
    }), "\n", _jsx(_components.p, {
      children: "There are a few reasons to move to WAX:"
    }), "\n", _jsxs(_components.ul, {
      children: ["\n", _jsx(_components.li, {
        children: "Proof of stake"
      }), "\n", _jsx(_components.li, {
        children: "Lower gas fees"
      }), "\n", _jsx(_components.li, {
        children: "Faster transaction times"
      }), "\n", _jsx(_components.li, {
        children: "Lower contract overhead"
      }), "\n"]
    }), "\n", _jsx(_components.p, {
      children: "WAX is a proof of stake blockchain. While ETH2.0 promises proof of stake and lower gas fees, I am not sure about the timeline and I don't want to publish an ETH contract that we have to migrate everyone from once proof of stake is released. We had a full set of contracts created, but random card mints from packs proved to be incredibly expensive due to gas. Gas constraints were starting to influence what we wanted to do with Dark Emblem and how we were going to implement it. With WAX, while we do have to worry about RAM costs, we are able to pay for this on behalf of our users via the WAXP used to purchase packs! Our contract will pay for the RAM to buy packs and mint cards!"
    }), "\n", _jsx(_components.p, {
      children: "We did do a full testnet testing round and found that transactions were incredibly slow on the Ethereum blockchain. Participants would purchase a pack and then sit there waiting to see what cards they got. With WAX, we are seeing incredible response times for transactions and are able to show purchased and opened packs quickly."
    }), "\n", _jsx(_components.p, {
      children: "WAX also has a built in concept of assets, asset transfers, and asset ownership. Using this means that others don't have to rely on us implementing the ERC721 standard correctly. Dark Emblem can focus on building an awesome card game on WAX, rather than worrying about interface compability, future extensibility, and security around our implementation of ERC721 and ERC20 standards."
    }), "\n", _jsx(_components.h2, {
      children: "How it will work"
    }), "\n", _jsx(_components.p, {
      children: "With Dark Emblem moving over to WAX, you will need to create a WAX account and buy WAXP. The WAX ecosystem make this easy by just going to https://all-access.wax.io/."
    }), "\n", _jsx(_components.p, {
      children: "Once you have an account, you can just visit our Dapp to start buying and opening packs."
    })]
  });
}
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">Dark Emblem is ditching ETH and Web3 and moving to WAX and WAXJS. This is a major change and was quite an overhaul of our system, but it&#x27;s also a big step forward.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Why WAX</h2>
<div class="text-base text-gray-50">There are a few reasons to move to WAX:</div>
<ul class="ml-4 list-disc p-0">
<li>Proof of stake</li>
<li>Lower gas fees</li>
<li>Faster transaction times</li>
<li>Lower contract overhead</li>
</ul>
<div class="text-base text-gray-50">WAX is a proof of stake blockchain. While ETH2.0 promises proof of stake and lower gas fees, I am not sure about the timeline and I don&#x27;t want to publish an ETH contract that we have to migrate everyone from once proof of stake is released. We had a full set of contracts created, but random card mints from packs proved to be incredibly expensive due to gas. Gas constraints were starting to influence what we wanted to do with Dark Emblem and how we were going to implement it. With WAX, while we do have to worry about RAM costs, we are able to pay for this on behalf of our users via the WAXP used to purchase packs! Our contract will pay for the RAM to buy packs and mint cards!</div>
<div class="text-base text-gray-50">We did do a full testnet testing round and found that transactions were incredibly slow on the Ethereum blockchain. Participants would purchase a pack and then sit there waiting to see what cards they got. With WAX, we are seeing incredible response times for transactions and are able to show purchased and opened packs quickly.</div>
<div class="text-base text-gray-50">WAX also has a built in concept of assets, asset transfers, and asset ownership. Using this means that others don&#x27;t have to rely on us implementing the ERC721 standard correctly. Dark Emblem can focus on building an awesome card game on WAX, rather than worrying about interface compability, future extensibility, and security around our implementation of ERC721 and ERC20 standards.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">How it will work</h2>
<div class="text-base text-gray-50">With Dark Emblem moving over to WAX, you will need to create a WAX account and buy WAXP. The WAX ecosystem make this easy by just going to https://all-access.wax.io/.</div>
<div class="text-base text-gray-50">Once you have an account, you can just visit our Dapp to start buying and opening packs.</div>

Dark Emblem is ditching ETH and Web3 and moving to WAX and WAXJS. This is a major change and was quite an overhaul of our system, but it's also a big step forward.



## Why WAX

There are a few reasons to move to WAX:

* Proof of stake
* Lower gas fees
* Faster transaction times
* Lower contract overhead

WAX is a proof of stake blockchain. While ETH2.0 promises proof of stake and lower gas fees, I am not sure about the timeline and I don't want to publish an ETH contract that we have to migrate everyone from once proof of stake is released. We had a full set of contracts created, but random card mints from packs proved to be incredibly expensive due to gas. Gas constraints were starting to influence what we wanted to do with Dark Emblem and how we were going to implement it. With WAX, while we do have to worry about RAM costs, we are able to pay for this on behalf of our users via the WAXP used to purchase packs! Our contract will pay for the RAM to buy packs and mint cards!

We did do a full testnet testing round and found that transactions were incredibly slow on the Ethereum blockchain. Participants would purchase a pack and then sit there waiting to see what cards they got. With WAX, we are seeing incredible response times for transactions and are able to show purchased and opened packs quickly.

WAX also has a built in concept of assets, asset transfers, and asset ownership. Using this means that others don't have to rely on us implementing the ERC721 standard correctly. Dark Emblem can focus on building an awesome card game on WAX, rather than worrying about interface compability, future extensibility, and security around our implementation of ERC721 and ERC20 standards.

## How it will work

With Dark Emblem moving over to WAX, you will need to create a WAX account and buy WAXP. The WAX ecosystem make this easy by just going to https://all-access.wax.io/.

Once you have an account, you can just visit our Dapp to start buying and opening packs.

Why WAX?

/*@jsxRuntime automatic @jsxImportSource react*/
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = Object.assign({
    p: "p",
    h2: "h2"
  }, props.components);
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "Dark Emblem is moving to AtomicHub – the one stop solution for creating, trading, buying and selling NFTs that is already used by hundreds of thousands of loyal users. This will give us a common place to display our WAX NFTs for others to see, buy, and sell."
    }), "\n", _jsx(_components.h2, {
      children: "Why Atomic Hub?"
    }), "\n", _jsx(_components.p, {
      children: "You can think of AtomicHub like the OpenSea for WAX based assets. By utilizing the\nAtomicAssets standard for Non Fungible Token (NFT) standard, our Dark Emblem cards and packs are able to be interacted with via AtomicHub."
    }), "\n", _jsx(_components.p, {
      children: "It offers a powerful feature set while keeping unnecessary complexity to a minimum and focusses on RAM efficiency."
    }), "\n", _jsx(_components.h2, {
      children: "No RAM Costs for users"
    }), "\n", _jsx(_components.p, {
      children: "The RAM cost is paid fully by our Dark Emblem dapps that creates the NFTs. Even when transfering assets, this stays the same."
    }), "\n", _jsx(_components.h2, {
      children: "Powerful Trade Offers"
    }), "\n", _jsx(_components.p, {
      children: "AtomicAssets features a native implementation of two sided trade offers (similar to Steam or WAX Express Trade). This allows creating and accepting offers with a single action. The implementation of the offers also allows for peer to peer marketplaces that don't require transferring ownership to a market contract."
    })]
  });
}
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">Dark Emblem is moving to AtomicHub – the one stop solution for creating, trading, buying and selling NFTs that is already used by hundreds of thousands of loyal users. This will give us a common place to display our WAX NFTs for others to see, buy, and sell.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Why Atomic Hub?</h2>
<div class="text-base text-gray-50">You can think of AtomicHub like the OpenSea for WAX based assets. By utilizing the
AtomicAssets standard for Non Fungible Token (NFT) standard, our Dark Emblem cards and packs are able to be interacted with via AtomicHub.</div>
<div class="text-base text-gray-50">It offers a powerful feature set while keeping unnecessary complexity to a minimum and focusses on RAM efficiency.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">No RAM Costs for users</h2>
<div class="text-base text-gray-50">The RAM cost is paid fully by our Dark Emblem dapps that creates the NFTs. Even when transfering assets, this stays the same.</div>
<h2 class="text-gray-50 text-2xl font-bold text-gray-50">Powerful Trade Offers</h2>
<div class="text-base text-gray-50">AtomicAssets features a native implementation of two sided trade offers (similar to Steam or WAX Express Trade). This allows creating and accepting offers with a single action. The implementation of the offers also allows for peer to peer marketplaces that don&#x27;t require transferring ownership to a market contract.</div>


Dark Emblem is moving to AtomicHub – the one stop solution for creating, trading, buying and selling NFTs that is already used by hundreds of thousands of loyal users. This will give us a common place to display our WAX NFTs for others to see, buy, and sell.

## Why Atomic Hub?

You can think of AtomicHub like the OpenSea for WAX based assets. By utilizing the
AtomicAssets standard for Non Fungible Token (NFT) standard, our Dark Emblem cards and packs are able to be interacted with via AtomicHub.

It offers a powerful feature set while keeping unnecessary complexity to a minimum and focusses on RAM efficiency.

## No RAM Costs for users

The RAM cost is paid fully by our Dark Emblem dapps that creates the NFTs. Even when transfering assets, this stays the same.

## Powerful Trade Offers

AtomicAssets features a native implementation of two sided trade offers (similar to Steam or WAX Express Trade). This allows creating and accepting offers with a single action. The implementation of the offers also allows for peer to peer marketplaces that don't require transferring ownership to a market contract.
