Audit of the BNK smart contract: security over speed

Since the beginning of Bankera’s project, security has been our main concern. This was reflected in our choice to use the ERC223 standard for the Banker (BNK) token source code, which was then fully developed by our team. Other companies could have opted for a quicker route and used other token codes to develop their own, but we knew this could result in potential security gaps, such as the ‘batch overflow’ bug recently discovered in several ERC20 smart contracts. Moreover, we are not creating a simple token, but a smart contract that distributes a net transactional revenue share weekly to BNK token holders, which has never been done by others. Thus, in addition to creating a unique source code for our BNK token, we have also submitted it for private and public audits to ensure its safety.

Audit of the BNK Smart Contract: Security over Speed
Continue reading “Audit of the BNK smart contract: security over speed”

Why is the BNK token unique?

As a team, we always choose security and quality results over rushed decisions. Supporting BNKs as ERC20 tokens has always been our goal, however, we decided to dedicate more time to it and release a more advanced version of the Ethereum based smart contract. This more advanced and secure version was required because of one of our token special features: its holders receive a weekly net transactional revenue share. Hence, the smart contract source code includes the function of storing weekly commission. However, that is just one of the several reasons why BNK tokens are special among others in the market. So let’s take a closer look at BNK tokens and what makes them unique.

Why is the BNK token unique?

Continue reading “Why is the BNK token unique?”