You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.
In setting up the migrations for the project I'm working on, the total supply of the bonded token is initially zero, which causes the call to priceToBuy etc. to fail.
I know this isn't the case in the tests for BC-DAO, as they mostly pass, but I can't figure out exactly where the testing ecosystem setup mints the initial tokens for the bonded token to avoid the above issue. I see the following line for the payment token though, in the BondingCurve.behaviour.js file:
In production deployment, would one just mint a probably insignificant number of tokens to the creator or perform some sort of hatch phase, and if so would that need to be done manually by minting or are there plans to have a contract method for this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi team :) I need some guidance with the tests.
In the
calculatePurchaseReturn
method of theBancorFormula
contract there is the following requirement set:In setting up the migrations for the project I'm working on, the total supply of the bonded token is initially zero, which causes the call to
priceToBuy
etc. to fail.I know this isn't the case in the tests for BC-DAO, as they mostly pass, but I can't figure out exactly where the testing ecosystem setup mints the initial tokens for the bonded token to avoid the above issue. I see the following line for the payment token though, in the
BondingCurve.behaviour.js
file:In production deployment, would one just mint a probably insignificant number of tokens to the creator or perform some sort of hatch phase, and if so would that need to be done manually by minting or are there plans to have a contract method for this?
The text was updated successfully, but these errors were encountered: