We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
near-api-js
Hi,
In nearcore 1.39.0, the default behavior for transaction execution level was changed to no longer waits for refund receipts
no longer waits for refund receipts
#[default] ExecutedOptimistic
near/nearcore#10948 https://docs.near.org/api/rpc/transactions#tx-status-result
However, in near-api-js, it still uses FINAL
FINAL
near-api-js/packages/providers/src/json-rpc-provider.ts
Lines 125 to 127 in b61b66d
Can this be changed to EXECUTED_OPTIMISTIC for all transactions or for Account.sendMoney?
EXECUTED_OPTIMISTIC
Account.sendMoney
await senderAccount.sendMoney(receiver, amount)
async sendTransaction(signedTransaction: SignedTransaction): Promise<FinalExecutionOutcome> { return this.sendTransactionUntil(signedTransaction, 'EXECUTED_OPTIMISTIC'); }
async sendTransaction(signedTransaction: SignedTransaction): Promise<FinalExecutionOutcome> { return this.sendTransactionUntil(signedTransaction, 'FINAL'); }
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Prerequisites
near-api-js
.Description
Hi,
In nearcore 1.39.0, the default behavior for transaction execution level was changed to
no longer waits for refund receipts
near/nearcore#10948
https://docs.near.org/api/rpc/transactions#tx-status-result
However, in near-api-js, it still uses
FINAL
near-api-js/packages/providers/src/json-rpc-provider.ts
Lines 125 to 127 in b61b66d
Can this be changed to
EXECUTED_OPTIMISTIC
for all transactions or forAccount.sendMoney
?Steps to reproduce
Expected behavior
Actual behavior
Self-service
The text was updated successfully, but these errors were encountered: