Gas Price Too Low - If you only want to pay 1.6 Euros/ Liter, then you have to wait until the supply / demand dynamics of gasoline cause the price to drop below this level. So, transactions with prices too low may take a while to go through. You might be waiting outside the gas station before you are able to take your trip.

Gas Limit Too Low - This is a problem. If the limit is too low, you might run out of fuel, and become stranded in the middle of nowhere.

Gas Price Too High - If you are willing to pay more than the market rate for anything, surely someone will quickly sell it to you.

Gas Limit Too High - This is NOT a problem. If your tank is 50 liters but the trip only takes 40 liters, you still have the 10 liters left for the next trip.

EVM Chains (Ethereum / Polygon / Etc)

Before you send a transaction, you must specify both the gas price (in Gwei) and limit (in gas units). Then, metamask will multiply these together to estimate the cost for your transaction.

However, when you view the transaction on the block explorer, you see that the transaction only used 5% of the gas limit, and thus the cost was significantly lower.

https://polygonscan.com/tx/0x860f359a2cac11c31b0423a30b4fa8bb9a2ec8c9271681151561a34b77075d06

So, why send extra gas in the first place, if it just makes users think that things are more expensive than they are? The reason is because if the gas limit is too low, the transaction will fail entirely, and you will lose all of the fee and gain no benefit.

Can’t Nerds Do Something About This?

Failed transactions need to cost gas because they cost network resources - if they were free then attackers could flood the network with them and bring it down. They still can, but it comes at tremendous cost so it does not happen.

There are many things that engineers have made to improve the user experience. The first one is that there are gas trackers where you can see current prices. Sometimes metamask will set them, but it can be inconsistent.

https://polygonscan.com/gastracker#gassender

Angel Battles needs to err on the side of providing more gas, because battle actions are not simple - sometimes for instance you might win a battle and receive rewards, move spots on a mountain, etc.

Another thing to note is that the minimum gas fees on polygon are 30 gwei. In the accounts section you can set defaults for Angel Battles, so you do not need to change them in your wallet each time.

In any case, the fees on Polygon are SIGNIFICANTLY cheaper than mainnet, which is why our game (and all other similar games) have moved to scaling solutions.

If you still have questions, come ask around in the Angel Battles discord.

These random numbers aren’t free, and must be paid for with LINK tokens. As of 12/2/2022, each random number costs 0.000763 USD, or 1300 numbers per dollar. The devs will initially fund both the BattleMtnData contract and the ABStore contract with an amount of tokens that should last for a significant amount of time. For instance, if battle mountain conditions were changed at the max rate of every 24 hrs, $1 worth of link tokens could last almost 4 years.

However, if usage is extremely high, the game lives on for decades, if the Angel Battles DAO votes to allow more frequent battle mountain changes or deploys additional contracts that protect other actions with commit / reveal schemes, funds will have to be replenished.

The key wrinkle is that chainlink uses TWO different LINK tokens on Polygon. The ERC20 token

0xb0897686c545045aFc77CF20eC7A532E3120E0F1

https://polygonscan.com/address/0xb0897686c545045aFc77CF20eC7A532E3120E0F1

is what can be purchased on exchanges, and the ERC677 version which is actually consumed when producing random numbers.

0x53E0bca35eC356BD5ddDFebbD1Fc0fD03FaBad39

https://polygonscan.com/address/0x53E0bca35eC356BD5ddDFebbD1Fc0fD03FaBad39

Users can purchase the ERC20 version and then go to pegswap.chain.link to switch between. The contract is at 0xAA1DC356dc4B18f30C347798FD5379F3D77ABC5b and the swap function requires approvals on the related contracts.

https://pegswap.chain.link/

ERC677 is a standard that allows information to be sent along with token transfers.

Once you have those tokens, simply send them to the angel battles contracts through your wallets. Thank you in advance for your help in decentralizing and keeping Angel Battles alive!

This contract wrapped the Jan 2018 angel, pet, and accessory data contracts. Thus, people who minted from this contract received historical NFTs that were 2022 mints on a 2018 contract.

People who held the original NFTs from 2018 and wrapped them are still in possession of 2018 mints on the 2018 contract.

How do collectors distinguish between the two?

All new mints in 2022 were made with base stats (0 experience, Aura values either 1 or 0)

OpenSea Searchable Metadata

Angels Only – Angel cards (card series 0-23) are the easiest to understand. Angel cards record a createdtime when the original card was minted.  This is in the unix timestamp format, which can be decoded with a site like https://www.unixtimestamp.com.

Angels also receive experience for winning battles. Thus, any card with experience > 0 is not only an older mint, but a card that was actually used in the game. Higher experience cards are more rare. 2018 angel mints can still have 0 experience if they were just held and not used in the game, but their createdtime will be from 2018.

Pets - Pet cards minted during 2022 have 1 for each aura color (auraRed, auraBlue, auraYellow). Angel cards have auras corresponding to their color components. For instance all orange angels have auraRed = 1, auraYellow = 1, and auraBlue = 0. Accessories have all auras 0.

Thus, if any pet has any aura color 2 or more, that pet was an original mint. The higher the aura colors the rarer. Pets with higher aura values (especially all 3 components) were likely bred from powerful parents and used in aura training.

Higher aura values will have a low % of cards that bear the trait.

Digging deeper with Non - Searchable Metadata

Wrapped cards are  connected to their underlying historic cards through an id system. It’s important to remember that the 721 contract has one numbering system for ALL cards together. For instance, token id 0 is a pet (kitten) while token id 1 is an angel (Berakiel).

With the historic cards, they used 3 different sets of ids. For instance angel id 1 is a Berakiel card, pet id 1 is a gecko named Matilda, accessory id 1 is a set of leather bracers.

The lower the id number is, the older the card, compared to other cards of that type. For instance, angel #42 was always made before angel #43. However, angel #42 might not be older than pet #42 or accessory #42.

You can also go to the wrapper contract listed above on Etherscan and then click ‘contract’ and ‘read contract’. Enter the token ID in ABTokenCollection and press ‘query’ (no wallet connection required).

Once you find the old id, you click through to the historic angel contract, historic pet contract, or historic accessory contract and read more information.

The first pet card minted in 2022 (721 id 0) was pet id 3165. The first angel card minted in 2022 (721 id 1) was angel id 1032. The first accessory card minted in 2022 (721 id 135) was accessory id 104.

There were 33 angels, 3 pets, and 6 accessories airdropped in 2022 to people who had used the 2019 destructive wrapper.

Thus, any angel with old id less than 998, pet with old id less than 3162, or accessory with old id less than 98 is a historic card. The lower the id number, the older the card. The data is in the blockchain to find exact mint dates, but it requires digging through internal transactions.

Other Timestamps

Pets have lastTrainingTime and lastBreedingTime timestamps. Angels have lastBattleTime and lastVsBattleTime. Not every card will have these, but they would establish that the card was used at least once for the specified action and when that happened.

Discord

We have renamed the #marketplace channel in to #find-2018-mints so players can talk about cards they are looking to buy of sell.

P. S. In retrospect, would it have been nice to include a is_2018 flag in the metadata? Of course! However, the metadata is returned directly from the contract and not updatable. This is blockchain – nothing is as easy as it could be!

Angel Battles is a limited-supply,  pre-ERC721 game with the first contract deployed on the Ethereum mainnet in block 4949586 (Jan-22-2018 01:42:39 AM +UTC).

The game was one of the most complex and functional games of its time, spanning 3 NFT data contracts and dozens of gameplay contracts. Features included:

              Three Token Types – Angel Cards were the base card and had one of 6 aura colors. Angels were sold and earned experience by winning arena battles. Pet Cards were not sold, but could be captured in battle and bred to create stronger types. For instance, a Falcon + a Unicorn could create a Pegasus. Accessory Cards were sold and helped in other parts of the game – for instance a cricket could increase your chance of luring pets of the lizard line.

              Global Leaderboard – Players around the world faced off with their angel/pet/accessory teams to try to climb their way to one of the top 20 worldwide ranks. The game featured both ‘player vs computer’ and ‘player vs player’ mechanics.

              Sponsored Leaderboards – Angel Battles was one of the first true play to earn games where players could earn Ethereum – any company could trustlessly open a sponsored leaderboard and display their logo on a 4 team board that was open for 1 week. The teams on the board when it closed received a % of the prize money and special medal NFTs.

              In Game NFT Burn Mechanic – Players could choose to ‘retire’ 6 of their pets in order to receive a higher level pet.

              Aura Training – Players could train their pets with angels of compatible auras to increase the aura power of their pets during future battles.

              Dynamic Battle Cooldowns – In order to increase competitiveness, the battle contract stored the experience level of the strongest angel – so that newer players could battle and earn experience points more frequently.

Angel Battles helped to onboard many new users to the Ethereum ecosystem as devs hosted IRL parties where users received free ETH and cards, help setting up a wallet, and guidance on how to best play the game. Angel Battles was in the top 5 for all Ethereum games in DAU on Dappradar, when gas was around 0.1 GWEI, but the complexity of the game meant that there was a steep drop off in users once gas prices increased. 

Angel Battles predates full adoption of the ERC721 standard, and thus our game created our own customized implementation of the ideas behind Non-Fungible Tokens. For instance, while ERC 721 uses ‘approvals’ for tokens, our game implemented a parallel mechanism with ‘token locks’.

Cards were bought and sold on the Wyvern Exchange, which allowed trading any Ethereum asset (even smart contracts!). Wyvern’s open source contracts later became the basis for OpenSea, but OpenSea supported trading only of ERC721 NFTs.

During the last 4.5 years, work has been progressing on the completely redesigned Angel Battles 2 (full guide), which is deployed on Polygon to take advantage of low gas fees. In the new game, 100% of the Matic used for purchasing cards goes to the Gitcoin Matching Fund Multisig.

We have also created an ERC721 wrapper contract for the historical NFTs to allow minting and trading. Prices and supply have in general been reduced from 2018 levels. Tokens now have a max total supply of 7525 total cards (2000 Angels, 1125 Accessories, 4400 pets).

For instance, Gabriel (card id #15) has a maximum supply of 45. There were 15 minted in 2018, which means 30 can be minted during the historical relaunch.

How can collectors be assured of the scarcity of supply from the 2018 contracts?

All 3 contracts are open source, verified, and follow the same general pattern.

AngelCardData - https://etherscan.io/address/0x6d2e76213615925c5fc436565b5ee788ee0e86dc#readContract

PetCardData – https://etherscan.io/address/0xb340686da996b8b3d486b4d27e38e38500a9e926#readContract

AccessoryData – https://etherscan.io/address/0x466c44812835f57b736ef9F63582b8a6693A14D0#readContract

There is no minting directly from the contract. All minting of new supply happens by calling the setAngel(), setPet(), and setAccessory() functions. These functions can only be called from a special list of addresses that have the ‘seraphim’ role. On each contract, you can call the totalSeraphims() function to get the number of addresses that hold the ‘seraphim’ role. You can also call seraphims(address) which returns true for addresses that are seraphim and false for addresses that are not.

Seraphim can be added and removed only by the admin key, which is called the creatorAddress. The creator address is the address that deployed the contract**, angelbattles.eth** (https://etherscan.io/address/0x20886ba6fd8731ed974ba00108f043fc9006e1f8 )

Supply is managed through the wrapper contract. This contract has the seraphim role on the angel, pet, and accessory contracts.

Once the wrapper contract is successfully deployed and tested, the removeCreator() function will be called on AngelCardData and AccessoryData. This will ‘burn’ the admin key (set it to the 0 address) and ensure that no other seraphim can ever be added. There is no admin key burn function on the Pets contract.

Wrapper Contract Details

The wrapper contract is open source and verified at: https://etherscan.io/address/0x1d9711c7c67ace347ff45661708aeac4bbb2aed3

There is no token uri server. All images are stored on IPFS and all other metadata is returned directly from the contract as a base64 encoded json object.  

The admin key on the wrapper cannot take NFTs, destroy NFTs, or change supply. It can only change the default gateway (website serving the IFPS images). This is to remove any certain public IPFS gateway as a single point of failure.

Angel Battles 2 Rewards For Historical NFT Owners

While historical collectors main purpose may be securing ownership of early digital assets, they will also receive bonus cards in order to play the Angel Battles 2 game.

Owners of cards purchased in 2018/2019 will receive their exact cards (experience, aura power, etc.) airdropped in Angel Battles 2 along with 5% of Halo token supply, according to a snapshot taken on  8/27/2022. (Free to mint cards are not airdropped)

Owners of newly minted wrapped historical cards will also receive exact copies of their cards airdropped at dev expense on Polygon, subject to the following exceptions:

The snapshot for these historic cards will be taken on 12/9/2022 around 1800 GMT.

How To Mint / Wrap

Collectors can visit www.angelbattles.com/historic where they can mint new cards, manage existing cards, see their sets, see the final state of the historic leaderboard, etc.

On the home page, users can see the existing and max supply of each token. These numbers include both wrapped and unwrapped cards. On the Manage Team section, owners of historical cards can choose to wrap them into the 721 wrapper for trading on OpenSea or other marketplaces. Pets can be wrapped directly, while angels and accessories must be ‘unlocked’ prior to wrapping.

When a historic card is wrapped, the wrapper contract itself takes ownership of the historic (pre-721) NFT. When a card is unwrapped, the wrapped (721) version is burned, and the original historic card is transferred back to the owner. Owners can wrap and unwrap their cards as often as they wish.

When new cards are minted from the wrapper, the wrapped (721) and historic (pre-721) versions are both created, with the historic card owned by the wrapper contract. Note: Wrapping and unwrapping cards can cause ‘duplicate’ cards to appear on OpenSea – there is only one card not owned by the 0 address, however.

2019 Destructive Wrapper

There was a 721 Wrapper created in 2019 which allowed minting new cards disconnected from the historical ones.

https://etherscan.io/address/0xdc32ff5aada11b5ce3caf2d00459cfda05293f96

The wrapper and associated contracts allowed historic card owners to ‘convert’ their cards to 721, but they had to burn them in the process.

Fortunately, only 110 tokens were ever issued from this contract, and only a handful were from burning.  Devs have airdropped identical historic cards to anyone who burned their previous historic cards or purchased cards from this wrapper.

The wrapper will receive no support going forward, has issues with metadata on Opensea (due to limits on Pinata’s free gateway) and should not be used.

Angel Battles 2 Game

The Angel Battles 2 game has implemented several design decisions to maximize decentralization, robustness, and sustainability:

              Game Parameter Governance Fully On Chain – Turning any of the game parameters can only be done by voting from the Halo Token holders and cannot be vetoed by devs.

              100% of Halo tokens streamed to community – Angel Battles 2 was made by volunteers and has no investors. Halo tokens were airdropped to previous players, game contracts, and holders of various NFTs. Tokens are streamed over 5 years to promote organic growth.

              Code and Images 100% Open Source  - All images are CC0 licensed and all code is released under the MIT license.

100% of New Revenues to Gitcoin – All Matic used to buy cards in the new version can be sent to the Gitcoin matching multisig at any time by any player.

              No Servers Needed – There are no Token URI servers or other gameplay servers. The front end is hosted on IPFS, open source on github, and linked from AngelBattles.eth (coming soon)

              Randomness Protected – The most powerful cards are protected through a commit / reveal scheme with randomness from Chainlink VRF to protect against MEV extracting flashbots bundles and other attacks.

We’re sorry you are having issues playing Angel Battles. First of all, it’s important to understand how Angel Battles works – you are playing a cutting edge, publicly available, globally distributed system that no one ‘owns’ or is ‘in charge’ of. Angel Battles original devs have done our best to ensure you have a smooth experience, but there may be certain issues.

If the question is about how the game works, strategy, etc. – make sure to check the official guides first.

The game is complex and the guides are detailed. If it’s a blockchain issue, however, try the following tips to help you troubleshoot.

Step 1 - Localize the Problem – Make sure you are logged in to your wallet and connected to the site. If you check your wallet and the tx says ‘pending’ or ‘queued’, then it’s probably an issue with the Poylgon network. If the web user interface (UI) looks out of wack, or things aren’t refreshing, it could be a problem with the web front end.

Try Refreshing the Page – In the case where your angels weren’t loading, a battle result was taking forever (but the transaction went through) or your wallet wasn’t connecting, refreshing the page can help.

Change RPC Provider – Unless you run your own node, you need to use someone else to provide this direct connection to the blockchain. These nodes generally work, but can become congested, fail, or implement rate limits. Sometimes switching to an alternative RPC provider can help restore your connection to the blockchain. This is more of an issue on testnets vs Polygon mainnet.

Reset Metamask – If you have many ‘queued’ transactions in metamask that are not going through, sometimes resetting metamask may help. Go to Settings >> advanced >> reset account. Note: resetting will NOT require you to reenter your seed phrase or affect anything on the blockchain.

Increase Gas Limit – Wallets will usually estimate how much gas you need for a certain action, but sometimes due to randomness or other user actions, this fails. If you have a tx that fails and the gas used is a high % of the gas available, increasing the gas limit might help. We have tried to hardcode this in where helpful. Note: Any unused gas is always refunded back to you, so although your wallet might estimate a higher fee, what you actually pay will be lower. Also, be careful not to confuse the gas limit with the gas price.

Run The Front End Locally – You can get a copy of the front end code and run it locally, if there are issues accessing the front end on IPFS. Running the front end locally will also allow you to insert logging statements or make other changes. If your front end change improves the user experience, consider opening a pull request.

Speed Up Tx - Most wallets will select a good gas price, but networks can quickly become congested (i.e., with spikes in prices, popular NFT mints, etc.). You can usually choose to ‘speed up’ a transaction by paying a higher price.

Try Later – RPC issues, network congestions, etc. will generally resolve themselves over time. Sometimes waiting a couple of hours can make for a much better experience.

Manual Update Button – For Arena and VS Battles, the UI should automatically update after the blockchain confirms the result of a battle. However, we have included a manual update button that will read the current state of the battle (round, hp, buffs, etc.) and update the UI.

Open The Console – You can right click and then ‘inspect’ if on desktop to see the browser console. We have embedded some statements that may help and you can use the browser’s built in debugger.

Be Aware of Card Quantity – The web UI needs to read each card from the blockchain, so if you own a very large number of cards (i.e., many hundreds) it might be best to split them between wallets.

Ask for More Help – You can always open an issue on the Angel Battles github repo or discord https://discord.gg/u2xgWuQ

1. Security – While we don’t need the full security of Ethereum, a more secure scaling solution is better.

2. Availability – Zk Rollups are promising, especially after proto-danksharding is implemented, but we need something available today.

3. Full EVM Compatibility – Angel Battles 2 is a complex game – we need something more than for instance a rollup which only allows NFT trading. We need a chain that allows our users to permissionlessly deploy battle mountains.

4. Infrastructure – While talking to our players and the larger Ethereum community, users constantly prioritized access to key infrastructure like Uniswap and Opensea. We also wanted a place where Tally.xyz was deployed for managing DAO proposals.

5. Ramps – We wanted a place where it was easy for a large amount of the world’s population to purchase the platform’s native token for gas. We also wanted a place that had wide bridge support from other networks.

6. Stable Native Token – We prefer a place where the native (gas) token is stable so card prices won’t fluctuate.

7. Low Gas Fees – Lower gas fees will enable more players to play more frequently with the convenience of not worrying about scheduling their playing.

8. Long Term Stability – We want a scaling solution that will be around for decades.

9. Community Ethos – We wanted a place aligned with the beliefs of Ethereum.

10. Technical Ability – We need a chain that actually works, has no downtime, good RPC endpoints, etc.

11. Gitcoin Matching - In order to donate all sales to Gitcoin, we need a chain where they have deployed their multi-sig.

While there were no scaling solutions that checked all the boxes, Polygon most closely aligns with the needs and wants of our users. There is a reason that several major brands are launching projects on Polygon.

We are excited to reach the next milestone towards getting Angel Battles 2 ready for the public.

Random numbers play a key role in Angel Battles and similar games. They control everything from how hard you might hit, to which cards you receive in each pack, to which monsters you will face. Yet, truly random numbers are one of the hardest problems in computer science.

If this wasn’t bad enough, flashbots and other Miner Extractable Value (MEV) tools allow all kinds of powerful manipulation. For instance, one thing you can do is submit a ‘bundle’ of transactions, where either ALL of the transactions will run or NONE of the transactions will run. For instance, a malicious user could submit a bundle of 2 transactions

1. Buy the ultimate card pack

2. Send the Michael card I just received to my other address.

Normally, a user has a 1% chance to receive a Michael card when purchasing the ultimate pack. However, by submitting this bundle, flashbots software would try to do this in every block, without any cost until the Michael card was successful. This is because the 99 times out of 100 when they received something other than the Michael card, the 2nd tx would fail so the first tx would never go in the block.

There are several key mitigations. We highly recommend this excellent blog post written by Martin from Quantstamp for technical details.

In general, the idea is to make it so that the cost of manipulating randomness in Angel Battles is higher than the benefit that an attacker can receive. We also have to balance this out with the difficulty imposed on honest players. For instance, the result of a simple swing of the sword uses only the built in randomness. If someone were to go to the time and expense to manipulate a single PVP battle on the leaderboard so that they could defeat a marginally stronger opponent, that opponent can always just reclaim the spot right afterwards.

However, there are two key aspects of Angel Battles that must be protected. These are getting the ultimate pack and changing conditions on the battle mountain.

NOTE: Sometimes, metamask may warn you that it cannot predict gas and therefore a tx may fail. If you have already committed, you should be safe to reveal. This is because it can be difficult to simulate these tx.

Getting the Ultimate Pack – You must burn Halo tokens in order to receive a card from the ultimate pack. In this case, you will first send a ‘commit’ transaction. This commits you to the action – you must burn your Halo tokens and information about the resulting card is stored in the contract. This information is private, meaning other contracts are not allowed to read it. Finally, you must come back at least 10 blocks later and send a ‘reveal’ transaction, where you will actually receive your card.

Changing Mountain Conditions – Mountain conditions can be changed every 24 hours, and any player may change the conditions for all players. Thus, one player commits, and then any player can reveal after 10 blocks. Once a player has committed, the next player must reveal.

Pet cards are special within the world of Angel Battles because you can acquire them by breeding or retiring existing pets. There are 5 levels of pets

1 Star: Domestic

2 Star: Wild Easy

3 Star: Wild Hard

4 Star: Epic Pets

5 Star: Elementals

Elementals cannot breed with each other, but all the other types can.

There are four lines of pets (Reptilian, Avian, Feline, and Equestrian) Breeding two pets of the same line will result in an offspring of that same line, while breeding pets from different lines gives a 50–50 chance of each.

• Parents with higher Aura Powers will generally have children that start with high aura powers, however, there is somewhat of a reset between generations.

• You can currently breed once per 24 hours and you must burn Halo tokens in order to breed.

0x0 Pastures

Although you can sell your cards on any ERC721 marketplace, there might come a time when your pets have served you long and well and deserve a life of leisure. You can send them to the ‘0x0 Pastures’ in exchange for receiving a guaranteed pet one level up. Simply select them in the UI and let them go. Of course, this is irreversible, so think carefully first. You will need to approve the pets contract for 721 tokens in the my account section in order to successfully recycle pets.

In Angel Battles, 100% of the money that comes in to the game through purchase of new packs goes to the Gitcoin Matching Fund to fund public goods. Having the game 100% on chain and the developers as volunteers means that we do not have ongoing hosting/server costs, which allows Angel Battles itself to be a public good which helps to fund other public goods.

Angel Battles is organized around two key principles – the game should be FUN and the game should be SUSTAINABLE. Being fun means that although the game is play to earn, players would still want to play without any incentives. Being sustainable means that the game is designed to run forever. This means things like balanced incentives, fully on-chain code (including metadata), the ability to play for free, fully open source code, etc.

Angel battles uses 2 basic types of tokens - Cards which you use to battle are non-fungible tokens (ERC721) because each card has its own unique type and stats which can often be improved. We also have Halo tokens which are fungible (ERC20) and can be earned through playing and burned to breed pets and get the ultimate card pack.

Here is a brief guide to each section of the game so you can get some cards and start playing!  Click on the detailed instructions for each section and be sure to head over to our discord.

Basics of Cards

The cards section shows all of the available cards as well as how many of each have been created. There are 4 types of cards – Angels are key team members and have one of six colored auras. Pets have one of four lines (Feline, Equine, Avian, and Reptilian) and can be bred with each other to create more pets. A team consists of one angel and one pet, and optionally one accessory. Accessories can give a boost to one of your stats. Medals can be earned through in-game achievements and can be burned in order to permanently buff your angels.

Getting Card Packs – The first thing to do it to get some cards! You can pick up a free pack, or purchase the bronze, silver, or gold packs. You can also burn 1000 Halo tokens in order to receive the ultimate pack. See how we protect randomness.

After you send the transaction to get your pack,  a window will pop up with your new cards once the transaction is mined. You can always see your cards under Account -> My Team.

Arena Battles

Battling is one of the most exciting parts of the Angel Battles game. (it’s right there in the name!) Your angels get stronger by earning experience by facing off against ‘the computer’ in one of three different battle arenas. You also earn 1% of the Halo tokens in the arena battles contract. See detailed instructions

Battle Mountains

Battle mountains are player vs player global 2D leaderboards with spots ranked from 1 to 64. Teams enter from one of eight gates, and then face others as you fight your way to the top. Certain sections of the mountain have buffs for certain colored angels, and every 24 hours the conditions can change. This can include things like buffs for attackers/defenders, aura colors, pet type, etc as well as which bridges are functional. Additionally, players earn 1% of the tokens in the battle mountain contract each time they win a battle as an attacker.

Players can use our UI to deploy and manage their own battle mountains where they can limit approved players and cards. See detailed instructions.

Stables (Pets)

Once you have two pets, you can breed them in order to gain a new, potent ally. The most powerful pets in the game can only be earned through breeding. Get a card that doesn’t fit in your strategy? You can always sell it on any ERC721 marketplace. You can also ‘retire’ 6 pets of one level to create one of a higher level. See detailed instructions.

Medals

Medals are ERC721 tokens which can be earned by completing some special achievements within Angel Battles. They can then be burned in order to give special permanent buffs to your angels. See detailed instructions.

My Account

The account sections contains some important settings and approvals. See detailed instructions.

We hope you enjoy playing and we will see you on the battle mountain!

In each arena battle, you will face a monster from human mythology with your team of an angel, pet, and optional accessory. When you win a battle you will receive experience points. If you win a battle with any angel besides Berakiel, you will also receive 1% of the Halo tokens currently in the arena battle contract.

When you first enter the battle, your initial stats are calculated and adjusted based on several factors. Your angel’s initial hit points (hp) is calculated based on their battle power and experience.

Next, we check the difference in aura strength between your pets and the monster. The difference in Red Aura increases your attack power, the difference in Blue Aura increases your defense power, and the difference in Yellow Aura increase your speed/luck.

When calculating damage, there is a random number based on your attack and the defense value is subtracted to get the final damage. The speed/luck value determines who goes first in each round.

When calculating these stats at the beginning of the battle, accessories are taken into account. For instance, if you have the cosmic scroll (+ 40 EXP) it acts as if your angel has 40 extra experience. If you have a Citrine Collar, it acts as if your yellow aura is greatly increased. It should be noted that these stats are ‘leveled’, so that if you get twice as much experience, you are less than twice as powerful.

In order to start a battle, select which cards you would like to use from the Arena Battles screen.

When selecting angels, keep in mind that each color has an aura passive and an aura burst. The passives for red, green, orange and blue auras are applied once at the beginning of a battle. The passives for yellow and purple auras are applied each round.

When in a battle, there are 4 possible actions. Attack launches a basic attack that deals damage to your opponent. Defend uses a turn to increase your defense for the rest of the battle. Aura Burst causes the effect listed in the above image. Calling a Pet causes your pet to step in and fight for you with wildly varying results. Attacking and defending can be done an unlimited number of times, while auras and pets can only be released once each. The exception to this is if you release your pet and then use the blue aura burst - you will then be able to call your pet a second time.

When reading the stats, the red heart stands for hit points (hp). Hit points are reduced by the amount of damage taken and the battle is over when one of the combatants reaches 0. The black lightning bolt represents the battle power - the more battle power, the harder you are likely to attack. The green shield represents the defense buff. This is an extra increase in defense that will result in enemy strikes causing less damage.

The red rocket ship for angels represents pet speed/luck. This helps in determining whether the angel or the monster will go first. The red, blue and yellow icons on the monster represent the monster’s aura components. They don’t change during the battle, but could help you troubleshoot how to defeat a particular monster. Finally, the angel stats specifies the angel’s aura color.

After the battle, you will be asked to confirm the results.

Notes:

• The strongest angel in the game (among all players) can only battle once per hour. Other angels have a delay based on how close they are to the strongest angel

• The battle contract (ABArenaBattles.sol) and the support contract (ABBattlesSupport.sol) are both open source and obviously the final authority on how arena battles are conducted.

• The Liquid Metal Cornu is a monster that becomes stronger anytime any player defeats it. They are rare and you can earn a Titanium medal if you are able to defeat one.

Medals are ERC721 tokens and you can buy/sell them on marketplaces or transfer them from the my team screen.

Medals go from the lowliest medal (1 ply paper towel) to the highest (zeronium).

Claiming Medals – Note that medals earned by having a certain spot on the leaderboard are claimed from the leaderboard (battle mountain) section. These medals can only be claimed from the main battle mountain, not custom mountains.

In general, medals are restricted so that you can only claim them once for each accomplishment. For instance, each angel may claim each of the battle mountain medals (gold, diamond and zeronium) once each. In order to claim a medal, click the ‘claim’ button, select the medal you would like to claim and then click the ‘start claim’ button to prove that you have met the appropriate conditions.

Burning Medals – In order to burn a medal, select the ‘burn’ functionality, the medal you wish to burn, and the card you wish to permanently strengthen. You must approve the medals contract before the burn option will appear. Remember that once a medal is burned it is gone forever, so choose carefully! Burning a medal does not mean that you can claim it again with the same angel. You can also burn the first four medals together in order to earn an accessory.

The second section is for approvals. Remember that your Angel Battle Token (ERC721) and Halo Tokens (ERC20) are really yours – no one can take them without your permission, not even the game. Thus, there are some approvals that you will need to give in order to do certain actions in the game.

1. You must approve the medals contract in order to burn your medals.

2. You must approve the store contract in order to buy the ultimate pack with Halo Tokens

3. You must approve the pets contract (ERC20) in order to breed with Halo Tokens

4. You must approve the pets contract (ERC721) in order to recycle pets and get a new one.

The next section is for claiming streams. It’s important to note that any ONE player can claim the stream for everyone. The arena battles and battle mountain contracts receive streams of Halo Tokens continually over 5 years, but they must be claimed. For instance, if no one has claimed the stream for 2 days, you could claim it and add tokens equal to 2 / (365 *5) of its 5 year allocation. Because these contracts give out 1% of their current balance after every battle, you can earn slightly more tokens if you claim their stream before entering battles.

Any one player can also move the balance of the store contract (in Matic) to the Gitcoin Matching Multisig any time. It would be great to do this before one of the quarterly rounds.

Default Gas Fee Settings - The final section lets you choose default gas fee settings if you wish.

My Team

In the my team section you can see tables of your cards and filter them by type. If you have multiple copies of one card, you can stack or expand them.

You can also see the details of any individual card through the ‘manage individual token’ section. If you are the owner, you can also transfer or rename the card in this area.

There are three layers of reasons why players would want to play.

• The first, and primary reason for people to play the game is to have FUN! From day 1 our overarching goal was to develop a game that is just fun to play, without considering the flow of any value.

• The second layer is the HALO layer - Players gain Halo tokens by winning arena battles (except w/Berakiel), winning battles on incentivized leaderboards, and other methods. Players burn Halo tokens to breed a pet or to purchase the Ultimate Pack (most powerful cards).

• The third layer is the Matic layer. – Players purchase gold, silver, and bronze card packs using a Matic on polygon. 100% of this goes to the Gitcoin Matching Grants pool. Players can send a tx to fund the pool with the store’s accumulated balance at any time. This layer means that by simply playing Angel Battles, you are helping to fund public goods! We considered making the game free, but then there would be no way to ensure rarity of key cards.

100% of HALO tokens are earmarked for the community. Angel Battles has no investors and devs are volunteers who receive no HALO tokens for their work.

The first and third incentive layers will last forever, but as HALO tokens are only burnt and not generated, the total supply will only decrease. However, lockups and streaming will ensure that HALO tokens will last at least for several decades. This model should ensure continual incentives for new players.

Why Would Someone Want to Start on Year 2,3,4, etc.?

There is an issue with many crypto projects, where the project only really works for early adopters. We want Angel Battles to be sustainable for the long term. There are 2 advantages of those who start (or continue to purchase angels) later.

• Because the Halo supply strictly decreases, but the arena battle and leaderboard contracts receive a constant amount of tokens streamed, people playing in years 2,3,4 will receive a higher % of existing tokens for the % of all battles that they fight.

• The weaker an angel is, the more often they can battle. New angels will be able to fight a higher % of all the battles than stronger angels.

How Are Halo Tokens Distributed?

There are a total of 1 billion Halo tokens. 52% of the tokens are linearly streamed over 10 years to the treasury. Users can use their HALO tokens to vote how to use these treasury tokens. The treasury intends to hold no other tokens. 22% of the tokens are streamed over 5 years to 6 different contracts, the arena battles as well as 5 battle mountains.

Finally, 26% of the tokens are streamed over 5 years to around 9,800 addresses. 6% is allocated for people who played the 2018 version of angel battles on mainnet, with a 1% bonus for the most active players, which was defined as those who were on the global leaderboard at any point. 5% was allocated for players who played on testnets during 2021 and 2022. 3% was allocated to each of 5 NFT collections consisting of people who have shown alignment with Ethereum community and values. The following POAP holders were included.

Genesis Depositor – Medalla Testnet Resuscitator – Kintsugi Validators – Kiln Validators – 2021 and 2011 Ethstaker Challenge POAP holders - Beacon Chain Diversity POAP holders.

How To Claim

There are two key steps in order to receive your tokens.

1. Claim And Open Stream - The first step is that you must open a stream by sending a merkle proof from the eligible address. You will be able to do this through the ‘account’ page in the front end, which will provide the proof. **There is no ‘expiration’ to the time that you can open your stream.

Note: **You may also claim your stream for a different address - for instance claim from a cold wallet for a hot wallet.

2. Claim Tokens - Once the stream is open, you will be able to claim tokens whenever you want. The amount of tokens you receive will be the total number of tokens multiplied by the time that has past - tokens already claimed.

For example: You receive 100,000 tokens streamed over 5 years. After one year you claim and you will receive 20,000 tokens. 6 months later you claim again. The total due would be 30,000, but you have claimed 20,000 already so the contract will give you 10,000.

**Important Notes: *

**The tokens are for direct use in the game and should not be construed to have any investment purpose or value outside of the game. Over time HALO tokens should cease to exist as they are burned in a one-way process during normal gameplay.

*There are no investors, and the Team Entity has never sold any Halo Tokens and will never sell any Halo Tokens in any jurisdiction. We have also not created any primary of secondary markets for Halo Tokens.

You can see the list of addresses on our github:

https://github.com/angelbattles/streamdrop/

If your address is not listed and you believe this is in error, please contact us on our discord before 9/12/2022 or open an issue on github.

https://discord.gg/u2xgWuQ

Basics - The leaderboard consists of 64 different spots. Teams can enter through 8 different gates. Spots are ranked by their number, with spot number 1 being the best. There are 8 different panels which let you ‘zoom in’ to a particular section. Terrain matters — for instance, angels with a red component to their auras (red, purple, orange) are strengthened in the lava fields.

Incentives - The battle mountain receives Halo tokens streamed for 5 years. For every battle that is won when you attack, you will receive 1% of the current Halo balance of the battle mountain contract.

Players do not receive experience points for vs battles and vs battles can be fought continually with no cooldowns or delays. Players do not receive Halo tokens when defending.

How to Play - You start off by attacking a gate. Choose an angel, pet, and accessory (optional) and face the team that currently occupies that gate. If you win, you will take their spot and knock them off the mountain. Choose your team wisely - once a team enters the mountain, you ride with them until they are kicked off. One player can have multiple teams on the same mountain, but each card can only be on the mountain once.

Every space must always be occupied. There is a ‘null team’ with a weak Berakiel which starts the game in each spot.

Possible Actions - When in battle, you have 4 possible actions. Attack launches a basic attack. Defend uses a turn to buff your defense for the rest of the battle. Aura bursts and pet summons have the same effects as in the arena battles.

Only the attacking team gets to choose an action after each round. However, the defending team can choose a set of 6 actions for the first 6 rounds of any battle. Click the “i” icon next to your team to set your actions and enter an optional team name.

Example - Say you entered through gate 55. Your only choice is to attack spot 46. If you win that battle, the team that was in 46 will switch with you and go to 55. Once in spot 46, you can choose to go back to 55, or to attack the teams in spots 48, 31, or 41. Which should you choose? When plotting a path to the top of the mountain, it’s a good idea to fight on the panels where your Aura color gives you an advantage.

Changing Buffs - Any player can change the mountain conditions once every 24 hours. This could result in a bonus to a particular type of angel or pet, a bonus to attackers or defenders, dark or light angels, etc. This can also open or close the bridges as well as cause a landslide that will knock a team completely off the mountain! This mechanism will prevent players from blocking the gates with their strongest angels.

Stuck on a certain path? You might just need to wait a few hours until the bonus conditions change.

You will need to do a commit and reveal to change the mountain conditions. See the protecting randomness article for more information.

VS Battle Strengths - In order to balance the game, no single aura color is dominant. In the most basic form with the three single colors, it looks like this.

With all 6 colors, the strengths and weaknesses are based on the component colors. Here is how to read the chart. When a green angel faces an orange one, the green has a single advantage. When a yellow angel faces a blue angel, the yellow angel has a double advantage.

Other Attributes - Other attributes are ‘leveled’ so that as these attributes reach extreme values, they do not confer insurmountable advantages. These values are calculated once at the beginning of a battle.

Custom Mountains - Any player can deploy their own custom mountain contract without writing any code. We have created a deploy tool to help you manage your mountain. As the owner, you can also choose to allow all cards or prohibit certain cards (i.e., only light angels, only unicorns as pets, etc.) You can also choose to have the mountain open to the public, or only to certain addresses. You can give native tokens or Halo tokens as incentives, although this is optional and not expected.

Medals - There are various medals which can be claimed for being on the mountain. You can claim a Gold Medal for being anywhere on the mountain, a Diamond Medal for making it on the first panel, and a Zeronium Medal for getting the top spot. Medals can be claimed only once per angel card. Medals are also ERC721 tokens which can be burned for one time, permanent boosts to your other cards.

Note - While the mountain should be fully operational, some of the buffs are still under development. We are looking for feedback and running numerous simulated battles to help with balancing.