neoneo-go/pkg/services
Anna Shaleva 1d1538c566 services: fix Oracle response transaction creation
Problem: transactions with wrong hashes are accepted to the chain if
consensus nodes are designated as Oracle nodes. The result is wrong
MerkleRoot for the accepted block. Consensus nodes got such blocks
right from the dbft and store them without errors, but if
non-consensus nodes are present in the network, they just can't accept
these "bad" blocks:
```
2021-11-29T12:56:40.533+0300	WARN	blockQueue: failed adding block into the blockchain	{"error": "invalid block: MerkleRoot mismatch (expected a866b57ad637934f7a7700e3635a549387e644970b42681d865a54c3b3a46122, calculated d465aafabaf4539a3f619d373d178eeeeab7acb9847e746e398706c8c1582bf8)", "blockHeight": 17, "nextIndex": 18}
```

This problem happens because of transaction hash caching. We can't set
transaction hash if transaction construction wasn't yet completed.
2021-11-30 10:43:58 +03:00
..
helpers/rpcbroadcaster config: use http for oracle nodes 2021-11-26 17:17:10 +03:00
notary rpc: refactor calculatenetworkfee handler 2021-10-25 19:07:25 +03:00
oracle services: fix Oracle response transaction creation 2021-11-30 10:43:58 +03:00
stateroot crypto: allow to provide non-default scrypt parameters 2021-06-11 15:22:28 +03:00