Denis Davidyuk
Denis Davidyuk
Dry-run looks to be a working solution, the only problems I see are: - if we find that tx stuck in mempool, call dry-run, and the tx gets included in...
> You'd still want nonces to be unique, right? (Or else it would be trivial to re-run profitable transactions) > Sequential transaction order is very important for double spending If...
> A random nonce would make the TX considerably larger It can be an arbitrary-size value so the user may decide its size. Also it can be used as a...
Yep, I've counted 3.5 bytes for the amount and the same for fee of spend tx. 7 bytes overall.
> Depending on the use-case it might be ok to ignore the contract store part On sdk side, I just need to decode/encode it accurately. The last question is `5827853751b48544d74aa30dc0a43aa7cd3354346ee41364f6f3b43e25049be0`...
Accordingly "protocol" field configures how aepps switches protocol. In a specific setup, these values are always the same, don't they? Except for `"1": 0` at the beginning of `hard_forks` https://github.com/aeternity/aeternity/issues/4203
I recalled that fee is a gas * gas price, so we can divide the fee by gas and get a gas price to sort by. Probably `-aetx:deep_fee(Tx), -int_gas_price(Tx)` can...
seems I reported the same issue in #4235 I can't use FSM on testnet and mainnet because of `{"event":"died"}`
My snippet expected to work fine on localhost, I have issues on public endpoints (wss://testnet.aeternity.io/channel and wss://mainnet.aeternity.io/channel)
This also can be a solution to https://github.com/aeternity/best-dev-xp-tools/issues/42