Executive summary
wavesplatform/Waves falls short of our standard for a template or a sample, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 53 out of 100 and is rated Adequate, and 41 of its 46 critical findings are security problems.
Accessibility, at 43, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 7 points. Structuring the pages comes next, worth about 6 points. Raising Accessibility to 58 would lift the score to about 59.
Twenty-eight passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Replacing each exposed password or key and passing outside input through environment variables would close both risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and the two unsafe settings in infrastructure or container files need changing to safe values. The four sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 70,773 lines, about €230,000 to rebuild.
If Accessibility rose from 43 to 58, the lowest score rated Strong, the score would rise from 53 to about 59.
New since the last survey: 80 findings
- Cognitive Complexity · ResumableInputStream.openHttp (cognitive 19) node/src/main/scala/com/wavesplatform/utils/ResumableInputStream.scala
- God Classes · MethodTooLong: UtilsEvaluator.executeExpression node/src/main/scala/com/wavesplatform/api/http/utils/UtilsEvaluator.scala
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) node/src/main/scala/com/wavesplatform/database/package.scala
- Code Duplication · Edited copy of a member (80 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala
- Code Duplication · Edited copy of a member (58 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala
- Code Duplication · Edited copy of a member (32 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/utils/package.scala
- Code Duplication · Edited copy of a member (45 corresponding lines) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala
- Code Duplication · Edited copy of a member (42 corresponding lines) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptDiff.scala
- Code Duplication · Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala
- Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala
- Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v2/ScriptEstimatorV2.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/package.scala
- Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala
- Code Duplication · Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala
- Code Duplication · Edited copy of a member (23 corresponding lines) node/src/main/scala/com/wavesplatform/state/appender/package.scala
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/SetAssetScriptTxSerializer.scala
- Code Duplication · Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/Implicits.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) node/src/main/scala/com/wavesplatform/state/SnapshotBlockchain.scala
- Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/NativeFunction.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/requests/SetAssetScriptRequest.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadOnly.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/history/package.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) node/src/main/scala/com/wavesplatform/account/Recipient.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) node/src/main/scala/com/wavesplatform/state/diffs/BlockDiffer.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/db/WithState.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/EvaluationContext.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/database/Caches.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/caches/disk/AsBytes.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) grpc-server/src/main/scala/com/wavesplatform/api/grpc/BlocksApiGrpcImpl.scala
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/SetAssetScriptTxSerializer.scala
- Code Duplication · Edited copy of a member (2 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/NativeFunction.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/CustomDirectives.scala
- Code Duplication · Edited copies of one member (6 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/CreateAliasTxSerializer.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ScriptResult.scala
- Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) node/src/main/scala/com/wavesplatform/database/package.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) node/src/main/scala/com/wavesplatform/database/Caches.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) node/src/main/scala/com/wavesplatform/transaction/lease/LeaseTransaction.scala
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/ReissueTxSerializer.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) node/src/main/scala/com/wavesplatform/utils/JsonFileStorage.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/block/Block.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/crypto/bls/BlsUtils.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/state/TxStateSnapshotHashBuilder.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadOnly.scala
- Code Duplication · Edited copies of one member (5 members, 2+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/DataTxSerializer.scala
- Code Duplication · Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala
- Code Duplication · Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/api/http/requests/BurnRequest.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/mining/BlockChallenger.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/transaction/assets/UpdateAssetInfoTransaction.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala
- Code Duplication · Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala
- Code Duplication · Edited copy of a member (3 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/utils/UtilsEvaluationRequest.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadWrite.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/state/patch/CancelAllLeases.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/crypto/bls/BlsPublicKey.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala
- Code Duplication · Edited copy of a member (3 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/network/PeerDatabaseImpl.scala
- Churn × Complexity Hotspots · Hotspot: node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala
- Secrets (history) · REDACTED
- Static Analysis (SAST) · REDACTED
- Change Coupling · Change-coupling hub: Common.scala → package.scala, Functions.scala, WavesEnvironment.scala, ErrorMessageEnvironment.scala, WebEnvironment.scala lang/testkit/src/main/scala/com/wavesplatform/lang/Common.scala
Fixed since the last survey: 123 findings
- Cyclomatic Complexity · NewTransactionInfo.elidedAffectedAddresses (cyclomatic 25) node/src/main/scala/com/wavesplatform/state/NewTransactionInfo.scala
- Cyclomatic Complexity · MinerImpl.generateBlockTask (cyclomatic 22) node/src/main/scala/com/wavesplatform/mining/Miner.scala
- Cyclomatic Complexity · Application.run (cyclomatic 16) REDACTED
- Cognitive Complexity · InvokeDiffsCommon.checkDataEntries (cognitive 20) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala
- Cognitive Complexity · ExchangeTransactionDiff.checkOrderPkRecover (cognitive 16) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) node/src/main/scala/com/wavesplatform/database/package.scala
- Code Duplication · Duplicated block (13 lines × 2) node/src/main/scala/com/wavesplatform/Explorer.scala
- Code Duplication · Duplicated block (11–12 lines × 2) node/src/main/scala/com/wavesplatform/Explorer.scala
- Code Duplication · Duplicated block (10 lines × 3) node/src/main/scala/com/wavesplatform/Explorer.scala
- Code Duplication · Duplicated block (10 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala
- Code Duplication · Duplicated block (8 lines × 2) node-generator/src/main/scala/com/wavesplatform/generator/TransactionsGeneratorApp.scala
- Churn × Complexity Hotspots · Hotspot: node/src/main/scala/com/wavesplatform/network/RxExtensionLoader.scala node/src/main/scala/com/wavesplatform/network/RxExtensionLoader.scala
- Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
- Explicit Debt · TodoComment node/src/main/scala/com/wavesplatform/mining/Miner.scala
- Explicit Debt · TodoComment node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelAllLeases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeaseOverflow-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeaseOverflow-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-T.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-W.json
- Secrets (history) · REDACTED: REDACTED node/src/main/resources/patches/CancelLeasesToDisabledAliases-W.json
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
- Secrets (history) · REDACTED: REDACTED src/it/resources/nodes.conf
Rebuild cost: about €230,000 · Estimate
| Cost to rebuild | €77,000 to €390,000, for 1,278 to 4,053 hours of work, about 1.6 person-years for 1 to 4 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 70,773 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 account | 2 common.state | 3 lang.directives.values | 4 lang.v1.compiler.Types | 5 lang.v1.compiler.Terms | 6 lang.v1.traits | 7 lang.v1.traits.domain | 8 transaction.Asset | 9 transaction.assets.exchange | 10 lang.script | 11 lang.v1.evaluator | 12 lang.v1.evaluator.ctx | 13 transaction.assets | 14 lang.v1.compiler | 15 lang.v1.evaluator.ctx.impl | 16 lang.v1 | 17 lang | 18 transaction.TxValidationError | 19 transaction.smart.script.trace | 20 state.diffs.invoke | 21 transaction.smart | 22 transaction | 23 utils | 24 events | 25 mining | 26 network | 27 database | 28 utx | 29 api | 30 state | 31 api.common | 32 settings | 33 block | 34 com.wavesplatform | 35 history | 36 ride.runner.blockchain | 37 state.diffs | 38 api.http | 39 db | 40 api.http.utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 account | ||||||||||||||||||||||||||||||||||||||||
| 2 common.state | ||||||||||||||||||||||||||||||||||||||||
| 3 lang.directives.values | ||||||||||||||||||||||||||||||||||||||||
| 4 lang.v1.compiler.Types | ||||||||||||||||||||||||||||||||||||||||
| 5 lang.v1.compiler.Terms | 1 | 10 | 1 | |||||||||||||||||||||||||||||||||||||
| 6 lang.v1.traits | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 lang.v1.traits.domain | 11 | |||||||||||||||||||||||||||||||||||||||
| 8 transaction.Asset | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 9 transaction.assets.exchange | 5 | 3 | 2 | 21 | ||||||||||||||||||||||||||||||||||||
| 10 lang.script | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 lang.v1.evaluator | 1 | 2 | 1 | 12 | 3 | 6 | 3 | 2 | ||||||||||||||||||||||||||||||||
| 12 lang.v1.evaluator.ctx | 3 | 2 | 5 | 1 | 2 | 1 | 5 | 3 | ||||||||||||||||||||||||||||||||
| 13 transaction.assets | 6 | 6 | 5 | 2 | 42 | |||||||||||||||||||||||||||||||||||
| 14 lang.v1.compiler | 1 | 10 | 18 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 15 lang.v1.evaluator.ctx.impl | 1 | 2 | 6 | 7 | 1 | 1 | 1 | 3 | 1 | 4 | 4 | |||||||||||||||||||||||||||||
| 16 lang.v1 | 3 | 1 | 2 | 1 | 1 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 17 lang | 1 | 6 | 4 | 2 | 3 | 2 | 1 | 7 | ||||||||||||||||||||||||||||||||
| 18 transaction.TxValidationError | 3 | 5 | 1 | 40 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 19 transaction.smart.script.trace | 2 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 20 state.diffs.invoke | 8 | 1 | 4 | 4 | 2 | 9 | 1 | 1 | 1 | 3 | 3 | 3 | 2 | 2 | 13 | |||||||||||||||||||||||||
| 21 transaction.smart | 7 | 8 | 3 | 2 | 2 | 4 | 4 | 2 | 1 | 1 | 1 | 1 | 3 | 23 | 1 | 8 | ||||||||||||||||||||||||
| 22 transaction | 18 | 16 | 1 | 2 | 4 | 4 | 2 | 6 | 5 | 2 | 3 | 11 | 6 | |||||||||||||||||||||||||||
| 23 utils | 3 | 2 | 1 | 2 | 3 | 13 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 24 events | 9 | 4 | 1 | 12 | 9 | |||||||||||||||||||||||||||||||||||
| 25 mining | 5 | 3 | 2 | 2 | 5 | 2 | 9 | 1 | 4 | |||||||||||||||||||||||||||||||
| 26 network | 1 | 12 | 3 | 1 | 6 | 17 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||
| 27 database | 4 | 5 | 2 | 3 | 2 | 1 | 40 | 4 | 3 | |||||||||||||||||||||||||||||||
| 28 utx | 1 | 3 | 2 | 2 | 3 | 2 | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||
| 29 api | 8 | 3 | 1 | 4 | 3 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||
| 30 state | 23 | 13 | 6 | 5 | 2 | 5 | 1 | 26 | 2 | 1 | 2 | 2 | 1 | 2 | 3 | 15 | ||||||||||||||||||||||||
| 31 api.common | 7 | 5 | 3 | 2 | 1 | 3 | 4 | 1 | 11 | |||||||||||||||||||||||||||||||
| 32 settings | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 block | 6 | 7 | 1 | 5 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 34 com.wavesplatform | 13 | 8 | 1 | 4 | 3 | 4 | 1 | 4 | 2 | 3 | 3 | 10 | 7 | 1 | 2 | 2 | 21 | 6 | 4 | |||||||||||||||||||||
| 35 history | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 3 | 1 | 4 | 5 | 2 | 8 | |||||||||||||||||||||||||||
| 36 ride.runner.blockchain | 6 | 3 | 2 | 2 | 2 | 5 | 2 | 25 | 2 | 2 | ||||||||||||||||||||||||||||||
| 37 state.diffs | 9 | 3 | 1 | 3 | 1 | 3 | 3 | 6 | 18 | 4 | 3 | 2 | 14 | 1 | 43 | 1 | 5 | |||||||||||||||||||||||
| 38 api.http | 5 | 5 | 2 | 1 | 3 | 1 | 7 | 10 | 8 | 1 | 1 | 14 | 11 | 11 | 1 | |||||||||||||||||||||||||
| 39 db | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 2 | 5 | 2 | 1 | 1 | |||||||||||||||||||||||||||
| 40 api.http.utils | 3 | 1 | 4 | 5 | 1 | 5 | 2 | 4 | 1 | 1 | 11 | 1 | 3 |
5→2 lang.v1.compiler.Terms uses common.state✕
- Connections
- 1 pair of types, where a type in lang.v1.compiler.Terms uses a type in common.state.
- The types involved
com.wavesplatform.lang.v1.compiler.Terms.CONST_BYTESTR→com.wavesplatform.common.state.ByteStr
- Direction
- lang.v1.compiler.Terms uses common.state, so a change to common.state can break lang.v1.compiler.Terms, while a change to lang.v1.compiler.Terms can't break common.state.
- Position
- Below the diagonal: lang.v1.compiler.Terms uses a module listed above it, which is the healthy direction.
5→4 lang.v1.compiler.Terms uses lang.v1.compiler.Types✕
- Connections
- 10 pairs of types, where a type in lang.v1.compiler.Terms uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.compiler.Terms.ARR→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CONST_BIGINT→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CONST_BOOLEAN→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CONST_BYTESTR→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CONST_LONG→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CONST_STRING→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.CaseObj→com.wavesplatform.lang.v1.compiler.Types.CASETYPEREFcom.wavesplatform.lang.v1.compiler.Terms.CaseObj→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.EVALUATED→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.compiler.Terms.FAIL→com.wavesplatform.lang.v1.compiler.Types.REAL
- Direction
- lang.v1.compiler.Terms uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.compiler.Terms, while a change to lang.v1.compiler.Terms can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.compiler.Terms uses a module listed above it, which is the healthy direction.
5→16 lang.v1.compiler.Terms uses lang.v1 part of a loop✕
- Connections
- 1 pair of types, where a type in lang.v1.compiler.Terms uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL→com.wavesplatform.lang.v1.FunctionHeader
- Direction
- lang.v1.compiler.Terms uses lang.v1, so a change to lang.v1 can break lang.v1.compiler.Terms, while a change to lang.v1.compiler.Terms can't break lang.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 lang.v1.traits uses lang.v1.compiler.Types✕
- Connections
- 1 pair of types, where a type in lang.v1.traits uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.traits.DataType→com.wavesplatform.lang.v1.compiler.Types.REAL
- Direction
- lang.v1.traits uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.traits, while a change to lang.v1.traits can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.traits uses a module listed above it, which is the healthy direction.
7→2 lang.v1.traits.domain uses common.state✕
- Connections
- 11 pairs of types, where a type in lang.v1.traits.domain uses a type in common.state.
- The types involved
com.wavesplatform.lang.v1.traits.domain.APair→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.AssetTransfer→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.BlockHeader→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.BlockInfo→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.Burn→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.Issue→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.LeaseCancel→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.Ord→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.Reissue→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.ScriptAssetInfo→com.wavesplatform.common.state.ByteStrcom.wavesplatform.lang.v1.traits.domain.SponsorFee→com.wavesplatform.common.state.ByteStr
- Direction
- lang.v1.traits.domain uses common.state, so a change to common.state can break lang.v1.traits.domain, while a change to lang.v1.traits.domain can't break common.state.
- Position
- Below the diagonal: lang.v1.traits.domain uses a module listed above it, which is the healthy direction.
8→2 transaction.Asset uses common.state✕
- Connections
- 2 pairs of types, where a type in transaction.Asset uses a type in common.state.
- The types involved
com.wavesplatform.transaction.Asset.AssetIdOps→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.Asset.IssuedAsset→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.Asset uses common.state, so a change to common.state can break transaction.Asset, while a change to transaction.Asset can't break common.state.
- Position
- Below the diagonal: transaction.Asset uses a module listed above it, which is the healthy direction.
8→22 transaction.Asset uses transaction part of a loop✕
- Connections
- 4 pairs of types, where a type in transaction.Asset uses a type in transaction.
- The types involved
com.wavesplatform.transaction.Asset.AssetIdOps→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.Asset.Formats→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.Asset.IssuedAsset→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.Asset.Waves→com.wavesplatform.transaction.Asset
- Direction
- transaction.Asset uses transaction, so a change to transaction can break transaction.Asset, while a change to transaction.Asset can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 transaction.assets.exchange uses account✕
- Connections
- 5 pairs of types, where a type in transaction.assets.exchange uses a type in account.
- The types involved
com.wavesplatform.transaction.assets.exchange.EthOrders→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.account.Addresscom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.account.PublicKey
- Direction
- transaction.assets.exchange uses account, so a change to account can break transaction.assets.exchange, while a change to transaction.assets.exchange can't break account.
- Position
- Below the diagonal: transaction.assets.exchange uses a module listed above it, which is the healthy direction.
9→2 transaction.assets.exchange uses common.state✕
- Connections
- 3 pairs of types, where a type in transaction.assets.exchange uses a type in common.state.
- The types involved
com.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.assets.exchange uses common.state, so a change to common.state can break transaction.assets.exchange, while a change to transaction.assets.exchange can't break common.state.
- Position
- Below the diagonal: transaction.assets.exchange uses a module listed above it, which is the healthy direction.
9→18 transaction.assets.exchange uses transaction.TxValidationError part of a loop✕
- Connections
- 2 pairs of types, where a type in transaction.assets.exchange uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- transaction.assets.exchange uses transaction.TxValidationError, so a change to transaction.TxValidationError can break transaction.assets.exchange, while a change to transaction.assets.exchange can't break transaction.TxValidationError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→22 transaction.assets.exchange uses transaction part of a loop✕
- Connections
- 21 pairs of types, where a type in transaction.assets.exchange uses a type in transaction.
- The types involved
com.wavesplatform.transaction.assets.exchange.AssetPair→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.HasSignaturecom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.TxExchangeAmountcom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.TxExchangePricecom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.assets.exchange.ExchangeTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.Provencom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.TxExchangeAmountcom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.TxMatcherFeecom.wavesplatform.transaction.assets.exchange.Order→com.wavesplatform.transaction.TxOrderPricecom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.transaction.TxExchangeAmountcom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.transaction.TxMatcherFeecom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.transaction.TxOrderPricecom.wavesplatform.transaction.assets.exchange.OrderJson→com.wavesplatform.transaction.TxVersion
- Direction
- transaction.assets.exchange uses transaction, so a change to transaction can break transaction.assets.exchange, while a change to transaction.assets.exchange can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 lang.script uses common.state✕
- Connections
- 1 pair of types, where a type in lang.script uses a type in common.state.
- The types involved
com.wavesplatform.lang.script.Script→com.wavesplatform.common.state.ByteStr
- Direction
- lang.script uses common.state, so a change to common.state can break lang.script, while a change to lang.script can't break common.state.
- Position
- Below the diagonal: lang.script uses a module listed above it, which is the healthy direction.
10→3 lang.script uses lang.directives.values✕
- Connections
- 3 pairs of types, where a type in lang.script uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.script.ContractScript→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.script.Script→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.script.ScriptPreprocessor→com.wavesplatform.lang.directives.values.Imports
- Direction
- lang.script uses lang.directives.values, so a change to lang.directives.values can break lang.script, while a change to lang.script can't break lang.directives.values.
- Position
- Below the diagonal: lang.script uses a module listed above it, which is the healthy direction.
10→5 lang.script uses lang.v1.compiler.Terms✕
- Connections
- 2 pairs of types, where a type in lang.script uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.script.ContractScript→com.wavesplatform.lang.v1.compiler.Terms.DECLARATIONcom.wavesplatform.lang.script.ContractScript→com.wavesplatform.lang.v1.compiler.Terms.EXPR
- Direction
- lang.script uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.script, while a change to lang.script can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.script uses a module listed above it, which is the healthy direction.
10→16 lang.script uses lang.v1 part of a loop✕
- Connections
- 2 pairs of types, where a type in lang.script uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.script.ContractScript→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.script.ScriptReader→com.wavesplatform.lang.v1.BaseGlobal
- Direction
- lang.script uses lang.v1, so a change to lang.v1 can break lang.script, while a change to lang.script can't break lang.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 lang.v1.evaluator uses common.state✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator uses a type in common.state.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.common.state.ByteStr
- Direction
- lang.v1.evaluator uses common.state, so a change to common.state can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break common.state.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→3 lang.v1.evaluator uses lang.directives.values✕
- Connections
- 2 pairs of types, where a type in lang.v1.evaluator uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang.v1.evaluator uses lang.directives.values, so a change to lang.directives.values can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.directives.values.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→4 lang.v1.evaluator uses lang.v1.compiler.Types✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContextfulNativeFunction→com.wavesplatform.lang.v1.compiler.Types.TYPE
- Direction
- lang.v1.evaluator uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→5 lang.v1.evaluator uses lang.v1.compiler.Terms✕
- Connections
- 12 pairs of types, where a type in lang.v1.evaluator uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContextfulUserFunction→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.evaluator.ContextfulVal→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.v1.compiler.Terms.DECLARATIONcom.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.compiler.Terms.BLOCK_DEFcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.evaluator.IncompleteResult→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.evaluator.ScriptResult→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.evaluator.ScriptResultV4→com.wavesplatform.lang.v1.compiler.Terms.EVALUATED
- Direction
- lang.v1.evaluator uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→6 lang.v1.evaluator uses lang.v1.traits✕
- Connections
- 3 pairs of types, where a type in lang.v1.evaluator uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.v1.traits.Environmentcom.wavesplatform.lang.v1.evaluator.EvaluatorV1→com.wavesplatform.lang.v1.traits.Environmentcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.traits.Environment
- Direction
- lang.v1.evaluator uses lang.v1.traits, so a change to lang.v1.traits can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.v1.traits.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→7 lang.v1.evaluator uses lang.v1.traits.domain✕
- Connections
- 6 pairs of types, where a type in lang.v1.evaluator uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.lang.v1.evaluator.IncompleteResult→com.wavesplatform.lang.v1.traits.domain.CallableActioncom.wavesplatform.lang.v1.evaluator.ScriptResult→com.wavesplatform.lang.v1.traits.domain.CallableActioncom.wavesplatform.lang.v1.evaluator.ScriptResultV3→com.wavesplatform.lang.v1.traits.domain.AssetTransfercom.wavesplatform.lang.v1.evaluator.ScriptResultV3→com.wavesplatform.lang.v1.traits.domain.CallableActioncom.wavesplatform.lang.v1.evaluator.ScriptResultV3→com.wavesplatform.lang.v1.traits.domain.DataItemcom.wavesplatform.lang.v1.evaluator.ScriptResultV4→com.wavesplatform.lang.v1.traits.domain.CallableAction
- Direction
- lang.v1.evaluator uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.v1.traits.domain.
- Position
- Below the diagonal: lang.v1.evaluator uses a module listed above it, which is the healthy direction.
11→12 lang.v1.evaluator uses lang.v1.evaluator.ctx part of a loop✕
- Connections
- 3 pairs of types, where a type in lang.v1.evaluator uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContextcom.wavesplatform.lang.v1.evaluator.EvalMOps→com.wavesplatform.lang.v1.evaluator.ctx.EnabledLogEvaluationContextcom.wavesplatform.lang.v1.evaluator.EvaluatorV2→com.wavesplatform.lang.v1.evaluator.ctx.LoggedEvaluationContext
- Direction
- lang.v1.evaluator uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.v1.evaluator.ctx.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 lang.v1.evaluator uses lang part of a loop✕
- Connections
- 2 pairs of types, where a type in lang.v1.evaluator uses a type in lang.
- The types involved
com.wavesplatform.lang.v1.evaluator.ContextfulVal→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ContractEvaluator→com.wavesplatform.lang.ExecutionError
- Direction
- lang.v1.evaluator uses lang, so a change to lang can break lang.v1.evaluator, while a change to lang.v1.evaluator can't break lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 lang.v1.evaluator.ctx uses lang.directives.values✕
- Connections
- 3 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.BaseFunction→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.v1.evaluator.ctx.NativeFunction→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.v1.evaluator.ctx.UserFunction→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang.v1.evaluator.ctx uses lang.directives.values, so a change to lang.directives.values can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.directives.values.
- Position
- Below the diagonal: lang.v1.evaluator.ctx uses a module listed above it, which is the healthy direction.
12→4 lang.v1.evaluator.ctx uses lang.v1.compiler.Types✕
- Connections
- 2 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContext→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.evaluator.ctx.FunctionTypeSignature→com.wavesplatform.lang.v1.compiler.Types.TYPE
- Direction
- lang.v1.evaluator.ctx uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.evaluator.ctx uses a module listed above it, which is the healthy direction.
12→5 lang.v1.evaluator.ctx uses lang.v1.compiler.Terms✕
- Connections
- 5 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.DisabledLogEvaluationContext→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.evaluator.ctx.EnabledLogEvaluationContext→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.evaluator.ctx.LazyVal→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.evaluator.ctx.LoggedEvaluationContext→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.evaluator.ctx.impl→com.wavesplatform.lang.v1.compiler.Terms.CaseObj
- Direction
- lang.v1.evaluator.ctx uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.v1.evaluator.ctx uses a module listed above it, which is the healthy direction.
12→6 lang.v1.evaluator.ctx uses lang.v1.traits✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.InvariableContext→com.wavesplatform.lang.v1.traits.Environment
- Direction
- lang.v1.evaluator.ctx uses lang.v1.traits, so a change to lang.v1.traits can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.traits.
- Position
- Below the diagonal: lang.v1.evaluator.ctx uses a module listed above it, which is the healthy direction.
12→11 lang.v1.evaluator.ctx uses lang.v1.evaluator✕
- Connections
- 2 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.evaluator.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.NativeFunction→com.wavesplatform.lang.v1.evaluator.ContextfulNativeFunctioncom.wavesplatform.lang.v1.evaluator.ctx.UserFunction→com.wavesplatform.lang.v1.evaluator.ContextfulUserFunction
- Direction
- lang.v1.evaluator.ctx uses lang.v1.evaluator, so a change to lang.v1.evaluator can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.evaluator.
- Position
- Below the diagonal: lang.v1.evaluator.ctx uses a module listed above it, which is the healthy direction.
12→14 lang.v1.evaluator.ctx uses lang.v1.compiler part of a loop✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.compiler.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl→com.wavesplatform.lang.v1.compiler.ScriptResultSource
- Direction
- lang.v1.evaluator.ctx uses lang.v1.compiler, so a change to lang.v1.compiler can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.compiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 lang.v1.evaluator.ctx uses lang.v1 part of a loop✕
- Connections
- 5 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.BaseFunction→com.wavesplatform.lang.v1.FunctionHeadercom.wavesplatform.lang.v1.evaluator.ctx.EvaluationContext→com.wavesplatform.lang.v1.FunctionHeadercom.wavesplatform.lang.v1.evaluator.ctx.FunctionTypeSignature→com.wavesplatform.lang.v1.FunctionHeadercom.wavesplatform.lang.v1.evaluator.ctx.InvariableContext→com.wavesplatform.lang.v1.CTXcom.wavesplatform.lang.v1.evaluator.ctx.impl→com.wavesplatform.lang.v1.FunctionHeader
- Direction
- lang.v1.evaluator.ctx uses lang.v1, so a change to lang.v1 can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 lang.v1.evaluator.ctx uses lang part of a loop✕
- Connections
- 3 pairs of types, where a type in lang.v1.evaluator.ctx uses a type in lang.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.EnabledLogEvaluationContext→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ctx.LazyVal→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ctx.impl→com.wavesplatform.lang.ExecutionError
- Direction
- lang.v1.evaluator.ctx uses lang, so a change to lang can break lang.v1.evaluator.ctx, while a change to lang.v1.evaluator.ctx can't break lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 transaction.assets uses account✕
- Connections
- 6 pairs of types, where a type in transaction.assets uses a type in account.
- The types involved
com.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.SponsorFeeTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.assets.UpdateAssetInfoTransaction→com.wavesplatform.account.PublicKey
- Direction
- transaction.assets uses account, so a change to account can break transaction.assets, while a change to transaction.assets can't break account.
- Position
- Below the diagonal: transaction.assets uses a module listed above it, which is the healthy direction.
13→2 transaction.assets uses common.state✕
- Connections
- 6 pairs of types, where a type in transaction.assets uses a type in common.state.
- The types involved
com.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.SponsorFeeTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.assets.UpdateAssetInfoTransaction→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.assets uses common.state, so a change to common.state can break transaction.assets, while a change to transaction.assets can't break common.state.
- Position
- Below the diagonal: transaction.assets uses a module listed above it, which is the healthy direction.
13→8 transaction.assets uses transaction.Asset✕
- Connections
- 5 pairs of types, where a type in transaction.assets uses a type in transaction.Asset.
- The types involved
com.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.assets.SponsorFeeTransaction→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.assets.UpdateAssetInfoTransaction→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- transaction.assets uses transaction.Asset, so a change to transaction.Asset can break transaction.assets, while a change to transaction.assets can't break transaction.Asset.
- Position
- Below the diagonal: transaction.assets uses a module listed above it, which is the healthy direction.
13→10 transaction.assets uses lang.script✕
- Connections
- 2 pairs of types, where a type in transaction.assets uses a type in lang.script.
- The types involved
com.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.lang.script.Scriptcom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.lang.script.Script
- Direction
- transaction.assets uses lang.script, so a change to lang.script can break transaction.assets, while a change to transaction.assets can't break lang.script.
- Position
- Below the diagonal: transaction.assets uses a module listed above it, which is the healthy direction.
13→22 transaction.assets uses transaction part of a loop✕
- Connections
- 42 pairs of types, where a type in transaction.assets uses a type in transaction. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.HasSignaturecom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.TxNonNegativeAmountcom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.assets.BurnTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.HasSignaturecom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.TxDecimalscom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.assets.IssueTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.HasSignaturecom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.assets.ReissueTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.assets.SetAssetScriptTransaction→com.wavesplatform.transaction.Proofs
- Direction
- transaction.assets uses transaction, so a change to transaction can break transaction.assets, while a change to transaction.assets can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 lang.v1.compiler uses lang.directives.values✕
- Connections
- 1 pair of types, where a type in lang.v1.compiler uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang.v1.compiler uses lang.directives.values, so a change to lang.directives.values can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.directives.values.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→4 lang.v1.compiler uses lang.v1.compiler.Types✕
- Connections
- 10 pairs of types, where a type in lang.v1.compiler uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.compiler.CompilationStepResultDec→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.CompilationStepResultExpr→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.CompilerContext→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.Terms→com.wavesplatform.lang.v1.compiler.Types.CASETYPEREFcom.wavesplatform.lang.v1.compiler.TypeCast→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.TypeInferrer→com.wavesplatform.lang.v1.compiler.Types.FINALcom.wavesplatform.lang.v1.compiler.TypeInferrer→com.wavesplatform.lang.v1.compiler.Types.TUPLEcom.wavesplatform.lang.v1.compiler.TypeInferrer→com.wavesplatform.lang.v1.compiler.Types.TYPEcom.wavesplatform.lang.v1.compiler.TypeInferrer→com.wavesplatform.lang.v1.compiler.Types.TYPEPARAM
- Direction
- lang.v1.compiler uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→5 lang.v1.compiler uses lang.v1.compiler.Terms✕
- Connections
- 18 pairs of types, where a type in lang.v1.compiler uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.v1.compiler.CompilerMacro→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler.ContractScriptCompactor→com.wavesplatform.lang.v1.compiler.Terms.DECLARATIONcom.wavesplatform.lang.v1.compiler.ContractScriptCompactor→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler.ContractScriptCompactor→com.wavesplatform.lang.v1.compiler.Terms.FUNCcom.wavesplatform.lang.v1.compiler.ContractScriptCompactor→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.compiler.Decompiler→com.wavesplatform.lang.v1.compiler.Terms.DECLARATIONcom.wavesplatform.lang.v1.compiler.Decompiler→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Terms.FUNCcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Terms.IFcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Terms.LETcom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.compiler.Terms.REFcom.wavesplatform.lang.v1.compiler.TermPrinter→com.wavesplatform.lang.v1.compiler.Terms.ARRcom.wavesplatform.lang.v1.compiler.TermPrinter→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.compiler.TermPrinter→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.compiler.TypeCast→com.wavesplatform.lang.v1.compiler.Terms.CONST_STRINGcom.wavesplatform.lang.v1.compiler.TypeCast→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler.TypeCast→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL
- Direction
- lang.v1.compiler uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→6 lang.v1.compiler uses lang.v1.traits✕
- Connections
- 1 pair of types, where a type in lang.v1.compiler uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.v1.compiler.TestCompiler→com.wavesplatform.lang.v1.traits.Environment
- Direction
- lang.v1.compiler uses lang.v1.traits, so a change to lang.v1.traits can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.v1.traits.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→10 lang.v1.compiler uses lang.script✕
- Connections
- 1 pair of types, where a type in lang.v1.compiler uses a type in lang.script.
- The types involved
com.wavesplatform.lang.v1.compiler.TestCompiler→com.wavesplatform.lang.script.Script
- Direction
- lang.v1.compiler uses lang.script, so a change to lang.script can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.script.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→12 lang.v1.compiler uses lang.v1.evaluator.ctx✕
- Connections
- 2 pairs of types, where a type in lang.v1.compiler uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.lang.v1.compiler.CompilerContext→com.wavesplatform.lang.v1.evaluator.ctx.FunctionTypeSignaturecom.wavesplatform.lang.v1.compiler.ExpressionCompiler→com.wavesplatform.lang.v1.evaluator.ctx.FunctionTypeSignature
- Direction
- lang.v1.compiler uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: lang.v1.compiler uses a module listed above it, which is the healthy direction.
14→16 lang.v1.compiler uses lang.v1 part of a loop✕
- Connections
- 3 pairs of types, where a type in lang.v1.compiler uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.v1.compiler.CompilerMacro→com.wavesplatform.lang.v1.FunctionHeadercom.wavesplatform.lang.v1.compiler.Decompiler→com.wavesplatform.lang.v1.FunctionHeadercom.wavesplatform.lang.v1.compiler.TestCompiler→com.wavesplatform.lang.v1.CTX
- Direction
- lang.v1.compiler uses lang.v1, so a change to lang.v1 can break lang.v1.compiler, while a change to lang.v1.compiler can't break lang.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 lang.v1.evaluator.ctx.impl uses common.state✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx.impl uses a type in common.state.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.converters→com.wavesplatform.common.state.ByteStr
- Direction
- lang.v1.evaluator.ctx.impl uses common.state, so a change to common.state can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break common.state.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→3 lang.v1.evaluator.ctx.impl uses lang.directives.values✕
- Connections
- 2 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang.v1.evaluator.ctx.impl uses lang.directives.values, so a change to lang.directives.values can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.directives.values.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→4 lang.v1.evaluator.ctx.impl uses lang.v1.compiler.Types✕
- Connections
- 6 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.compiler.Types.CASETYPEREFcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Types.CASETYPEREFcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Types.REALcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Types.TYPEcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Types.UNIONcom.wavesplatform.lang.v1.evaluator.ctx.impl.Rounding→com.wavesplatform.lang.v1.compiler.Types.CASETYPEREF
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→5 lang.v1.evaluator.ctx.impl uses lang.v1.compiler.Terms✕
- Connections
- 7 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.evaluator.ctx.impl.EnvironmentFunctions→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Terms.CONST_STRINGcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.lang.v1.evaluator.ctx.impl.Rounding→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.evaluator.ctx.impl.converters→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.v1.evaluator.ctx.impl.converters→com.wavesplatform.lang.v1.compiler.Terms.EVALUATED
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→6 lang.v1.evaluator.ctx.impl uses lang.v1.traits✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.EnvironmentFunctions→com.wavesplatform.lang.v1.traits.DataType
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.traits, so a change to lang.v1.traits can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.traits.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→7 lang.v1.evaluator.ctx.impl uses lang.v1.traits.domain✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.EnvironmentFunctions→com.wavesplatform.lang.v1.traits.domain.Recipient
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.traits.domain.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→11 lang.v1.evaluator.ctx.impl uses lang.v1.evaluator✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.evaluator.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.evaluator.ContextfulVal
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.evaluator, so a change to lang.v1.evaluator can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.evaluator.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→12 lang.v1.evaluator.ctx.impl uses lang.v1.evaluator.ctx✕
- Connections
- 3 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContextcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.evaluator.ctx.BaseFunctioncom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.evaluator.ctx.NativeFunction
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→14 lang.v1.evaluator.ctx.impl uses lang.v1.compiler✕
- Connections
- 1 pair of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.compiler.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.compiler.CompilerContext
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1.compiler, so a change to lang.v1.compiler can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.compiler.
- Position
- Below the diagonal: lang.v1.evaluator.ctx.impl uses a module listed above it, which is the healthy direction.
15→16 lang.v1.evaluator.ctx.impl uses lang.v1 part of a loop✕
- Connections
- 4 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.v1.CTXcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.v1.CTX
- Direction
- lang.v1.evaluator.ctx.impl uses lang.v1, so a change to lang.v1 can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→17 lang.v1.evaluator.ctx.impl uses lang part of a loop✕
- Connections
- 4 pairs of types, where a type in lang.v1.evaluator.ctx.impl uses a type in lang.
- The types involved
com.wavesplatform.lang.v1.evaluator.ctx.impl.CryptoContext→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ctx.impl.EnvironmentFunctions→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ctx.impl.PureContext→com.wavesplatform.lang.ExecutionErrorcom.wavesplatform.lang.v1.evaluator.ctx.impl.converters→com.wavesplatform.lang.ExecutionError
- Direction
- lang.v1.evaluator.ctx.impl uses lang, so a change to lang can break lang.v1.evaluator.ctx.impl, while a change to lang.v1.evaluator.ctx.impl can't break lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→3 lang.v1 uses lang.directives.values✕
- Connections
- 3 pairs of types, where a type in lang.v1 uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.directives.values.ScriptTypecom.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.v1.ContractLimits→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang.v1 uses lang.directives.values, so a change to lang.directives.values can break lang.v1, while a change to lang.v1 can't break lang.directives.values.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→4 lang.v1 uses lang.v1.compiler.Types✕
- Connections
- 1 pair of types, where a type in lang.v1 uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.lang.v1.CTX→com.wavesplatform.lang.v1.compiler.Types.FINAL
- Direction
- lang.v1 uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break lang.v1, while a change to lang.v1 can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→5 lang.v1 uses lang.v1.compiler.Terms✕
- Connections
- 2 pairs of types, where a type in lang.v1 uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.v1.compiler→com.wavesplatform.lang.v1.compiler.Terms.EXPR
- Direction
- lang.v1 uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang.v1, while a change to lang.v1 can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→6 lang.v1 uses lang.v1.traits✕
- Connections
- 1 pair of types, where a type in lang.v1 uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.v1.repl→com.wavesplatform.lang.v1.traits.Environment
- Direction
- lang.v1 uses lang.v1.traits, so a change to lang.v1.traits can break lang.v1, while a change to lang.v1 can't break lang.v1.traits.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→10 lang.v1 uses lang.script✕
- Connections
- 1 pair of types, where a type in lang.v1 uses a type in lang.script.
- The types involved
com.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.script.Script
- Direction
- lang.v1 uses lang.script, so a change to lang.script can break lang.v1, while a change to lang.v1 can't break lang.script.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→12 lang.v1 uses lang.v1.evaluator.ctx✕
- Connections
- 2 pairs of types, where a type in lang.v1 uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.lang.v1.CTX→com.wavesplatform.lang.v1.evaluator.ctx.BaseFunctioncom.wavesplatform.lang.v1.CTX→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContext
- Direction
- lang.v1 uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break lang.v1, while a change to lang.v1 can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→14 lang.v1 uses lang.v1.compiler✕
- Connections
- 3 pairs of types, where a type in lang.v1 uses a type in lang.v1.compiler.
- The types involved
com.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.v1.compiler.CompilerContextcom.wavesplatform.lang.v1.CTX→com.wavesplatform.lang.v1.compiler.CompilerContextcom.wavesplatform.lang.v1.CTX→com.wavesplatform.lang.v1.compiler.DecompilerContext
- Direction
- lang.v1 uses lang.v1.compiler, so a change to lang.v1.compiler can break lang.v1, while a change to lang.v1 can't break lang.v1.compiler.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→15 lang.v1 uses lang.v1.evaluator.ctx.impl✕
- Connections
- 1 pair of types, where a type in lang.v1 uses a type in lang.v1.evaluator.ctx.impl.
- The types involved
com.wavesplatform.lang.v1.BaseGlobal→com.wavesplatform.lang.v1.evaluator.ctx.impl.Rounding
- Direction
- lang.v1 uses lang.v1.evaluator.ctx.impl, so a change to lang.v1.evaluator.ctx.impl can break lang.v1, while a change to lang.v1 can't break lang.v1.evaluator.ctx.impl.
- Position
- Below the diagonal: lang.v1 uses a module listed above it, which is the healthy direction.
16→17 lang.v1 uses lang part of a loop✕
- Connections
- 1 pair of types, where a type in lang.v1 uses a type in lang.
- The types involved
com.wavesplatform.lang.v1.evaluator→com.wavesplatform.lang.ExecutionError
- Direction
- lang.v1 uses lang, so a change to lang can break lang.v1, while a change to lang.v1 can't break lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 lang uses common.state✕
- Connections
- 1 pair of types, where a type in lang uses a type in common.state.
- The types involved
com.wavesplatform.lang.utils→com.wavesplatform.common.state.ByteStr
- Direction
- lang uses common.state, so a change to common.state can break lang, while a change to lang can't break common.state.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→3 lang uses lang.directives.values✕
- Connections
- 6 pairs of types, where a type in lang uses a type in lang.directives.values.
- The types involved
com.wavesplatform.lang.API→com.wavesplatform.lang.directives.values.Expressioncom.wavesplatform.lang.API→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.CompileResult→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.lang.utils→com.wavesplatform.lang.directives.values.ContentTypecom.wavesplatform.lang.utils→com.wavesplatform.lang.directives.values.ScriptTypecom.wavesplatform.lang.utils→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- lang uses lang.directives.values, so a change to lang.directives.values can break lang, while a change to lang can't break lang.directives.values.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→5 lang uses lang.v1.compiler.Terms✕
- Connections
- 4 pairs of types, where a type in lang uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.lang.Common→com.wavesplatform.lang.v1.compiler.Terms.CaseObjcom.wavesplatform.lang.Common→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.Lang→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.lang.Testing→com.wavesplatform.lang.v1.compiler.Terms.EVALUATED
- Direction
- lang uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break lang, while a change to lang can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→6 lang uses lang.v1.traits✕
- Connections
- 2 pairs of types, where a type in lang uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.lang.Common→com.wavesplatform.lang.v1.traits.Environmentcom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.traits.Environment
- Direction
- lang uses lang.v1.traits, so a change to lang.v1.traits can break lang, while a change to lang can't break lang.v1.traits.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→12 lang uses lang.v1.evaluator.ctx✕
- Connections
- 3 pairs of types, where a type in lang uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.lang.Common→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContextcom.wavesplatform.lang.Common→com.wavesplatform.lang.v1.evaluator.ctx.NativeFunctioncom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContext
- Direction
- lang uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break lang, while a change to lang can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→14 lang uses lang.v1.compiler✕
- Connections
- 2 pairs of types, where a type in lang uses a type in lang.v1.compiler.
- The types involved
com.wavesplatform.lang.utils→com.wavesplatform.lang.v1.compiler.CompilerContextcom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.compiler.DecompilerContext
- Direction
- lang uses lang.v1.compiler, so a change to lang.v1.compiler can break lang, while a change to lang can't break lang.v1.compiler.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→15 lang uses lang.v1.evaluator.ctx.impl✕
- Connections
- 1 pair of types, where a type in lang uses a type in lang.v1.evaluator.ctx.impl.
- The types involved
com.wavesplatform.lang.Global→com.wavesplatform.lang.v1.evaluator.ctx.impl.Rounding
- Direction
- lang uses lang.v1.evaluator.ctx.impl, so a change to lang.v1.evaluator.ctx.impl can break lang, while a change to lang can't break lang.v1.evaluator.ctx.impl.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
17→16 lang uses lang.v1✕
- Connections
- 7 pairs of types, where a type in lang uses a type in lang.v1.
- The types involved
com.wavesplatform.lang.API→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.Common→com.wavesplatform.lang.v1.CTXcom.wavesplatform.lang.Global→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.hacks→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.BaseGlobalcom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.CTXcom.wavesplatform.lang.utils→com.wavesplatform.lang.v1.FunctionHeader
- Direction
- lang uses lang.v1, so a change to lang.v1 can break lang, while a change to lang can't break lang.v1.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
18→1 transaction.TxValidationError uses account✕
- Connections
- 3 pairs of types, where a type in transaction.TxValidationError uses a type in account.
- The types involved
com.wavesplatform.transaction.TxValidationError.AccountBalanceError→com.wavesplatform.account.Addresscom.wavesplatform.transaction.TxValidationError.AliasDoesNotExist→com.wavesplatform.account.Aliascom.wavesplatform.transaction.TxValidationError.AliasIsDisabled→com.wavesplatform.account.Alias
- Direction
- transaction.TxValidationError uses account, so a change to account can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break account.
- Position
- Below the diagonal: transaction.TxValidationError uses a module listed above it, which is the healthy direction.
18→2 transaction.TxValidationError uses common.state✕
- Connections
- 5 pairs of types, where a type in transaction.TxValidationError uses a type in common.state.
- The types involved
com.wavesplatform.transaction.TxValidationError.AlreadyInTheState→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TxValidationError.FailedTransactionError→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TxValidationError.InvalidStateHash→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TxValidationError.ScriptExecutionError→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TxValidationError.TransactionNotAllowedByScript→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.TxValidationError uses common.state, so a change to common.state can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break common.state.
- Position
- Below the diagonal: transaction.TxValidationError uses a module listed above it, which is the healthy direction.
18→9 transaction.TxValidationError uses transaction.assets.exchange✕
- Connections
- 1 pair of types, where a type in transaction.TxValidationError uses a type in transaction.assets.exchange.
- The types involved
com.wavesplatform.transaction.TxValidationError.OrderValidationError→com.wavesplatform.transaction.assets.exchange.Order
- Direction
- transaction.TxValidationError uses transaction.assets.exchange, so a change to transaction.assets.exchange can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break transaction.assets.exchange.
- Position
- Below the diagonal: transaction.TxValidationError uses a module listed above it, which is the healthy direction.
18→17 transaction.TxValidationError uses lang✕
- Connections
- 40 pairs of types, where a type in transaction.TxValidationError uses a type in lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.wavesplatform.transaction.TxValidationError.AccountBalanceError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.ActivationError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.AliasDoesNotExist→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.AliasIsDisabled→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.AlreadyInTheState→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.BlockAppendError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.BlockFromFuture→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.DuplicatedDataKeys→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.EmptyDataKey→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.FailedTransactionError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.GenericError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InsufficientFee→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidAddress→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidAssetId→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidDecimals→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidName→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidRequestSignature→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidSignature→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvalidStateHash→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.InvokeRejectError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.MicroBlockAppendError→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.MissingSenderPrivateKey→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.Mistiming→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.NegativeAmount→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TxValidationError.NegativeMinFee→com.wavesplatform.lang.ValidationError
- Direction
- transaction.TxValidationError uses lang, so a change to lang can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break lang.
- Position
- Below the diagonal: transaction.TxValidationError uses a module listed above it, which is the healthy direction.
18→22 transaction.TxValidationError uses transaction part of a loop✕
- Connections
- 1 pair of types, where a type in transaction.TxValidationError uses a type in transaction.
- The types involved
com.wavesplatform.transaction.TxValidationError.InvalidSignature→com.wavesplatform.transaction.Signed
- Direction
- transaction.TxValidationError uses transaction, so a change to transaction can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→30 transaction.TxValidationError uses state part of a loop✕
- Connections
- 1 pair of types, where a type in transaction.TxValidationError uses a type in state.
- The types involved
com.wavesplatform.transaction.TxValidationError.AlreadyInTheState→com.wavesplatform.state.Height
- Direction
- transaction.TxValidationError uses state, so a change to state can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→33 transaction.TxValidationError uses block part of a loop✕
- Connections
- 2 pairs of types, where a type in transaction.TxValidationError uses a type in block.
- The types involved
com.wavesplatform.transaction.TxValidationError.BlockAppendError→com.wavesplatform.block.Blockcom.wavesplatform.transaction.TxValidationError.MicroBlockAppendError→com.wavesplatform.block.MicroBlock
- Direction
- transaction.TxValidationError uses block, so a change to block can break transaction.TxValidationError, while a change to transaction.TxValidationError can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 transaction.smart.script.trace uses account✕
- Connections
- 2 pairs of types, where a type in transaction.smart.script.trace uses a type in account.
- The types involved
com.wavesplatform.transaction.smart.script.trace.AccountVerifierTrace→com.wavesplatform.account.Addresscom.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.account.AddressOrAlias
- Direction
- transaction.smart.script.trace uses account, so a change to account can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break account.
- Position
- Below the diagonal: transaction.smart.script.trace uses a module listed above it, which is the healthy direction.
19→2 transaction.smart.script.trace uses common.state✕
- Connections
- 1 pair of types, where a type in transaction.smart.script.trace uses a type in common.state.
- The types involved
com.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.smart.script.trace uses common.state, so a change to common.state can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break common.state.
- Position
- Below the diagonal: transaction.smart.script.trace uses a module listed above it, which is the healthy direction.
19→5 transaction.smart.script.trace uses lang.v1.compiler.Terms✕
- Connections
- 1 pair of types, where a type in transaction.smart.script.trace uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL
- Direction
- transaction.smart.script.trace uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: transaction.smart.script.trace uses a module listed above it, which is the healthy direction.
19→11 transaction.smart.script.trace uses lang.v1.evaluator✕
- Connections
- 1 pair of types, where a type in transaction.smart.script.trace uses a type in lang.v1.evaluator.
- The types involved
com.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.lang.v1.evaluator.ScriptResult
- Direction
- transaction.smart.script.trace uses lang.v1.evaluator, so a change to lang.v1.evaluator can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break lang.v1.evaluator.
- Position
- Below the diagonal: transaction.smart.script.trace uses a module listed above it, which is the healthy direction.
19→17 transaction.smart.script.trace uses lang✕
- Connections
- 3 pairs of types, where a type in transaction.smart.script.trace uses a type in lang.
- The types involved
com.wavesplatform.transaction.smart.script.trace.AccountVerifierTrace→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.smart.script.trace.CoevalR→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.lang.ValidationError
- Direction
- transaction.smart.script.trace uses lang, so a change to lang can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break lang.
- Position
- Below the diagonal: transaction.smart.script.trace uses a module listed above it, which is the healthy direction.
19→30 transaction.smart.script.trace uses state part of a loop✕
- Connections
- 1 pair of types, where a type in transaction.smart.script.trace uses a type in state.
- The types involved
com.wavesplatform.transaction.smart.script.trace.InvokeScriptTrace→com.wavesplatform.state.InvokeScriptResult
- Direction
- transaction.smart.script.trace uses state, so a change to state can break transaction.smart.script.trace, while a change to transaction.smart.script.trace can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 state.diffs.invoke uses account✕
- Connections
- 8 pairs of types, where a type in state.diffs.invoke uses a type in account.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.account.PublicKeycom.wavesplatform.state.diffs.invoke.InvokeScript→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.invoke.InvokeScript→com.wavesplatform.account.PublicKeycom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.invoke.InvokeScriptLike→com.wavesplatform.account.AddressOrAliascom.wavesplatform.state.diffs.invoke.InvokeScriptLike→com.wavesplatform.account.PublicKeycom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.account.Address
- Direction
- state.diffs.invoke uses account, so a change to account can break state.diffs.invoke, while a change to state.diffs.invoke can't break account.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→2 state.diffs.invoke uses common.state✕
- Connections
- 1 pair of types, where a type in state.diffs.invoke uses a type in common.state.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.common.state.ByteStr
- Direction
- state.diffs.invoke uses common.state, so a change to common.state can break state.diffs.invoke, while a change to state.diffs.invoke can't break common.state.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→3 state.diffs.invoke uses lang.directives.values✕
- Connections
- 4 pairs of types, where a type in state.diffs.invoke uses a type in lang.directives.values.
- The types involved
com.wavesplatform.state.diffs.invoke.CachedDAppCTX→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- state.diffs.invoke uses lang.directives.values, so a change to lang.directives.values can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.directives.values.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→5 state.diffs.invoke uses lang.v1.compiler.Terms✕
- Connections
- 4 pairs of types, where a type in state.diffs.invoke uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.state.diffs.invoke.CallArgumentPolicy→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.state.diffs.invoke.InvokeScript→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALLcom.wavesplatform.state.diffs.invoke.InvokeScriptLike→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALLcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL
- Direction
- state.diffs.invoke uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→6 state.diffs.invoke uses lang.v1.traits✕
- Connections
- 2 pairs of types, where a type in state.diffs.invoke uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.lang.v1.traits.Environmentcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.lang.v1.traits.Environment
- Direction
- state.diffs.invoke uses lang.v1.traits, so a change to lang.v1.traits can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.v1.traits.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→7 state.diffs.invoke uses lang.v1.traits.domain✕
- Connections
- 9 pairs of types, where a type in state.diffs.invoke uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.AssetTransfercom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.CallableActioncom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.DataOpcom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.Issuecom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.Leasecom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.LeaseCancelcom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.traits.domain.PseudoTxcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.lang.v1.traits.domain.Issuecom.wavesplatform.state.diffs.invoke.StructuredCallableActions→com.wavesplatform.lang.v1.traits.domain.CallableAction
- Direction
- state.diffs.invoke uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.v1.traits.domain.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→10 state.diffs.invoke uses lang.script✕
- Connections
- 1 pair of types, where a type in state.diffs.invoke uses a type in lang.script.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.script.Script
- Direction
- state.diffs.invoke uses lang.script, so a change to lang.script can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.script.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→11 state.diffs.invoke uses lang.v1.evaluator✕
- Connections
- 1 pair of types, where a type in state.diffs.invoke uses a type in lang.v1.evaluator.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.v1.evaluator.ScriptResult
- Direction
- state.diffs.invoke uses lang.v1.evaluator, so a change to lang.v1.evaluator can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.v1.evaluator.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→12 state.diffs.invoke uses lang.v1.evaluator.ctx✕
- Connections
- 1 pair of types, where a type in state.diffs.invoke uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.state.diffs.invoke.CachedDAppCTX→com.wavesplatform.lang.v1.evaluator.ctx.InvariableContext
- Direction
- state.diffs.invoke uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→17 state.diffs.invoke uses lang✕
- Connections
- 3 pairs of types, where a type in state.diffs.invoke uses a type in lang.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.lang.ValidationError
- Direction
- state.diffs.invoke uses lang, so a change to lang can break state.diffs.invoke, while a change to state.diffs.invoke can't break lang.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→18 state.diffs.invoke uses transaction.TxValidationError✕
- Connections
- 3 pairs of types, where a type in state.diffs.invoke uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.transaction.TxValidationError.FailedTransactionErrorcom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- state.diffs.invoke uses transaction.TxValidationError, so a change to transaction.TxValidationError can break state.diffs.invoke, while a change to state.diffs.invoke can't break transaction.TxValidationError.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→19 state.diffs.invoke uses transaction.smart.script.trace✕
- Connections
- 3 pairs of types, where a type in state.diffs.invoke uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.transaction.smart.script.trace.TracedResultcom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.transaction.smart.script.trace.CoevalRcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- state.diffs.invoke uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break state.diffs.invoke, while a change to state.diffs.invoke can't break transaction.smart.script.trace.
- Position
- Below the diagonal: state.diffs.invoke uses a module listed above it, which is the healthy direction.
20→21 state.diffs.invoke uses transaction.smart part of a loop✕
- Connections
- 2 pairs of types, where a type in state.diffs.invoke uses a type in transaction.smart.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.transaction.smart.DAppEnvironmentcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.transaction.smart.InvokeExpressionTransaction
- Direction
- state.diffs.invoke uses transaction.smart, so a change to transaction.smart can break state.diffs.invoke, while a change to state.diffs.invoke can't break transaction.smart.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 state.diffs.invoke uses transaction part of a loop✕
- Connections
- 2 pairs of types, where a type in state.diffs.invoke uses a type in transaction.
- The types involved
com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLike→com.wavesplatform.transaction.Authorizedcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLike→com.wavesplatform.transaction.TransactionBase
- Direction
- state.diffs.invoke uses transaction, so a change to transaction can break state.diffs.invoke, while a change to state.diffs.invoke can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→30 state.diffs.invoke uses state part of a loop✕
- Connections
- 13 pairs of types, where a type in state.diffs.invoke uses a type in state.
- The types involved
com.wavesplatform.state.diffs.invoke.CachedDAppCTX→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.state.DataEntrycom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.state.InvokeScriptResultcom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.state.Portfoliocom.wavesplatform.state.diffs.invoke.InvokeDiffsCommon→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.invoke.InvokeScriptDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.state.InvokeScriptResultcom.wavesplatform.state.diffs.invoke.InvokeScriptTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.invoke.StructuredCallableActions→com.wavesplatform.state.Blockchain
- Direction
- state.diffs.invoke uses state, so a change to state can break state.diffs.invoke, while a change to state.diffs.invoke can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 transaction.smart uses account✕
- Connections
- 7 pairs of types, where a type in transaction.smart uses a type in account.
- The types involved
com.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.account.AddressOrAliascom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.account.Addresscom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.account.AddressOrAliascom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.account.AddressOrAliascom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.account.PublicKey
- Direction
- transaction.smart uses account, so a change to account can break transaction.smart, while a change to transaction.smart can't break account.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→2 transaction.smart uses common.state✕
- Connections
- 8 pairs of types, where a type in transaction.smart uses a type in common.state.
- The types involved
com.wavesplatform.transaction.smart.AssetScript→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.BlockchainContext→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.smart.WavesEnvironment→com.wavesplatform.common.state.ByteStr
- Direction
- transaction.smart uses common.state, so a change to common.state can break transaction.smart, while a change to transaction.smart can't break common.state.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→3 transaction.smart uses lang.directives.values✕
- Connections
- 3 pairs of types, where a type in transaction.smart uses a type in lang.directives.values.
- The types involved
com.wavesplatform.transaction.smart.AttachedPaymentExtractor→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.transaction.smart.BlockchainContext→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- transaction.smart uses lang.directives.values, so a change to lang.directives.values can break transaction.smart, while a change to transaction.smart can't break lang.directives.values.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→5 transaction.smart uses lang.v1.compiler.Terms✕
- Connections
- 2 pairs of types, where a type in transaction.smart uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALLcom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.lang.v1.compiler.Terms.EVALUATED
- Direction
- transaction.smart uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break transaction.smart, while a change to transaction.smart can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→6 transaction.smart uses lang.v1.traits✕
- Connections
- 2 pairs of types, where a type in transaction.smart uses a type in lang.v1.traits.
- The types involved
com.wavesplatform.transaction.smart.BlockchainContext→com.wavesplatform.lang.v1.traits.Environmentcom.wavesplatform.transaction.smart.DAppEnvironmentInterface→com.wavesplatform.lang.v1.traits.Environment
- Direction
- transaction.smart uses lang.v1.traits, so a change to lang.v1.traits can break transaction.smart, while a change to transaction.smart can't break lang.v1.traits.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→7 transaction.smart uses lang.v1.traits.domain✕
- Connections
- 4 pairs of types, where a type in transaction.smart uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.transaction.smart.AttachedPaymentExtractor→com.wavesplatform.lang.v1.traits.domain.AttachedPaymentscom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.lang.v1.traits.domain.APaircom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.lang.v1.traits.domain.Ordcom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.lang.v1.traits.domain.Tx
- Direction
- transaction.smart uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break transaction.smart, while a change to transaction.smart can't break lang.v1.traits.domain.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→9 transaction.smart uses transaction.assets.exchange✕
- Connections
- 4 pairs of types, where a type in transaction.smart uses a type in transaction.assets.exchange.
- The types involved
com.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.transaction.assets.exchange.AssetPaircom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.transaction.assets.exchange.Ordercom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.assets.exchange.ExchangeTransactioncom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.assets.exchange.Order
- Direction
- transaction.smart uses transaction.assets.exchange, so a change to transaction.assets.exchange can break transaction.smart, while a change to transaction.smart can't break transaction.assets.exchange.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→10 transaction.smart uses lang.script✕
- Connections
- 2 pairs of types, where a type in transaction.smart uses a type in lang.script.
- The types involved
com.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.lang.script.Scriptcom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.lang.script.Script
- Direction
- transaction.smart uses lang.script, so a change to lang.script can break transaction.smart, while a change to transaction.smart can't break lang.script.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→12 transaction.smart uses lang.v1.evaluator.ctx✕
- Connections
- 1 pair of types, where a type in transaction.smart uses a type in lang.v1.evaluator.ctx.
- The types involved
com.wavesplatform.transaction.smart.BlockchainContext→com.wavesplatform.lang.v1.evaluator.ctx.EvaluationContext
- Direction
- transaction.smart uses lang.v1.evaluator.ctx, so a change to lang.v1.evaluator.ctx can break transaction.smart, while a change to transaction.smart can't break lang.v1.evaluator.ctx.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→17 transaction.smart uses lang✕
- Connections
- 1 pair of types, where a type in transaction.smart uses a type in lang.
- The types involved
com.wavesplatform.transaction.smart.Verifier→com.wavesplatform.lang.ValidationError
- Direction
- transaction.smart uses lang, so a change to lang can break transaction.smart, while a change to transaction.smart can't break lang.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→18 transaction.smart uses transaction.TxValidationError✕
- Connections
- 1 pair of types, where a type in transaction.smart uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- transaction.smart uses transaction.TxValidationError, so a change to transaction.TxValidationError can break transaction.smart, while a change to transaction.smart can't break transaction.TxValidationError.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→19 transaction.smart uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in transaction.smart uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- transaction.smart uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break transaction.smart, while a change to transaction.smart can't break transaction.smart.script.trace.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→20 transaction.smart uses state.diffs.invoke✕
- Connections
- 3 pairs of types, where a type in transaction.smart uses a type in state.diffs.invoke.
- The types involved
com.wavesplatform.transaction.smart.AttachedPaymentExtractor→com.wavesplatform.state.diffs.invoke.InvokeScriptLikecom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLikecom.wavesplatform.transaction.smart.InvokeTransaction→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLike
- Direction
- transaction.smart uses state.diffs.invoke, so a change to state.diffs.invoke can break transaction.smart, while a change to transaction.smart can't break state.diffs.invoke.
- Position
- Below the diagonal: transaction.smart uses a module listed above it, which is the healthy direction.
21→22 transaction.smart uses transaction part of a loop✕
- Connections
- 23 pairs of types, where a type in transaction.smart uses a type in transaction.
- The types involved
com.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.smart.InvokeExpressionTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.transaction.Assetcom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.smart.InvokeScriptTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.smart.InvokeTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.smart.InvokeTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.smart.InvokeTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.transaction.TransactionBasecom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.FastHashIdcom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.Proofscom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.ProvenTransactioncom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.transaction.smart.SetScriptTransaction→com.wavesplatform.transaction.TxVersioncom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.Transactioncom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.transaction.TransactionBase
- Direction
- transaction.smart uses transaction, so a change to transaction can break transaction.smart, while a change to transaction.smart can't break transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→23 transaction.smart uses utils part of a loop✕
- Connections
- 1 pair of types, where a type in transaction.smart uses a type in utils.
- The types involved
com.wavesplatform.transaction.smart.Verifier→com.wavesplatform.utils.ScorexLogging
- Direction
- transaction.smart uses utils, so a change to utils can break transaction.smart, while a change to transaction.smart can't break utils.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→30 transaction.smart uses state part of a loop✕
- Connections
- 8 pairs of types, where a type in transaction.smart uses a type in state.
- The types involved
com.wavesplatform.transaction.smart.AttachedPaymentExtractor→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.smart.BlockchainContext→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.smart.DAppEnvironmentInterface→com.wavesplatform.state.StateSnapshotcom.wavesplatform.transaction.smart.RealTransactionWrapper→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.smart.Verifier→com.wavesplatform.state.StateSnapshotcom.wavesplatform.transaction.smart.WavesEnvironment→com.wavesplatform.state.Blockchain
- Direction
- transaction.smart uses state, so a change to state can break transaction.smart, while a change to transaction.smart can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 transaction uses account✕
- Connections
- 18 pairs of types, where a type in transaction uses a type in account.
- The types involved
com.wavesplatform.transaction.AssetAcc→com.wavesplatform.account.Addresscom.wavesplatform.transaction.Authorized→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.CommitToGenerationTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.CreateAliasTransaction→com.wavesplatform.account.Aliascom.wavesplatform.transaction.CreateAliasTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.DataTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.EthTxGenerator→com.wavesplatform.account.Addresscom.wavesplatform.transaction.EthereumTransaction→com.wavesplatform.account.Addresscom.wavesplatform.transaction.EthereumTransaction→com.wavesplatform.account.AddressOrAliascom.wavesplatform.transaction.EthereumTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.GenesisTransaction→com.wavesplatform.account.Addresscom.wavesplatform.transaction.PaymentTransaction→com.wavesplatform.account.Addresscom.wavesplatform.transaction.PaymentTransaction→com.wavesplatform.account.PublicKeycom.wavesplatform.transaction.TransactionFactory→com.wavesplatform.account.KeyPaircom.wavesplatform.transaction.TxHelpers→com.wavesplatform.account.Addresscom.wavesplatform.transaction.TxHelpers→com.wavesplatform.account.AddressOrAliascom.wavesplatform.transaction.TxHelpers→com.wavesplatform.account.KeyPaircom.wavesplatform.transaction.TxHelpers→com.wavesplatform.account.SeedKeyPair
- Direction
- transaction uses account, so a change to account can break transaction, while a change to transaction can't break account.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→2 transaction uses common.state✕
- Connections
- 16 pairs of types, where a type in transaction uses a type in common.state.
- The types involved
com.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.CommitToGenerationTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.CreateAliasTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.DataTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.DiffToLogConverter→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.DiscardedBlock→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.ERC20Address→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.EthereumTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.FastHashId→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.GenesisTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.HasSignature→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.PaymentTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.Proofs→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.ProvenTransaction→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TransactionBase→com.wavesplatform.common.state.ByteStrcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.common.state.ByteStr
- Direction
- transaction uses common.state, so a change to common.state can break transaction, while a change to transaction can't break common.state.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→3 transaction uses lang.directives.values✕
- Connections
- 1 pair of types, where a type in transaction uses a type in lang.directives.values.
- The types involved
com.wavesplatform.transaction.TxHelpers→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- transaction uses lang.directives.values, so a change to lang.directives.values can break transaction, while a change to transaction can't break lang.directives.values.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→5 transaction uses lang.v1.compiler.Terms✕
- Connections
- 2 pairs of types, where a type in transaction uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.transaction.TxHelpers→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL
- Direction
- transaction uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break transaction, while a change to transaction can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→8 transaction uses transaction.Asset✕
- Connections
- 4 pairs of types, where a type in transaction uses a type in transaction.Asset.
- The types involved
com.wavesplatform.transaction.ERC20Address→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.Transaction→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.TransactionBase→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- transaction uses transaction.Asset, so a change to transaction.Asset can break transaction, while a change to transaction can't break transaction.Asset.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→9 transaction uses transaction.assets.exchange✕
- Connections
- 4 pairs of types, where a type in transaction uses a type in transaction.assets.exchange.
- The types involved
com.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.exchange.ExchangeTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.exchange.Ordercom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.exchange.OrderPriceModecom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.exchange.OrderType
- Direction
- transaction uses transaction.assets.exchange, so a change to transaction.assets.exchange can break transaction, while a change to transaction can't break transaction.assets.exchange.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→10 transaction uses lang.script✕
- Connections
- 2 pairs of types, where a type in transaction uses a type in lang.script.
- The types involved
com.wavesplatform.transaction.EthABIConverter→com.wavesplatform.lang.script.Scriptcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.lang.script.Script
- Direction
- transaction uses lang.script, so a change to lang.script can break transaction, while a change to transaction can't break lang.script.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→13 transaction uses transaction.assets✕
- Connections
- 6 pairs of types, where a type in transaction uses a type in transaction.assets.
- The types involved
com.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.BurnTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.IssueTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.ReissueTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.SetAssetScriptTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.SponsorFeeTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.assets.UpdateAssetInfoTransaction
- Direction
- transaction uses transaction.assets, so a change to transaction.assets can break transaction, while a change to transaction can't break transaction.assets.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→17 transaction uses lang✕
- Connections
- 5 pairs of types, where a type in transaction uses a type in lang.
- The types involved
com.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.EthABIConverter→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.RefinedTypeOps→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TransactionFactory→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.transaction.TransactionValidationOps→com.wavesplatform.lang.ValidationError
- Direction
- transaction uses lang, so a change to lang can break transaction, while a change to transaction can't break lang.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→18 transaction uses transaction.TxValidationError✕
- Connections
- 2 pairs of types, where a type in transaction uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.transaction.Proven→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.transaction.Signed→com.wavesplatform.transaction.TxValidationError.InvalidSignature
- Direction
- transaction uses transaction.TxValidationError, so a change to transaction.TxValidationError can break transaction, while a change to transaction can't break transaction.TxValidationError.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→21 transaction uses transaction.smart✕
- Connections
- 3 pairs of types, where a type in transaction uses a type in transaction.smart.
- The types involved
com.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.smart.InvokeExpressionTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.smart.InvokeScriptTransactioncom.wavesplatform.transaction.TxHelpers→com.wavesplatform.transaction.smart.SetScriptTransaction
- Direction
- transaction uses transaction.smart, so a change to transaction.smart can break transaction, while a change to transaction can't break transaction.smart.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
22→30 transaction uses state part of a loop✕
- Connections
- 11 pairs of types, where a type in transaction uses a type in state.
- The types involved
com.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.state.Heightcom.wavesplatform.transaction.CommitToGenerationTransaction→com.wavesplatform.state.Heightcom.wavesplatform.transaction.DataTransaction→com.wavesplatform.state.DataEntrycom.wavesplatform.transaction.DiffToLogConverter→com.wavesplatform.state.StateSnapshotcom.wavesplatform.transaction.EthABIConverter→com.wavesplatform.state.Blockchaincom.wavesplatform.transaction.LastBlockInfo→com.wavesplatform.state.Heightcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.state.DataEntrycom.wavesplatform.transaction.TxHelpers→com.wavesplatform.state.Heightcom.wavesplatform.transaction.TxHelpers→com.wavesplatform.state.TransactionIdcom.wavesplatform.transaction.smart→com.wavesplatform.state.Blockchain
- Direction
- transaction uses state, so a change to state can break transaction, while a change to transaction can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→33 transaction uses block part of a loop✕
- Connections
- 6 pairs of types, where a type in transaction uses a type in block.
- The types involved
com.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.block.Blockcom.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.block.BlockSnapshotcom.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.block.MicroBlockcom.wavesplatform.transaction.BlockchainUpdater→com.wavesplatform.block.MicroBlockSnapshotcom.wavesplatform.transaction.DiscardedBlock→com.wavesplatform.block.Blockcom.wavesplatform.transaction.DiscardedBlock→com.wavesplatform.block.BlockSnapshot
- Direction
- transaction uses block, so a change to block can break transaction, while a change to transaction can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→1 utils uses account✕
- Connections
- 3 pairs of types, where a type in utils uses a type in account.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.account.Addresscom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.account.Aliascom.wavesplatform.utils.UtilApp→com.wavesplatform.account.KeyPair
- Direction
- utils uses account, so a change to account can break utils, while a change to utils can't break account.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
23→2 utils uses common.state✕
- Connections
- 2 pairs of types, where a type in utils uses a type in common.state.
- The types involved
com.wavesplatform.utils.DiffMatchers→com.wavesplatform.common.state.ByteStrcom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.common.state.ByteStr
- Direction
- utils uses common.state, so a change to common.state can break utils, while a change to utils can't break common.state.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
23→8 utils uses transaction.Asset✕
- Connections
- 1 pair of types, where a type in utils uses a type in transaction.Asset.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- utils uses transaction.Asset, so a change to transaction.Asset can break utils, while a change to utils can't break transaction.Asset.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
23→17 utils uses lang✕
- Connections
- 2 pairs of types, where a type in utils uses a type in lang.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.utils.UtilApp→com.wavesplatform.lang.ValidationError
- Direction
- utils uses lang, so a change to lang can break utils, while a change to utils can't break lang.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
23→22 utils uses transaction✕
- Connections
- 3 pairs of types, where a type in utils uses a type in transaction.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.transaction.Transaction
- Direction
- utils uses transaction, so a change to transaction can break utils, while a change to utils can't break transaction.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
23→30 utils uses state part of a loop✕
- Connections
- 13 pairs of types, where a type in utils uses a type in state.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.AssetScriptInfocom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.BalanceSnapshotcom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.Blockchaincom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.ConflictGeneratorscom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.DataEntrycom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.GenerationPeriodcom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.Heightcom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.LeaseBalancecom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.LeaseDetailscom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.TxMetacom.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.state.VolumeAndFee
- Direction
- utils uses state, so a change to state can break utils, while a change to utils can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→32 utils uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in settings.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.settings.BlockchainSettings
- Direction
- utils uses settings, so a change to settings can break utils, while a change to utils can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→33 utils uses block part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in block.
- The types involved
com.wavesplatform.utils.EmptyBlockchain→com.wavesplatform.block.SignedBlockHeader
- Direction
- utils uses block, so a change to block can break utils, while a change to utils can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→2 events uses common.state✕
- Connections
- 9 pairs of types, where a type in events uses a type in common.state.
- The types involved
com.wavesplatform.events.BlockAppended→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.BlockchainUpdateTriggers→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.BlockchainUpdated→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.BlockchainUpdates→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.MicroBlockAppended→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.MicroBlockRollbackCompleted→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.Repo→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.RollbackCompleted→com.wavesplatform.common.state.ByteStrcom.wavesplatform.events.RollbackResult→com.wavesplatform.common.state.ByteStr
- Direction
- events uses common.state, so a change to common.state can break events, while a change to events can't break common.state.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
24→23 events uses utils✕
- Connections
- 4 pairs of types, where a type in events uses a type in utils.
- The types involved
com.wavesplatform.events.BlockchainUpdates→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.events.Handler→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.events.Loader→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.events.Repo→com.wavesplatform.utils.ScorexLogging
- Direction
- events uses utils, so a change to utils can break events, while a change to events can't break utils.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
24→27 events uses database part of a loop✕
- Connections
- 1 pair of types, where a type in events uses a type in database.
- The types involved
com.wavesplatform.events.Loader→com.wavesplatform.database.DBResource
- Direction
- events uses database, so a change to database can break events, while a change to events can't break database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→30 events uses state part of a loop✕
- Connections
- 12 pairs of types, where a type in events uses a type in state.
- The types involved
com.wavesplatform.events.BlockAppended→com.wavesplatform.state.AssetInfocom.wavesplatform.events.BlockchainUpdateTriggers→com.wavesplatform.state.Blockchaincom.wavesplatform.events.BlockchainUpdateTriggers→com.wavesplatform.state.StateSnapshotcom.wavesplatform.events.BlockchainUpdates→com.wavesplatform.state.Blockchaincom.wavesplatform.events.BlockchainUpdates→com.wavesplatform.state.StateSnapshotcom.wavesplatform.events.Loader→com.wavesplatform.state.Heightcom.wavesplatform.events.MicroBlockAppended→com.wavesplatform.state.AssetInfocom.wavesplatform.events.MicroBlockRollbackCompleted→com.wavesplatform.state.AssetInfocom.wavesplatform.events.Repo→com.wavesplatform.state.Blockchaincom.wavesplatform.events.Repo→com.wavesplatform.state.Heightcom.wavesplatform.events.Repo→com.wavesplatform.state.StateSnapshotcom.wavesplatform.events.RollbackCompleted→com.wavesplatform.state.AssetInfo
- Direction
- events uses state, so a change to state can break events, while a change to events can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→33 events uses block part of a loop✕
- Connections
- 9 pairs of types, where a type in events uses a type in block.
- The types involved
com.wavesplatform.events.BlockAppended→com.wavesplatform.block.Blockcom.wavesplatform.events.BlockchainUpdateTriggers→com.wavesplatform.block.Blockcom.wavesplatform.events.BlockchainUpdateTriggers→com.wavesplatform.block.MicroBlockcom.wavesplatform.events.BlockchainUpdates→com.wavesplatform.block.Blockcom.wavesplatform.events.BlockchainUpdates→com.wavesplatform.block.MicroBlockcom.wavesplatform.events.MicroBlockAppended→com.wavesplatform.block.MicroBlockcom.wavesplatform.events.Repo→com.wavesplatform.block.Blockcom.wavesplatform.events.Repo→com.wavesplatform.block.MicroBlockcom.wavesplatform.events.RollbackResult→com.wavesplatform.block.Block
- Direction
- events uses block, so a change to block can break events, while a change to events can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 mining uses account✕
- Connections
- 5 pairs of types, where a type in mining uses a type in account.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.account.Addresscom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.account.Addresscom.wavesplatform.mining.MinerDebugInfo→com.wavesplatform.account.KeyPaircom.wavesplatform.mining.MinerImpl→com.wavesplatform.account.Addresscom.wavesplatform.mining.MinerImpl→com.wavesplatform.account.KeyPair
- Direction
- mining uses account, so a change to account can break mining, while a change to mining can't break account.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→2 mining uses common.state✕
- Connections
- 3 pairs of types, where a type in mining uses a type in common.state.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.common.state.ByteStrcom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.common.state.ByteStrcom.wavesplatform.mining.MinerImpl→com.wavesplatform.common.state.ByteStr
- Direction
- mining uses common.state, so a change to common.state can break mining, while a change to mining can't break common.state.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→17 mining uses lang✕
- Connections
- 2 pairs of types, where a type in mining uses a type in lang.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.lang.ValidationError
- Direction
- mining uses lang, so a change to lang can break mining, while a change to mining can't break lang.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→18 mining uses transaction.TxValidationError✕
- Connections
- 2 pairs of types, where a type in mining uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- mining uses transaction.TxValidationError, so a change to transaction.TxValidationError can break mining, while a change to mining can't break transaction.TxValidationError.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→22 mining uses transaction✕
- Connections
- 5 pairs of types, where a type in mining uses a type in transaction.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.transaction.Transactioncom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.transaction.Transactioncom.wavesplatform.mining.MiningConstraint→com.wavesplatform.transaction.Transactioncom.wavesplatform.mining.MultiDimensionalMiningConstraint→com.wavesplatform.transaction.Transactioncom.wavesplatform.mining.OneDimensionalMiningConstraint→com.wavesplatform.transaction.Transaction
- Direction
- mining uses transaction, so a change to transaction can break mining, while a change to mining can't break transaction.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→23 mining uses utils✕
- Connections
- 2 pairs of types, where a type in mining uses a type in utils.
- The types involved
com.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.mining.MinerImpl→com.wavesplatform.utils.ScorexLogging
- Direction
- mining uses utils, so a change to utils can break mining, while a change to mining can't break utils.
- Position
- Below the diagonal: mining uses a module listed above it, which is the healthy direction.
25→30 mining uses state part of a loop✕
- Connections
- 9 pairs of types, where a type in mining uses a type in state.
- The types involved
com.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.Miner→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.MinerImpl→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.MiningConstraint→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.MiningConstraint→com.wavesplatform.state.StateSnapshotcom.wavesplatform.mining.MultiDimensionalMiningConstraint→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.MultiDimensionalMiningConstraint→com.wavesplatform.state.StateSnapshotcom.wavesplatform.mining.OneDimensionalMiningConstraint→com.wavesplatform.state.Blockchaincom.wavesplatform.mining.OneDimensionalMiningConstraint→com.wavesplatform.state.StateSnapshot
- Direction
- mining uses state, so a change to state can break mining, while a change to mining can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 mining uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in mining uses a type in settings.
- The types involved
com.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.settings.WavesSettings
- Direction
- mining uses settings, so a change to settings can break mining, while a change to mining can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→33 mining uses block part of a loop✕
- Connections
- 4 pairs of types, where a type in mining uses a type in block.
- The types involved
com.wavesplatform.mining.BlockChallenger→com.wavesplatform.block.Blockcom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.block.Blockcom.wavesplatform.mining.BlockChallengerImpl→com.wavesplatform.block.FinalizationVotingcom.wavesplatform.mining.MinerImpl→com.wavesplatform.block.Block
- Direction
- mining uses block, so a change to block can break mining, while a change to mining can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→1 network uses account✕
- Connections
- 1 pair of types, where a type in network uses a type in account.
- The types involved
com.wavesplatform.network.MicroBlockInv→com.wavesplatform.account.PublicKey
- Direction
- network uses account, so a change to account can break network, while a change to network can't break account.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→2 network uses common.state✕
- Connections
- 12 pairs of types, where a type in network uses a type in common.state.
- The types involved
com.wavesplatform.network.EndorseBlock→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.GetBlock→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.GetSignatures→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.GetSignaturesSpec→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.InvalidBlockStorage→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.InvalidBlockStorageImpl→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.MicroBlockInv→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.MicroBlockRequest→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.MicroBlockSynchronizer→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.RxExtensionLoader→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.Signatures→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network.TransactionSynchronizer→com.wavesplatform.common.state.ByteStr
- Direction
- network uses common.state, so a change to common.state can break network, while a change to network can't break common.state.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→17 network uses lang✕
- Connections
- 3 pairs of types, where a type in network uses a type in lang.
- The types involved
com.wavesplatform.network.InvalidBlockStorage→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.network.InvalidBlockStorageImpl→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.network.TransactionPublisher→com.wavesplatform.lang.ValidationError
- Direction
- network uses lang, so a change to lang can break network, while a change to network can't break lang.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→19 network uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in network uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.network.TransactionPublisher→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- network uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break network, while a change to network can't break transaction.smart.script.trace.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→22 network uses transaction✕
- Connections
- 6 pairs of types, where a type in network uses a type in transaction.
- The types involved
com.wavesplatform.network.MessageObserver→com.wavesplatform.transaction.Transactioncom.wavesplatform.network.MicroBlockInv→com.wavesplatform.transaction.Signedcom.wavesplatform.network.NetworkServerL1→com.wavesplatform.transaction.LastBlockInfocom.wavesplatform.network.PBTransactionSpec→com.wavesplatform.transaction.Transactioncom.wavesplatform.network.TransactionPublisher→com.wavesplatform.transaction.Transactioncom.wavesplatform.network.TransactionSpec→com.wavesplatform.transaction.Transaction
- Direction
- network uses transaction, so a change to transaction can break network, while a change to network can't break transaction.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→23 network uses utils✕
- Connections
- 17 pairs of types, where a type in network uses a type in utils.
- The types involved
com.wavesplatform.network.BrokenConnectionDetector→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.DiscardingHandler→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.FatalErrorHandler→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.HandshakeDecoder→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.HandshakeHandler→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.HandshakeTimeoutHandler→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.HistoryReplier→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.InboundConnectionFilter→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.LegacyFrameCodec→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.MessageCodec→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.MicroBlockSynchronizer→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.PeerDatabaseImpl→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.PeerSynchronizer→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.RxExtensionLoader→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.RxScoreObserver→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.UPnP→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.network.WriteErrorHandler→com.wavesplatform.utils.ScorexLogging
- Direction
- network uses utils, so a change to utils can break network, while a change to network can't break utils.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
26→30 network uses state part of a loop✕
- Connections
- 1 pair of types, where a type in network uses a type in state.
- The types involved
com.wavesplatform.network.EndorseBlock→com.wavesplatform.state.Height
- Direction
- network uses state, so a change to state can break network, while a change to network can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→32 network uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in network uses a type in settings.
- The types involved
com.wavesplatform.network.NetworkServerL1→com.wavesplatform.settings.WavesSettings
- Direction
- network uses settings, so a change to settings can break network, while a change to network can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→33 network uses block part of a loop✕
- Connections
- 6 pairs of types, where a type in network uses a type in block.
- The types involved
com.wavesplatform.network.BlockForged→com.wavesplatform.block.Blockcom.wavesplatform.network.BlockSpec→com.wavesplatform.block.Blockcom.wavesplatform.network.ExtensionBlocks→com.wavesplatform.block.Blockcom.wavesplatform.network.MessageObserver→com.wavesplatform.block.Blockcom.wavesplatform.network.MicroBlockResponse→com.wavesplatform.block.MicroBlockcom.wavesplatform.network.PBBlockSpec→com.wavesplatform.block.Block
- Direction
- network uses block, so a change to block can break network, while a change to network can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 database uses account✕
- Connections
- 4 pairs of types, where a type in database uses a type in account.
- The types involved
com.wavesplatform.database.Caches→com.wavesplatform.account.Addresscom.wavesplatform.database.Caches→com.wavesplatform.account.Aliascom.wavesplatform.database.Keys→com.wavesplatform.account.Addresscom.wavesplatform.database.Keys→com.wavesplatform.account.Alias
- Direction
- database uses account, so a change to account can break database, while a change to database can't break account.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→2 database uses common.state✕
- Connections
- 5 pairs of types, where a type in database uses a type in common.state.
- The types involved
com.wavesplatform.database.ByteArrayDataInputExt→com.wavesplatform.common.state.ByteStrcom.wavesplatform.database.ByteArrayDataOutputExt→com.wavesplatform.common.state.ByteStrcom.wavesplatform.database.Caches→com.wavesplatform.common.state.ByteStrcom.wavesplatform.database.Keys→com.wavesplatform.common.state.ByteStrcom.wavesplatform.database.Storage→com.wavesplatform.common.state.ByteStr
- Direction
- database uses common.state, so a change to common.state can break database, while a change to database can't break common.state.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→8 database uses transaction.Asset✕
- Connections
- 2 pairs of types, where a type in database uses a type in transaction.Asset.
- The types involved
com.wavesplatform.database.Caches→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.database.Keys→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- database uses transaction.Asset, so a change to transaction.Asset can break database, while a change to database can't break transaction.Asset.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→22 database uses transaction✕
- Connections
- 3 pairs of types, where a type in database uses a type in transaction.
- The types involved
com.wavesplatform.database.Caches→com.wavesplatform.transaction.Assetcom.wavesplatform.database.Caches→com.wavesplatform.transaction.Transactioncom.wavesplatform.database.Keys→com.wavesplatform.transaction.ERC20Address
- Direction
- database uses transaction, so a change to transaction can break database, while a change to database can't break transaction.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→23 database uses utils✕
- Connections
- 2 pairs of types, where a type in database uses a type in utils.
- The types involved
com.wavesplatform.database.RocksDBWriter→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.database.TestStorageFactory→com.wavesplatform.utils.Time
- Direction
- database uses utils, so a change to utils can break database, while a change to database can't break utils.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→24 database uses events✕
- Connections
- 1 pair of types, where a type in database uses a type in events.
- The types involved
com.wavesplatform.database.TestStorageFactory→com.wavesplatform.events.BlockchainUpdateTriggers
- Direction
- database uses events, so a change to events can break database, while a change to database can't break events.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
27→30 database uses state part of a loop✕
- Connections
- 40 pairs of types, where a type in database uses a type in state. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.wavesplatform.database.BalanceNode→com.wavesplatform.state.Heightcom.wavesplatform.database.Caches→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.database.Caches→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.database.Caches→com.wavesplatform.state.AssetScriptInfocom.wavesplatform.database.Caches→com.wavesplatform.state.Blockchaincom.wavesplatform.database.Caches→com.wavesplatform.state.ConflictGeneratorscom.wavesplatform.database.Caches→com.wavesplatform.state.DataEntrycom.wavesplatform.database.Caches→com.wavesplatform.state.GenerationPeriodcom.wavesplatform.database.Caches→com.wavesplatform.state.GeneratorIndexcom.wavesplatform.database.Caches→com.wavesplatform.state.Heightcom.wavesplatform.database.Caches→com.wavesplatform.state.LeaseBalancecom.wavesplatform.database.Caches→com.wavesplatform.state.StateSnapshotcom.wavesplatform.database.Caches→com.wavesplatform.state.TransactionIdcom.wavesplatform.database.Caches→com.wavesplatform.state.VolumeAndFeecom.wavesplatform.database.CurrentBalance→com.wavesplatform.state.Heightcom.wavesplatform.database.CurrentData→com.wavesplatform.state.DataEntrycom.wavesplatform.database.CurrentData→com.wavesplatform.state.Heightcom.wavesplatform.database.CurrentLeaseBalance→com.wavesplatform.state.Heightcom.wavesplatform.database.CurrentVolumeAndFee→com.wavesplatform.state.Heightcom.wavesplatform.database.DataNode→com.wavesplatform.state.DataEntrycom.wavesplatform.database.DataNode→com.wavesplatform.state.Heightcom.wavesplatform.database.KeyHelpers→com.wavesplatform.state.Heightcom.wavesplatform.database.KeyHelpers→com.wavesplatform.state.TxNumcom.wavesplatform.database.Keys→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.database.Keys→com.wavesplatform.state.AssetScriptInfo
- Direction
- database uses state, so a change to state can break database, while a change to database can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→32 database uses settings part of a loop✕
- Connections
- 4 pairs of types, where a type in database uses a type in settings.
- The types involved
com.wavesplatform.database.Caches→com.wavesplatform.settings.DBSettingscom.wavesplatform.database.RocksDBWriter→com.wavesplatform.settings.BlockchainSettingscom.wavesplatform.database.RocksDBWriter→com.wavesplatform.settings.DBSettingscom.wavesplatform.database.TestStorageFactory→com.wavesplatform.settings.WavesSettings
- Direction
- database uses settings, so a change to settings can break database, while a change to database can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→33 database uses block part of a loop✕
- Connections
- 3 pairs of types, where a type in database uses a type in block.
- The types involved
com.wavesplatform.database.Caches→com.wavesplatform.block.Blockcom.wavesplatform.database.Caches→com.wavesplatform.block.SignedBlockHeadercom.wavesplatform.database.Storage→com.wavesplatform.block.Block
- Direction
- database uses block, so a change to block can break database, while a change to database can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→1 utx uses account✕
- Connections
- 1 pair of types, where a type in utx uses a type in account.
- The types involved
com.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.account.Address
- Direction
- utx uses account, so a change to account can break utx, while a change to utx can't break account.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→2 utx uses common.state✕
- Connections
- 3 pairs of types, where a type in utx uses a type in common.state.
- The types involved
com.wavesplatform.utx.UtxPool→com.wavesplatform.common.state.ByteStrcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.common.state.ByteStrcom.wavesplatform.utx.UtxPriorityPool→com.wavesplatform.common.state.ByteStr
- Direction
- utx uses common.state, so a change to common.state can break utx, while a change to utx can't break common.state.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→17 utx uses lang✕
- Connections
- 2 pairs of types, where a type in utx uses a type in lang.
- The types involved
com.wavesplatform.utx.UtxPool→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.lang.ValidationError
- Direction
- utx uses lang, so a change to lang can break utx, while a change to utx can't break lang.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→19 utx uses transaction.smart.script.trace✕
- Connections
- 2 pairs of types, where a type in utx uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.utx.UtxPool→com.wavesplatform.transaction.smart.script.trace.TracedResultcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- utx uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break utx, while a change to utx can't break transaction.smart.script.trace.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→22 utx uses transaction✕
- Connections
- 3 pairs of types, where a type in utx uses a type in transaction.
- The types involved
com.wavesplatform.utx.UtxPool→com.wavesplatform.transaction.Transactioncom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.transaction.Transactioncom.wavesplatform.utx.UtxPriorityPool→com.wavesplatform.transaction.Transaction
- Direction
- utx uses transaction, so a change to transaction can break utx, while a change to utx can't break transaction.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→23 utx uses utils✕
- Connections
- 2 pairs of types, where a type in utx uses a type in utils.
- The types involved
com.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.utils.Time
- Direction
- utx uses utils, so a change to utils can break utx, while a change to utx can't break utils.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→24 utx uses events✕
- Connections
- 1 pair of types, where a type in utx uses a type in events.
- The types involved
com.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.events.UtxEvent
- Direction
- utx uses events, so a change to events can break utx, while a change to utx can't break events.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→25 utx uses mining✕
- Connections
- 2 pairs of types, where a type in utx uses a type in mining.
- The types involved
com.wavesplatform.utx.UtxPool→com.wavesplatform.mining.MultiDimensionalMiningConstraintcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.mining.MultiDimensionalMiningConstraint
- Direction
- utx uses mining, so a change to mining can break utx, while a change to utx can't break mining.
- Position
- Below the diagonal: utx uses a module listed above it, which is the healthy direction.
28→30 utx uses state part of a loop✕
- Connections
- 4 pairs of types, where a type in utx uses a type in state.
- The types involved
com.wavesplatform.utx.UtxForAppender→com.wavesplatform.state.StateSnapshotcom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.state.Blockchaincom.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.state.StateSnapshotcom.wavesplatform.utx.UtxPriorityPool→com.wavesplatform.state.StateSnapshot
- Direction
- utx uses state, so a change to state can break utx, while a change to utx can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→32 utx uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in utx uses a type in settings.
- The types involved
com.wavesplatform.utx.UtxPoolImpl→com.wavesplatform.settings.UtxSettings
- Direction
- utx uses settings, so a change to settings can break utx, while a change to utx can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 api uses account✕
- Connections
- 8 pairs of types, where a type in api uses a type in account.
- The types involved
com.wavesplatform.api.BlockchainApi→com.wavesplatform.account.Addresscom.wavesplatform.api.BlockchainApi→com.wavesplatform.account.Aliascom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.account.Addresscom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.account.Aliascom.wavesplatform.api.RideMulticastHttpApi→com.wavesplatform.account.Addresscom.wavesplatform.api.common→com.wavesplatform.account.Addresscom.wavesplatform.api.http→com.wavesplatform.account.Addresscom.wavesplatform.api.http→com.wavesplatform.account.PublicKey
- Direction
- api uses account, so a change to account can break api, while a change to api can't break account.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→2 api uses common.state✕
- Connections
- 3 pairs of types, where a type in api uses a type in common.state.
- The types involved
com.wavesplatform.api.BlockMeta→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.common→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.http→com.wavesplatform.common.state.ByteStr
- Direction
- api uses common.state, so a change to common.state can break api, while a change to api can't break common.state.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→8 api uses transaction.Asset✕
- Connections
- 1 pair of types, where a type in api uses a type in transaction.Asset.
- The types involved
com.wavesplatform.api.http→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- api uses transaction.Asset, so a change to transaction.Asset can break api, while a change to api can't break transaction.Asset.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→22 api uses transaction✕
- Connections
- 4 pairs of types, where a type in api uses a type in transaction.
- The types involved
com.wavesplatform.api.BlockchainApi→com.wavesplatform.transaction.Assetcom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.transaction.Assetcom.wavesplatform.api.common→com.wavesplatform.transaction.Assetcom.wavesplatform.api.http→com.wavesplatform.transaction.Transaction
- Direction
- api uses transaction, so a change to transaction can break api, while a change to api can't break transaction.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→23 api uses utils✕
- Connections
- 3 pairs of types, where a type in api uses a type in utils.
- The types involved
com.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.GrpcConnector→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.RideMulticastHttpApi→com.wavesplatform.utils.ScorexLogging
- Direction
- api uses utils, so a change to utils can break api, while a change to api can't break utils.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→27 api uses database✕
- Connections
- 1 pair of types, where a type in api uses a type in database.
- The types involved
com.wavesplatform.api.common→com.wavesplatform.database.RDB
- Direction
- api uses database, so a change to database can break api, while a change to api can't break database.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
29→30 api uses state part of a loop✕
- Connections
- 8 pairs of types, where a type in api uses a type in state.
- The types involved
com.wavesplatform.api.BlockchainApi→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.api.BlockchainApi→com.wavesplatform.state.DataEntrycom.wavesplatform.api.BlockchainApi→com.wavesplatform.state.Heightcom.wavesplatform.api.BlockchainApi→com.wavesplatform.state.TransactionIdcom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.state.DataEntrycom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.state.Heightcom.wavesplatform.api.DefaultBlockchainApi→com.wavesplatform.state.TransactionId
- Direction
- api uses state, so a change to state can break api, while a change to api can't break state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 api uses block part of a loop✕
- Connections
- 2 pairs of types, where a type in api uses a type in block.
- The types involved
com.wavesplatform.api.BlockMeta→com.wavesplatform.block.BlockHeadercom.wavesplatform.api.BlockMeta→com.wavesplatform.block.SignedBlockHeader
- Direction
- api uses block, so a change to block can break api, while a change to api can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 state uses account✕
- Connections
- 23 pairs of types, where a type in state uses a type in account.
- The types involved
com.wavesplatform.state.AccountScriptInfo→com.wavesplatform.account.PublicKeycom.wavesplatform.state.AssetDescription→com.wavesplatform.account.PublicKeycom.wavesplatform.state.AssetStaticInfo→com.wavesplatform.account.PublicKeycom.wavesplatform.state.BlockRewardCalculator→com.wavesplatform.account.Addresscom.wavesplatform.state.Blockchain→com.wavesplatform.account.Addresscom.wavesplatform.state.Blockchain→com.wavesplatform.account.Aliascom.wavesplatform.state.BlockchainOverrides→com.wavesplatform.account.Addresscom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.account.Addresscom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.account.Aliascom.wavesplatform.state.FinalizationState→com.wavesplatform.account.Addresscom.wavesplatform.state.GeneratorInfo→com.wavesplatform.account.Addresscom.wavesplatform.state.LeaseStaticInfo→com.wavesplatform.account.Addresscom.wavesplatform.state.LeaseStaticInfo→com.wavesplatform.account.PublicKeycom.wavesplatform.state.NewTransactionInfo→com.wavesplatform.account.Addresscom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.account.Addresscom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.account.Aliascom.wavesplatform.state.StateSnapshot→com.wavesplatform.account.Addresscom.wavesplatform.state.StateSnapshot→com.wavesplatform.account.Aliascom.wavesplatform.state.StateSnapshot→com.wavesplatform.account.PublicKeycom.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.account.KeyPaircom.wavesplatform.state.appender→com.wavesplatform.account.Addresscom.wavesplatform.state.patch→com.wavesplatform.account.Addresscom.wavesplatform.state.utils→com.wavesplatform.account.Address
- Direction
- state uses account, so a change to account can break state, while a change to state can't break account.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→2 state uses common.state✕
- Connections
- 13 pairs of types, where a type in state uses a type in common.state.
- The types involved
com.wavesplatform.state.AssetStaticInfo→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.BinaryDataEntry→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.BlockMinerInfo→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.Blockchain→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.StateHash→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.StateHashBuilder→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.StateSnapshot→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.TransactionId→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.appender→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.utils→com.wavesplatform.common.state.ByteStr
- Direction
- state uses common.state, so a change to common.state can break state, while a change to state can't break common.state.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→7 state uses lang.v1.traits.domain✕
- Connections
- 6 pairs of types, where a type in state uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.Burncom.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.Issuecom.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.Leasecom.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.LeaseCancelcom.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.Reissuecom.wavesplatform.state.InvokeScriptResult→com.wavesplatform.lang.v1.traits.domain.SponsorFee
- Direction
- state uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break state, while a change to state can't break lang.v1.traits.domain.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→8 state uses transaction.Asset✕
- Connections
- 5 pairs of types, where a type in state uses a type in transaction.Asset.
- The types involved
com.wavesplatform.state.Blockchain→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.state.Portfolio→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.state.StateSnapshot→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- state uses transaction.Asset, so a change to transaction.Asset can break state, while a change to state can't break transaction.Asset.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→10 state uses lang.script✕
- Connections
- 2 pairs of types, where a type in state uses a type in lang.script.
- The types involved
com.wavesplatform.state.AccountScriptInfo→com.wavesplatform.lang.script.Scriptcom.wavesplatform.state.AssetScriptInfo→com.wavesplatform.lang.script.Script
- Direction
- state uses lang.script, so a change to lang.script can break state, while a change to state can't break lang.script.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→17 state uses lang✕
- Connections
- 5 pairs of types, where a type in state uses a type in lang.
- The types involved
com.wavesplatform.state.Blockchain→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.appender→com.wavesplatform.lang.ValidationError
- Direction
- state uses lang, so a change to lang can break state, while a change to state can't break lang.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→19 state uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in state uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- state uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break state, while a change to state can't break transaction.smart.script.trace.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→22 state uses transaction✕
- Connections
- 26 pairs of types, where a type in state uses a type in transaction. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.wavesplatform.state.BinaryDataEntry→com.wavesplatform.transaction.TxVersioncom.wavesplatform.state.Blockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.state.Blockchain→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.state.Blockchain→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.BlockchainOverrides→com.wavesplatform.transaction.Assetcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.Assetcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.BlockchainUpdatercom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.LastBlockInfocom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.DataEntry→com.wavesplatform.transaction.TxVersioncom.wavesplatform.state.EmptyDataEntry→com.wavesplatform.transaction.TxVersioncom.wavesplatform.state.ForwardingBlockchainUpdaterImpl→com.wavesplatform.transaction.BlockchainUpdatercom.wavesplatform.state.LeaseStaticInfo→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.state.NewTransactionInfo→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.ParSignatureChecker→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.Portfolio→com.wavesplatform.transaction.Assetcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.StateSnapshot→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.state.StateSnapshot→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.StringDataEntry→com.wavesplatform.transaction.TxVersioncom.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.transaction.GenesisTransactioncom.wavesplatform.state.TxStateSnapshotHashBuilder→com.wavesplatform.transaction.Transaction
- Direction
- state uses transaction, so a change to transaction can break state, while a change to state can't break transaction.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→23 state uses utils✕
- Connections
- 2 pairs of types, where a type in state uses a type in utils.
- The types involved
com.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.state.appender→com.wavesplatform.utils.Time
- Direction
- state uses utils, so a change to utils can break state, while a change to state can't break utils.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→25 state uses mining✕
- Connections
- 1 pair of types, where a type in state uses a type in mining.
- The types involved
com.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.mining.MiningConstraint
- Direction
- state uses mining, so a change to mining can break state, while a change to state can't break mining.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→26 state uses network✕
- Connections
- 2 pairs of types, where a type in state uses a type in network.
- The types involved
com.wavesplatform.state.EndorsementStorage→com.wavesplatform.network.EndorseBlockcom.wavesplatform.state.appender→com.wavesplatform.network.BlockSnapshotResponse
- Direction
- state uses network, so a change to network can break state, while a change to state can't break network.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→27 state uses database✕
- Connections
- 2 pairs of types, where a type in state uses a type in database.
- The types involved
com.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.database.RocksDBWritercom.wavesplatform.state.utils→com.wavesplatform.database.RDB
- Direction
- state uses database, so a change to database can break state, while a change to state can't break database.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→28 state uses utx✕
- Connections
- 1 pair of types, where a type in state uses a type in utx.
- The types involved
com.wavesplatform.state.appender→com.wavesplatform.utx.UtxPool
- Direction
- state uses utx, so a change to utx can break state, while a change to state can't break utx.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→29 state uses api✕
- Connections
- 2 pairs of types, where a type in state uses a type in api.
- The types involved
com.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.api.BlockMetacom.wavesplatform.state.NG→com.wavesplatform.api.BlockMeta
- Direction
- state uses api, so a change to api can break state, while a change to state can't break api.
- Position
- Below the diagonal: state uses a module listed above it, which is the healthy direction.
30→32 state uses settings part of a loop✕
- Connections
- 3 pairs of types, where a type in state uses a type in settings.
- The types involved
com.wavesplatform.state.Blockchain→com.wavesplatform.settings.BlockchainSettingscom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.settings.BlockchainSettingscom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.settings.BlockchainSettings
- Direction
- state uses settings, so a change to settings can break state, while a change to state can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→33 state uses block part of a loop✕
- Connections
- 15 pairs of types, where a type in state uses a type in block.
- The types involved
com.wavesplatform.state.Blockchain→com.wavesplatform.block.SignedBlockHeadercom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.block.Blockcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.block.BlockSnapshotcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.block.MicroBlockcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.block.MicroBlockSnapshotcom.wavesplatform.state.BlockchainUpdaterImpl→com.wavesplatform.block.SignedBlockHeadercom.wavesplatform.state.EndorsementStorage→com.wavesplatform.block.FinalizationVotingcom.wavesplatform.state.FinalizationState→com.wavesplatform.block.FinalizationVotingcom.wavesplatform.state.NG→com.wavesplatform.block.Blockcom.wavesplatform.state.NG→com.wavesplatform.block.MicroBlockcom.wavesplatform.state.ParSignatureChecker→com.wavesplatform.block.Blockcom.wavesplatform.state.SnapshotBlockchain→com.wavesplatform.block.SignedBlockHeadercom.wavesplatform.state.appender→com.wavesplatform.block.Blockcom.wavesplatform.state.appender→com.wavesplatform.block.BlockEndorsementcom.wavesplatform.state.appender→com.wavesplatform.block.BlockSnapshot
- Direction
- state uses block, so a change to block can break state, while a change to state can't break block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→1 api.common uses account✕
- Connections
- 7 pairs of types, where a type in api.common uses a type in account.
- The types involved
com.wavesplatform.api.common.AddressPortfolio→com.wavesplatform.account.Addresscom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.account.Addresscom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.account.Addresscom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.account.Aliascom.wavesplatform.api.common.CommonAssetsApi→com.wavesplatform.account.Addresscom.wavesplatform.api.common.CommonBlocksApi→com.wavesplatform.account.Addresscom.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.account.Address
- Direction
- api.common uses account, so a change to account can break api.common, while a change to api.common can't break account.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→2 api.common uses common.state✕
- Connections
- 5 pairs of types, where a type in api.common uses a type in common.state.
- The types involved
com.wavesplatform.api.common.AddressTransactions→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.common.CommonBlocksApi→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.common.LeaseInfo→com.wavesplatform.common.state.ByteStr
- Direction
- api.common uses common.state, so a change to common.state can break api.common, while a change to api.common can't break common.state.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→8 api.common uses transaction.Asset✕
- Connections
- 3 pairs of types, where a type in api.common uses a type in transaction.Asset.
- The types involved
com.wavesplatform.api.common.AddressPortfolio→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.api.common.CommonAssetsApi→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- api.common uses transaction.Asset, so a change to transaction.Asset can break api.common, while a change to api.common can't break transaction.Asset.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→17 api.common uses lang✕
- Connections
- 2 pairs of types, where a type in api.common uses a type in lang.
- The types involved
com.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.lang.ValidationError
- Direction
- api.common uses lang, so a change to lang can break api.common, while a change to api.common can't break lang.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→19 api.common uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in api.common uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- api.common uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break api.common, while a change to api.common can't break transaction.smart.script.trace.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→22 api.common uses transaction✕
- Connections
- 3 pairs of types, where a type in api.common uses a type in transaction.
- The types involved
com.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.transaction.Transactioncom.wavesplatform.api.common.CommonTransactionsApi→com.wavesplatform.transaction.TransactionTypecom.wavesplatform.api.common.TransactionMeta→com.wavesplatform.transaction.Transaction
- Direction
- api.common uses transaction, so a change to transaction can break api.common, while a change to api.common can't break transaction.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→27 api.common uses database✕
- Connections
- 4 pairs of types, where a type in api.common uses a type in database.
- The types involved
com.wavesplatform.api.common.AddressPortfolio→com.wavesplatform.database.DBResourcecom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.database.DBResourcecom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.database.Keycom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.database.RDB
- Direction
- api.common uses database, so a change to database can break api.common, while a change to api.common can't break database.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→29 api.common uses api✕
- Connections
- 1 pair of types, where a type in api.common uses a type in api.
- The types involved
com.wavesplatform.api.common.CommonBlocksApi→com.wavesplatform.api.BlockMeta
- Direction
- api.common uses api, so a change to api can break api.common, while a change to api.common can't break api.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
31→30 api.common uses state✕
- Connections
- 11 pairs of types, where a type in api.common uses a type in state.
- The types involved
com.wavesplatform.api.common.AddressPortfolio→com.wavesplatform.state.StateSnapshotcom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.state.Heightcom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.state.InvokeScriptResultcom.wavesplatform.api.common.AddressTransactions→com.wavesplatform.state.TxNumcom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.api.common.CommonAccountsApi→com.wavesplatform.state.DataEntrycom.wavesplatform.api.common.CommonAssetsApi→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.api.common.CommonBlocksApi→com.wavesplatform.state.Heightcom.wavesplatform.api.common.CommonGeneratorsApi→com.wavesplatform.state.Heightcom.wavesplatform.api.common.LeaseInfo→com.wavesplatform.state.LeaseDetailscom.wavesplatform.api.common.TransactionMeta→com.wavesplatform.state.Height
- Direction
- api.common uses state, so a change to state can break api.common, while a change to api.common can't break state.
- Position
- Below the diagonal: api.common uses a module listed above it, which is the healthy direction.
32→1 settings uses account✕
- Connections
- 2 pairs of types, where a type in settings uses a type in account.
- The types involved
com.wavesplatform.settings.FunctionalitySettings→com.wavesplatform.account.Addresscom.wavesplatform.settings.MinerSettings→com.wavesplatform.account.PrivateKey
- Direction
- settings uses account, so a change to account can break settings, while a change to settings can't break account.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
32→2 settings uses common.state✕
- Connections
- 2 pairs of types, where a type in settings uses a type in common.state.
- The types involved
com.wavesplatform.settings.GenesisSettings→com.wavesplatform.common.state.ByteStrcom.wavesplatform.settings.WalletSettings→com.wavesplatform.common.state.ByteStr
- Direction
- settings uses common.state, so a change to common.state can break settings, while a change to settings can't break common.state.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
32→30 settings uses state✕
- Connections
- 1 pair of types, where a type in settings uses a type in state.
- The types involved
com.wavesplatform.settings.RewardsSettings→com.wavesplatform.state.Height
- Direction
- settings uses state, so a change to state can break settings, while a change to settings can't break state.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
33→1 block uses account✕
- Connections
- 6 pairs of types, where a type in block uses a type in account.
- The types involved
com.wavesplatform.block.Block→com.wavesplatform.account.PublicKeycom.wavesplatform.block.BlockHeader→com.wavesplatform.account.PublicKeycom.wavesplatform.block.BlockSignOps→com.wavesplatform.account.PrivateKeycom.wavesplatform.block.ChallengedHeader→com.wavesplatform.account.PublicKeycom.wavesplatform.block.MicroBlock→com.wavesplatform.account.PublicKeycom.wavesplatform.block.MicroBlockSignOps→com.wavesplatform.account.PrivateKey
- Direction
- block uses account, so a change to account can break block, while a change to block can't break account.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
33→2 block uses common.state✕
- Connections
- 7 pairs of types, where a type in block uses a type in common.state.
- The types involved
com.wavesplatform.block.Block→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.BlockHeader→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.ChallengedHeader→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.MerkleTreeOps→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.MicroBlock→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.SignedBlockHeader→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block.serialization→com.wavesplatform.common.state.ByteStr
- Direction
- block uses common.state, so a change to common.state can break block, while a change to block can't break common.state.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
33→18 block uses transaction.TxValidationError✕
- Connections
- 1 pair of types, where a type in block uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.block.FinalizationVoting→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- block uses transaction.TxValidationError, so a change to transaction.TxValidationError can break block, while a change to block can't break transaction.TxValidationError.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
33→22 block uses transaction✕
- Connections
- 5 pairs of types, where a type in block uses a type in transaction.
- The types involved
com.wavesplatform.block.Block→com.wavesplatform.transaction.Signedcom.wavesplatform.block.Block→com.wavesplatform.transaction.Transactioncom.wavesplatform.block.MicroBlock→com.wavesplatform.transaction.Signedcom.wavesplatform.block.MicroBlock→com.wavesplatform.transaction.Transactioncom.wavesplatform.block.serialization→com.wavesplatform.transaction.Transaction
- Direction
- block uses transaction, so a change to transaction can break block, while a change to block can't break transaction.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
33→30 block uses state✕
- Connections
- 4 pairs of types, where a type in block uses a type in state.
- The types involved
com.wavesplatform.block.BlockEndorsement→com.wavesplatform.state.GeneratorIndexcom.wavesplatform.block.BlockEndorsement→com.wavesplatform.state.Heightcom.wavesplatform.block.FinalizationVoting→com.wavesplatform.state.GeneratorIndexcom.wavesplatform.block.FinalizationVoting→com.wavesplatform.state.Height
- Direction
- block uses state, so a change to state can break block, while a change to block can't break state.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
33→32 block uses settings✕
- Connections
- 1 pair of types, where a type in block uses a type in settings.
- The types involved
com.wavesplatform.block.BlockValidationOps→com.wavesplatform.settings.GenesisSettings
- Direction
- block uses settings, so a change to settings can break block, while a change to block can't break settings.
- Position
- Below the diagonal: block uses a module listed above it, which is the healthy direction.
34→1 com.wavesplatform uses account✕
- Connections
- 13 pairs of types, where a type in com.wavesplatform uses a type in account.
- The types involved
com.wavesplatform.Explorer→com.wavesplatform.account.Addresscom.wavesplatform.TestHelpers→com.wavesplatform.account.Addresscom.wavesplatform.TestValues→com.wavesplatform.account.Addresscom.wavesplatform.TestValues→com.wavesplatform.account.KeyPaircom.wavesplatform.TransactionGenBase→com.wavesplatform.account.Addresscom.wavesplatform.TransactionGenBase→com.wavesplatform.account.AddressOrAliascom.wavesplatform.TransactionGenBase→com.wavesplatform.account.Aliascom.wavesplatform.TransactionGenBase→com.wavesplatform.account.KeyPaircom.wavesplatform.TransactionGenBase→com.wavesplatform.account.SeedKeyPaircom.wavesplatform.crypto→com.wavesplatform.account.PrivateKeycom.wavesplatform.crypto→com.wavesplatform.account.PublicKeycom.wavesplatform.history→com.wavesplatform.account.KeyPaircom.wavesplatform.settings→com.wavesplatform.account.PrivateKey
- Direction
- com.wavesplatform uses account, so a change to account can break com.wavesplatform, while a change to com.wavesplatform can't break account.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→2 com.wavesplatform uses common.state✕
- Connections
- 8 pairs of types, where a type in com.wavesplatform uses a type in common.state.
- The types involved
com.wavesplatform.TransactionGenBase→com.wavesplatform.common.state.ByteStrcom.wavesplatform.block→com.wavesplatform.common.state.ByteStrcom.wavesplatform.crypto→com.wavesplatform.common.state.ByteStrcom.wavesplatform.database→com.wavesplatform.common.state.ByteStrcom.wavesplatform.history→com.wavesplatform.common.state.ByteStrcom.wavesplatform.network→com.wavesplatform.common.state.ByteStrcom.wavesplatform.settings→com.wavesplatform.common.state.ByteStrcom.wavesplatform.utils→com.wavesplatform.common.state.ByteStr
- Direction
- com.wavesplatform uses common.state, so a change to common.state can break com.wavesplatform, while a change to com.wavesplatform can't break common.state.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→4 com.wavesplatform uses lang.v1.compiler.Types✕
- Connections
- 1 pair of types, where a type in com.wavesplatform uses a type in lang.v1.compiler.Types.
- The types involved
com.wavesplatform.JsApiUtils→com.wavesplatform.lang.v1.compiler.Types.TYPE
- Direction
- com.wavesplatform uses lang.v1.compiler.Types, so a change to lang.v1.compiler.Types can break com.wavesplatform, while a change to com.wavesplatform can't break lang.v1.compiler.Types.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→5 com.wavesplatform uses lang.v1.compiler.Terms✕
- Connections
- 4 pairs of types, where a type in com.wavesplatform uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.JsApiUtils→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.TransactionGenBase→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.TransactionGenBase→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALLcom.wavesplatform.utils→com.wavesplatform.lang.v1.compiler.Terms.EVALUATED
- Direction
- com.wavesplatform uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break com.wavesplatform, while a change to com.wavesplatform can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→8 com.wavesplatform uses transaction.Asset✕
- Connections
- 3 pairs of types, where a type in com.wavesplatform uses a type in transaction.Asset.
- The types involved
com.wavesplatform.TestValues→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.database→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- com.wavesplatform uses transaction.Asset, so a change to transaction.Asset can break com.wavesplatform, while a change to com.wavesplatform can't break transaction.Asset.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→9 com.wavesplatform uses transaction.assets.exchange✕
- Connections
- 4 pairs of types, where a type in com.wavesplatform uses a type in transaction.assets.exchange.
- The types involved
com.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.exchange.AssetPaircom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.exchange.ExchangeTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.exchange.Ordercom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.exchange.OrderType
- Direction
- com.wavesplatform uses transaction.assets.exchange, so a change to transaction.assets.exchange can break com.wavesplatform, while a change to com.wavesplatform can't break transaction.assets.exchange.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→10 com.wavesplatform uses lang.script✕
- Connections
- 1 pair of types, where a type in com.wavesplatform uses a type in lang.script.
- The types involved
com.wavesplatform.TransactionGenBase→com.wavesplatform.lang.script.Script
- Direction
- com.wavesplatform uses lang.script, so a change to lang.script can break com.wavesplatform, while a change to com.wavesplatform can't break lang.script.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→13 com.wavesplatform uses transaction.assets✕
- Connections
- 4 pairs of types, where a type in com.wavesplatform uses a type in transaction.assets.
- The types involved
com.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.BurnTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.IssueTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.ReissueTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.assets.SponsorFeeTransaction
- Direction
- com.wavesplatform uses transaction.assets, so a change to transaction.assets can break com.wavesplatform, while a change to com.wavesplatform can't break transaction.assets.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→14 com.wavesplatform uses lang.v1.compiler✕
- Connections
- 2 pairs of types, where a type in com.wavesplatform uses a type in lang.v1.compiler.
- The types involved
com.wavesplatform.JsApiUtils→com.wavesplatform.lang.v1.compiler.CompilationErrorcom.wavesplatform.JsApiUtils→com.wavesplatform.lang.v1.compiler.CompilerContext
- Direction
- com.wavesplatform uses lang.v1.compiler, so a change to lang.v1.compiler can break com.wavesplatform, while a change to com.wavesplatform can't break lang.v1.compiler.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→17 com.wavesplatform uses lang✕
- Connections
- 3 pairs of types, where a type in com.wavesplatform uses a type in lang.
- The types involved
com.wavesplatform.ResponsivenessLogs→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.TransactionGenBase→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.crypto→com.wavesplatform.lang.ValidationError
- Direction
- com.wavesplatform uses lang, so a change to lang can break com.wavesplatform, while a change to com.wavesplatform can't break lang.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→21 com.wavesplatform uses transaction.smart✕
- Connections
- 3 pairs of types, where a type in com.wavesplatform uses a type in transaction.smart.
- The types involved
com.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.smart.InvokeExpressionTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.smart.InvokeScriptTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.smart.SetScriptTransaction
- Direction
- com.wavesplatform uses transaction.smart, so a change to transaction.smart can break com.wavesplatform, while a change to com.wavesplatform can't break transaction.smart.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→22 com.wavesplatform uses transaction✕
- Connections
- 10 pairs of types, where a type in com.wavesplatform uses a type in transaction.
- The types involved
com.wavesplatform.ResponsivenessLogs→com.wavesplatform.transaction.Transactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.Assetcom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.CreateAliasTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.DataTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.GenesisTransactioncom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.Proofscom.wavesplatform.TransactionGenBase→com.wavesplatform.transaction.Transactioncom.wavesplatform.block→com.wavesplatform.transaction.Transactioncom.wavesplatform.database→com.wavesplatform.transaction.Transactioncom.wavesplatform.history→com.wavesplatform.transaction.Transaction
- Direction
- com.wavesplatform uses transaction, so a change to transaction can break com.wavesplatform, while a change to com.wavesplatform can't break transaction.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→23 com.wavesplatform uses utils✕
- Connections
- 7 pairs of types, where a type in com.wavesplatform uses a type in utils.
- The types involved
com.wavesplatform.Application→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.Explorer→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.Exporter→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.Importer→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.Importer→com.wavesplatform.utils.Timecom.wavesplatform.NTPTime→com.wavesplatform.utils.Timecom.wavesplatform.ResponsivenessLogs→com.wavesplatform.utils.ScorexLogging
- Direction
- com.wavesplatform uses utils, so a change to utils can break com.wavesplatform, while a change to com.wavesplatform can't break utils.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→26 com.wavesplatform uses network✕
- Connections
- 1 pair of types, where a type in com.wavesplatform uses a type in network.
- The types involved
com.wavesplatform.Application→com.wavesplatform.network.NetworkServer
- Direction
- com.wavesplatform uses network, so a change to network can break com.wavesplatform, while a change to com.wavesplatform can't break network.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→27 com.wavesplatform uses database✕
- Connections
- 2 pairs of types, where a type in com.wavesplatform uses a type in database.
- The types involved
com.wavesplatform.Exporter→com.wavesplatform.database.RDBcom.wavesplatform.Importer→com.wavesplatform.database.RDB
- Direction
- com.wavesplatform uses database, so a change to database can break com.wavesplatform, while a change to com.wavesplatform can't break database.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→28 com.wavesplatform uses utx✕
- Connections
- 2 pairs of types, where a type in com.wavesplatform uses a type in utx.
- The types involved
com.wavesplatform.Application→com.wavesplatform.utx.UtxPoolcom.wavesplatform.Importer→com.wavesplatform.utx.UtxPool
- Direction
- com.wavesplatform uses utx, so a change to utx can break com.wavesplatform, while a change to com.wavesplatform can't break utx.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→30 com.wavesplatform uses state✕
- Connections
- 21 pairs of types, where a type in com.wavesplatform uses a type in state.
- The types involved
com.wavesplatform.Explorer→com.wavesplatform.state.Blockchaincom.wavesplatform.Explorer→com.wavesplatform.state.Portfoliocom.wavesplatform.Importer→com.wavesplatform.state.Blockchaincom.wavesplatform.Importer→com.wavesplatform.state.BlockchainUpdaterImplcom.wavesplatform.TestValues→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.TransactionGenBase→com.wavesplatform.state.BinaryDataEntrycom.wavesplatform.TransactionGenBase→com.wavesplatform.state.BooleanDataEntrycom.wavesplatform.TransactionGenBase→com.wavesplatform.state.DataEntrycom.wavesplatform.TransactionGenBase→com.wavesplatform.state.EmptyDataEntrycom.wavesplatform.TransactionGenBase→com.wavesplatform.state.IntegerDataEntrycom.wavesplatform.TransactionGenBase→com.wavesplatform.state.StringDataEntrycom.wavesplatform.database→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.database→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.database→com.wavesplatform.state.AssetScriptInfocom.wavesplatform.database→com.wavesplatform.state.DataEntrycom.wavesplatform.database→com.wavesplatform.state.GeneratorIndexcom.wavesplatform.database→com.wavesplatform.state.Heightcom.wavesplatform.database→com.wavesplatform.state.LeaseDetailscom.wavesplatform.database→com.wavesplatform.state.SponsorshipValuecom.wavesplatform.database→com.wavesplatform.state.StateHashcom.wavesplatform.database→com.wavesplatform.state.TransactionId
- Direction
- com.wavesplatform uses state, so a change to state can break com.wavesplatform, while a change to com.wavesplatform can't break state.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→32 com.wavesplatform uses settings✕
- Connections
- 6 pairs of types, where a type in com.wavesplatform uses a type in settings.
- The types involved
com.wavesplatform.Application→com.wavesplatform.settings.WavesSettingscom.wavesplatform.Importer→com.wavesplatform.settings.WavesSettingscom.wavesplatform.TestHelpers→com.wavesplatform.settings.FunctionalitySettingscom.wavesplatform.TestHelpers→com.wavesplatform.settings.GenesisSettingscom.wavesplatform.TestHelpers→com.wavesplatform.settings.WavesSettingscom.wavesplatform.history→com.wavesplatform.settings.WavesSettings
- Direction
- com.wavesplatform uses settings, so a change to settings can break com.wavesplatform, while a change to com.wavesplatform can't break settings.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
34→33 com.wavesplatform uses block✕
- Connections
- 4 pairs of types, where a type in com.wavesplatform uses a type in block.
- The types involved
com.wavesplatform.database→com.wavesplatform.block.Blockcom.wavesplatform.database→com.wavesplatform.block.BlockHeadercom.wavesplatform.history→com.wavesplatform.block.Blockcom.wavesplatform.network→com.wavesplatform.block.Block
- Direction
- com.wavesplatform uses block, so a change to block can break com.wavesplatform, while a change to com.wavesplatform can't break block.
- Position
- Below the diagonal: com.wavesplatform uses a module listed above it, which is the healthy direction.
35→1 history uses account✕
- Connections
- 2 pairs of types, where a type in history uses a type in account.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.account.Addresscom.wavesplatform.history.Domain→com.wavesplatform.account.KeyPair
- Direction
- history uses account, so a change to account can break history, while a change to history can't break account.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→2 history uses common.state✕
- Connections
- 2 pairs of types, where a type in history uses a type in common.state.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.common.state.ByteStrcom.wavesplatform.history.History→com.wavesplatform.common.state.ByteStr
- Direction
- history uses common.state, so a change to common.state can break history, while a change to history can't break common.state.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→17 history uses lang✕
- Connections
- 2 pairs of types, where a type in history uses a type in lang.
- The types involved
com.wavesplatform.history.DefaultAppender→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.history.Domain→com.wavesplatform.lang.ValidationError
- Direction
- history uses lang, so a change to lang can break history, while a change to history can't break lang.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→22 history uses transaction✕
- Connections
- 2 pairs of types, where a type in history uses a type in transaction.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.transaction.Assetcom.wavesplatform.history.Domain→com.wavesplatform.transaction.Transaction
- Direction
- history uses transaction, so a change to transaction can break history, while a change to history can't break transaction.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→23 history uses utils✕
- Connections
- 2 pairs of types, where a type in history uses a type in utils.
- The types involved
com.wavesplatform.history.StorageFactory→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.history.StorageFactory→com.wavesplatform.utils.Time
- Direction
- history uses utils, so a change to utils can break history, while a change to history can't break utils.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→24 history uses events✕
- Connections
- 2 pairs of types, where a type in history uses a type in events.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.events.BlockchainUpdateTriggerscom.wavesplatform.history.StorageFactory→com.wavesplatform.events.BlockchainUpdateTriggers
- Direction
- history uses events, so a change to events can break history, while a change to history can't break events.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→25 history uses mining✕
- Connections
- 2 pairs of types, where a type in history uses a type in mining.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.mining.BlockChallengercom.wavesplatform.history.StorageFactory→com.wavesplatform.mining.Miner
- Direction
- history uses mining, so a change to mining can break history, while a change to history can't break mining.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→27 history uses database✕
- Connections
- 3 pairs of types, where a type in history uses a type in database.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.database.RDBcom.wavesplatform.history.Domain→com.wavesplatform.database.RocksDBWritercom.wavesplatform.history.StorageFactory→com.wavesplatform.database.RDB
- Direction
- history uses database, so a change to database can break history, while a change to history can't break database.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→28 history uses utx✕
- Connections
- 1 pair of types, where a type in history uses a type in utx.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.utx.UtxPoolImpl
- Direction
- history uses utx, so a change to utx can break history, while a change to history can't break utx.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→30 history uses state✕
- Connections
- 4 pairs of types, where a type in history uses a type in state.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.state.BlockEndorsercom.wavesplatform.history.Domain→com.wavesplatform.state.EndorsementStoragecom.wavesplatform.history.Domain→com.wavesplatform.state.NgStatecom.wavesplatform.history.Domain→com.wavesplatform.state.StateSnapshot
- Direction
- history uses state, so a change to state can break history, while a change to history can't break state.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→31 history uses api.common✕
- Connections
- 5 pairs of types, where a type in history uses a type in api.common.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.api.common.CommonAccountsApicom.wavesplatform.history.Domain→com.wavesplatform.api.common.CommonAssetsApicom.wavesplatform.history.Domain→com.wavesplatform.api.common.CommonBlocksApicom.wavesplatform.history.Domain→com.wavesplatform.api.common.CommonGeneratorsApicom.wavesplatform.history.Domain→com.wavesplatform.api.common.CommonTransactionsApi
- Direction
- history uses api.common, so a change to api.common can break history, while a change to history can't break api.common.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→32 history uses settings✕
- Connections
- 2 pairs of types, where a type in history uses a type in settings.
- The types involved
com.wavesplatform.history.Domain→com.wavesplatform.settings.WavesSettingscom.wavesplatform.history.StorageFactory→com.wavesplatform.settings.WavesSettings
- Direction
- history uses settings, so a change to settings can break history, while a change to history can't break settings.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
35→33 history uses block✕
- Connections
- 8 pairs of types, where a type in history uses a type in block.
- The types involved
com.wavesplatform.history.DefaultAppender→com.wavesplatform.block.Blockcom.wavesplatform.history.Domain→com.wavesplatform.block.Blockcom.wavesplatform.history.Domain→com.wavesplatform.block.BlockSnapshotcom.wavesplatform.history.Domain→com.wavesplatform.block.ChallengedHeadercom.wavesplatform.history.Domain→com.wavesplatform.block.FinalizationVotingcom.wavesplatform.history.Domain→com.wavesplatform.block.MicroBlockcom.wavesplatform.history.History→com.wavesplatform.block.MicroBlockcom.wavesplatform.history.MicroBlockWithTotalId→com.wavesplatform.block.MicroBlock
- Direction
- history uses block, so a change to block can break history, while a change to history can't break block.
- Position
- Below the diagonal: history uses a module listed above it, which is the healthy direction.
36→1 ride.runner.blockchain uses account✕
- Connections
- 6 pairs of types, where a type in ride.runner.blockchain uses a type in account.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.account.Addresscom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.account.Aliascom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.account.Addresscom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.account.Aliascom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.account.PublicKeycom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.account.Address
- Direction
- ride.runner.blockchain uses account, so a change to account can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break account.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→2 ride.runner.blockchain uses common.state✕
- Connections
- 3 pairs of types, where a type in ride.runner.blockchain uses a type in common.state.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.common.state.ByteStrcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.common.state.ByteStrcom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.common.state.ByteStr
- Direction
- ride.runner.blockchain uses common.state, so a change to common.state can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break common.state.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→8 ride.runner.blockchain uses transaction.Asset✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in transaction.Asset.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.transaction.Asset.IssuedAssetcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- ride.runner.blockchain uses transaction.Asset, so a change to transaction.Asset can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break transaction.Asset.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→10 ride.runner.blockchain uses lang.script✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in lang.script.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.lang.script.Scriptcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.lang.script.Script
- Direction
- ride.runner.blockchain uses lang.script, so a change to lang.script can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break lang.script.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→17 ride.runner.blockchain uses lang✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in lang.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.lang.ValidationError
- Direction
- ride.runner.blockchain uses lang, so a change to lang can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break lang.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→22 ride.runner.blockchain uses transaction✕
- Connections
- 5 pairs of types, where a type in ride.runner.blockchain uses a type in transaction.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.transaction.Assetcom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.transaction.ERC20Addresscom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.transaction.Transaction
- Direction
- ride.runner.blockchain uses transaction, so a change to transaction can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break transaction.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→23 ride.runner.blockchain uses utils✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in utils.
- The types involved
com.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.utils.ScorexLogging
- Direction
- ride.runner.blockchain uses utils, so a change to utils can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break utils.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→30 ride.runner.blockchain uses state✕
- Connections
- 25 pairs of types, where a type in ride.runner.blockchain uses a type in state.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.BalanceSnapshotcom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.ConflictGeneratorscom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.DataEntrycom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.GenerationPeriodcom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.Heightcom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.LeaseBalancecom.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.state.TxMetacom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.AssetDescriptioncom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.AssetScriptInfocom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.BalanceSnapshotcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.ConflictGeneratorscom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.DataEntrycom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.GenerationPeriodcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.Heightcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.LeaseBalancecom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.TransactionIdcom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.state.TxMetacom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.state.AssetScriptInfocom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.state.Blockchaincom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.state.Heightcom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.state.LeaseDetailscom.wavesplatform.ride.runner.blockchain.SupportedBlockchain→com.wavesplatform.state.VolumeAndFee
- Direction
- ride.runner.blockchain uses state, so a change to state can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break state.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→32 ride.runner.blockchain uses settings✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in settings.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.settings.BlockchainSettingscom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.settings.BlockchainSettings
- Direction
- ride.runner.blockchain uses settings, so a change to settings can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break settings.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
36→33 ride.runner.blockchain uses block✕
- Connections
- 2 pairs of types, where a type in ride.runner.blockchain uses a type in block.
- The types involved
com.wavesplatform.ride.runner.blockchain.ImmutableBlockchain→com.wavesplatform.block.SignedBlockHeadercom.wavesplatform.ride.runner.blockchain.LazyBlockchain→com.wavesplatform.block.SignedBlockHeader
- Direction
- ride.runner.blockchain uses block, so a change to block can break ride.runner.blockchain, while a change to ride.runner.blockchain can't break block.
- Position
- Below the diagonal: ride.runner.blockchain uses a module listed above it, which is the healthy direction.
37→1 state.diffs uses account✕
- Connections
- 9 pairs of types, where a type in state.diffs uses a type in account.
- The types involved
com.wavesplatform.state.diffs.BalanceDiffValidation→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.account.AddressOrAliascom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.account.PublicKeycom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.TransferDiff→com.wavesplatform.account.Addresscom.wavesplatform.state.diffs.TransferDiff→com.wavesplatform.account.AddressOrAlias
- Direction
- state.diffs uses account, so a change to account can break state.diffs, while a change to state.diffs can't break account.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→2 state.diffs uses common.state✕
- Connections
- 3 pairs of types, where a type in state.diffs uses a type in common.state.
- The types involved
com.wavesplatform.state.diffs.BalanceDiffValidation→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.common.state.ByteStrcom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.common.state.ByteStr
- Direction
- state.diffs uses common.state, so a change to common.state can break state.diffs, while a change to state.diffs can't break common.state.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→3 state.diffs uses lang.directives.values✕
- Connections
- 1 pair of types, where a type in state.diffs uses a type in lang.directives.values.
- The types involved
com.wavesplatform.state.diffs.SetScriptTransactionDiff→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- state.diffs uses lang.directives.values, so a change to lang.directives.values can break state.diffs, while a change to state.diffs can't break lang.directives.values.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→7 state.diffs uses lang.v1.traits.domain✕
- Connections
- 3 pairs of types, where a type in state.diffs uses a type in lang.v1.traits.domain.
- The types involved
com.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.lang.v1.traits.domain.Burncom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.lang.v1.traits.domain.Reissuecom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.lang.v1.traits.domain.SponsorFee
- Direction
- state.diffs uses lang.v1.traits.domain, so a change to lang.v1.traits.domain can break state.diffs, while a change to state.diffs can't break lang.v1.traits.domain.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→8 state.diffs uses transaction.Asset✕
- Connections
- 1 pair of types, where a type in state.diffs uses a type in transaction.Asset.
- The types involved
com.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- state.diffs uses transaction.Asset, so a change to transaction.Asset can break state.diffs, while a change to state.diffs can't break transaction.Asset.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→9 state.diffs uses transaction.assets.exchange✕
- Connections
- 3 pairs of types, where a type in state.diffs uses a type in transaction.assets.exchange.
- The types involved
com.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.transaction.assets.exchange.ExchangeTransactioncom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.transaction.assets.exchange.Ordercom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.transaction.assets.exchange.Order
- Direction
- state.diffs uses transaction.assets.exchange, so a change to transaction.assets.exchange can break state.diffs, while a change to state.diffs can't break transaction.assets.exchange.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→10 state.diffs uses lang.script✕
- Connections
- 3 pairs of types, where a type in state.diffs uses a type in lang.script.
- The types involved
com.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.lang.script.Scriptcom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.lang.script.Scriptcom.wavesplatform.state.diffs.SetScriptTransactionDiff→com.wavesplatform.lang.script.Script
- Direction
- state.diffs uses lang.script, so a change to lang.script can break state.diffs, while a change to state.diffs can't break lang.script.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→13 state.diffs uses transaction.assets✕
- Connections
- 6 pairs of types, where a type in state.diffs uses a type in transaction.assets.
- The types involved
com.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.BurnTransactioncom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.IssueTransactioncom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.ReissueTransactioncom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.SetAssetScriptTransactioncom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.SponsorFeeTransactioncom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.assets.UpdateAssetInfoTransaction
- Direction
- state.diffs uses transaction.assets, so a change to transaction.assets can break state.diffs, while a change to state.diffs can't break transaction.assets.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→17 state.diffs uses lang✕
- Connections
- 18 pairs of types, where a type in state.diffs uses a type in lang.
- The types involved
com.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.CommitToGenerationTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.CommonValidation→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.CreateAliasTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.DataTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.EthereumTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.FeeValidation→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.GenesisTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.LeaseTransactionsDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.MassTransferTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.PaymentTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.SetScriptTransactionDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.TransferDiff→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.state.diffs.TransferTransactionDiff→com.wavesplatform.lang.ValidationError
- Direction
- state.diffs uses lang, so a change to lang can break state.diffs, while a change to state.diffs can't break lang.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→18 state.diffs uses transaction.TxValidationError✕
- Connections
- 4 pairs of types, where a type in state.diffs uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.state.diffs.BalanceDiffValidation→com.wavesplatform.transaction.TxValidationError.AccountBalanceErrorcom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.state.diffs.SetScriptTransactionDiff→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- state.diffs uses transaction.TxValidationError, so a change to transaction.TxValidationError can break state.diffs, while a change to state.diffs can't break transaction.TxValidationError.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→19 state.diffs uses transaction.smart.script.trace✕
- Connections
- 3 pairs of types, where a type in state.diffs uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.transaction.smart.script.trace.TracedResultcom.wavesplatform.state.diffs.EthereumTransactionDiff→com.wavesplatform.transaction.smart.script.trace.TracedResultcom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- state.diffs uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break state.diffs, while a change to state.diffs can't break transaction.smart.script.trace.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→21 state.diffs uses transaction.smart✕
- Connections
- 2 pairs of types, where a type in state.diffs uses a type in transaction.smart.
- The types involved
com.wavesplatform.state.diffs.SetScriptTransactionDiff→com.wavesplatform.transaction.smart.SetScriptTransactioncom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.transaction.smart.InvokeScriptTransaction
- Direction
- state.diffs uses transaction.smart, so a change to transaction.smart can break state.diffs, while a change to state.diffs can't break transaction.smart.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→22 state.diffs uses transaction✕
- Connections
- 14 pairs of types, where a type in state.diffs uses a type in transaction.
- The types involved
com.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.diffs.CommitToGenerationTransactionDiff→com.wavesplatform.transaction.CommitToGenerationTransactioncom.wavesplatform.state.diffs.CreateAliasTransactionDiff→com.wavesplatform.transaction.CreateAliasTransactioncom.wavesplatform.state.diffs.DataTransactionDiff→com.wavesplatform.transaction.DataTransactioncom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.transaction.TxPositiveAmountcom.wavesplatform.state.diffs.EthereumTransactionDiff→com.wavesplatform.transaction.EthereumTransactioncom.wavesplatform.state.diffs.FeeValidation→com.wavesplatform.transaction.Assetcom.wavesplatform.state.diffs.FeeValidation→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.diffs.FeeValidation→com.wavesplatform.transaction.TransactionTypecom.wavesplatform.state.diffs.GenesisTransactionDiff→com.wavesplatform.transaction.GenesisTransactioncom.wavesplatform.state.diffs.PaymentTransactionDiff→com.wavesplatform.transaction.PaymentTransactioncom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.transaction.Transactioncom.wavesplatform.state.diffs.TransactionDiffer→com.wavesplatform.transaction.TransactionBasecom.wavesplatform.state.diffs.TransferDiff→com.wavesplatform.transaction.Asset
- Direction
- state.diffs uses transaction, so a change to transaction can break state.diffs, while a change to state.diffs can't break transaction.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→25 state.diffs uses mining✕
- Connections
- 1 pair of types, where a type in state.diffs uses a type in mining.
- The types involved
com.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.mining.MiningConstraint
- Direction
- state.diffs uses mining, so a change to mining can break state.diffs, while a change to state.diffs can't break mining.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→30 state.diffs uses state✕
- Connections
- 43 pairs of types, where a type in state.diffs uses a type in state. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.AssetTransactionsDiffs→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.BalanceDiffValidation→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.BalanceDiffValidation→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.state.GenerationPeriodcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.state.Portfoliocom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.CommitToGenerationTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.CommitToGenerationTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.CommonValidation→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.CreateAliasTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.CreateAliasTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.DataTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.DataTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.DiffsCommon→com.wavesplatform.state.TransactionIdcom.wavesplatform.state.diffs.EthereumTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.EthereumTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.state.Portfoliocom.wavesplatform.state.diffs.ExchangeTransactionDiff→com.wavesplatform.state.StateSnapshotcom.wavesplatform.state.diffs.FeeValidation→com.wavesplatform.state.Blockchaincom.wavesplatform.state.diffs.GenesisTransactionDiff→com.wavesplatform.state.Blockchain
- Direction
- state.diffs uses state, so a change to state can break state.diffs, while a change to state.diffs can't break state.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→32 state.diffs uses settings✕
- Connections
- 1 pair of types, where a type in state.diffs uses a type in settings.
- The types involved
com.wavesplatform.state.diffs.CommonValidation→com.wavesplatform.settings.FunctionalitySettings
- Direction
- state.diffs uses settings, so a change to settings can break state.diffs, while a change to state.diffs can't break settings.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
37→33 state.diffs uses block✕
- Connections
- 5 pairs of types, where a type in state.diffs uses a type in block.
- The types involved
com.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.block.Blockcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.block.BlockSnapshotcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.block.FinalizationVotingcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.block.MicroBlockcom.wavesplatform.state.diffs.BlockDiffer→com.wavesplatform.block.MicroBlockSnapshot
- Direction
- state.diffs uses block, so a change to block can break state.diffs, while a change to state.diffs can't break block.
- Position
- Below the diagonal: state.diffs uses a module listed above it, which is the healthy direction.
38→1 api.http uses account✕
- Connections
- 5 pairs of types, where a type in api.http uses a type in account.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.account.Addresscom.wavesplatform.api.http.JsonFormats→com.wavesplatform.account.Addresscom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.account.Addresscom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.account.AddressOrAliascom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.account.Address
- Direction
- api.http uses account, so a change to account can break api.http, while a change to api.http can't break account.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→2 api.http uses common.state✕
- Connections
- 5 pairs of types, where a type in api.http uses a type in common.state.
- The types involved
com.wavesplatform.api.http.ApiMarshallers→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.common.state.ByteStrcom.wavesplatform.api.http.requests→com.wavesplatform.common.state.ByteStr
- Direction
- api.http uses common.state, so a change to common.state can break api.http, while a change to api.http can't break common.state.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→5 api.http uses lang.v1.compiler.Terms✕
- Connections
- 2 pairs of types, where a type in api.http uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.lang.v1.compiler.Terms.EVALUATEDcom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.lang.v1.compiler.Terms.FUNCTION_CALL
- Direction
- api.http uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break api.http, while a change to api.http can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→8 api.http uses transaction.Asset✕
- Connections
- 1 pair of types, where a type in api.http uses a type in transaction.Asset.
- The types involved
com.wavesplatform.api.http.requests→com.wavesplatform.transaction.Asset.IssuedAsset
- Direction
- api.http uses transaction.Asset, so a change to transaction.Asset can break api.http, while a change to api.http can't break transaction.Asset.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→17 api.http uses lang✕
- Connections
- 3 pairs of types, where a type in api.http uses a type in lang.
- The types involved
com.wavesplatform.api.http.ApiMarshallers→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.RewardApiRoute→com.wavesplatform.lang.ValidationError
- Direction
- api.http uses lang, so a change to lang can break api.http, while a change to api.http can't break lang.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→19 api.http uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in api.http uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.api.http.ApiMarshallers→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- api.http uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break api.http, while a change to api.http can't break transaction.smart.script.trace.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→22 api.http uses transaction✕
- Connections
- 7 pairs of types, where a type in api.http uses a type in transaction.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.transaction.Assetcom.wavesplatform.api.http.BroadcastRoute→com.wavesplatform.transaction.Transactioncom.wavesplatform.api.http.JsonFormats→com.wavesplatform.transaction.Transactioncom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.transaction.Assetcom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.transaction.Transactioncom.wavesplatform.api.http.requests→com.wavesplatform.transaction.Assetcom.wavesplatform.api.http.requests→com.wavesplatform.transaction.Proofs
- Direction
- api.http uses transaction, so a change to transaction can break api.http, while a change to api.http can't break transaction.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→23 api.http uses utils✕
- Connections
- 10 pairs of types, where a type in api.http uses a type in utils.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.utils.Timecom.wavesplatform.api.http.ApiRoute→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.http.BlocksApiRoute→com.wavesplatform.utils.Timecom.wavesplatform.api.http.CompositeHttpService→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.http.CustomDirectives→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.utils.Timecom.wavesplatform.api.http.GeneratorsApiRoute→com.wavesplatform.utils.Timecom.wavesplatform.api.http.NodeApiRoute→com.wavesplatform.utils.ScorexLoggingcom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.utils.Time
- Direction
- api.http uses utils, so a change to utils can break api.http, while a change to api.http can't break utils.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→26 api.http uses network✕
- Connections
- 8 pairs of types, where a type in api.http uses a type in network.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.network.TransactionPublishercom.wavesplatform.api.http.BroadcastRoute→com.wavesplatform.network.TransactionPublishercom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.network.HistoryRepliercom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.network.PeerDatabasecom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.network.PeerInfocom.wavesplatform.api.http.PeersApiRoute→com.wavesplatform.network.PeerDatabasecom.wavesplatform.api.http.PeersApiRoute→com.wavesplatform.network.PeerInfocom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.network.TransactionPublisher
- Direction
- api.http uses network, so a change to network can break api.http, while a change to api.http can't break network.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→27 api.http uses database✕
- Connections
- 1 pair of types, where a type in api.http uses a type in database.
- The types involved
com.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.database.RocksDBWriter
- Direction
- api.http uses database, so a change to database can break api.http, while a change to api.http can't break database.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→28 api.http uses utx✕
- Connections
- 1 pair of types, where a type in api.http uses a type in utx.
- The types involved
com.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.utx.UtxPool
- Direction
- api.http uses utx, so a change to utx can break api.http, while a change to api.http can't break utx.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→30 api.http uses state✕
- Connections
- 14 pairs of types, where a type in api.http uses a type in state.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.state.DataEntrycom.wavesplatform.api.http.BlocksApiRoute→com.wavesplatform.state.Heightcom.wavesplatform.api.http.FinalityApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.GeneratorsApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.NodeApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.RewardApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.RewardApiRoute→com.wavesplatform.state.Heightcom.wavesplatform.api.http.StateSnapshotJson→com.wavesplatform.state.AssetStaticInfocom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.state.Heightcom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.state.InvokeScriptResultcom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.state.TxMetacom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.state.Blockchain
- Direction
- api.http uses state, so a change to state can break api.http, while a change to api.http can't break state.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→31 api.http uses api.common✕
- Connections
- 11 pairs of types, where a type in api.http uses a type in api.common.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.api.common.CommonAccountsApicom.wavesplatform.api.http.BlocksApiRoute→com.wavesplatform.api.common.CommonBlocksApicom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.api.common.CommonAccountsApicom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.api.common.CommonAssetsApicom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.api.common.CommonTransactionsApicom.wavesplatform.api.http.FinalityApiRoute→com.wavesplatform.api.common.CommonBlocksApicom.wavesplatform.api.http.FinalityApiRoute→com.wavesplatform.api.common.CommonGeneratorsApicom.wavesplatform.api.http.GeneratorsApiRoute→com.wavesplatform.api.common.CommonGeneratorsApicom.wavesplatform.api.http.TransactionJsonSerializer→com.wavesplatform.api.common.TransactionMetacom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.api.common.CommonTransactionsApicom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.api.common.TransactionMeta
- Direction
- api.http uses api.common, so a change to api.common can break api.http, while a change to api.http can't break api.common.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→32 api.http uses settings✕
- Connections
- 11 pairs of types, where a type in api.http uses a type in settings.
- The types involved
com.wavesplatform.api.http.AddressApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.AuthRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.BlocksApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.CompositeHttpService→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.DebugApiRoute→com.wavesplatform.settings.WavesSettingscom.wavesplatform.api.http.GeneratorsApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.NodeApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.PeersApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.TransactionsApiRoute→com.wavesplatform.settings.RestAPISettingscom.wavesplatform.api.http.WalletApiRoute→com.wavesplatform.settings.RestAPISettings
- Direction
- api.http uses settings, so a change to settings can break api.http, while a change to api.http can't break settings.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
38→34 api.http uses com.wavesplatform✕
- Connections
- 1 pair of types, where a type in api.http uses a type in com.wavesplatform.
- The types involved
com.wavesplatform.api.http.NodeApiRoute→com.wavesplatform.Shutdownable
- Direction
- api.http uses com.wavesplatform, so a change to com.wavesplatform can break api.http, while a change to api.http can't break com.wavesplatform.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
39→1 db uses account✕
- Connections
- 1 pair of types, where a type in db uses a type in account.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.account.KeyPair
- Direction
- db uses account, so a change to account can break db, while a change to db can't break account.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→3 db uses lang.directives.values✕
- Connections
- 1 pair of types, where a type in db uses a type in lang.directives.values.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- db uses lang.directives.values, so a change to lang.directives.values can break db, while a change to db can't break lang.directives.values.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→17 db uses lang✕
- Connections
- 1 pair of types, where a type in db uses a type in lang.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.lang.ValidationError
- Direction
- db uses lang, so a change to lang can break db, while a change to db can't break lang.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→19 db uses transaction.smart.script.trace✕
- Connections
- 1 pair of types, where a type in db uses a type in transaction.smart.script.trace.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.transaction.smart.script.trace.TracedResult
- Direction
- db uses transaction.smart.script.trace, so a change to transaction.smart.script.trace can break db, while a change to db can't break transaction.smart.script.trace.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→22 db uses transaction✕
- Connections
- 1 pair of types, where a type in db uses a type in transaction.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.transaction.GenesisTransaction
- Direction
- db uses transaction, so a change to transaction can break db, while a change to db can't break transaction.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→24 db uses events✕
- Connections
- 1 pair of types, where a type in db uses a type in events.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.events.BlockchainUpdateTriggers
- Direction
- db uses events, so a change to events can break db, while a change to db can't break events.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→25 db uses mining✕
- Connections
- 1 pair of types, where a type in db uses a type in mining.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.mining.Miner
- Direction
- db uses mining, so a change to mining can break db, while a change to db can't break mining.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→27 db uses database✕
- Connections
- 3 pairs of types, where a type in db uses a type in database.
- The types involved
com.wavesplatform.db.TempRDB→com.wavesplatform.database.RDBcom.wavesplatform.db.WithState→com.wavesplatform.database.RDBcom.wavesplatform.db.WithState→com.wavesplatform.database.RocksDBWriter
- Direction
- db uses database, so a change to database can break db, while a change to db can't break database.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→30 db uses state✕
- Connections
- 2 pairs of types, where a type in db uses a type in state.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.state.BlockchainUpdaterImplcom.wavesplatform.db.WithState→com.wavesplatform.state.StateSnapshot
- Direction
- db uses state, so a change to state can break db, while a change to db can't break state.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→32 db uses settings✕
- Connections
- 5 pairs of types, where a type in db uses a type in settings.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.settings.FunctionalitySettingscom.wavesplatform.db.WithDomain→com.wavesplatform.settings.WavesSettingscom.wavesplatform.db.WithState→com.wavesplatform.settings.BlockchainSettingscom.wavesplatform.db.WithState→com.wavesplatform.settings.FunctionalitySettingscom.wavesplatform.db.WithState→com.wavesplatform.settings.WavesSettings
- Direction
- db uses settings, so a change to settings can break db, while a change to db can't break settings.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→33 db uses block✕
- Connections
- 2 pairs of types, where a type in db uses a type in block.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.block.Blockcom.wavesplatform.db.WithState→com.wavesplatform.block.Block
- Direction
- db uses block, so a change to block can break db, while a change to db can't break block.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→34 db uses com.wavesplatform✕
- Connections
- 1 pair of types, where a type in db uses a type in com.wavesplatform.
- The types involved
com.wavesplatform.db.WithState→com.wavesplatform.NTPTime
- Direction
- db uses com.wavesplatform, so a change to com.wavesplatform can break db, while a change to db can't break com.wavesplatform.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
39→35 db uses history✕
- Connections
- 1 pair of types, where a type in db uses a type in history.
- The types involved
com.wavesplatform.db.WithDomain→com.wavesplatform.history.Domain
- Direction
- db uses history, so a change to history can break db, while a change to db can't break history.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
40→1 api.http.utils uses account✕
- Connections
- 3 pairs of types, where a type in api.http.utils uses a type in account.
- The types involved
com.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.account.Addresscom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.account.Addresscom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.account.PublicKey
- Direction
- api.http.utils uses account, so a change to account can break api.http.utils, while a change to api.http.utils can't break account.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→2 api.http.utils uses common.state✕
- Connections
- 1 pair of types, where a type in api.http.utils uses a type in common.state.
- The types involved
com.wavesplatform.api.http.utils.UtilsInvocationRequest→com.wavesplatform.common.state.ByteStr
- Direction
- api.http.utils uses common.state, so a change to common.state can break api.http.utils, while a change to api.http.utils can't break common.state.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→3 api.http.utils uses lang.directives.values✕
- Connections
- 4 pairs of types, where a type in api.http.utils uses a type in lang.directives.values.
- The types involved
com.wavesplatform.api.http.utils.InvocationEvaluation→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.lang.directives.values.StdLibVersioncom.wavesplatform.api.http.utils.UtilsExprRequest→com.wavesplatform.lang.directives.values.StdLibVersion
- Direction
- api.http.utils uses lang.directives.values, so a change to lang.directives.values can break api.http.utils, while a change to api.http.utils can't break lang.directives.values.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→5 api.http.utils uses lang.v1.compiler.Terms✕
- Connections
- 5 pairs of types, where a type in api.http.utils uses a type in lang.v1.compiler.Terms.
- The types involved
com.wavesplatform.api.http.utils.Evaluation→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.api.http.utils.ExprEvaluation→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.api.http.utils.InvocationEvaluation→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.lang.v1.compiler.Terms.EXPRcom.wavesplatform.api.http.utils.UtilsExprRequest→com.wavesplatform.lang.v1.compiler.Terms.EXPR
- Direction
- api.http.utils uses lang.v1.compiler.Terms, so a change to lang.v1.compiler.Terms can break api.http.utils, while a change to api.http.utils can't break lang.v1.compiler.Terms.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→10 api.http.utils uses lang.script✕
- Connections
- 1 pair of types, where a type in api.http.utils uses a type in lang.script.
- The types involved
com.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.lang.script.Script
- Direction
- api.http.utils uses lang.script, so a change to lang.script can break api.http.utils, while a change to api.http.utils can't break lang.script.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→17 api.http.utils uses lang✕
- Connections
- 5 pairs of types, where a type in api.http.utils uses a type in lang.
- The types involved
com.wavesplatform.api.http.utils.Evaluation→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.utils.ExprEvaluation→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.utils.InvocationEvaluation→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.lang.ValidationErrorcom.wavesplatform.api.http.utils.UtilsInvocationRequest→com.wavesplatform.lang.ValidationError
- Direction
- api.http.utils uses lang, so a change to lang can break api.http.utils, while a change to api.http.utils can't break lang.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→18 api.http.utils uses transaction.TxValidationError✕
- Connections
- 2 pairs of types, where a type in api.http.utils uses a type in transaction.TxValidationError.
- The types involved
com.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.transaction.TxValidationError.GenericErrorcom.wavesplatform.api.http.utils.UtilsExprRequest→com.wavesplatform.transaction.TxValidationError.GenericError
- Direction
- api.http.utils uses transaction.TxValidationError, so a change to transaction.TxValidationError can break api.http.utils, while a change to api.http.utils can't break transaction.TxValidationError.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→20 api.http.utils uses state.diffs.invoke✕
- Connections
- 4 pairs of types, where a type in api.http.utils uses a type in state.diffs.invoke.
- The types involved
com.wavesplatform.api.http.utils.Evaluation→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLikecom.wavesplatform.api.http.utils.ExprEvaluation→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLikecom.wavesplatform.api.http.utils.InvocationEvaluation→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLikecom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.state.diffs.invoke.InvokeScriptTransactionLike
- Direction
- api.http.utils uses state.diffs.invoke, so a change to state.diffs.invoke can break api.http.utils, while a change to api.http.utils can't break state.diffs.invoke.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→21 api.http.utils uses transaction.smart✕
- Connections
- 1 pair of types, where a type in api.http.utils uses a type in transaction.smart.
- The types involved
com.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.transaction.smart.DAppEnvironment
- Direction
- api.http.utils uses transaction.smart, so a change to transaction.smart can break api.http.utils, while a change to api.http.utils can't break transaction.smart.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→23 api.http.utils uses utils✕
- Connections
- 1 pair of types, where a type in api.http.utils uses a type in utils.
- The types involved
com.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.utils.Time
- Direction
- api.http.utils uses utils, so a change to utils can break api.http.utils, while a change to api.http.utils can't break utils.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→30 api.http.utils uses state✕
- Connections
- 11 pairs of types, where a type in api.http.utils uses a type in state.
- The types involved
com.wavesplatform.api.http.utils.Evaluation→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.ExprEvaluation→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.InvocationEvaluation→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.UtilsEvaluationRequest→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.UtilsEvaluationRequest→com.wavesplatform.state.BlockchainOverridescom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.state.AccountScriptInfocom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.state.Blockchaincom.wavesplatform.api.http.utils.UtilsEvaluator→com.wavesplatform.state.StateSnapshotcom.wavesplatform.api.http.utils.UtilsExprRequest→com.wavesplatform.state.BlockchainOverridescom.wavesplatform.api.http.utils.UtilsInvocationRequest→com.wavesplatform.state.BlockchainOverrides
- Direction
- api.http.utils uses state, so a change to state can break api.http.utils, while a change to api.http.utils can't break state.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→32 api.http.utils uses settings✕
- Connections
- 1 pair of types, where a type in api.http.utils uses a type in settings.
- The types involved
com.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.settings.RestAPISettings
- Direction
- api.http.utils uses settings, so a change to settings can break api.http.utils, while a change to api.http.utils can't break settings.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
40→38 api.http.utils uses api.http✕
- Connections
- 3 pairs of types, where a type in api.http.utils uses a type in api.http.
- The types involved
com.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.api.http.ApiRoutecom.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.api.http.AuthRoutecom.wavesplatform.api.http.utils.UtilsApiRoute→com.wavesplatform.api.http.TimeLimitedRoute
- Direction
- api.http.utils uses api.http, so a change to api.http can break api.http.utils, while a change to api.http.utils can't break api.http.
- Position
- Below the diagonal: api.http.utils uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 31 | High / Critical |
| A05:2025 — Injection | 10 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +7.2 pts | Medium | Keyboard semantics |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +6.1 pts | Medium | Page structure |
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +2.2 pts | Low | REDACTED Scanning |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.2 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +1.9 pts | Medium | Structured logging |
| Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`). | +1.5 pts | Medium | Web-Security Posture |
| Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live. | +1.1 pts | Medium | Incompleteness & stubs |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 3.5 | Mixed | IaC & Container Security: High IaC: REDACTED |
| lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala | 4.2 | Mixed | Change Coupling: Boundary-crossing change coupling: Functions.scala ↔ ErrorMessageEnvironment.scala |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| node/src/main/scala/com/wavesplatform/transaction/smart/WavesEnvironment.scala | 4.7 | Mixed | Change Coupling: Boundary-crossing change coupling: WavesEnvironment.scala ↔ WebEnvironment.scala |
| lang/shared/src/main/scala/com/wavesplatform/lang/utils/package.scala | 4.7 | Mixed | Change Coupling: Boundary-crossing change coupling: package.scala ↔ ErrorMessageEnvironment.scala |
| REDACTED | 5.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala | 5.9 | Mixed | Cyclomatic Complexity: EvaluatorV2.root (cyclomatic 47) |
| node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala | 6.0 | Near-clean | Explicit Debt: TodoComment |
| node/src/main/scala/com/wavesplatform/state/EndorsementStorage.scala | 6.0 | Near-clean | Explicit Debt: TodoComment |
| node/src/main/scala/com/wavesplatform/state/appender/package.scala | 6.0 | Near-clean | Explicit Debt: TodoComment |
| lang/shared/src/main/scala/com/wavesplatform/lang/script/ScriptReader.scala | 6.0 | Near-clean | Explicit Debt: HackComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 65 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 738 of 756 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 899 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `benchmark/src/main/scala/com/wavesplatform/state/Settings.scala`, `grpc-server/src/main/scala/com/wavesplatform/events/settings/BlockchainUpdatesSettings.scala`, `lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/GeneratorSettings.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/Mode.scala`, … (+57 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:34 -------------------- 32 | ENV MALLOC_CONF="prof:true,lg_prof_interval:29,lg_prof_sample:21" 33 | 34 | >>> COPY target /tmp/ 35 | COPY main.conf $RIDE_CONFIG 36 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b7fec57d-8bd9-428a-8fc7-5d3daf529613::hr8rm2xo7nvxzq710n988jbuo: "/target": not found; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
49 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CryptoContext.buildNew at 84. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being RealTransactionWrapper.apply at 27 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: node/src/main/scala/com/wavesplatform/transaction/smart/RealTransactionWrapper.scala (RealTransactionWrapper.apply at 27), node/src/main/scala/com/wavesplatform/transaction/TransactionFactory.scala (TransactionFactory.parseRequest at 24), node/src/main/scala/com/wavesplatform/state/NewTransactionInfo.scala (NewTransactionInfo.txParticipants at 19), node/src/main/scala/com/wavesplatform/network/MessageCodec.scala (MessageCodec.encode at 18), lang/shared/src/main/scala/com/wavesplatform/lang/contract/DApp.scala (DApp.containsSyncCall at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with CryptoContext.buildNew (cyclomatic 84), NarrowTransactionGenerator.generate (cyclomatic 69), Explorer.main (cyclomatic 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D2 · Cognitive Complexity
132 method(s) exceeded the cognitive complexity threshold of 15; the worst was InvokeScriptDiff.apply at 404.
What to do
- Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with InvokeScriptDiff.apply (cognitive 404). — Refactoring it lifts Cognitive Complexity from 3.9 to about 4.5/10.
D3 · God Classes
27 god class(es) detected.
What to do
- Resolve the 14 FileTooLong finding(s) in God Classes — start with PureContext.scala, RocksDBWriter.scala, ExpressionCompiler.scala. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with package.scala, Keys.scala, Blockchain.scala. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with InvokeScriptDiff.scala, EvaluatorV2.scala, NetworkServer.scala. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
37 duplicated block group(s) detected. 3.5 % of the production lines (2,500 of 70,773) are in a reported copy. A further 74 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 8 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with NativeFunction.scala, PureContext.scala, CustomDirectives.scala. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with BlocksApiGrpcImpl.scala, TransactionGen.scala, ScriptResult.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with ScriptEstimatorV2.scala, LazyBlockchain.scala, BatchedReadOnly.scala. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
15 production modules (npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 11 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 65 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with LazyBlockchain.scala, RocksDBWriter.scala. — One of this dimension's main actionable groups (2 warning-level).
D12 · Dependency Hygiene
7 outdated direct sbt declarations. 52 of 53 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 51 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 19 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 3 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. 1 name a copyleft licence without stating its version (e.g. "GNU Lesser General Public Licence"), which this policy bans only at specific versions; they are reported here and not charged, because guessing the version would either accuse an LGPL-2.1 artifact or clear an LGPL-3.0 one.
D15 · Churn × Complexity Hotspots
Top hotspots: node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala (2×28=56)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with InvokeScriptTransactionDiff.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
27 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala. Counted over 324 of the 816 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
75 deducted task-comment markers across 70773 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 61 TodoComment finding(s) in Explicit Debt — start with InvokeScriptTransactionRideV5Suite.scala (15), RocksDBWriter.scala (6), ExchangeWithContractsSuite.scala (4). — One of this dimension's main actionable groups (61 warning-level).
- Resolve the 13 HackComment finding(s) in Explicit Debt — start with Parser.scala (2), package.scala (2), DefaultDAppEnvironmentTracker.scala. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with InvokeScriptResult.scala. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 3 unit(s).
D21 · Naming Consistency
2 naming inconsistencies among 59 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `RestAPISettings` spells `API` where 41 names in the project spell it… finding(s) in Naming Consistency — start with RestAPISettings.scala. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `RocksDBStats` spells `DB` where 16 names in the project spell it `Db` finding(s) in Naming Consistency — start with RocksDBStats.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
3 of 10 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
28 finding(s): 0 critical, 28 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 23 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 9 high, 1 medium, 0 low. semgrep hit a parse error in 38 file(s) — `REDACTED` (line 39, line 40, line 41, …), `lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/GeneratorSettings.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/MultisigTransactionGenerator.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/NarrowTransactionGenerator.scala`, … (+33 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
8 finding(s): 0 critical, 2 high, 6 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
181 of 324 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala. Counted over 324 of the 816 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 178 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (4), Types.scala (2), Parser.scala. — One of this dimension's main actionable groups (178 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with PureContext.scala, ExpressionCompiler.scala, Functions.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ErrorMessageEnvironment.scala↔WebEnvironment.scala 93%; package.scala↔Common.scala 93%; package.scala↔ErrorMessageEnvironment.scala 87%
What to do
- Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with Functions.scala (2), package.scala, WavesEnvironment.scala. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with ErrorMessageEnvironment.scala, NetworkServer.scala, InboundConnectionFilter.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Common.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — lang/doc.template.html:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — lang/doc.template.html:1
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×9) — lang/doc.template.html:7, lang/doc.template.html:15, lang/doc.template.html:40, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — lang/doc.template.html:9
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `BaseGlobal` declares 19 abstract members: `base58Encode`, `base58Decode`, `base64Encode`, `base64Decode`, `curve25519verify`, `rsaVerify`, `keccak256`, `blake2b256`, `sha256`, `merkleVerify`, `pow`, `log`, `powBigInt`, `logBigInt`, `groth16Verify`, `bn256Groth16Verify`, `ecrecover`, `p256verify`, `validateTDXCertChain`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — lang/shared/src/main/scala/com/wavesplatform/lang/v1/BaseGlobal.scala:35
- `Environment[F]` declares 23 abstract members: `chainId`, `inputEntity`, `tthis`, `height`, `transactionById`, `transferTransactionById`, `transactionHeightById`, `assetInfoById`, `lastBlockOpt`, `blockInfoByHeight`, `data`, `hasData`, `resolveAlias`, `accountBalanceOf`, `accountWavesBalanceOf`, `multiPaymentAllowed`, `txId`, `transferTransactionFromProto`, `addressFromString`, `addressFromPublicKey`, `accountScript`, `callScript`, `calculateDelay`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — lang/shared/src/main/scala/com/wavesplatform/lang/v1/traits/Environment.scala:21
- `Blockchain` declares 42 abstract members: `settings`, `height`, `finalizedHeight`, `finalizedHeightAt`, `score`, `blockHeader`, `hitSource`, `carryFee`, `heightOf`, `approvedFeatures`, `activatedFeatures`, `featureVotes`, `blockReward`, `blockRewardVotes`, `wavesAmount`, `transferById`, `transactionInfo`, `transactionInfos`, `transactionMeta`, `transactionSnapshot`, `containsTransaction`, `assetDescription`, `resolveAlias`, `leaseDetails`, `filledVolumeAndFee`, `balanceAtHeight`, `balanceSnapshots`, `accountScript`, `hasAccountScript`, `assetScript`, `accountData`, `hasData`, `leaseBalance`, `leaseBalances`, `balance`, `balances`, `wavesBalances`, `effectiveBalanceBanHeights`, `committedGenerators`, `conflictGenerators`, and 2 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/src/main/scala/com/wavesplatform/state/Blockchain.scala:23
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
- `groth16Verify` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:137
- `bn256Groth16Verify` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:139
- `ecrecover` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:141
- `p256verify` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:143
- `validateTDXCertChain` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:149
- `inputEntity` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:138
- `transactionById` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:139
- `multiPaymentAllowed` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:140
- `txId` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:141
- `transferTransactionFromProto` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:143
- `accountScript` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:148
- `calculateDelay` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:150
- `callScript` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:152
- `finalizedHeight` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:100
- `finalizedHeightAt` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:102
- `carryFee` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:187, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:92
- `transactionInfos` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:189, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:94
- `transactionSnapshot` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:191, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:96
- `leaseBalances` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:193, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:98
- `balances` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:195, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:100
- `wavesBalances` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:197, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:102
- `lastStateHash` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:205, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:106
- `effectiveBalanceBanHeights` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:104
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `groth16Verify` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:137
- `bn256Groth16Verify` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:139
- `ecrecover` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:141
- `p256verify` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:143
- `validateTDXCertChain` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:149
- `inputEntity` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:138
- `transactionById` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:139
- `multiPaymentAllowed` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:140
- `txId` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:141
- `transferTransactionFromProto` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:143
- `accountScript` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:148
- `calculateDelay` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:150
- `callScript` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:152
- `finalizedHeight` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:100
- `finalizedHeightAt` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:102
- `carryFee` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:187, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:92
- `transactionInfos` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:189, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:94
- `transactionSnapshot` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:191, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:96
- `leaseBalances` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:193, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:98
- `balances` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:195, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:100
- `wavesBalances` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:197, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:102
- `lastStateHash` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:205, ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:106
- `effectiveBalanceBanHeights` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:104
- `empty` has an empty body — confirm it's an intentional no-op and not an unfinished method. — lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/Contextful.scala:86
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — lang/tests/src/test/scala/com/wavesplatform/lang/compiler/ExpressionCompilerV1Test.scala:372, lang/tests/src/test/scala/com/wavesplatform/lang/parser/ScriptParserTest.scala:823, lang/tests/src/test/scala/com/wavesplatform/utils/RSATest.scala:328, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/check-pr.yaml:3
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmark/src/test/scala/com/wavesplatform/transaction/smart/VerifierLoggerBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: grpc-server/src/main/scala/com/wavesplatform/api/grpc/GRPCServerExtension.scala:8 — `NettyServerBuilder`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: grpc-server/src/main/scala/com/wavesplatform/api/grpc/GRPCServerExtension.scala:8 — `NettyServerBuilder`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X15 · Unvalidated length from an untrusted reader
- `length` is read from the bytes being parsed at line 91 (`getInt`), then used to size a `new Array[Byte]` at line 98 — and nowhere in its scope is `length` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining and a maximum the format allows before allocating. — node/src/main/scala/com/wavesplatform/serialization/package.scala:98
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — project/Tasks.scala:21, project/Tasks.scala:135
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn` at line 59 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — ride-runner/src/main/scala/com/wavesplatform/ride/runner/entrypoints/WavesRideRunnerWithPreparedStateApp.scala:59
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 796 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by D2, X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 87% | Exemplary | Solid. |
| Readiness | 61% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 43% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:34 -------------------- 32 | ENV MALLOC_CONF="prof:true,lg_prof_interval:29,lg_prof_sample:21" 33 | 34 | >>> COPY target /tmp/ 35 | COPY main.conf $RIDE_CONFIG 36 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b7fec57d-8bd9-428a-8fc7-5d3daf529613::hr8rm2xo7nvxzq710n988jbuo: "/target": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~136244 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 62 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: package.scala ↔ ErrorMessageEnvironment.scala lang/shared/src/main/scala/com/wavesplatform/lang/utils/package.scala:1
- Boundary-crossing change coupling: Functions.scala ↔ ErrorMessageEnvironment.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:1
- Boundary-crossing change coupling: WavesEnvironment.scala ↔ WebEnvironment.scala node/src/main/scala/com/wavesplatform/transaction/smart/WavesEnvironment.scala:1
- Boundary-crossing change coupling: Functions.scala ↔ WebEnvironment.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang lang/doc.template.html:1
- REDACTED
- REDACTED
Serious — 486 finding(s)
- TodoComment ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:118
- TodoComment ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:120
- TodoComment repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/response/ChainDependentMapper.scala:81
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/ExchangeWithContractsSuite.scala:94
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/ExchangeWithContractsSuite.scala:129
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/ExchangeWithContractsSuite.scala:158
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/ExchangeWithContractsSuite.scala:211
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:94
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:111
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:128
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:134
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:152
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:100
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:107
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:117
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:124
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:141
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:148
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:159
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:166
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:136
- TodoComment node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:154
- TodoComment node-it/src/test/scala/com/wavesplatform/it/account/storage/RemoveEntrySuite.scala:63
- TodoComment node/tests/src/test/scala/com/wavesplatform/transaction/assets/exchange/EthOrderSpec.scala:374
- TodoComment node/tests/src/test/scala/com/wavesplatform/state/diffs/BlockDifferTest.scala:245
- Unfinished stub — body is `???` lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:137
- Unfinished stub — body is `???` lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:139
- Unfinished stub — body is `???` lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:141
- Unfinished stub — body is `???` lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:143
- Unfinished stub — body is `???` lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:149
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:138
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:139
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:140
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:141
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:143
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:148
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:150
- Unfinished stub — body is `???` repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:152
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:100
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:102
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:187
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:189
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:191
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:193
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:195
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:197
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:205
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:92
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:94
- Unfinished stub — body is `???` ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:96
- Unfinished stub — body is ??? / NotImplementedError lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:137
- Unfinished stub — body is ??? / NotImplementedError lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:139
- Unfinished stub — body is ??? / NotImplementedError lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:141
- Unfinished stub — body is ??? / NotImplementedError lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:143
- Unfinished stub — body is ??? / NotImplementedError lang/js/src/main/scala/com/wavesplatform/lang/Global.scala:149
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:138
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:139
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:140
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:141
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:143
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:148
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:150
- Unfinished stub — body is ??? / NotImplementedError repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/http/WebEnvironment.scala:152
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:100
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:102
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:187
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:189
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:191
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:193
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:195
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:197
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/ImmutableBlockchain.scala:205
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:92
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:94
- Unfinished stub — body is ??? / NotImplementedError ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:96
- FileTooLong: impl/PureContext.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala
- FileTooLong: database/RocksDBWriter.scala node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala
- FileTooLong: compiler/ExpressionCompiler.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala
- FileTooLong: waves/Functions.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala
- FileTooLong: wavesplatform/TransactionGen.scala node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala
- FileTooLong: invoke/InvokeDiffsCommon.scala node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala
- FileTooLong: transaction/PBTransactions.scala node/src/main/scala/com/wavesplatform/protobuf/transaction/PBTransactions.scala
- FileTooLong: state/BlockchainUpdaterImpl.scala node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala
- FileTooLong: database/package.scala node/src/main/scala/com/wavesplatform/database/package.scala
- FileTooLong: history/Domain.scala node/testkit/src/main/scala/com/wavesplatform/history/Domain.scala
- FileTooLong: impl/CryptoContext.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala
- FileTooLong: REDACTED REDACTED
- FileTooLong: generator/NarrowTransactionGenerator.scala node-generator/src/main/scala/com/wavesplatform/generator/NarrowTransactionGenerator.scala
- FileTooLong: events/events.scala grpc-server/src/main/scala/com/wavesplatform/events/events.scala
- HackComment ride-runner/src/main/scala/com/wavesplatform/ride/runner/environments/DefaultDAppEnvironmentTracker.scala:52
- HackComment ride-runner/src/main/scala/com/wavesplatform/ride/runner/caches/disk/DefaultDiskCaches.scala:98
- HackComment node-it/src/test/scala/com/wavesplatform/it/sync/transactions/OverflowBlock.scala:11
- HackComment node/tests/src/test/scala/com/wavesplatform/transaction/LeaseTransactionSpecification.scala:131
- HackComment node/tests/src/test/scala/com/wavesplatform/finalization/ChallengingAfterFinalizationSuite.scala:40
- HackComment node/testkit/src/main/scala/com/wavesplatform/history/Domain.scala:444
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala:27
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/v1/hacks/package.scala:6
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/utils/package.scala:28
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/script/ContractScript.scala:26
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/script/ScriptReader.scala:13
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/script/v1/ExprScript.scala:19
- HackComment lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala:473
- Data table has no header cells lang/doc.template.html:7
- Data table has no header cells lang/doc.template.html:15
- Data table has no header cells lang/doc.template.html:40
- Data table has no header cells lang/doc.template.html:65
- Data table has no header cells lang/doc.template.html:94
- Data table has no header cells lang/doc.template.html:124
- Data table has no header cells lang/doc.template.html:156
- Data table has no header cells lang/doc.template.html:187
- Data table has no header cells lang/doc.template.html:193
- TooManyMethods: database node/src/main/scala/com/wavesplatform/database/package.scala:41
- TooManyMethods: Keys node/src/main/scala/com/wavesplatform/database/Keys.scala:56
- TooManyMethods: BlockchainExt node/src/main/scala/com/wavesplatform/state/Blockchain.scala:106
- TooManyMethods: TxHelpers node/testkit/src/main/scala/com/wavesplatform/transaction/TxHelpers.scala:39
- TooManyMethods: Caches node/src/main/scala/com/wavesplatform/database/Caches.scala:29
- TooManyMethods: PureContext lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:32
- TooManyMethods: TransactionGenBase node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:32
- TooManyMethods: Types lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Types.scala:7
- Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/NativeFunction.scala:80
- Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1391
- Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/CustomDirectives.scala:40
- Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/block/Block.scala:288
- Edited copy of a member (4 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:120
- Edited copy of a member (4 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:150
- Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/state/patch/CancelAllLeases.scala:25
- Edited copy of a member (4 corresponding lines) node/src/main/scala/com/wavesplatform/crypto/bls/BlsPublicKey.scala:24
- Edited copy of a member (6 corresponding lines) grpc-server/src/main/scala/com/wavesplatform/api/grpc/BlocksApiGrpcImpl.scala:68
- Edited copy of a member (6 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:272
- Edited copy of a member (6 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ScriptResult.scala:233
- Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/state/TxStateSnapshotHashBuilder.scala:181
- Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/transaction/assets/UpdateAssetInfoTransaction.scala:86
- Edited copy of a member (6 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadWrite.scala:14
- Edited copy of a member (6 corresponding lines) node/src/main/scala/com/wavesplatform/network/PeerDatabaseImpl.scala:175
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: InvokeScriptDiff.apply node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptDiff.scala:47
- MethodTooLong: EvaluatorV2.root lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala:36
- MethodTooLong: NetworkServer.apply node/src/main/scala/com/wavesplatform/network/NetworkServer.scala:36
- MethodTooLong: UtxPoolImpl.pack node/src/main/scala/com/wavesplatform/utx/UtxPoolImpl.scala:333
- MethodTooLong: UtilsEvaluator.executeExpression node/src/main/scala/com/wavesplatform/api/http/utils/UtilsEvaluator.scala:99
- Edited copy of a member (15 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v2/ScriptEstimatorV2.scala:27
- Edited copy of a member (15 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:70
- Edited copy of a member (15 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadOnly.scala:36
- Edited copy of a member (15 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/history/package.scala:87
- Edited copy of a member (15 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/db/WithState.scala:63
- Edited copy of a member (12 corresponding lines) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala:87
- Edited copy of a member (12 corresponding lines) node/src/main/scala/com/wavesplatform/account/Recipient.scala:142
- Edited copy of a member (12 corresponding lines) node/src/main/scala/com/wavesplatform/state/diffs/BlockDiffer.scala:293
- Edited copy of a member (12 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:133
- Edited copy of a member (12 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala:93
- Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/requests/SetAssetScriptRequest.scala:34
- Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/database/Caches.scala:518
- Edited copy of a member (8 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/caches/disk/AsBytes.scala:96
- Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/crypto/bls/BlsUtils.scala:52
- Edited copy of a member (8 corresponding lines) node/src/main/scala/com/wavesplatform/mining/BlockChallenger.scala:254
- Duplicated block (12 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:441
- Duplicated block (12 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:493
- Duplicated block (12 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:547
- Duplicated block (12 lines × 2) node/src/main/scala/com/wavesplatform/database/package.scala:547
- Duplicated block (12 lines × 2) node/src/main/scala/com/wavesplatform/utils/generator/BlockchainGeneratorApp.scala:141
- Duplicated block (9 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/package.scala:37
- Duplicated block (9 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:448
- Duplicated block (9 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:474
- Duplicated block (9 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1700
- Duplicated block (9 lines × 2) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala:87
- Duplicated block (7 lines × 2) node/src/main/scala/com/wavesplatform/api/common/AddressTransactions.scala:156
- Duplicated block (7 lines × 2) node/src/main/scala/com/wavesplatform/database/package.scala:504
- Duplicated block (7 lines × 2) ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:367
- Duplicated block (7 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Decompiler.scala:82
- Duplicated block (7 lines × 2) node/src/main/scala/com/wavesplatform/metrics/RocksDBStats.scala:10
- Change coupling: ErrorMessageEnvironment.scala ↔ WebEnvironment.scala repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/node/ErrorMessageEnvironment.scala:1
- Change coupling: NetworkServer.scala ↔ PeerSynchronizer.scala node/src/main/scala/com/wavesplatform/network/NetworkServer.scala:1
- Change coupling: InboundConnectionFilter.scala ↔ PeerSynchronizer.scala node/src/main/scala/com/wavesplatform/network/InboundConnectionFilter.scala:1
- Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:699
- Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala:23
- Edited copy of a member (26 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala:432
- Edited copy of a member (7 corresponding lines) repl/shared/src/main/scala/com/wavesplatform/lang/v1/repl/Implicits.scala:10
- Edited copy of a member (7 corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala:38
- Edited copy of a member (7 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/EvaluationContext.scala:78
- Edited copy of a member (11 corresponding lines) node/src/main/scala/com/wavesplatform/state/SnapshotBlockchain.scala:45
- Edited copy of a member (11 corresponding lines) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:194
- Edited copy of a member (11 corresponding lines) node/src/main/scala/com/wavesplatform/database/Caches.scala:222
- Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala:27
- Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala:30
- Edited copy of a member (1 corresponding lines) node/src/main/scala/com/wavesplatform/database/KeyHelpers.scala:41
- Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/api/http/requests/BurnRequest.scala:23
- Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala:11
- Edited copies of one member (3 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala:29
- Duplicated block (8 lines × 2) node/src/main/scala/com/wavesplatform/api/http/TransactionJsonSerializer.scala:296
- Duplicated block (8 lines × 2) node/src/main/scala/com/wavesplatform/database/package.scala:500
- Duplicated block (8 lines × 2) node/src/main/scala/com/wavesplatform/database/package.scala:543
- Duplicated block (6 lines × 2) node/src/main/scala/com/wavesplatform/database/Caches.scala:518
- Duplicated block (6 lines × 2) node/src/main/scala/com/wavesplatform/api/http/assets/AssetsApiRoute.scala:319
- Duplicated block (6 lines × 2) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:256
- REDACTED
- REDACTED
- Edited copy of a member (18 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/package.scala:28
- Edited copy of a member (18 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:21
- Edited copy of a member (9 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:23
- Edited copy of a member (9 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:86
- Edited copy of a member (5 corresponding lines) node/src/main/scala/com/wavesplatform/transaction/lease/LeaseTransaction.scala:58
- Edited copy of a member (5 corresponding lines) ride-runner/src/main/scala/com/wavesplatform/ride/runner/db/BatchedReadOnly.scala:20
- Edited copy of a member (3 corresponding lines) node/src/main/scala/com/wavesplatform/api/http/utils/UtilsEvaluationRequest.scala:67
- Edited copy of a member (3 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/contract/serialization/ContractSerDeV1.scala:72
- Duplicated block (10–11 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1645
- Duplicated block (10–11 lines × 2) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/OrderSerializer.scala:58
- Duplicated block (10 lines × 2) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala:32
- Duplicated block (10 lines × 2) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/OrderSerializer.scala:46
- Duplicated block (5 lines × 2) node/src/main/scala/com/wavesplatform/database/package.scala:123
- Duplicated block (5 lines × 2) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/LeaseCancelTxSerializer.scala:32
- Low cohesion: LazyBlockchain (LCOM4 7) ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:41
- Low cohesion: RocksDBWriter (LCOM4 4) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:153
- Disposable created and abandoned in the function that made it project/Tasks.scala:21
- Disposable created and abandoned in the function that made it project/Tasks.scala:135
- Page without a main landmark lang/doc.template.html:1
- Anchor without href lang/doc.template.html:9
- CryptoContext.buildNew (cyclomatic 84) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:57
- NarrowTransactionGenerator.generate (cyclomatic 69) node-generator/src/main/scala/com/wavesplatform/generator/NarrowTransactionGenerator.scala:59
- Explorer.main (cyclomatic 67) node/src/main/scala/com/wavesplatform/Explorer.scala:46
- CommonValidation.disallowBeforeActivationTime (cyclomatic 52) node/src/main/scala/com/wavesplatform/state/diffs/CommonValidation.scala:147
- RxExtensionLoader.apply (cyclomatic 51) node/src/main/scala/com/wavesplatform/network/RxExtensionLoader.scala:36
- InvokeScriptDiff.apply (cyclomatic 49) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptDiff.scala:47
- EvaluatorV2.root (cyclomatic 47) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala:36
- Decompiler.expr (cyclomatic 44) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Decompiler.scala:128
- Caches.append (cyclomatic 44) node/src/main/scala/com/wavesplatform/database/Caches.scala:271
- PBTransactions.createVanilla (cyclomatic 44) node/src/main/scala/com/wavesplatform/protobuf/transaction/PBTransactions.scala:114
- InvokeDiffsCommon.foldActions (cyclomatic 43) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala:453
- ApiError.fromValidationError (cyclomatic 34) node/src/main/scala/com/wavesplatform/api/http/ApiError.scala:30
- RocksDBWriter.doRollback (cyclomatic 34) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:997
- RocksDBWriter.doAppend (cyclomatic 33) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:491
- UtxPoolImpl.pack (cyclomatic 32) node/src/main/scala/com/wavesplatform/utx/UtxPoolImpl.scala:333
- CommonValidation.disallowSendingGreaterThanBalance (cyclomatic 31) node/src/main/scala/com/wavesplatform/state/diffs/CommonValidation.scala:30
- Bindings.transactionObject (cyclomatic 29) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Bindings.scala:222
- SerdeV1.desAuxR (cyclomatic 28) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:66
- InvokeScriptTransactionDiff.apply (cyclomatic 28) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala:48
- Importer.startImport (cyclomatic 27) node/src/main/scala/com/wavesplatform/Importer.scala:195
- ResponsivenessLogs.writeEvent (cyclomatic 27) node/src/main/scala/com/wavesplatform/ResponsivenessLogs.scala:37
- ExpressionCompiler.mkIfCases (cyclomatic 26) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:628
- BlockDiffer.fromBlockTraced (cyclomatic 25) node/src/main/scala/com/wavesplatform/state/diffs/BlockDiffer.scala:113
- ExpressionCompiler.compileMatch (cyclomatic 24) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:164
- TypeInferrer.matchTypes (cyclomatic 24) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/TypeInferrer.scala:76
- SerdeV2.desAuxR (cyclomatic 24) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV2.scala:67
- ExchangeTransactionDiff.getPortfolios (cyclomatic 24) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala:85
- InMemory.tryAdd (cyclomatic 23) node/src/main/scala/com/wavesplatform/state/EndorsementStorage.scala:75
- appender.validateFinalizationVoting (cyclomatic 23) node/src/main/scala/com/wavesplatform/state/appender/package.scala:357
- UtxPoolImpl.putNewTx (cyclomatic 23) node/src/main/scala/com/wavesplatform/utx/UtxPoolImpl.scala:74
- EXPR.equals (cyclomatic 22) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Terms.scala:102
- ScriptGen.toString (cyclomatic 22) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:145
- ScriptReader.fromBytes (cyclomatic 21) lang/shared/src/main/scala/com/wavesplatform/lang/script/ScriptReader.scala:16
- ScriptEstimatorV1.apply (cyclomatic 21) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/ScriptEstimatorV1.scala:11
- Functions.callDAppF (cyclomatic 21) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:595
- ScriptRunner.applyGeneric (cyclomatic 21) node/src/main/scala/com/wavesplatform/transaction/smart/script/ScriptRunner.scala:65
- MicroBlockSynchronizer.apply (cyclomatic 20) node/src/main/scala/com/wavesplatform/network/MicroBlockSynchronizer.scala:22
- BlockchainUpdaterImpl.processBlock (cyclomatic 19) node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala:235
- ExtensionAppender.apply (cyclomatic 19) node/src/main/scala/com/wavesplatform/state/appender/ExtensionAppender.scala:25
- TransferDiff.apply (cyclomatic 19) node/src/main/scala/com/wavesplatform/state/diffs/TransferDiff.scala:21
- ContractCompiler.compileContract (cyclomatic 18) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala:130
- ExchangeTransactionDiff.apply (cyclomatic 18) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala:28
- FeeValidation.feeInUnits (cyclomatic 18) node/src/main/scala/com/wavesplatform/state/diffs/FeeValidation.scala:76
- TransactionDiffer.validate (cyclomatic 18) node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:74
- BlockchainState.apply (cyclomatic 18) ride-runner/src/main/scala/com/wavesplatform/ride/runner/BlockchainState.scala:141
- BlockchainGeneratorApp.start (cyclomatic 17) node/src/main/scala/com/wavesplatform/utils/generator/BlockchainGeneratorApp.scala:95
- SerdeV1.serAux (cyclomatic 16) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:158
- SerdeV2.serAux (cyclomatic 16) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV2.scala:151
- StateUpdate.transactionsMetadata (cyclomatic 16) grpc-server/src/main/scala/com/wavesplatform/events/events.scala:458
- Hotspot: node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala:48
- XxxComment node/src/main/scala/com/wavesplatform/state/InvokeScriptResult.scala:179
- InvokeScriptDiff.apply (cognitive 404) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptDiff.scala:47
- appender.validateFinalizationVoting (cognitive 184) node/src/main/scala/com/wavesplatform/state/appender/package.scala:357
- CryptoContext.buildNew (cognitive 158) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:57
- ExpressionCompiler.compileMatch (cognitive 129) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:164
- NarrowTransactionGenerator.generate (cognitive 119) node-generator/src/main/scala/com/wavesplatform/generator/NarrowTransactionGenerator.scala:59
- InvokeDiffsCommon.foldActions (cognitive 107) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala:453
- ContractCompiler.compileContract (cognitive 99) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala:130
- RxExtensionLoader.apply (cognitive 96) node/src/main/scala/com/wavesplatform/network/RxExtensionLoader.scala:36
- ExchangeTransactionDiff.getPortfolios (cognitive 92) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala:85
- InMemory.tryAdd (cognitive 89) node/src/main/scala/com/wavesplatform/state/EndorsementStorage.scala:75
- BlockDiffer.fromBlockTraced (cognitive 85) node/src/main/scala/com/wavesplatform/state/diffs/BlockDiffer.scala:113
- Explorer.main (cognitive 84) node/src/main/scala/com/wavesplatform/Explorer.scala:46
- CommonValidation.disallowSendingGreaterThanBalance (cognitive 69) node/src/main/scala/com/wavesplatform/state/diffs/CommonValidation.scala:30
- UtxPoolImpl.pack (cognitive 67) node/src/main/scala/com/wavesplatform/utx/UtxPoolImpl.scala:333
- UtilsEvaluator.executeExpression (cognitive 66) node/src/main/scala/com/wavesplatform/api/http/utils/UtilsEvaluator.scala:99
- Importer.startImport (cognitive 65) node/src/main/scala/com/wavesplatform/Importer.scala:195
- EvaluatorV2.root (cognitive 63) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala:36
- ScriptReader.fromBytes (cognitive 62) lang/shared/src/main/scala/com/wavesplatform/lang/script/ScriptReader.scala:16
- TransferDiff.apply (cognitive 62) node/src/main/scala/com/wavesplatform/state/diffs/TransferDiff.scala:21
- PBTransactions.createVanilla (cognitive 61) node/src/main/scala/com/wavesplatform/protobuf/transaction/PBTransactions.scala:114
- ExpressionCompiler.compileFold (cognitive 60) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:567
- RocksDBWriter.doRollback (cognitive 59) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:997
- ExchangeTransactionDiff.apply (cognitive 59) node/src/main/scala/com/wavesplatform/state/diffs/ExchangeTransactionDiff.scala:28
- Worker.pullAndWrite (cognitive 59) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala:124
- TransactionDiffer.validateFunds (cognitive 57) node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:140
- InvokeScriptTransactionDiff.apply (cognitive 57) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala:48
- Caches.append (cognitive 56) node/src/main/scala/com/wavesplatform/database/Caches.scala:271
- appender.validateConflictingEndorsement (cognitive 56) node/src/main/scala/com/wavesplatform/state/appender/package.scala:315
- Decompiler.expr (cognitive 55) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Decompiler.scala:128
- InMemory.vote (cognitive 54) node/src/main/scala/com/wavesplatform/state/BlockEndorser.scala:33
- ExtensionAppender.apply (cognitive 50) node/src/main/scala/com/wavesplatform/state/appender/ExtensionAppender.scala:25
- Domain.createBlockE (cognitive 50) node/testkit/src/main/scala/com/wavesplatform/history/Domain.scala:415
- ExpressionCompiler.mkIfCases (cognitive 49) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:628
- EthereumTransactionDiff.apply (cognitive 48) node/src/main/scala/com/wavesplatform/state/diffs/EthereumTransactionDiff.scala:57
- BlockchainUpdaterImpl.processBlock (cognitive 47) node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala:235
- ScriptEstimatorV3.evalLetBlock (cognitive 46) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v3/ScriptEstimatorV3.scala:62
- ScriptEstimatorV3.evalFuncCall (cognitive 46) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v3/ScriptEstimatorV3.scala:166
- BlockChallengerImpl.createChallengingBlock (cognitive 46) node/src/main/scala/com/wavesplatform/mining/BlockChallenger.scala:150
- RocksDBWriter.doAppend (cognitive 45) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:491
- TransactionDiffer.validate (cognitive 45) node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:74
- Functions.callDAppF (cognitive 42) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:595
- ExpressionCompiler.compileFunctionCall (cognitive 41) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:474
- EXPR.equals (cognitive 41) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Terms.scala:102
- Validators.validateBlock (cognitive 41) node/src/main/scala/com/wavesplatform/block/validation/Validators.scala:16
- CommitToGenerationTransactionDiff.apply (cognitive 41) node/src/main/scala/com/wavesplatform/state/diffs/CommitToGenerationTransactionDiff.scala:12
- ExpressionCompiler.compileFunc (cognitive 40) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:333
- CommonValidation.disallowBeforeActivationTime (cognitive 40) node/src/main/scala/com/wavesplatform/state/diffs/CommonValidation.scala:147
- UtxPoolImpl.putNewTx (cognitive 40) node/src/main/scala/com/wavesplatform/utx/UtxPoolImpl.scala:74
- SerdeV1.desAuxR (cognitive 39) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:66
- InvokeDiffsCommon.processActions (cognitive 39) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala:142
- appender.blockConsensusValidation (cognitive 38) node/src/main/scala/com/wavesplatform/state/appender/package.scala:236
- MicroBlockMinerImpl.generateOneMicroBlockTask (cognitive 37) node/src/main/scala/com/wavesplatform/mining/microblocks/MicroBlockMinerImpl.scala:64
- TransactionDiffer.validateCommon (cognitive 37) node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:118
- ScriptGen.toString (cognitive 36) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:145
- TypedScriptGen.contractGen (cognitive 36) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/TypedScriptGen.scala:54
- ScriptEstimatorV1.apply (cognitive 33) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/ScriptEstimatorV1.scala:11
- MinerImpl.forgeBlock (cognitive 33) node/src/main/scala/com/wavesplatform/mining/Miner.scala:183
- TransactionGenBase.dataTransactionGen (cognitive 32) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:796
- SerdeV2.desAuxR (cognitive 31) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV2.scala:67
- MicroBlockSynchronizer.apply (cognitive 31) node/src/main/scala/com/wavesplatform/network/MicroBlockSynchronizer.scala:22
- BlockchainGeneratorApp.start (cognitive 31) node/src/main/scala/com/wavesplatform/utils/generator/BlockchainGeneratorApp.scala:95
- ContractCompiler.compileAnnotatedFunc (cognitive 30) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala:33
- ExpressionCompiler.handleCompositeType (cognitive 30) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:915
- BlockchainUpdaterImpl.processMicroBlock (cognitive 29) node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala:564
- InvokeDiffsCommon.checkActions (cognitive 29) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala:217
- Worker.writeInitial (cognitive 29) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala:86
- Worker.writeTailInitial (cognitive 29) node-generator/src/main/scala/com/wavesplatform/generator/Worker.scala:110
- TypeInferrer.matchTypes (cognitive 28) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/TypeInferrer.scala:76
- ScriptEstimatorV2.evalUserFuncCall (cognitive 28) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v2/ScriptEstimatorV2.scala:103
- ResponsivenessLogs.writeEvent (cognitive 28) node/src/main/scala/com/wavesplatform/ResponsivenessLogs.scala:37
- BlockchainState.apply (cognitive 27) ride-runner/src/main/scala/com/wavesplatform/ride/runner/BlockchainState.scala:141
- ScriptEstimatorV3.evalFuncBlock (cognitive 26) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v3/ScriptEstimatorV3.scala:116
- Format.reads (cognitive 25) node/src/main/scala/com/wavesplatform/state/DataEntry.scala:48
- ScriptRunner.applyGeneric (cognitive 25) node/src/main/scala/com/wavesplatform/transaction/smart/script/ScriptRunner.scala:65
- SerdeV1.deserializeDeclaration (cognitive 24) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:40
- AssetTransactionsDiffs.issue (cognitive 24) node/src/main/scala/com/wavesplatform/state/diffs/AssetTransactionsDiffs.scala:98
- BlockChallengerImpl.challengeMicroblock (cognitive 23) node/src/main/scala/com/wavesplatform/mining/BlockChallenger.scala:84
- SetScriptTransactionDiff.apply (cognitive 23) node/src/main/scala/com/wavesplatform/state/diffs/SetScriptTransactionDiff.scala:23
- JsonManipulations.regexReplace (cognitive 23) ride-runner/src/main/scala/com/wavesplatform/json/JsonManipulations.scala:19
- ScriptEstimatorV3.saveGlobalLetCost (cognitive 22) lang/shared/src/main/scala/com/wavesplatform/lang/v1/estimator/v3/ScriptEstimatorV3.scala:75
- InvokeScriptResult.fromLangResult (cognitive 22) node/src/main/scala/com/wavesplatform/state/InvokeScriptResult.scala:162
- BalanceDiffValidation.apply (cognitive 22) node/src/main/scala/com/wavesplatform/state/diffs/BalanceDiffValidation.scala:19
- FeeValidation.feeInUnits (cognitive 22) node/src/main/scala/com/wavesplatform/state/diffs/FeeValidation.scala:76
- TransactionGenBase.issueReissueBurnGeneratorP (cognitive 22) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:417
- FastBase58.decode (cognitive 21) lang/shared/src/main/scala/com/wavesplatform/common/utils/FastBase58.scala:55
- BaseGlobal.median (cognitive 21) lang/shared/src/main/scala/com/wavesplatform/lang/v1/BaseGlobal.scala:356
- TransactionGenBase.invokeScriptGen (cognitive 21) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:495
- TypedScriptGen.funcGen (cognitive 20) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/TypedScriptGen.scala:23
- CommonGeneratorsApi.apply (cognitive 20) node/src/main/scala/com/wavesplatform/api/common/CommonGeneratorsApi.scala:20
- RocksDBWriter.merge3 (cognitive 20) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:90
- MinerImpl.generateBlockTask (cognitive 20) node/src/main/scala/com/wavesplatform/mining/Miner.scala:305
- PBOrders.vanilla (cognitive 20) node/src/main/scala/com/wavesplatform/protobuf/transaction/PBOrders.scala:20
- InMemory.tryCollectAndClear (cognitive 20) node/src/main/scala/com/wavesplatform/state/EndorsementStorage.scala:150
- FinalizationState.isParentFinalized (cognitive 20) node/src/main/scala/com/wavesplatform/state/FinalizationState.scala:94
- DiffsCommon.processLease (cognitive 20) node/src/main/scala/com/wavesplatform/state/diffs/DiffsCommon.scala:146
- DAppEnvironment.callScript (cognitive 20) node/src/main/scala/com/wavesplatform/transaction/smart/WavesEnvironment.scala:425
- AddressDataIterator.doComputeNext (cognitive 19) node/src/main/scala/com/wavesplatform/api/common/CommonAccountsApi.scala:153
- BlockchainUpdaterImpl.removeAfter (cognitive 19) node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala:513
- AssetTransactionsDiffs.updateInfo (cognitive 19) node/src/main/scala/com/wavesplatform/state/diffs/AssetTransactionsDiffs.scala:24
- AssetTransactionsDiffs.setAssetScript (cognitive 19) node/src/main/scala/com/wavesplatform/state/diffs/AssetTransactionsDiffs.scala:72
- FeeValidation.feeAfterSponsorship (cognitive 19) node/src/main/scala/com/wavesplatform/state/diffs/FeeValidation.scala:122
- ResumableInputStream.openHttp (cognitive 19) node/src/main/scala/com/wavesplatform/utils/ResumableInputStream.scala:75
- ScriptResult.processScriptTransfer (cognitive 18) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ScriptResult.scala:107
- grpc.wrapObservable (cognitive 18) grpc-server/src/main/scala/com/wavesplatform/api/grpc/package.scala:76
- Application.run (cognitive 18) REDACTED:128
- BlockSnapshotIterator.computeNext (cognitive 18) node/src/main/scala/com/wavesplatform/Exporter.scala:197
- RocksDBWriter.committedHeights (cognitive 18) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:1492
- Verifier.assets (cognitive 18) node/src/main/scala/com/wavesplatform/transaction/smart/Verifier.scala:90
- BaseGlobal.divide (cognitive 17) lang/shared/src/main/scala/com/wavesplatform/lang/v1/BaseGlobal.scala:294
- TypeInferrer.apply (cognitive 17) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/TypeInferrer.scala:10
- PureContext.makeStringF (cognitive 17) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1252
- BalanceIterator.findNextBalance (cognitive 17) node/src/main/scala/com/wavesplatform/api/common/BalanceDistribution.scala:25
- HandshakeHandler.channelRead (cognitive 17) node/src/main/scala/com/wavesplatform/network/HandshakeHandler.scala:89
- NetworkServer.apply (cognitive 17) node/src/main/scala/com/wavesplatform/network/NetworkServer.scala:36
- BlockchainUpdaterImpl.computeNextReward (cognitive 17) node/src/main/scala/com/wavesplatform/state/BlockchainUpdaterImpl.scala:161
- appender.appendKeyBlock (cognitive 17) node/src/main/scala/com/wavesplatform/state/appender/package.scala:85
- appender.processBlockWithChallenge (cognitive 17) node/src/main/scala/com/wavesplatform/state/appender/package.scala:186
- DiffsCommon.processLeaseCancel (cognitive 17) node/src/main/scala/com/wavesplatform/state/diffs/DiffsCommon.scala:188
- TransactionGenBase.exchangeV2GeneratorP (cognitive 17) node/testkit/src/main/scala/com/wavesplatform/TransactionGen.scala:677
- WavesRideRunnerWithPreparedStateApp.run (cognitive 17) ride-runner/src/main/scala/com/wavesplatform/ride/runner/entrypoints/WavesRideRunnerWithPreparedStateApp.scala:74
- API.parseAndCompile (cognitive 16) lang/shared/src/main/scala/com/wavesplatform/lang/API.scala:88
- ExpressionCompiler.compileLet (cognitive 16) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:309
- ExpressionCompiler.compileGetter (cognitive 16) lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:447
- PureContext.fractionBigIntRounds (cognitive 16) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:449
- Importer.main (cognitive 16) node/src/main/scala/com/wavesplatform/Importer.scala:327
- TxByAddressIterator.computeNext (cognitive 16) node/src/main/scala/com/wavesplatform/api/common/AddressTransactions.scala:144
- RocksDBWriter.balanceSnapshots (cognitive 16) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:1402
- TransactionDiffer.feePortfolios (cognitive 16) node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:345
- InvokeDiffsCommon.checkCallResultLimits (cognitive 16) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeDiffsCommon.scala:778
- InvokeScriptTransactionDiff.evaluateV2 (cognitive 16) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptTransactionDiff.scala:292
- BlockchainUpdaterExt.processBlock (cognitive 16) node/testkit/src/main/scala/com/wavesplatform/history/Domain.scala:652
- DefaultRequestService.start (cognitive 16) ride-runner/src/main/scala/com/wavesplatform/ride/runner/requests/RequestService.scala:95
- REDACTED
- Change-coupling hub: Common.scala → package.scala, Functions.scala, WavesEnvironment.scala, ErrorMessageEnvironment.scala, WebEnvironment.scala lang/testkit/src/main/scala/com/wavesplatform/lang/Common.scala
- Change coupling clique: EvaluatorV2.scala, InvokeScriptDiff.scala, InvokeScriptTransactionDiff.scala lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala
- Members sharing a duplicated core (4 members, 50+ identical tokens) node/src/main/scala/com/wavesplatform/database/package.scala:496
- Edited copy of a member (80 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:158
- Edited copy of a member (58 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/serialization/SerdeV1.scala:66
- Edited copy of a member (32 corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/utils/package.scala:32
- Edited copy of a member (45 corresponding lines) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:836
- Edited copy of a member (42 corresponding lines) node/src/main/scala/com/wavesplatform/state/diffs/invoke/InvokeScriptDiff.scala:399
- Edited copies of one member (4 members, 22+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala:45
- Edited copies of one member (4 members, 18+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1631
- Edited copies of one member (4 members, 23+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:518
- Edited copy of a member (23 corresponding lines) node/src/main/scala/com/wavesplatform/state/appender/package.scala:139
- Edited copies of one member (3 members, 14+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/SetAssetScriptTxSerializer.scala:44
- Edited copy of a member (19 corresponding lines) node/src/main/scala/com/wavesplatform/database/RocksDBWriter.scala:295
- Edited copies of one member (6 members, 10+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala:22
- Edited copies of one member (3 members, 16+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/SetAssetScriptTxSerializer.scala:22
- Edited copy of a member (2 corresponding lines) lang/testkit/src/main/scala/com/wavesplatform/lang/v1/testing/ScriptGen.scala:19
- Edited copies of one member (3 members, 7+ corresponding lines) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/NativeFunction.scala:54
- Edited copies of one member (6 members, 5+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/CreateAliasTxSerializer.scala:34
- Edited copies of one member (4 members, 3+ corresponding lines) node/src/main/scala/com/wavesplatform/database/package.scala:114
- Edited copies of one member (3 members, 6+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/ReissueTxSerializer.scala:14
- Edited copy of a member (10 corresponding lines) node/src/main/scala/com/wavesplatform/utils/JsonFileStorage.scala:68
- Edited copies of one member (5 members, 2+ corresponding lines) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/DataTxSerializer.scala:54
- Duplicated block (30 lines × 2) ride-runner/src/main/scala/com/wavesplatform/ride/runner/entrypoints/WavesRideRunnerCompareService.scala:71
- Duplicated block (17–18 lines × 2) node/src/main/scala/com/wavesplatform/utils/generator/BlockchainGeneratorApp.scala:154
- Duplicated block (6–14 lines × 3) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala:32
- Duplicated block (13 lines × 3) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:128
- Duplicated block (13 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:703
- Duplicated block (6–12 lines × 3) node/src/main/scala/com/wavesplatform/transaction/serialization/impl/BurnTxSerializer.scala:28
- Duplicated block (9–12 lines × 2) node/src/main/scala/com/wavesplatform/state/appender/package.scala:145
- Duplicated block (9–11 lines × 2) lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1642
- Duplicated block (8–9 lines × 2) node/src/main/scala/com/wavesplatform/block/Block.scala:227
- Duplicated block (5 lines × 3) node/src/main/scala/com/wavesplatform/state/appender/package.scala:101
- Off the main sequence: node
- Length read from the parsed input is spent without ever being bounded node/src/main/scala/com/wavesplatform/serialization/package.scala:98
Minor — 217 finding(s)
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala:1
- Orphaned file node/testkit/src/main/scala/com/wavesplatform/history/Domain.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/CryptoContext.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/api/http/TransactionJsonSerializer.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/ride/runner/blockchain/LazyBlockchain.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractCompiler.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/EvaluatorV2.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/api/http/ApiError.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Types.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/state/diffs/TransactionDiffer.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Bindings.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/ride/runner/caches/disk/DefaultDiskCaches.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/BaseGlobal.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/ride/runner/entrypoints/WavesRideRunnerWithPreparedStateApp.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/ride/runner/input/RideRunnerInputParser.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ScriptResult.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/transaction/smart/Verifier.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/Decompiler.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/ride/runner/requests/RequestService.scala:1
- Orphaned file ride-runner/src/main/scala/com/wavesplatform/api/DefaultBlockchainApi.scala:1
- Orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ContractScriptCompactor.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/utils/generator/MinerChallengeSimulator.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/GenesisBlockGenerator.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/state/StateSnapshot.scala:1
- Orphaned file node/src/main/scala/com/wavesplatform/mining/BlockChallenger.scala:1
- Disabled test lang/tests/src/test/scala/com/wavesplatform/lang/compiler/ExpressionCompilerV1Test.scala:372
- Disabled test lang/tests/src/test/scala/com/wavesplatform/lang/parser/ScriptParserTest.scala:823
- Disabled test lang/tests/src/test/scala/com/wavesplatform/utils/RSATest.scala:328
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeListForCallable.scala:129
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeListForCallable.scala:145
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeListForCallable.scala:162
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:95
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:112
- Disabled test node-it/src/test/scala/com/wavesplatform/it/sync/smartcontract/InvokeScriptTransactionRideV5Suite.scala:129
- Duplicated predicate node/src/main/scala/com/wavesplatform/utils/generator/BlockchainGeneratorApp.scala:230
- Duplicated predicate node/src/main/scala/com/wavesplatform/state/diffs/DiffsCommon.scala:52
- Duplicated predicate node/src/main/scala/com/wavesplatform/api/common/AddressPortfolio.scala:41
- Duplicated predicate node/src/main/scala/com/wavesplatform/transaction/serialization/impl/DataTxSerializer.scala:60
- Duplicated predicate node/src/main/scala/com/wavesplatform/database/ReadOnlyDB.scala:50
- Fat interface: BaseGlobal (19 abstract members) lang/shared/src/main/scala/com/wavesplatform/lang/v1/BaseGlobal.scala:35
- Fat interface: Environment[F] (23 abstract members) lang/shared/src/main/scala/com/wavesplatform/lang/v1/traits/Environment.scala:21
- Fat interface: Blockchain (42 abstract members) node/src/main/scala/com/wavesplatform/state/Blockchain.scala:23
- Most significant orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/PureContext.scala:1
- Most significant orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/compiler/ExpressionCompiler.scala:1
- Most significant orphaned file lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/ctx/impl/waves/Functions.scala:1
- Subsumed condition operand project/ExtensionPackaging.scala:139
- Subsumed condition operand project/ExtensionPackaging.scala:139
- Off-boarding risk: anonymized user #1
- `RestAPISettings` spells `API` where 41 names in the project spell it `Api` node/src/main/scala/com/wavesplatform/settings/RestAPISettings.scala:5
- `RocksDBStats` spells `DB` where 16 names in the project spell it `Db` ride-runner/src/main/scala/com/wavesplatform/database/rocksdb/stats/RocksDBStats.scala:8
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- Empty method body lang/shared/src/main/scala/com/wavesplatform/lang/v1/evaluator/Contextful.scala:86
- No SAST .github/workflows/check-pr.yaml:3
- Dependabot does not watch npm REDACTED:2
- No changelog
- Benchmarks don't track allocations benchmark/src/test/scala/com/wavesplatform/transaction/smart/VerifierLoggerBenchmark.scala
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Interpolated log message defeats structured logging ride-runner/src/main/scala/com/wavesplatform/ride/runner/entrypoints/WavesRideRunnerWithPreparedStateApp.scala:59
- Scala's null is not held to the type system everywhere
Minor — 7 finding(s)
- Outdated: org.apache.commons:commons-lang3
- Outdated: org.bouncycastle:bcprov-jdk18on
- Outdated: org.conscrypt:conscrypt-openjdk-uber
- Outdated: org.jline:jline-reader
- Outdated: org.jsoup:jsoup
- Outdated: tools.jackson.core:jackson-core
- Outdated: tools.jackson.core:jackson-databind
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d0ce52bbff234868a72b01e03a1f75de/history.json --exit-code 0 --source . | 305 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d0ce52bbff234868a72b01e03a1f75de/tree.json --exit-code 0 --source . | 125 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude node/src/main/resources/swagger-ui . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 62 file(s) — `benchmark/src/main/scala/com/wavesplatform/state/Settings.scala`, `grpc-server/src/main/scala/com/wavesplatform/events/settings/BlockchainUpdatesSettings.scala`, `lang/shared/src/main/scala/com/wavesplatform/lang/v1/parser/Parser.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/GeneratorSettings.scala`, `node-generator/src/main/scala/com/wavesplatform/generator/Mode.scala`, … (+57 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |