# Frog Team Safety Assurances

We will **NEVER** have a surprise mint. 

We will **NEVER** do a "limited time" giveaway. 

There will **NEVER** be a surprise anything 'risky' (connect wallet, click link, claim prize, etc). 

There will **NEVER** be a 'first X number to claim' promotion.

{% hint style="danger" %}
**IF IT SEEMS TOO GOOD TO BE TRUE, IT PROBABLY IS.** Especially if there is pressure being applied to 'hurry and claim', or do it 'before it runs out', it is NOT the Frog Team, and likely a scam. 
{% endhint %}

If we ARE doing a giveaway or a surprise, **THERE WILL NEVER BE ANY RUSH/TIMELINE** to claim.

If we ARE doing a limited run of an item or event, **THERE WILL BE PLENTY OF PRIOR CONFIRMATIONS, AND PLENTY OF TIME TO CONFIRM AGAIN.**

{% hint style="success" %}
If we ARE doing something that seems too good to be true, **WE WILL NEVER FAULT OR PENALIZE YOU FOR CONFIRMING YOU/YOUR ASSETS' SAFETY AND SECURITY.** Taking the time to ask another member of the Frog Team or Mod Squad, verifying via a different communication channel, or even sleeping on it to make sure you feel comfortable is NEVER something that will cause you to lose or miss out. 
{% endhint %}

Double or triple confirming your safety **IS ALWAYS ENCOURAGED.** If you're being pressured to NOT double or triple check, it's not a member of the team and is likely a scam. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://frogland.gitbook.io/toadex/community/web3-blockchain-and-crypto-tips-and-safety/frog-team-safety-assurances.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.