During the process of developing our smart contract on the NEAR blockchain, we encountered a series of frustrating bugs and hurdles that significantly impeded our progress. One particularly challenging issue was the lack of specific error messages provided by the terminal when our code contained bugs. This made it extremely difficult to pinpoint the exact location of errors within our codebase, as we were left without information about which line or file was causing the problem. To overcome this, we resorted to initializing a new project and painstakingly copying each line of code from the old source, which proved to be a time-consuming and cumbersome solution.

Another obstacle we faced was related to the transfer of NEAR tokens using the “near-sdk-js” library. We discovered that some of our transfers were failing due to the transfer amount being too low, but the error messages provided were not very informative, leading to confusion and delays in resolving the issue. Additionally, we encountered problems when our functions didn't properly return promises, causing unexpected behavior and further complications. To tackle these problems, we had to meticulously review our code, ensure proper promise handling, and adjust the transfer amounts to meet the requirements.