Bantiample Exit Scam

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' and 'General Prevention' sections to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

Bantiample

Bantiample was a fork of Antiample, but not a functional one. It took advantage of the hype around the Antiample project to launch. The project did not run for long before the anonymous creator made off with everyone's funds.

This is a global/international case not involving a specific country.

About Bantiample

"Bantiample tokens were released on September 15th. The project was an analogue of the Antiample DeFi protocol, which is gaining momentum." "Fork of AntiAmple listed on Binance Smart Chain, where there's barely projects active atm. It's getting attention from twitter but not a lot so still early."

"Bantiample is a BEP-20 token issued on the Binance Smart Chain blockchain. Bantiample holders have the opportunity to earn rewards in the token pool , write the creators of the fraudulent scheme." "$BAMP holders at time of snapshot will receive 2:1 $BASH tokens compared to other two tokens. $BOB and $BOAB token holders at time of snapshot will receive bonus farming rewards on the launch of $BASH so long as they also have an equal BNB value of $BAMP. These bonus farming reward “packages” will also be able to be traded. The burnt liquidity pool tokens will not be included in snapshot."

"Some guy took Bill Drummond's projects and just forked them. Super low amount of holders right now. Dev in TG and burned the fuck out of the supply. Do what you want with this information, but imagine not riding the same train that just happened with XAMP -> TOB -> BOA -> ASH. Dev already said he's doing BAMP -> BOB -> BOAB -> BASH. Airdropping tokens for BAMP holders. Be a BAMP whale and you get free money off all those upcoming projects. If you don't, you're probably [f***ing] retarded."

"Earlier it became known about the exit-scam of the Bantiample project at the Binance Smart Chain." "Bantiample, a project on the Binance Smart Chain, has reportedly cashed out 3k BNB and disappeared. In the meantime its account on Telegram was closed and the token BMAP was on a day-to-day decrease of over 90%."

"In reality, Bantiample had almost no functionality and was created solely to raise funds. At the moment, the pages in social networks Bantiample have been removed by their creators. The native Bantiample token has lost almost 90% of its value in the last 24 hours."

"The Bantiample team, a project on the Binance Smart Chain, has cashed out 3000 BNB to run away. At present, the main developer of the team has deleted the Telegram account, and the project token BMAP has fallen by more than 90% in a single day. According to the project's description, BMAP is a kind of AMPL-like imitation. Every time a user participates in a transaction, the total amount is reduced by 1%. However, it is actually just a common token, and it does not have the functions described by the project party. It just uses the AMPL project hotspot to commit fraud."

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

• Known history of when and how the service was started.
• What problems does the company or service claim to solve?
• What marketing materials were used by the firm or business?
• Audits performed, and excerpts that may have been included.
• Business registration documents shown (fake or legitimate).
• How were people recruited to participate?
• Public warnings and announcements prior to the event.

Don't Include:

• Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
• Anything that wasn't reasonably knowable at the time of the event.

There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

The Reality

This sections is included if a case involved deception or information that was unknown at the time. Examples include:

• When the service was actually started (if different than the "official story").
• Who actually ran a service and their own personal history.
• How the service was structured behind the scenes. (For example, there was no "trading bot".)
• Details of what audits reported and how vulnerabilities were missed during auditing.

What Happened

The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.

Key Event Timeline - Bantiample Exit Scam

Date	Event	Description
September 18th, 2020	Main Event	Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.

Technical Details

This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

Total Amount Lost

The total amount lost has been estimated at $83,000 USD.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Total Amount Recovered

There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

Ongoing Developments

What parts of this case are still remaining to be concluded?

General Prevention Policies

A basic analysis of the smart contract would have revealed the lack of functionality. One should question projects that place significant trust in an anonymous entity. This project did not run for long before the platform was closed.

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.