Logo: 
Name: Cold Beer 404
Ticker Symbol: BEER404
Network: Pulsechain
Contract Address: 0x0760F66ed7139aaa70Dc21c8f9E75167e295D4Ab
Purpose:
Who doesn’t love a Cold Beer?
If you obtain a whole token you will be gifted 1 of 5 mouthwatering pints of Cold Beer, in the form of an NFT. If beer spills and that value goes below 1 your NFT will be burned.
Cold Beer 404 was created using the PulseCoin ERC-404 Factory.
It was also launched in collaboration with CoinHub, a telegram channel affiliated with the 9inch DEX.
Enjoy a Cold Beer today!! 
Project URL: https://pulsemarket.app/collection/0x0760f66ed7139aaa70dc21c8f9e75167e295d4ab
Project social media: Twitter, Telegram
Contract Source Code: Link
Audit(s): B9.xyz
REVIEWED BY: Elmyre
Preface
This is a complete review of the BEER404 token whose code can be found at https://scan.9mm.pro/token/0x0760F66ed7139aaa70Dc21c8f9E75167e295D4Ab?tab=contract.
Although the code is simple, I would advise anyone reading this document to also look at other reviews of the contract! Some issues or security concerns might not be covered here due to my lack of knowledge or understanding. Getting a second opinion is always a good thing to keep in mind!
Code Review
The BEER4040 token is based on a template provided by the GoPulse.com front end to facilitate the creation of tokens based on the V1 version of the ERC404 “standard”.
Right out of the gate, this implies it has the same issues and concerns as the ERC404 V1 contract, developed by 0xacme for which the review can be found “here”.
The template contract, PulseCoinERC404, is a simple contract that implements functions from ERC404 and allows the NFT image properties to be set.
- Inheritance:
- ERC404: https://github.com/0xacme/ERC404/blob/main/src/ERC404.sol – This is an experimental standard that aims to provide mixed ERC20 and ERC721 features. This dependency is not audited and has some known limitations, so there are risks in using it.
The contract has a constructor that allows the creator to provide the attributes for the five different NFTs it supports, as well as define the name, symbol, decimals, total supply, owner, and creator of the contract. For BEER404, these are “Cold Beer 404”, “BEER404”, “18”, “5000”, “0x6c70d5301a5db2689e37f1921e0360934c07f09a” and “0x24ea18d5ba2ff3a1b305cdbb7aa2d749fc667c72”, respectively. The entire supply is allocated to the creator’s address.
LIMITATION: The contract does not force the creator to provide attributes for 5 images, which means, depending on the deployer, there can be tokens without any associated NFT.
The contract implements the following functions:
- Public Functions:
- setDataURI: Allows the owner to change the URI for the NFTs.
- setTokenURI: Allows the creator to set the tokenURI.
- setNameSymbol: Allows the creator to set the contract’s name and symbol.
- tokenURI: View function that returns the NFT metadata associated with a specific NFT ID. The image/Data associated with said NFT is pseudo-randomized based on its ID.
Conclusion & Security Concerns
This contract has the same limitations as the ERC404 “standard”, and the image and contract data can be changed by the creator’s and owner’s address. The creator also received the total supply, meaning there is a rug risk if he kept most of it.
No bugs or risks were found, other than the previously mentioned ones.