Problem with sync/triggers

Technical Issue Reporting
#1

I found that problem:
I have defined watching own contract events + ā€œafterSaveā€ trigger what checks ā€œconfirmedā€ field in DB
Everything works fine (as on docs ) but I have a problem with a confirmation time. It takes too long. The transaction is sent. on ā€œtestnet.bscscan.comā€ it is confirmed but I must wait up to 4 minutes [!!] sometimes to get the results of this trigger. Is any problem in my server or on paid servers this problem is solved?

I cannot force users to use paid ā€œspeedy nodesā€ because it is a frontend dapp so they can use metamask or another wallet and forcing it to add a new ā€œnetworkā€ would be a UX killer :frowning:

My server subdomain: adaiuy3orkmr

#2

Hi,

That is expected behaviour to wait few minutes until confirmed flag is set. That is because it waits a number of blocks until the transaction is considered as confirmed. You can process it directly as unconfirmed if you want to process it later, but it may be reverted by a reorg later.

#3

Is there option to change number of blocks to be confirmed ? Because on bscscan it is marked as ā€œconfimedā€ but on Moralis is not. Also i wait on frontend side to confirmation from metamsk and also this confirmation is received much faster.

Ps. I know why confirmation is. Just mention that moralis get this with huge lagg. In common with metamask/bscscan

#4

you can not change that number of blocks that moralis uses for confirmation, now, on bsc testnet it could also happen that blocks are mined more rarely sometimes compared to mainnet

1 Like
#5

Ok thanks. Iā€™ll check what happend on BSC Mainnet