Roman Khimov
Roman Khimov
**Summary or problem description** 1. Some private chains like NeoFS sidechain have well-known IDs for non-native contracts, but their hashes can change from one network to another (because contracts change...
**Summary or problem description** Storage.Find contract API exposed by the system allows to iterate over a set of keys with various options, but it only does so in one direction...
**Summary or problem description** Many protocol-related experiments and extensions around transactions can start as simple attributes. Some private networks may also want to have extensions based on attributes for their...
**Summary or problem description** We have `MaxTraceableBlocks` protocol parameter that controls how deep a smart contract can go with its requests for blocks and transactions and subsequently this allows nodes...
**Describe the bug** `CheckWitness` logic for oracle responses uses original transaction's signers list. If we have a transaction with a signer using `CalledByEntry` scope it would work fine for `CONTRACT_A`...
**Summary or problem description** The topic of free/sponsored transactions had been touched several times by at least #1104, #1147, #1468, #2442 and neo-project/proposals#137. Some of those discussions are no longer...
**Summary or problem description** The need for P2P state exchange has been noted several times already, I'll just quickly recap the most important points: * as chain grows processing it...
**Summary or problem description** At the moment Oracle contract only supports `request` method with URL and associated data that essentially allows to get something from the outside, but contracts also...
(from #1555: https://github.com/neo-project/neo/pull/1555#discussion_r408706349) **Summary or problem description** Generating multisignature transaction requires some interaction between signing parties. Currently this interaction is not handled by the network in any way and requires...
**Describe the bug** Nodes have problems accepting a block when they reach mempool capacity. Probably a lot of change views are being made and/or transaction exchange is not happening fast...