DCA Order and Execution

[kailust]

DCA Order and Execution

[kaimen-sano]

cosmwasm implementation allows contracts to access some verified data produced at call-time. For more information, please see here.

In most cosmos-based chains (such as Terra), this is produced by the median block time of the validator set.

[kailust]

I understand the contracts can access verified data produced at call-time.. my question is how does the smart contract automatically perform "call-time" itself without a third party or someone else running a command. Smart contracts are not self running, so does this contract need an outside cron job or bot to send messages to the smart contract for example every minute or every hour and retieve verfied data from such as block height and time, and compare it to user dca order configuration, then run execution. Or does this contract have the ability to self run and do call-time verifications itself?

[kaimen-sano]

It does not. An external user has to call ExecuteMsg::PerformDcaPurchase in order to invoke purchases.

[kailust]

ok thats what I thought, so a bot needs to run, and check for example every hour and check each users configurations with

QueryMsg::UserDcaOrders

then if the users orders are valid based on time and balance, then it needs to execute

ExecuteMsg::PerformDcaPurchase

Is this correct?

[kaimen-sano]

Yep!

[kailust]

Also can you update the
https://github.com/kaimen-sano/astroport-dca/tree/master/contracts/dca#create_dca_order
to use Luna and another cw20 token because UST is not on Terra 2.0

Thanks

[kaimen-sano]

The underlying process is still the same, so there is no need to update it

[kailust]

https://github.com/kaimen-sano/astroport-dca/tree/master/contracts/dca#instantiatemsg

"contract_ddr should be "contract_addr"

also it missing "whitelisted_fee_assets" attributes