Alethea

Alethea AI is a protocol to create intelligent and interactive NFTs powered by Open AI’s GPT-3 engine. We embed cutting edge AI animation, interaction and generative AI capabilities into NFTs. Through our award-winning AI Avatar studio, we enable the creation, monetization and ownership of Intelligent NFTs resulting in a thriving and diverse metaverse.

As creators of the First ever iNFT, Alethea partnered with the leading auction house Sotheby’s to create and auction the first interactive and intelligent NFT (iNFT), Alice.

Users can create a unique, intelligent, GPT-3 powered and interactive version of their digital asset.

For more information about Alethea, please visit https://alethea.ai/.

This bug bounty program is focused on their smart contracts and is focused on preventing the following impacts:

• Loss of funds, nonoptimal gas usage
• Frozen/malfunctioning contract state
• Unexpected behavior (not as designed, documented, including undocumented, poorly documented, counterintuitive behaviour)

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

A suggestion for a fix is required for all bug reports.

Vulnerabilities indicating that any assets (including ERC20, ERC721, ERC1155, but not limited) accidentally sent to any of the deployed contracts may get lost are not in-scope of the bug bounty program.

Payouts are handled by the Alethea team directly and are denominated in USD. However, payouts are done in ETH.

The Alethea GitHub is currently private. As such, PoCs are not required for any of its severity levels.

Once Alethea’s code is published on mainnet, the contracts reflected here will be modified to their mainnet contracts.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

• Loss of funds
• Nonoptimal gas usage
• Frozen/malfunctioning contract state
• Unexpected behavior (not as designed, documented, including undocumented, poorly documented, contr-intuitive behaviour)

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces
• Sandwich attacks
• Frontrunning attacks

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
• Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third-party systems and applications (e.g., browser extensions) as well as websites (e.g., SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty