Valazan

This issue also applies to Next 15. @davidecarpini

Hi @ifavo , the SDK can send that same transaction using the following code: ``` typescript const contract = thor.contracts.load( CONTRACT_ADDRESS, CONTRACT_ABI, senderPrivateKey ); await contract.transact.increment(); ``` Maybe the missing...

@ifavo the design is inspired by ethers but under the hood, it's basically doing what you mentioned above. Yes, I'll add an issue for the delegator (we had already one...

Hi @ifavo, we have decided to call the functionalities with read and transact before to keep the types returned predictable. A transact call returns the transaction id, while a read...

@ifavo yes, I'll speak with the team to see if we can add to the roadmap the ethers-like loader you proposed for the contracts.

@ifavo I'm closing this task since the contract module has received a lot of improvements, including the type inference with abitype and the building of clauses for multiclauses transactions. I...

@ifavo nice suggestions, I've opened a specific task (https://github.com/vechain/vechain-sdk-js/issues/1003). In the meantime I'm closing this one, since it has been opened for a long time with different topics.

Hi @ifavo, even in this case, you can access the filter from the contract object and the topics will be encoded: ``` typescript const contract = thorSoloClient.contracts.load( CONTRACT_ADDRESS, CONTRACT_ABI );...

@ifavo yes, currently multiple events are not supported. I'll create an issue to implement your suggested call to enable the direct use of fragments with encoded args and the filtering...

@ifavo I'm adding to the planning also the possibility to build a criteria from a contract object. So this call ``` typescript await thor.logs.filterEventLogs( criteriaSet: [ { address: '0x0000000000000000000000000000456e65726779', fragment:...