Follow This:

We are launching a podcast and a new YouTube series and would love your support! We are giving 5,000 $NOBS to every No BS Crypto community member who successfully completes all of the steps in this form.
In short, we’d like you to do the following:
  1. Listen to one of more of our podcasts here on iTunes. <<–You must actually listen!
  2. Rate and write a review of our podcast on iTunes.  <<—The more detailed the better!
  3. Subscribe to our YouTube channel here.
You can upload screenshots of you doing the above steps in the form linked above.
Below are examples of what screenshots should look similar to that you need to upload to the airdrop form. They will vary based on whether you’re using phone/desktop or your phone is Android/iPhone, but they should all look pretty similar.
If people seem to be cheating or taking advantage of this airdrop, or if it gets TOO popular, we reserve the right to call it off entirely or disqualify people individually.
You MUST fully fill out the form to be eligible for the airdrop. Distribution will be next week.
Thank you for your support and enjoy the podcast! New episodes will be released weekly!
– Chris – Screenshot examples are below:


Another audit nailed by SNTR token

Ongoing preparations for listing on major exchanges. This time SNTR token passed a security audition by chinese cybersecurity company SlowMist.
The token was specifically tested for:
  • Overflow audit. Overflow vulnerabilities are based on exploiting an ERC20 token standard vulnerability called integer overflow or underflow. This problem happens when the result of a math operation is outside the range that can be represented by a variable. In the case of smart contracts in Ethereum, if you subtract anything from zero, you’ll get a very large value. If you add two large values together, the result will wrap around and will be close to zero. Result: Passed (SNTR token has no such vulnerabilities)
  • Race conditions audit. Race Condition allows a malicious application to obtain several access_token and refresh_token pairs while only one pair should be generated. Further, it leads to authorization bypass when access would be revoked. Result: Passed (SNTR token has no such vulnerabilities)
  • Authority Control Audit. Includes all risks resulted from improper authority allocation, e.g. set “owner” by anyone. Result: Passed (SNTR token has no such vulnerabilities)
  • Safety design audit. A check for design-related risks like bad compiler version or proper return values. Might render tokens non-retractable if done wrong. Result: Passed (SNTR token has no such vulnerabilities)
  • Denial of Service audit. A check if the token could malfunction because of denial of service attacks (DDoS). Result: Passed (SNTR token has no such vulnerabilities)
  • Gas optimization audit — a check if the token uses gas for it’s transactions efficiently. Result: Passed (SNTR token has no such issues)
  • Design logic audit — a check if token actually designed to do what it is described to do. Result: Passed (SNTR token does exactly what it says on the tin)
  • “False top-up” vulnerability audit — a check for vulnerability that results from the mild judgement of if/else in transfer sensitive function scenarios. Result: Passed (SNTR token has no such vulnerabilities)
  • Uninitialized storage pointers audit — we have a strong opinion that this check is added just to increase report volume. Solidity compiler runs these checks automatically and will not allow you to compile your code if you have them. Result: Passed (SNTR token has no such issues, duh)

Leave a Reply

Your email address will not be published. Required fields are marked *