@@ -136,7 +136,7 @@ const signTransaction = async config => {
136136 return stx;
137137};
138138
139−const sendSignedTransaction = (web3, stx, doubtNonceError, confirmationCb) => {
139+const sendSignedTransaction = (web3, stx, doubtNonceError) => {
140140 const txn = stx.matchWith({
141141 Just: tx => tx.value,
142142 Nothing: () => {
@@ -152,14 +152,6 @@ const sendSignedTransaction = (web3, stx, doubtNonceError, confirmationCb) => {
152152 .on('transactionHash', hash => {
153153 resolve(hash);
154154 })
155− //TODO do we also reach this if network is slow? web3 only tries a set
156− // amount of times... should we instead do waitForTransactionConfirm
157− // in on-transactionHash? we don't care (much) about additional
158− // confirms anyway.
159− .on('confirmation', (confirmationNum, txn) => {
160− confirmationCb(txn.transactionHash, confirmationNum + 1);
161− resolve(txn.transactionHash);
162− })
163155 .on('error', err => {
164156 // if there's a nonce error, but we used the gas tank, it's likely
165157 // that it's because the tank already submitted our transaction.
@@ -176,16 +168,7 @@ const sendSignedTransaction = (web3, stx, doubtNonceError, confirmationCb) => {
176168 'tx send error likely from gas tank submission, ignoring'
177169 );
178170 const txHash = web3.utils.keccak256(rawTx);
179− //TODO can we do does-exists check first?
180− //TODO max wait time before assume fail?
181− waitForTransactionConfirm(web3, txHash).then(res => {
182− if (res) {
183− resolve(txHash);
184− confirmationCb(txHash, 1);
185− } else {
186− reject('Unexpected tx failure');
187− }
188− });
171+ resolve(txHash);
189172 } else {
190173 reject(err.message || 'Transaction sending failed!');
191174 }