Submitted by 0x3b, also found by AvantGard and lanrebayode77
As explained by the docs, several steps can occur during the minting process. However, an airdrop before salesOption 3 can lead to price inflation.
Under salesOption 3, getPrice returns:
This is the increased rate based on the NFTs already in circulation. If an airdrop occurs before a mint with salesOption 3, the price will be much higher than intended.
Example:
With the current three steps, after the airdrop, salesOption 3 should start at 1 ETH and gradually increase to 2 ETH. Afterward, it should mint at a constant rate of 2 ETH.
However, when sales option 3 starts, getPrice will return 3 ETH instead of 1 ETH. This will cause the initial users to pay an inflated price, which was not intended by the owner and can harm their reputation. Its also unfair to the users, as these so-called special (whitelisted) users will pay increased prices.
Note: see original submission for math breakdown provided.
Gist here. 
Add to remappings - contracts/=smart-contracts/ and run it with forge test --match-test test_airdrop --lib-paths ../smart-contracts.
You can implement a mapping with the airdropped NFTs and deduct this value from gencore.viewCirSupply(_collectionId) to avoid disrupting the minting process.
Error
a2rocket (NextGen) confirmed via duplicate issue #246
0xsomeone (judge) commented:
MrPotatoMagic (warden) commented:
0xsomeone (judge) commented:
