cdr
cdr
@christoph2806 Yes, I’ve discussed with Nate about this. It’s a hard problem to solve since we’re moving the nonce logic from the transaction level up to the smart contract level...
@christoph2806 > what could an attacker possibly do? The main thing is a DoS attack: you try sending a transaction, the attacker sends a transaction with the same data packet,...
@ScJa The front-running issue doesn't require the attacker to be able to create signatures, they would simply grab the already signatures from a transaction in the mempool and send them...
I'm leaning towards erring on the side of simplicity here: The mitigations against replay attacks will increase complexity of the contract, and I think the risks are relatively niche. You...
In v2.0.0 we've addressed this by including the option of specifying an executor to execute a transaction. I feel that this should take care of most replay attack concerns.
Hi @ripper234! Since the contract supports any function call with arbitrary data it will also support handling ERC20 tokens. The linked Medium article states that ERC20 tokens are supported but...
@ripper234 Yeah you'd need to have the destination address be the token contract address, the value sent be 0, and the data field would encode that you are sending X...
Related to https://github.com/bitpay/bitcore-lib/issues/47
@fanatid Good tip, thanks! :+1:
I'm still having trouble with this issue: ``` error @transmute/[email protected]: The engine "node" is incompatible with this module. Expected version ">=10.0