Executive summary
ACINQ/eclair is rated At risk because critical security findings are open. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 47, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 7 points. Recording design decisions comes next, worth about 2 points. Raising Production Readiness to 62 would lift the score to about 64.
Fifteen known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nine weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the two unsafe settings in infrastructure or container files need changing to safe values. The two sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 57,964 lines, about €130,000 to rebuild.
If Production Readiness rose from 47 to 62, the lowest score rated Strong, the score would rise from 57 to about 64.
New since the last survey: 7 findings
- Cognitive Complexity · ReplaceableTxPrePublisher.checkLocalCommitAnchorPreconditions (cognitive 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala
- Cognitive Complexity · Transactions.isWitnessStandard (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala
- Churn × Complexity Hotspots · Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala
- Churn × Complexity Hotspots · Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala
- Knowledge Freshness · Orphaned knowledge eclair-core/src/main/scala/fr/acinq/eclair/crypto/Noise.scala
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €130,000 · Estimate
| Cost to rebuild | €45,000 to €220,000, for 744 to 2,361 hours of work, about 0.9 person-years for 1 to 2 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.8 at a score of 57. 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: 57,964 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: which parts of the code depend on which
| uses → | 1 blockchain | 2 channel.Upstream | 3 crypto.Sphinx.RouteBlinding | 4 crypto.TransportHandler | 5 io.PeerReadyManager | 6 payment.relay.Relayer | 7 crypto.Sphinx | 8 crypto.keymanager | 9 io.PeerReadyNotifier | 10 wire.protocol.OfferTypes | 11 db | 12 io.MessageRelay | 13 transactions.Transactions | 14 payment | 15 wire.protocol.LiquidityAds | 16 wire.protocol.MessageOnion | 17 message.OnionMessages | 18 payment.offer.OfferManager | 19 payment.receive.MultiPartHandler | 20 payment.offer.OfferManager.InvoiceRequestActor | 21 router | 22 router.Router | 23 io.PeerConnection | 24 io | 25 io.Peer | 26 wire.protocol | 27 transactions | 28 channel.fund.InteractiveTxSigningSession | 29 channel.fund.InteractiveTxBuilder | 30 blockchain.bitcoind.rpc | 31 blockchain.fee | 32 channel | 33 balance.BalanceActor | 34 payment.send.PaymentInitiator | 35 payment.send | 36 fr.acinq.eclair | 37 channel.publish.TxPublisher | 38 payment.relay.NodeRelay | 39 channel.fsm | 40 payment.relay |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 blockchain | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 2 channel.Upstream | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 3 crypto.Sphinx.RouteBlinding | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 crypto.TransportHandler | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 io.PeerReadyManager | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 payment.relay.Relayer | 4 | 3 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 7 crypto.Sphinx | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 8 crypto.keymanager | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 io.PeerReadyNotifier | 1 | 3 | 12 | 5 | ||||||||||||||||||||||||||||||||||||
| 10 wire.protocol.OfferTypes | 3 | 1 | 4 | 13 | ||||||||||||||||||||||||||||||||||||
| 11 db | 1 | 1 | 2 | 9 | 1 | 3 | 5 | 9 | 3 | 24 | ||||||||||||||||||||||||||||||
| 12 io.MessageRelay | 1 | 1 | 1 | 1 | 1 | 5 | 3 | |||||||||||||||||||||||||||||||||
| 13 transactions.Transactions | 21 | 14 | ||||||||||||||||||||||||||||||||||||||
| 14 payment | 1 | 1 | 4 | 3 | 9 | 4 | 2 | 1 | 39 | |||||||||||||||||||||||||||||||
| 15 wire.protocol.LiquidityAds | 1 | 3 | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 16 wire.protocol.MessageOnion | 1 | 1 | 19 | 2 | ||||||||||||||||||||||||||||||||||||
| 17 message.OnionMessages | 1 | 1 | 1 | 10 | 7 | |||||||||||||||||||||||||||||||||||
| 18 payment.offer.OfferManager | 1 | 5 | 1 | 3 | 2 | 9 | 4 | |||||||||||||||||||||||||||||||||
| 19 payment.receive.MultiPartHandler | 1 | 2 | 3 | 2 | 3 | 1 | 2 | 6 | 2 | 10 | ||||||||||||||||||||||||||||||
| 20 payment.offer.OfferManager.InvoiceRequestActor | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 6 | 3 | |||||||||||||||||||||||||||||||
| 21 router | 1 | 4 | 2 | 1 | 2 | 1 | 1 | 2 | 26 | 24 | 5 | 1 | 38 | |||||||||||||||||||||||||||
| 22 router.Router | 2 | 1 | 1 | 1 | 1 | 1 | 5 | 2 | 20 | 7 | 35 | |||||||||||||||||||||||||||||
| 23 io.PeerConnection | 10 | 1 | 1 | 3 | 7 | 3 | ||||||||||||||||||||||||||||||||||
| 24 io | 1 | 1 | 1 | 1 | 1 | 4 | 8 | 4 | 5 | 5 | 7 | 14 | ||||||||||||||||||||||||||||
| 25 io.Peer | 1 | 1 | 8 | 1 | 2 | 1 | 1 | 3 | 2 | 10 | 2 | 10 | 2 | 11 | ||||||||||||||||||||||||||
| 26 wire.protocol | 2 | 6 | 1 | 36 | 4 | 2 | 15 | 2 | 9 | 10 | 72 | |||||||||||||||||||||||||||||
| 27 transactions | 3 | 11 | 3 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 28 channel.fund.InteractiveTxSigningSession | 1 | 1 | 1 | 3 | 1 | 2 | 7 | 1 | ||||||||||||||||||||||||||||||||
| 29 channel.fund.InteractiveTxBuilder | 1 | 2 | 1 | 3 | 2 | 7 | 5 | 1 | 7 | 10 | 8 | 9 | ||||||||||||||||||||||||||||
| 30 blockchain.bitcoind.rpc | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 31 blockchain.fee | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 channel | 1 | 8 | 1 | 10 | 1 | 17 | 10 | 12 | 55 | 5 | 1 | 26 | 8 | 99 | ||||||||||||||||||||||||||
| 33 balance.BalanceActor | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 payment.send.PaymentInitiator | 1 | 5 | 1 | 5 | 2 | 2 | 2 | 9 | ||||||||||||||||||||||||||||||||
| 35 payment.send | 1 | 4 | 1 | 5 | 4 | 4 | 3 | 1 | 6 | 3 | 1 | 24 | ||||||||||||||||||||||||||||
| 36 fr.acinq.eclair | 1 | 1 | 2 | 5 | 3 | 3 | 5 | 2 | 7 | 7 | 1 | 1 | 1 | 1 | 10 | 2 | 2 | 4 | 11 | 10 | 26 | 1 | 3 | 2 | ||||||||||||||||
| 37 channel.publish.TxPublisher | 1 | 1 | 2 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||||
| 38 payment.relay.NodeRelay | 1 | 1 | 1 | 14 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 39 channel.fsm | 2 | 2 | 1 | 2 | 1 | 6 | 1 | 2 | 1 | 23 | 1 | 3 | 1 | |||||||||||||||||||||||||||
| 40 payment.relay | 1 | 2 | 1 | 1 | 1 | 5 | 1 | 6 | 1 | 3 | 5 | 11 | 2 |
1→31 blockchain uses blockchain.fee part of a loop✕
- Connections
- 3 pairs of types, where a type in blockchain uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.blockchain.CurrentFeerates→fr.acinq.eclair.blockchain.fee.FeeratesPerKwfr.acinq.eclair.blockchain.Monitoring→fr.acinq.eclair.blockchain.fee.FeeratesPerKwfr.acinq.eclair.blockchain.OnChainChannelFunder→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- blockchain uses blockchain.fee, so a change to blockchain.fee can break blockchain, while a change to blockchain can't break blockchain.fee.
- 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.
1→36 blockchain uses fr.acinq.eclair part of a loop✕
- Connections
- 1 pair of types, where a type in blockchain uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.blockchain.CurrentBlockHeight→fr.acinq.eclair.BlockHeight
- Direction
- blockchain uses fr.acinq.eclair, so a change to fr.acinq.eclair can break blockchain, while a change to blockchain can't break fr.acinq.eclair.
- 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.
2→32 channel.Upstream uses channel part of a loop✕
- Connections
- 2 pairs of types, where a type in channel.Upstream uses a type in channel.
- The types involved
fr.acinq.eclair.channel.Upstream.Cold→fr.acinq.eclair.channel.Upstreamfr.acinq.eclair.channel.Upstream.Hot→fr.acinq.eclair.channel.Upstream
- Direction
- channel.Upstream uses channel, so a change to channel can break channel.Upstream, while a change to channel.Upstream can't break channel.
- 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.
2→36 channel.Upstream uses fr.acinq.eclair part of a loop✕
- Connections
- 1 pair of types, where a type in channel.Upstream uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.channel.Upstream.Local→fr.acinq.eclair.MilliSatoshi
- Direction
- channel.Upstream uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel.Upstream, while a change to channel.Upstream can't break fr.acinq.eclair.
- 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.
3→36 crypto.Sphinx.RouteBlinding uses fr.acinq.eclair part of a loop✕
- Connections
- 2 pairs of types, where a type in crypto.Sphinx.RouteBlinding uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.crypto.Sphinx.RouteBlinding.FirstNode→fr.acinq.eclair.EncodedNodeId
- Direction
- crypto.Sphinx.RouteBlinding uses fr.acinq.eclair, so a change to fr.acinq.eclair can break crypto.Sphinx.RouteBlinding, while a change to crypto.Sphinx.RouteBlinding can't break fr.acinq.eclair.
- 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.
4→26 crypto.TransportHandler uses wire.protocol part of a loop✕
- Connections
- 2 pairs of types, where a type in crypto.TransportHandler uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.crypto.TransportHandler.NormalData→fr.acinq.eclair.wire.protocol.LightningMessagefr.acinq.eclair.crypto.TransportHandler.SendBuffer→fr.acinq.eclair.wire.protocol.LightningMessage
- Direction
- crypto.TransportHandler uses wire.protocol, so a change to wire.protocol can break crypto.TransportHandler, while a change to crypto.TransportHandler can't break wire.protocol.
- 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.
5→33 io.PeerReadyManager uses balance.BalanceActor part of a loop✕
- Connections
- 3 pairs of types, where a type in io.PeerReadyManager uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.io.PeerReadyManager.Completed→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyManager.List→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyManager.Register→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- io.PeerReadyManager uses balance.BalanceActor, so a change to balance.BalanceActor can break io.PeerReadyManager, while a change to io.PeerReadyManager can't break balance.BalanceActor.
- 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→26 payment.relay.Relayer uses wire.protocol part of a loop✕
- Connections
- 4 pairs of types, where a type in payment.relay.Relayer uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.relay.Relayer.OutgoingChannel→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.payment.relay.Relayer.OutgoingChannel→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.payment.relay.Relayer.OutgoingChannelParams→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.payment.relay.Relayer.RelayForward→fr.acinq.eclair.wire.protocol.UpdateAddHtlc
- Direction
- payment.relay.Relayer uses wire.protocol, so a change to wire.protocol can break payment.relay.Relayer, while a change to payment.relay.Relayer can't break wire.protocol.
- 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→32 payment.relay.Relayer uses channel part of a loop✕
- Connections
- 3 pairs of types, where a type in payment.relay.Relayer uses a type in channel.
- The types involved
fr.acinq.eclair.payment.relay.Relayer.ChannelBalance→fr.acinq.eclair.channel.ShortIdAliasesfr.acinq.eclair.payment.relay.Relayer.OutgoingChannel→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.payment.relay.Relayer.OutgoingChannel→fr.acinq.eclair.channel.ShortIdAliases
- Direction
- payment.relay.Relayer uses channel, so a change to channel can break payment.relay.Relayer, while a change to payment.relay.Relayer can't break channel.
- 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→33 payment.relay.Relayer uses balance.BalanceActor part of a loop✕
- Connections
- 1 pair of types, where a type in payment.relay.Relayer uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.relay.Relayer.ChildActors→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.relay.Relayer uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.relay.Relayer, while a change to payment.relay.Relayer can't break balance.BalanceActor.
- 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→36 payment.relay.Relayer uses fr.acinq.eclair part of a loop✕
- Connections
- 5 pairs of types, where a type in payment.relay.Relayer uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.relay.Relayer.AsyncPaymentsParams→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.payment.relay.Relayer.ChannelBalance→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.relay.Relayer.ChannelBalance→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.payment.relay.Relayer.OutgoingChannel→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.payment.relay.Relayer.RelayFees→fr.acinq.eclair.MilliSatoshi
- Direction
- payment.relay.Relayer uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.relay.Relayer, while a change to payment.relay.Relayer can't break fr.acinq.eclair.
- 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.
7→3 crypto.Sphinx uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in crypto.Sphinx uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.crypto.Sphinx.RouteBlinding→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRouteDetails
- Direction
- crypto.Sphinx uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break crypto.Sphinx, while a change to crypto.Sphinx can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: crypto.Sphinx uses a module listed above it, which is the healthy direction.
7→26 crypto.Sphinx uses wire.protocol part of a loop✕
- Connections
- 4 pairs of types, where a type in crypto.Sphinx uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.crypto.Sphinx.DecryptedFailurePacket→fr.acinq.eclair.wire.protocol.FailureMessagefr.acinq.eclair.crypto.Sphinx.DecryptedPacket→fr.acinq.eclair.wire.protocol.OnionRoutingPacketfr.acinq.eclair.crypto.Sphinx.FailurePacket→fr.acinq.eclair.wire.protocol.FailureMessagefr.acinq.eclair.crypto.Sphinx.PacketAndSecrets→fr.acinq.eclair.wire.protocol.OnionRoutingPacket
- Direction
- crypto.Sphinx uses wire.protocol, so a change to wire.protocol can break crypto.Sphinx, while a change to crypto.Sphinx can't break wire.protocol.
- 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.
8→5 crypto.keymanager uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in crypto.keymanager uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.crypto.keymanager.LocalNodeKeyManager→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- crypto.keymanager uses io.PeerReadyManager, so a change to io.PeerReadyManager can break crypto.keymanager, while a change to crypto.keymanager can't break io.PeerReadyManager.
- Position
- Below the diagonal: crypto.keymanager uses a module listed above it, which is the healthy direction.
8→32 crypto.keymanager uses channel part of a loop✕
- Connections
- 2 pairs of types, where a type in crypto.keymanager uses a type in channel.
- The types involved
fr.acinq.eclair.crypto.keymanager.ChannelKeyManager→fr.acinq.eclair.channel.ChannelConfigfr.acinq.eclair.crypto.keymanager.LocalChannelKeyManager→fr.acinq.eclair.channel.ChannelConfig
- Direction
- crypto.keymanager uses channel, so a change to channel can break crypto.keymanager, while a change to crypto.keymanager can't break channel.
- 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→5 io.PeerReadyNotifier uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in io.PeerReadyNotifier uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.io.PeerReadyNotifier.WrappedRegistered→fr.acinq.eclair.io.PeerReadyManager.Registered
- Direction
- io.PeerReadyNotifier uses io.PeerReadyManager, so a change to io.PeerReadyManager can break io.PeerReadyNotifier, while a change to io.PeerReadyNotifier can't break io.PeerReadyManager.
- Position
- Below the diagonal: io.PeerReadyNotifier uses a module listed above it, which is the healthy direction.
9→25 io.PeerReadyNotifier uses io.Peer part of a loop✕
- Connections
- 3 pairs of types, where a type in io.PeerReadyNotifier uses a type in io.Peer.
- The types involved
fr.acinq.eclair.io.PeerReadyNotifier.PeerReady→fr.acinq.eclair.io.Peer.ChannelInfofr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerChannels→fr.acinq.eclair.io.Peer.PeerChannelsfr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerInfo→fr.acinq.eclair.io.Peer.GetPeerChannels
- Direction
- io.PeerReadyNotifier uses io.Peer, so a change to io.Peer can break io.PeerReadyNotifier, while a change to io.PeerReadyNotifier can't break io.Peer.
- 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→33 io.PeerReadyNotifier uses balance.BalanceActor part of a loop✕
- Connections
- 12 pairs of types, where a type in io.PeerReadyNotifier uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.io.PeerReadyNotifier.CheckChannelsReady→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.NewBlockNotTimedOut→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.NotifyWhenPeerReady→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.PeerConnected→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.PeerDisconnected→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.PeerNotConnected→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.Timeout→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.ToBeIgnored→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.WrappedListing→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerChannels→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerInfo→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier.WrappedRegistered→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- io.PeerReadyNotifier uses balance.BalanceActor, so a change to balance.BalanceActor can break io.PeerReadyNotifier, while a change to io.PeerReadyNotifier can't break balance.BalanceActor.
- 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→36 io.PeerReadyNotifier uses fr.acinq.eclair part of a loop✕
- Connections
- 5 pairs of types, where a type in io.PeerReadyNotifier uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.io.PeerReadyNotifier.NewBlockNotTimedOut→fr.acinq.eclair.BlockHeightfr.acinq.eclair.io.PeerReadyNotifier.PeerReady→fr.acinq.eclair.Featuresfr.acinq.eclair.io.PeerReadyNotifier.PeerReady→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerInfo→fr.acinq.eclair.Featuresfr.acinq.eclair.io.PeerReadyNotifier.WrappedPeerInfo→fr.acinq.eclair.InitFeature
- Direction
- io.PeerReadyNotifier uses fr.acinq.eclair, so a change to fr.acinq.eclair can break io.PeerReadyNotifier, while a change to io.PeerReadyNotifier can't break fr.acinq.eclair.
- 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→3 wire.protocol.OfferTypes uses crypto.Sphinx.RouteBlinding✕
- Connections
- 3 pairs of types, where a type in wire.protocol.OfferTypes uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.wire.protocol.OfferTypes.BlindedPath→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoutefr.acinq.eclair.wire.protocol.OfferTypes.InvoicePaths→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoutefr.acinq.eclair.wire.protocol.OfferTypes.OfferPaths→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- wire.protocol.OfferTypes uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break wire.protocol.OfferTypes, while a change to wire.protocol.OfferTypes can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: wire.protocol.OfferTypes uses a module listed above it, which is the healthy direction.
10→17 wire.protocol.OfferTypes uses message.OnionMessages part of a loop✕
- Connections
- 1 pair of types, where a type in wire.protocol.OfferTypes uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.message.OnionMessages.BlindedPath
- Direction
- wire.protocol.OfferTypes uses message.OnionMessages, so a change to message.OnionMessages can break wire.protocol.OfferTypes, while a change to wire.protocol.OfferTypes can't break message.OnionMessages.
- 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→26 wire.protocol.OfferTypes uses wire.protocol part of a loop✕
- Connections
- 4 pairs of types, where a type in wire.protocol.OfferTypes uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.wire.protocol.OfferTypes.Bolt12Tlv→fr.acinq.eclair.wire.protocol.Tlvfr.acinq.eclair.wire.protocol.OfferTypes.InvoiceError→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequest→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.wire.protocol.TlvStream
- Direction
- wire.protocol.OfferTypes uses wire.protocol, so a change to wire.protocol can break wire.protocol.OfferTypes, while a change to wire.protocol.OfferTypes can't break wire.protocol.
- 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→36 wire.protocol.OfferTypes uses fr.acinq.eclair part of a loop✕
- Connections
- 13 pairs of types, where a type in wire.protocol.OfferTypes uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceAmount→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.OfferTypes.InvoiceCreatedAt→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequest→fr.acinq.eclair.Bolt12Featurefr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequest→fr.acinq.eclair.Featuresfr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequest→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestAmount→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.Bolt12Featurefr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.Featuresfr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.OfferTypes.Offer→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.wire.protocol.OfferTypes.OfferAbsoluteExpiry→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo→fr.acinq.eclair.MilliSatoshi
- Direction
- wire.protocol.OfferTypes uses fr.acinq.eclair, so a change to fr.acinq.eclair can break wire.protocol.OfferTypes, while a change to wire.protocol.OfferTypes can't break fr.acinq.eclair.
- 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→5 db uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in db uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.db.FailureSummary→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- db uses io.PeerReadyManager, so a change to io.PeerReadyManager can break db, while a change to db can't break io.PeerReadyManager.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
11→6 db uses payment.relay.Relayer✕
- Connections
- 1 pair of types, where a type in db uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.db.PeersDb→fr.acinq.eclair.payment.relay.Relayer.RelayFees
- Direction
- db uses payment.relay.Relayer, so a change to payment.relay.Relayer can break db, while a change to db can't break payment.relay.Relayer.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
11→10 db uses wire.protocol.OfferTypes✕
- Connections
- 2 pairs of types, where a type in db uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.db.OfferData→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.db.OffersDb→fr.acinq.eclair.wire.protocol.OfferTypes.Offer
- Direction
- db uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break db, while a change to db can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
11→14 db uses payment part of a loop✕
- Connections
- 9 pairs of types, where a type in db uses a type in payment.
- The types involved
fr.acinq.eclair.db.AuditDb→fr.acinq.eclair.payment.PathFindingExperimentMetricsfr.acinq.eclair.db.AuditDb→fr.acinq.eclair.payment.PaymentRelayedfr.acinq.eclair.db.IncomingBlindedPayment→fr.acinq.eclair.payment.MinimalBolt12Invoicefr.acinq.eclair.db.IncomingPayment→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.db.IncomingPaymentsDb→fr.acinq.eclair.payment.Bolt11Invoicefr.acinq.eclair.db.IncomingPaymentsDb→fr.acinq.eclair.payment.MinimalBolt12Invoicefr.acinq.eclair.db.IncomingStandardPayment→fr.acinq.eclair.payment.Bolt11Invoicefr.acinq.eclair.db.OutgoingPayment→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.db.OutgoingPaymentsDb→fr.acinq.eclair.payment.PaymentFailed
- Direction
- db uses payment, so a change to payment can break db, while a change to db can't break payment.
- 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→22 db uses router.Router part of a loop✕
- Connections
- 1 pair of types, where a type in db uses a type in router.Router.
- The types involved
fr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.router.Router.PublicChannel
- Direction
- db uses router.Router, so a change to router.Router can break db, while a change to db can't break router.Router.
- 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→23 db uses io.PeerConnection part of a loop✕
- Connections
- 3 pairs of types, where a type in db uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.db.FileBackupHandler→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.db.PeerStorageCleaner→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.db.RevokedHtlcInfoCleaner→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- db uses io.PeerConnection, so a change to io.PeerConnection can break db, while a change to db can't break io.PeerConnection.
- 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→26 db uses wire.protocol part of a loop✕
- Connections
- 5 pairs of types, where a type in db uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.db.PeersDb→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.db.PeersDb→fr.acinq.eclair.wire.protocol.NodeInfo
- Direction
- db uses wire.protocol, so a change to wire.protocol can break db, while a change to db can't break wire.protocol.
- 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→32 db uses channel part of a loop✕
- Connections
- 9 pairs of types, where a type in db uses a type in channel.
- The types involved
fr.acinq.eclair.db.AuditDb→fr.acinq.eclair.channel.ChannelEventfr.acinq.eclair.db.AuditDb→fr.acinq.eclair.channel.ChannelUpdateParametersChangedfr.acinq.eclair.db.AuditDb→fr.acinq.eclair.channel.TransactionConfirmedfr.acinq.eclair.db.AuditDb→fr.acinq.eclair.channel.TransactionPublishedfr.acinq.eclair.db.ChannelsDb→fr.acinq.eclair.channel.DATA_CLOSEDfr.acinq.eclair.db.ChannelsDb→fr.acinq.eclair.channel.PersistentChannelDatafr.acinq.eclair.db.LiquidityDb→fr.acinq.eclair.channel.ChannelLiquidityPurchasedfr.acinq.eclair.db.LiquidityDb→fr.acinq.eclair.channel.LiquidityPurchasefr.acinq.eclair.db.PendingCommandsDb→fr.acinq.eclair.channel.HtlcSettlementCommand
- Direction
- db uses channel, so a change to channel can break db, while a change to db can't break channel.
- 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→33 db uses balance.BalanceActor part of a loop✕
- Connections
- 3 pairs of types, where a type in db uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.db.FileBackupHandler→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.db.PeerStorageCleaner→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.db.RevokedHtlcInfoCleaner→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- db uses balance.BalanceActor, so a change to balance.BalanceActor can break db, while a change to db can't break balance.BalanceActor.
- 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→36 db uses fr.acinq.eclair part of a loop✕
- Connections
- 24 pairs of types, where a type in db uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.db.AuditDb→fr.acinq.eclair.Paginatedfr.acinq.eclair.db.AuditDb→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.ChannelsDb→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.db.ChannelsDb→fr.acinq.eclair.Paginatedfr.acinq.eclair.db.HopSummary→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.db.IncomingBlindedPayment→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.IncomingPayment→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.IncomingPaymentsDb→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.db.IncomingPaymentsDb→fr.acinq.eclair.Paginatedfr.acinq.eclair.db.IncomingPaymentsDb→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.IncomingStandardPayment→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.LiquidityDb→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.db.LiquidityDb→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.db.NetworkDb→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.db.OfferData→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.OffersDb→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.OutgoingPayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.db.OutgoingPayment→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.OutgoingPaymentsDb→fr.acinq.eclair.TimestampMillifr.acinq.eclair.db.PeerStorageCleaner→fr.acinq.eclair.PeerStorageConfigfr.acinq.eclair.db.PeersDb→fr.acinq.eclair.Featuresfr.acinq.eclair.db.PeersDb→fr.acinq.eclair.InitFeaturefr.acinq.eclair.db.PeersDb→fr.acinq.eclair.TimestampSecond
- Direction
- db uses fr.acinq.eclair, so a change to fr.acinq.eclair can break db, while a change to db can't break fr.acinq.eclair.
- 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→9 io.MessageRelay uses io.PeerReadyNotifier✕
- Connections
- 1 pair of types, where a type in io.MessageRelay uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.io.MessageRelay.WrappedPeerReadyResult→fr.acinq.eclair.io.PeerReadyNotifier.Result
- Direction
- io.MessageRelay uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break io.MessageRelay, while a change to io.MessageRelay can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: io.MessageRelay uses a module listed above it, which is the healthy direction.
12→17 io.MessageRelay uses message.OnionMessages part of a loop✕
- Connections
- 1 pair of types, where a type in io.MessageRelay uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.io.MessageRelay.DroppedMessage→fr.acinq.eclair.message.OnionMessages.DropReason
- Direction
- io.MessageRelay uses message.OnionMessages, so a change to message.OnionMessages can break io.MessageRelay, while a change to io.MessageRelay can't break message.OnionMessages.
- 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→23 io.MessageRelay uses io.PeerConnection part of a loop✕
- Connections
- 1 pair of types, where a type in io.MessageRelay uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.io.MessageRelay.WrappedConnectionResult→fr.acinq.eclair.io.PeerConnection.ConnectionResult
- Direction
- io.MessageRelay uses io.PeerConnection, so a change to io.PeerConnection can break io.MessageRelay, while a change to io.MessageRelay can't break io.PeerConnection.
- 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→25 io.MessageRelay uses io.Peer part of a loop✕
- Connections
- 1 pair of types, where a type in io.MessageRelay uses a type in io.Peer.
- The types involved
fr.acinq.eclair.io.MessageRelay.WrappedPeerInfo→fr.acinq.eclair.io.Peer.PeerInfoResponse
- Direction
- io.MessageRelay uses io.Peer, so a change to io.Peer can break io.MessageRelay, while a change to io.MessageRelay can't break io.Peer.
- 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→26 io.MessageRelay uses wire.protocol part of a loop✕
- Connections
- 1 pair of types, where a type in io.MessageRelay uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.io.MessageRelay.RelayMessage→fr.acinq.eclair.wire.protocol.OnionMessage
- Direction
- io.MessageRelay uses wire.protocol, so a change to wire.protocol can break io.MessageRelay, while a change to io.MessageRelay can't break wire.protocol.
- 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→33 io.MessageRelay uses balance.BalanceActor part of a loop✕
- Connections
- 5 pairs of types, where a type in io.MessageRelay uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.io.MessageRelay.RelayMessage→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.MessageRelay.WrappedConnectionResult→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.MessageRelay.WrappedOptionalNodeId→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.MessageRelay.WrappedPeerInfo→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.MessageRelay.WrappedPeerReadyResult→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- io.MessageRelay uses balance.BalanceActor, so a change to balance.BalanceActor can break io.MessageRelay, while a change to io.MessageRelay can't break balance.BalanceActor.
- 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→36 io.MessageRelay uses fr.acinq.eclair part of a loop✕
- Connections
- 3 pairs of types, where a type in io.MessageRelay uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.io.MessageRelay.RelayMessage→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.io.MessageRelay.RelayMessage→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.io.MessageRelay.UnknownChannel→fr.acinq.eclair.ShortChannelId
- Direction
- io.MessageRelay uses fr.acinq.eclair, so a change to fr.acinq.eclair can break io.MessageRelay, while a change to io.MessageRelay can't break fr.acinq.eclair.
- 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→8 transactions.Transactions uses crypto.keymanager✕
- Connections
- 21 pairs of types, where a type in transactions.Transactions uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.transactions.Transactions.ClaimHtlcDelayedOutputPenaltyTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimHtlcSuccessTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimHtlcTimeoutTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimLocalAnchorTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimLocalDelayedOutputTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimRemoteAnchorTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.ClaimRemoteMainOutputTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.HtlcDelayedTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.HtlcPenaltyTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.HtlcSuccessTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.HtlcTimeoutTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.LocalCommitForceCloseTransaction→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.MainPenaltyTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.RemoteCommitForceCloseTransaction→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcSuccessTx→fr.acinq.eclair.crypto.keymanager.CommitmentPublicKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcSuccessTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTimeoutTx→fr.acinq.eclair.crypto.keymanager.CommitmentPublicKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTimeoutTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTx→fr.acinq.eclair.crypto.keymanager.CommitmentPublicKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTx→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTx→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeys
- Direction
- transactions.Transactions uses crypto.keymanager, so a change to crypto.keymanager can break transactions.Transactions, while a change to transactions.Transactions can't break crypto.keymanager.
- Position
- Below the diagonal: transactions.Transactions uses a module listed above it, which is the healthy direction.
13→36 transactions.Transactions uses fr.acinq.eclair part of a loop✕
- Connections
- 14 pairs of types, where a type in transactions.Transactions uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.transactions.Transactions.ClaimHtlcDelayedOutputPenaltyTx→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions.ClaimHtlcSuccessTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.ClaimHtlcTimeoutTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.ClaimHtlcTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.ClaimLocalDelayedOutputTx→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions.HtlcDelayedTx→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions.HtlcPenaltyRedeemDetails→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.HtlcPenaltyTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.HtlcSuccessTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.HtlcTimeoutTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.HtlcTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.MainPenaltyTx→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions.UnsignedHtlcSuccessTx→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Transactions.UnsignedHtlcTimeoutTx→fr.acinq.eclair.CltvExpiry
- Direction
- transactions.Transactions uses fr.acinq.eclair, so a change to fr.acinq.eclair can break transactions.Transactions, while a change to transactions.Transactions can't break fr.acinq.eclair.
- 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 payment uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in payment uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.payment.PaymentBlindedRoute→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- payment uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break payment, while a change to payment can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: payment uses a module listed above it, which is the healthy direction.
14→5 payment uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in payment uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- payment uses io.PeerReadyManager, so a change to io.PeerReadyManager can break payment, while a change to payment can't break io.PeerReadyManager.
- Position
- Below the diagonal: payment uses a module listed above it, which is the healthy direction.
14→7 payment uses crypto.Sphinx✕
- Connections
- 4 pairs of types, where a type in payment uses a type in crypto.Sphinx.
- The types involved
fr.acinq.eclair.payment.OutgoingPaymentPacket→fr.acinq.eclair.crypto.Sphinx.SharedSecretfr.acinq.eclair.payment.RemoteFailure→fr.acinq.eclair.crypto.Sphinx.DecryptedFailurePacketfr.acinq.eclair.payment.UnreadableRemoteFailure→fr.acinq.eclair.crypto.Sphinx.CannotDecryptFailurePacketfr.acinq.eclair.payment.UnreadableRemoteFailure→fr.acinq.eclair.crypto.Sphinx.HoldTime
- Direction
- payment uses crypto.Sphinx, so a change to crypto.Sphinx can break payment, while a change to payment can't break crypto.Sphinx.
- Position
- Below the diagonal: payment uses a module listed above it, which is the healthy direction.
14→10 payment uses wire.protocol.OfferTypes✕
- Connections
- 3 pairs of types, where a type in payment uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceTlvfr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceTlvfr.acinq.eclair.payment.PaymentBlindedRoute→fr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo
- Direction
- payment uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break payment, while a change to payment can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: payment uses a module listed above it, which is the healthy direction.
14→11 payment uses db✕
- Connections
- 9 pairs of types, where a type in payment uses a type in db.
- The types involved
fr.acinq.eclair.payment.ChannelPaymentRelayed→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.ChannelPaymentRelayed→fr.acinq.eclair.db.OutgoingPaymentfr.acinq.eclair.payment.OnTheFlyFundingPaymentRelayed→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.OnTheFlyFundingPaymentRelayed→fr.acinq.eclair.db.OutgoingPaymentfr.acinq.eclair.payment.PaymentReceived→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.PaymentRelayed→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.PaymentRelayed→fr.acinq.eclair.db.OutgoingPaymentfr.acinq.eclair.payment.TrampolinePaymentRelayed→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.TrampolinePaymentRelayed→fr.acinq.eclair.db.OutgoingPayment
- Direction
- payment uses db, so a change to db can break payment, while a change to payment can't break db.
- Position
- Below the diagonal: payment uses a module listed above it, which is the healthy direction.
14→22 payment uses router.Router part of a loop✕
- Connections
- 4 pairs of types, where a type in payment uses a type in router.Router.
- The types involved
fr.acinq.eclair.payment.LocalFailure→fr.acinq.eclair.router.Router.Hopfr.acinq.eclair.payment.PaymentFailure→fr.acinq.eclair.router.Router.Hopfr.acinq.eclair.payment.RemoteFailure→fr.acinq.eclair.router.Router.Hopfr.acinq.eclair.payment.UnreadableRemoteFailure→fr.acinq.eclair.router.Router.Hop
- Direction
- payment uses router.Router, so a change to router.Router can break payment, while a change to payment can't break router.Router.
- 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→26 payment uses wire.protocol part of a loop✕
- Connections
- 2 pairs of types, where a type in payment uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.wire.protocol.TlvStream
- Direction
- payment uses wire.protocol, so a change to wire.protocol can break payment, while a change to payment can't break wire.protocol.
- 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→32 payment uses channel part of a loop✕
- Connections
- 1 pair of types, where a type in payment uses a type in channel.
- The types involved
fr.acinq.eclair.payment.OutgoingPaymentPacket→fr.acinq.eclair.channel.CMD_ADD_HTLC
- Direction
- payment uses channel, so a change to channel can break payment, while a change to payment can't break channel.
- 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→36 payment uses fr.acinq.eclair part of a loop✕
- Connections
- 39 pairs of types, where a type in payment uses a type in fr.acinq.eclair. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.Bolt11Invoice→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.Bolt12Invoice→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.payment.IncomingPaymentPacket→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.Invoice→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.Invoice→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.Invoice→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.Invoice→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.payment.LocalFailure→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.MinimalBolt12Invoice→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.payment.OutgoingPaymentPacket→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.payment.PathFindingExperimentMetrics→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.PathFindingExperimentMetrics→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.PaymentEvent→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.PaymentFailed→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.PaymentFailure→fr.acinq.eclair.MilliSatoshi
- Direction
- payment uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment, while a change to payment can't break fr.acinq.eclair.
- 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→5 wire.protocol.LiquidityAds uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in wire.protocol.LiquidityAds uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- wire.protocol.LiquidityAds uses io.PeerReadyManager, so a change to io.PeerReadyManager can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break io.PeerReadyManager.
- Position
- Below the diagonal: wire.protocol.LiquidityAds uses a module listed above it, which is the healthy direction.
15→11 wire.protocol.LiquidityAds uses db✕
- Connections
- 3 pairs of types, where a type in wire.protocol.LiquidityAds uses a type in db.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.OnTheFlyFundingPaymentType→fr.acinq.eclair.db.PaymentTypefr.acinq.eclair.wire.protocol.LiquidityAds.PaymentDetails→fr.acinq.eclair.db.PaymentTypefr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates→fr.acinq.eclair.db.PaymentType
- Direction
- wire.protocol.LiquidityAds uses db, so a change to db can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break db.
- Position
- Below the diagonal: wire.protocol.LiquidityAds uses a module listed above it, which is the healthy direction.
15→26 wire.protocol.LiquidityAds uses wire.protocol part of a loop✕
- Connections
- 1 pair of types, where a type in wire.protocol.LiquidityAds uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.PaymentDetails→fr.acinq.eclair.wire.protocol.Tlv
- Direction
- wire.protocol.LiquidityAds uses wire.protocol, so a change to wire.protocol can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break wire.protocol.
- 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→31 wire.protocol.LiquidityAds uses blockchain.fee part of a loop✕
- Connections
- 3 pairs of types, where a type in wire.protocol.LiquidityAds uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.FundingRate→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.LiquidityAds.RequestFunding→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- wire.protocol.LiquidityAds uses blockchain.fee, so a change to blockchain.fee can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break blockchain.fee.
- 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→32 wire.protocol.LiquidityAds uses channel part of a loop✕
- Connections
- 2 pairs of types, where a type in wire.protocol.LiquidityAds uses a type in channel.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFunding→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates→fr.acinq.eclair.channel.ChannelException
- Direction
- wire.protocol.LiquidityAds uses channel, so a change to channel can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break channel.
- 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→36 wire.protocol.LiquidityAds uses fr.acinq.eclair part of a loop✕
- Connections
- 2 pairs of types, where a type in wire.protocol.LiquidityAds uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.wire.protocol.LiquidityAds.FundingFee→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates→fr.acinq.eclair.MilliSatoshi
- Direction
- wire.protocol.LiquidityAds uses fr.acinq.eclair, so a change to fr.acinq.eclair can break wire.protocol.LiquidityAds, while a change to wire.protocol.LiquidityAds can't break fr.acinq.eclair.
- 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 wire.protocol.MessageOnion uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in wire.protocol.MessageOnion uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.wire.protocol.MessageOnion.InvoiceRequestPayload→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- wire.protocol.MessageOnion uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break wire.protocol.MessageOnion, while a change to wire.protocol.MessageOnion can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: wire.protocol.MessageOnion uses a module listed above it, which is the healthy direction.
16→14 wire.protocol.MessageOnion uses payment✕
- Connections
- 1 pair of types, where a type in wire.protocol.MessageOnion uses a type in payment.
- The types involved
fr.acinq.eclair.wire.protocol.MessageOnion.InvoicePayload→fr.acinq.eclair.payment.Bolt12Invoice
- Direction
- wire.protocol.MessageOnion uses payment, so a change to payment can break wire.protocol.MessageOnion, while a change to wire.protocol.MessageOnion can't break payment.
- Position
- Below the diagonal: wire.protocol.MessageOnion uses a module listed above it, which is the healthy direction.
16→26 wire.protocol.MessageOnion uses wire.protocol part of a loop✕
- Connections
- 19 pairs of types, where a type in wire.protocol.MessageOnion uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.wire.protocol.MessageOnion.FinalPayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.FinalPayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.IntermediatePayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.IntermediatePayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.IntermediatePayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.InvalidResponsePayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvalidResponsePayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvalidResponsePayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceErrorPayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceErrorPayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceErrorPayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.InvoicePayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoicePayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoicePayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceRequestPayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceRequestPayload→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.wire.protocol.MessageOnion.InvoiceRequestPayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.wire.protocol.MessageOnion.PerHopPayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.wire.protocol.MessageOnion.PerHopPayload→fr.acinq.eclair.wire.protocol.TlvStream
- Direction
- wire.protocol.MessageOnion uses wire.protocol, so a change to wire.protocol can break wire.protocol.MessageOnion, while a change to wire.protocol.MessageOnion can't break wire.protocol.
- 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→36 wire.protocol.MessageOnion uses fr.acinq.eclair part of a loop✕
- Connections
- 2 pairs of types, where a type in wire.protocol.MessageOnion uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.wire.protocol.MessageOnion.IntermediatePayload→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.wire.protocol.MessageOnion.IntermediatePayload→fr.acinq.eclair.ShortChannelId
- Direction
- wire.protocol.MessageOnion uses fr.acinq.eclair, so a change to fr.acinq.eclair can break wire.protocol.MessageOnion, while a change to wire.protocol.MessageOnion can't break fr.acinq.eclair.
- 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→3 message.OnionMessages uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in message.OnionMessages uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.message.OnionMessages.BlindedPath→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- message.OnionMessages uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break message.OnionMessages, while a change to message.OnionMessages can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: message.OnionMessages uses a module listed above it, which is the healthy direction.
17→12 message.OnionMessages uses io.MessageRelay✕
- Connections
- 1 pair of types, where a type in message.OnionMessages uses a type in io.MessageRelay.
- The types involved
fr.acinq.eclair.message.OnionMessages.OnionMessageConfig→fr.acinq.eclair.io.MessageRelay.RelayPolicy
- Direction
- message.OnionMessages uses io.MessageRelay, so a change to io.MessageRelay can break message.OnionMessages, while a change to message.OnionMessages can't break io.MessageRelay.
- Position
- Below the diagonal: message.OnionMessages uses a module listed above it, which is the healthy direction.
17→16 message.OnionMessages uses wire.protocol.MessageOnion✕
- Connections
- 1 pair of types, where a type in message.OnionMessages uses a type in wire.protocol.MessageOnion.
- The types involved
fr.acinq.eclair.message.OnionMessages.ReceiveMessage→fr.acinq.eclair.wire.protocol.MessageOnion.FinalPayload
- Direction
- message.OnionMessages uses wire.protocol.MessageOnion, so a change to wire.protocol.MessageOnion can break message.OnionMessages, while a change to message.OnionMessages can't break wire.protocol.MessageOnion.
- Position
- Below the diagonal: message.OnionMessages uses a module listed above it, which is the healthy direction.
17→26 message.OnionMessages uses wire.protocol part of a loop✕
- Connections
- 10 pairs of types, where a type in message.OnionMessages uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.message.OnionMessages.DecodedEncryptedData→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.message.OnionMessages.DecodedEncryptedData→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.message.OnionMessages.DecodedOnionPacket→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.message.OnionMessages.DecodedOnionPacket→fr.acinq.eclair.wire.protocol.OnionRoutingPacketfr.acinq.eclair.message.OnionMessages.DecodedOnionPacket→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.message.OnionMessages.IntermediateNode→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.message.OnionMessages.IntermediateNode→fr.acinq.eclair.wire.protocol.RouteBlindingEncryptedDataTlvfr.acinq.eclair.message.OnionMessages.IntermediateNode→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.message.OnionMessages.Recipient→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.message.OnionMessages.SendMessage→fr.acinq.eclair.wire.protocol.OnionMessage
- Direction
- message.OnionMessages uses wire.protocol, so a change to wire.protocol can break message.OnionMessages, while a change to message.OnionMessages can't break wire.protocol.
- 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→36 message.OnionMessages uses fr.acinq.eclair part of a loop✕
- Connections
- 7 pairs of types, where a type in message.OnionMessages uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.message.OnionMessages.BlindedPath→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.message.OnionMessages.Destination→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.message.OnionMessages.IntermediateNode→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.message.OnionMessages.IntermediateNode→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.message.OnionMessages.Recipient→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.message.OnionMessages.SendMessage→fr.acinq.eclair.EncodedNodeIdfr.acinq.eclair.message.OnionMessages.SendMessage→fr.acinq.eclair.ShortChannelId
- Direction
- message.OnionMessages uses fr.acinq.eclair, so a change to fr.acinq.eclair can break message.OnionMessages, while a change to message.OnionMessages can't break fr.acinq.eclair.
- 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→3 payment.offer.OfferManager uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- payment.offer.OfferManager uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: payment.offer.OfferManager uses a module listed above it, which is the healthy direction.
18→10 payment.offer.OfferManager uses wire.protocol.OfferTypes✕
- Connections
- 5 pairs of types, where a type in payment.offer.OfferManager uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.DisableOffer→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.payment.offer.OfferManager.HandlePayment→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.payment.offer.OfferManager.PaymentActor→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.payment.offer.OfferManager.RegisterOffer→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.payment.offer.OfferManager.RegisteredOffer→fr.acinq.eclair.wire.protocol.OfferTypes.Offer
- Direction
- payment.offer.OfferManager uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: payment.offer.OfferManager uses a module listed above it, which is the healthy direction.
18→16 payment.offer.OfferManager uses wire.protocol.MessageOnion✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager uses a type in wire.protocol.MessageOnion.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.RequestInvoice→fr.acinq.eclair.wire.protocol.MessageOnion.InvoiceRequestPayload
- Direction
- payment.offer.OfferManager uses wire.protocol.MessageOnion, so a change to wire.protocol.MessageOnion can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break wire.protocol.MessageOnion.
- Position
- Below the diagonal: payment.offer.OfferManager uses a module listed above it, which is the healthy direction.
18→23 payment.offer.OfferManager uses io.PeerConnection part of a loop✕
- Connections
- 3 pairs of types, where a type in payment.offer.OfferManager uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.offer.OfferManager.OfferManager→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.offer.OfferManager.PaymentActor→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- payment.offer.OfferManager uses io.PeerConnection, so a change to io.PeerConnection can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break io.PeerConnection.
- 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→29 payment.offer.OfferManager uses channel.fund.InteractiveTxBuilder part of a loop✕
- Connections
- 2 pairs of types, where a type in payment.offer.OfferManager uses a type in channel.fund.InteractiveTxBuilder.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SendMessagefr.acinq.eclair.payment.offer.OfferManager.RequestInvoice→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SendMessage
- Direction
- payment.offer.OfferManager uses channel.fund.InteractiveTxBuilder, so a change to channel.fund.InteractiveTxBuilder can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break channel.fund.InteractiveTxBuilder.
- 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 payment.offer.OfferManager uses balance.BalanceActor part of a loop✕
- Connections
- 9 pairs of types, where a type in payment.offer.OfferManager uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.DisableOffer→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.HandleInvoiceRequest→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.HandlePayment→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.OfferManager→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.PaymentActor→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.ReceivePayment→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.RegisterOffer→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.RequestInvoice→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.offer.OfferManager uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break balance.BalanceActor.
- 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→36 payment.offer.OfferManager uses fr.acinq.eclair part of a loop✕
- Connections
- 4 pairs of types, where a type in payment.offer.OfferManager uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.offer.OfferManager.PaymentActor→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.offer.OfferManager.PaymentActor→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.offer.OfferManager.ReceivePayment→fr.acinq.eclair.MilliSatoshi
- Direction
- payment.offer.OfferManager uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.offer.OfferManager, while a change to payment.offer.OfferManager can't break fr.acinq.eclair.
- 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→5 payment.receive.MultiPartHandler uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in payment.receive.MultiPartHandler uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveStandardPayment→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- payment.receive.MultiPartHandler uses io.PeerReadyManager, so a change to io.PeerReadyManager can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break io.PeerReadyManager.
- Position
- Below the diagonal: payment.receive.MultiPartHandler uses a module listed above it, which is the healthy direction.
19→10 payment.receive.MultiPartHandler uses wire.protocol.OfferTypes✕
- Connections
- 2 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveOfferPayment→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceTlvfr.acinq.eclair.payment.receive.MultiPartHandler.ReceivingRoute→fr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo
- Direction
- payment.receive.MultiPartHandler uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: payment.receive.MultiPartHandler uses a module listed above it, which is the healthy direction.
19→11 payment.receive.MultiPartHandler uses db✕
- Connections
- 3 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in db.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.DoFulfill→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.payment.receive.MultiPartHandler.ProcessBlindedPacket→fr.acinq.eclair.db.IncomingBlindedPaymentfr.acinq.eclair.payment.receive.MultiPartHandler.ProcessPacket→fr.acinq.eclair.db.IncomingStandardPayment
- Direction
- payment.receive.MultiPartHandler uses db, so a change to db can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break db.
- Position
- Below the diagonal: payment.receive.MultiPartHandler uses a module listed above it, which is the healthy direction.
19→14 payment.receive.MultiPartHandler uses payment✕
- Connections
- 2 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in payment.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveOfferPayment→fr.acinq.eclair.payment.Bolt12Invoicefr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveStandardPayment→fr.acinq.eclair.payment.Bolt11Invoice
- Direction
- payment.receive.MultiPartHandler uses payment, so a change to payment can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break payment.
- Position
- Below the diagonal: payment.receive.MultiPartHandler uses a module listed above it, which is the healthy direction.
19→18 payment.receive.MultiPartHandler uses payment.offer.OfferManager✕
- Connections
- 3 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in payment.offer.OfferManager.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.payment.offer.OfferManager.ReceivePaymentfr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveOfferPayment→fr.acinq.eclair.payment.offer.OfferManager.ReceivePaymentfr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveStandardPayment→fr.acinq.eclair.payment.offer.OfferManager.ReceivePayment
- Direction
- payment.receive.MultiPartHandler uses payment.offer.OfferManager, so a change to payment.offer.OfferManager can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break payment.offer.OfferManager.
- Position
- Below the diagonal: payment.receive.MultiPartHandler uses a module listed above it, which is the healthy direction.
19→22 payment.receive.MultiPartHandler uses router.Router part of a loop✕
- Connections
- 1 pair of types, where a type in payment.receive.MultiPartHandler uses a type in router.Router.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.ReceivingRoute→fr.acinq.eclair.router.Router.ChannelHop
- Direction
- payment.receive.MultiPartHandler uses router.Router, so a change to router.Router can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break router.Router.
- 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→23 payment.receive.MultiPartHandler uses io.PeerConnection part of a loop✕
- Connections
- 2 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.CreateInvoiceActor→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- payment.receive.MultiPartHandler uses io.PeerConnection, so a change to io.PeerConnection can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break io.PeerConnection.
- 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→26 payment.receive.MultiPartHandler uses wire.protocol part of a loop✕
- Connections
- 6 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.payment.receive.MultiPartHandler.ProcessBlindedPacket→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.payment.receive.MultiPartHandler.ProcessPacket→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveOfferPayment→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.payment.receive.MultiPartHandler.RejectPacket→fr.acinq.eclair.wire.protocol.FailureMessagefr.acinq.eclair.payment.receive.MultiPartHandler.RejectPacket→fr.acinq.eclair.wire.protocol.UpdateAddHtlc
- Direction
- payment.receive.MultiPartHandler uses wire.protocol, so a change to wire.protocol can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break wire.protocol.
- 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→33 payment.receive.MultiPartHandler uses balance.BalanceActor part of a loop✕
- Connections
- 2 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.CreateInvoiceActor→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.receive.MultiPartHandler uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break balance.BalanceActor.
- 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→36 payment.receive.MultiPartHandler uses fr.acinq.eclair part of a loop✕
- Connections
- 10 pairs of types, where a type in payment.receive.MultiPartHandler uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.receive.MultiPartHandler.CreateInvoiceActor→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.receive.MultiPartHandler.GetIncomingPaymentActor→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.receive.MultiPartHandler.ProcessBlindedPacket→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.receive.MultiPartHandler.ProcessBlindedPacket→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.receive.MultiPartHandler.ProcessPacket→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveOfferPayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.receive.MultiPartHandler.ReceiveStandardPayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.receive.MultiPartHandler.ReceivingRoute→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.payment.receive.MultiPartHandler.RejectPacket→fr.acinq.eclair.TimestampMilli
- Direction
- payment.receive.MultiPartHandler uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.receive.MultiPartHandler, while a change to payment.receive.MultiPartHandler can't break fr.acinq.eclair.
- 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→6 payment.offer.OfferManager.InvoiceRequestActor uses payment.relay.Relayer✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route→fr.acinq.eclair.payment.relay.Relayer.RelayFees
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses payment.relay.Relayer, so a change to payment.relay.Relayer can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break payment.relay.Relayer.
- Position
- Below the diagonal: payment.offer.OfferManager.InvoiceRequestActor uses a module listed above it, which is the healthy direction.
20→10 payment.offer.OfferManager.InvoiceRequestActor uses wire.protocol.OfferTypes✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.ApproveRequest→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceTlv
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: payment.offer.OfferManager.InvoiceRequestActor uses a module listed above it, which is the healthy direction.
20→14 payment.offer.OfferManager.InvoiceRequestActor uses payment✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in payment.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.WrappedInvoiceResponse→fr.acinq.eclair.payment.Bolt12Invoice
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses payment, so a change to payment can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break payment.
- Position
- Below the diagonal: payment.offer.OfferManager.InvoiceRequestActor uses a module listed above it, which is the healthy direction.
20→19 payment.offer.OfferManager.InvoiceRequestActor uses payment.receive.MultiPartHandler✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in payment.receive.MultiPartHandler.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route→fr.acinq.eclair.payment.receive.MultiPartHandler.ReceivingRoute
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses payment.receive.MultiPartHandler, so a change to payment.receive.MultiPartHandler can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break payment.receive.MultiPartHandler.
- Position
- Below the diagonal: payment.offer.OfferManager.InvoiceRequestActor uses a module listed above it, which is the healthy direction.
20→22 payment.offer.OfferManager.InvoiceRequestActor uses router.Router part of a loop✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in router.Router.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route→fr.acinq.eclair.router.Router.ChannelHop
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses router.Router, so a change to router.Router can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break router.Router.
- 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→23 payment.offer.OfferManager.InvoiceRequestActor uses io.PeerConnection part of a loop✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.InvoiceRequestActor→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses io.PeerConnection, so a change to io.PeerConnection can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break io.PeerConnection.
- 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→26 payment.offer.OfferManager.InvoiceRequestActor uses wire.protocol part of a loop✕
- Connections
- 1 pair of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.ApproveRequest→fr.acinq.eclair.wire.protocol.GenericTlv
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses wire.protocol, so a change to wire.protocol can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break wire.protocol.
- 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→33 payment.offer.OfferManager.InvoiceRequestActor uses balance.BalanceActor part of a loop✕
- Connections
- 6 pairs of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.ApproveRequest→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.InvoiceRequestActor→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.RejectRequest→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.RequestInvoice→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.WrappedInvoiceResponse→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.WrappedOnionMessageResponse→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break balance.BalanceActor.
- 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→36 payment.offer.OfferManager.InvoiceRequestActor uses fr.acinq.eclair part of a loop✕
- Connections
- 3 pairs of types, where a type in payment.offer.OfferManager.InvoiceRequestActor uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.ApproveRequest→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route→fr.acinq.eclair.MilliSatoshi
- Direction
- payment.offer.OfferManager.InvoiceRequestActor uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.offer.OfferManager.InvoiceRequestActor, while a change to payment.offer.OfferManager.InvoiceRequestActor can't break fr.acinq.eclair.
- 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→3 router uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in router uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRouteDetails
- Direction
- router uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break router, while a change to router can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→4 router uses crypto.TransportHandler✕
- Connections
- 4 pairs of types, where a type in router uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.router.StaleChannels→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.router.Sync→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.router.Validation→fr.acinq.eclair.crypto.TransportHandler.Data
- Direction
- router uses crypto.TransportHandler, so a change to crypto.TransportHandler can break router, while a change to router can't break crypto.TransportHandler.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→5 router uses io.PeerReadyManager✕
- Connections
- 2 pairs of types, where a type in router uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.router.Announcements→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.router.Sync→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- router uses io.PeerReadyManager, so a change to io.PeerReadyManager can break router, while a change to router can't break io.PeerReadyManager.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→10 router uses wire.protocol.OfferTypes✕
- Connections
- 1 pair of types, where a type in router uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo
- Direction
- router uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break router, while a change to router can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→11 router uses db✕
- Connections
- 2 pairs of types, where a type in router uses a type in db.
- The types involved
fr.acinq.eclair.router.StaleChannels→fr.acinq.eclair.db.NetworkDbfr.acinq.eclair.router.Validation→fr.acinq.eclair.db.NetworkDb
- Direction
- router uses db, so a change to db can break router, while a change to router can't break db.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→15 router uses wire.protocol.LiquidityAds✕
- Connections
- 1 pair of types, where a type in router uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates
- Direction
- router uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break router, while a change to router can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→17 router uses message.OnionMessages✕
- Connections
- 1 pair of types, where a type in router uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.message.OnionMessages.Recipient
- Direction
- router uses message.OnionMessages, so a change to message.OnionMessages can break router, while a change to router can't break message.OnionMessages.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→20 router uses payment.offer.OfferManager.InvoiceRequestActor✕
- Connections
- 2 pairs of types, where a type in router uses a type in payment.offer.OfferManager.InvoiceRequestActor.
- The types involved
fr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route
- Direction
- router uses payment.offer.OfferManager.InvoiceRequestActor, so a change to payment.offer.OfferManager.InvoiceRequestActor can break router, while a change to router can't break payment.offer.OfferManager.InvoiceRequestActor.
- Position
- Below the diagonal: router uses a module listed above it, which is the healthy direction.
21→22 router uses router.Router part of a loop✕
- Connections
- 26 pairs of types, where a type in router uses a type in router.Router. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.router.BalanceEstimate→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.router.BalancesEstimates→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.router.BalancesEstimates→fr.acinq.eclair.router.Router.ChannelHopfr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.router.Router.ChannelHopfr.acinq.eclair.router.Graph→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.router.Router.ChannelHopfr.acinq.eclair.router.PathFindingExperimentConf→fr.acinq.eclair.router.Router.PathFindingConffr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.BlindedRouteRequestfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.FinalizeRoutefr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.MessageRouteParamsfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.MessageRouteRequestfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.PublicChannelfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.RouteParamsfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.router.Router.RouteRequestfr.acinq.eclair.router.Sync→fr.acinq.eclair.router.Router.PublicChannelfr.acinq.eclair.router.Sync→fr.acinq.eclair.router.Router.RemoteGossipfr.acinq.eclair.router.Sync→fr.acinq.eclair.router.Router.RouterConffr.acinq.eclair.router.Sync→fr.acinq.eclair.router.Router.SendChannelQueryfr.acinq.eclair.router.Validation→fr.acinq.eclair.router.Router.GossipDecisionfr.acinq.eclair.router.Validation→fr.acinq.eclair.router.Router.GossipOriginfr.acinq.eclair.router.Validation→fr.acinq.eclair.router.Router.PrivateChannelfr.acinq.eclair.router.Validation→fr.acinq.eclair.router.Router.PublicChannelfr.acinq.eclair.router.Validation→fr.acinq.eclair.router.Router.RemoteChannelUpdate
- Direction
- router uses router.Router, so a change to router.Router can break router, while a change to router can't break router.Router.
- 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→26 router uses wire.protocol part of a loop✕
- Connections
- 24 pairs of types, where a type in router uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.ChannelAnnouncementTlvfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.ChannelUpdateTlvfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.Colorfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.NodeAnnouncementTlvfr.acinq.eclair.router.Announcements→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.router.ChannelUpdatesReceived→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.NodeUpdated→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.NodesDiscovered→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.SingleChannelDiscovered→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.SingleChannelDiscovered→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.StaleChannels→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.StaleChannels→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Sync→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Sync→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Sync→fr.acinq.eclair.wire.protocol.EncodingTypefr.acinq.eclair.router.Sync→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Sync→fr.acinq.eclair.wire.protocol.ReplyShortChannelIdsEndfr.acinq.eclair.router.Validation→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Validation→fr.acinq.eclair.wire.protocol.NodeAnnouncement
- Direction
- router uses wire.protocol, so a change to wire.protocol can break router, while a change to router can't break wire.protocol.
- 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→32 router uses channel part of a loop✕
- Connections
- 5 pairs of types, where a type in router uses a type in channel.
- The types involved
fr.acinq.eclair.router.Announcements→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.router.Validation→fr.acinq.eclair.channel.AvailableBalanceChangedfr.acinq.eclair.router.Validation→fr.acinq.eclair.channel.LocalChannelDownfr.acinq.eclair.router.Validation→fr.acinq.eclair.channel.LocalChannelUpdatefr.acinq.eclair.router.Validation→fr.acinq.eclair.channel.ShortChannelIdAssigned
- Direction
- router uses channel, so a change to channel can break router, while a change to router can't break channel.
- 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→33 router uses balance.BalanceActor part of a loop✕
- Connections
- 1 pair of types, where a type in router uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.router.Validation→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- router uses balance.BalanceActor, so a change to balance.BalanceActor can break router, while a change to router can't break balance.BalanceActor.
- 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→36 router uses fr.acinq.eclair part of a loop✕
- Connections
- 38 pairs of types, where a type in router uses a type in fr.acinq.eclair. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.router.Announcements→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.router.Announcements→fr.acinq.eclair.Featurefr.acinq.eclair.router.Announcements→fr.acinq.eclair.Featuresfr.acinq.eclair.router.Announcements→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Announcements→fr.acinq.eclair.NodeFeaturefr.acinq.eclair.router.Announcements→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.Announcements→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.Announcements→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.router.BalanceEstimate→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.BalanceEstimate→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.BalanceEstimate→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.BalanceEstimate→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.router.BalancesEstimates→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.BalancesEstimates→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.router.BlindedRouteCreation→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.ChannelLost→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.FrontRouter→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.router.Graph→fr.acinq.eclair.BlockHeightfr.acinq.eclair.router.Graph→fr.acinq.eclair.Featuresfr.acinq.eclair.router.Graph→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.GraphWithBalanceEstimates→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.RouteCalculation→fr.acinq.eclair.BlockHeight
- Direction
- router uses fr.acinq.eclair, so a change to fr.acinq.eclair can break router, while a change to router can't break fr.acinq.eclair.
- 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→4 router.Router uses crypto.TransportHandler✕
- Connections
- 2 pairs of types, where a type in router.Router uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.router.Router.NORMAL→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.router.Router.WAIT_FOR_INIT→fr.acinq.eclair.crypto.TransportHandler.State
- Direction
- router.Router uses crypto.TransportHandler, so a change to crypto.TransportHandler can break router.Router, while a change to router.Router can't break crypto.TransportHandler.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→5 router.Router uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in router.Router uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.router.Router.Syncing→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- router.Router uses io.PeerReadyManager, so a change to io.PeerReadyManager can break router.Router, while a change to router.Router can't break io.PeerReadyManager.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→6 router.Router uses payment.relay.Relayer✕
- Connections
- 1 pair of types, where a type in router.Router uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.router.Router.HopRelayParams→fr.acinq.eclair.payment.relay.Relayer.RelayFees
- Direction
- router.Router uses payment.relay.Relayer, so a change to payment.relay.Relayer can break router.Router, while a change to router.Router can't break payment.relay.Relayer.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→7 router.Router uses crypto.Sphinx✕
- Connections
- 1 pair of types, where a type in router.Router uses a type in crypto.Sphinx.
- The types involved
fr.acinq.eclair.router.Router.ReportedHoldTimes→fr.acinq.eclair.crypto.Sphinx.HoldTime
- Direction
- router.Router uses crypto.Sphinx, so a change to crypto.Sphinx can break router.Router, while a change to router.Router can't break crypto.Sphinx.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→10 router.Router uses wire.protocol.OfferTypes✕
- Connections
- 1 pair of types, where a type in router.Router uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.router.Router.BlindedHop→fr.acinq.eclair.wire.protocol.OfferTypes.PaymentInfo
- Direction
- router.Router uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break router.Router, while a change to router.Router can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→17 router.Router uses message.OnionMessages✕
- Connections
- 1 pair of types, where a type in router.Router uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.router.Router.RouteRequest→fr.acinq.eclair.message.OnionMessages.Recipient
- Direction
- router.Router uses message.OnionMessages, so a change to message.OnionMessages can break router.Router, while a change to router.Router can't break message.OnionMessages.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→20 router.Router uses payment.offer.OfferManager.InvoiceRequestActor✕
- Connections
- 5 pairs of types, where a type in router.Router uses a type in payment.offer.OfferManager.InvoiceRequestActor.
- The types involved
fr.acinq.eclair.router.Router.Route→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.router.Router.RouteCouldRelay→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.router.Router.RouteDidRelay→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.router.Router.RouteRequest→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.router.Router.RouteResponse→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route
- Direction
- router.Router uses payment.offer.OfferManager.InvoiceRequestActor, so a change to payment.offer.OfferManager.InvoiceRequestActor can break router.Router, while a change to router.Router can't break payment.offer.OfferManager.InvoiceRequestActor.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→21 router.Router uses router✕
- Connections
- 2 pairs of types, where a type in router.Router uses a type in router.
- The types involved
fr.acinq.eclair.router.Router.Data→fr.acinq.eclair.router.GraphWithBalanceEstimatesfr.acinq.eclair.router.Router.RouterConf→fr.acinq.eclair.router.PathFindingExperimentConf
- Direction
- router.Router uses router, so a change to router can break router.Router, while a change to router.Router can't break router.
- Position
- Below the diagonal: router.Router uses a module listed above it, which is the healthy direction.
22→26 router.Router uses wire.protocol part of a loop✕
- Connections
- 20 pairs of types, where a type in router.Router uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.router.Router.Data→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Router.Data→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.GossipDecision→fr.acinq.eclair.wire.protocol.AnnouncementMessagefr.acinq.eclair.router.Router.Init→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.KnownChannel→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.Nothing→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.PrivateChannel→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.PublicChannel→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Router.PublicChannel→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.PublicNode→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.Rebroadcast→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.router.Router.Rebroadcast→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.Rebroadcast→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.RemoteChannelUpdate→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.RouterData→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.RoutingState→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.SendChannelQuery→fr.acinq.eclair.wire.protocol.QueryChannelRangeTlvfr.acinq.eclair.router.Router.Stash→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.router.Router.Stash→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.router.Router.SyncConf→fr.acinq.eclair.wire.protocol.EncodingType
- Direction
- router.Router uses wire.protocol, so a change to wire.protocol can break router.Router, while a change to router.Router can't break wire.protocol.
- 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→32 router.Router uses channel part of a loop✕
- Connections
- 7 pairs of types, where a type in router.Router uses a type in channel.
- The types involved
fr.acinq.eclair.router.Router.KnownChannel→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.router.Router.KnownChannel→fr.acinq.eclair.channel.LocalChannelUpdatefr.acinq.eclair.router.Router.PrivateChannel→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.router.Router.PrivateChannel→fr.acinq.eclair.channel.LocalChannelUpdatefr.acinq.eclair.router.Router.PrivateChannel→fr.acinq.eclair.channel.ShortIdAliasesfr.acinq.eclair.router.Router.PublicChannel→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.router.Router.PublicChannel→fr.acinq.eclair.channel.LocalChannelUpdate
- Direction
- router.Router uses channel, so a change to channel can break router.Router, while a change to router.Router can't break channel.
- 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→36 router.Router uses fr.acinq.eclair part of a loop✕
- Connections
- 35 pairs of types, where a type in router.Router uses a type in fr.acinq.eclair. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.router.Router.BlindedHop→fr.acinq.eclair.Aliasfr.acinq.eclair.router.Router.BlindedHop→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.BlindedRouteRequest→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.ChannelCouldNotRelay→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.ChannelDesc→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.Router.ChannelHop→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.ChannelHop→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.Router.ChannelMeta→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.Data→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.Router.Data→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.Router.ExcludedUntil→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.router.Router.GetNodeId→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.Router.Hop→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.router.Router.Hop→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.HopRelayParams→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.router.Router.HopRelayParams→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.Init→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.Router.KnownChannel→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.NodeHop→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.router.Router.NodeHop→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.Nothing→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.router.Router.PredefinedChannelRoute→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.PredefinedChannelRoute→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.router.Router.PredefinedNodeRoute→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.router.Router.PredefinedRoute→fr.acinq.eclair.MilliSatoshi
- Direction
- router.Router uses fr.acinq.eclair, so a change to fr.acinq.eclair can break router.Router, while a change to router.Router can't break fr.acinq.eclair.
- 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→4 io.PeerConnection uses crypto.TransportHandler✕
- Connections
- 10 pairs of types, where a type in io.PeerConnection uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.io.PeerConnection.AUTHENTICATING→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.PeerConnection.AuthenticatingData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.PeerConnection.BEFORE_AUTH→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.PeerConnection.BEFORE_INIT→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.PeerConnection.BeforeInitData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.PeerConnection.CONNECTED→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.PeerConnection.ConnectedData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.PeerConnection.INITIALIZING→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.PeerConnection.InitializingData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.PeerConnection.Nothing→fr.acinq.eclair.crypto.TransportHandler.Data
- Direction
- io.PeerConnection uses crypto.TransportHandler, so a change to crypto.TransportHandler can break io.PeerConnection, while a change to io.PeerConnection can't break crypto.TransportHandler.
- Position
- Below the diagonal: io.PeerConnection uses a module listed above it, which is the healthy direction.
23→15 io.PeerConnection uses wire.protocol.LiquidityAds✕
- Connections
- 1 pair of types, where a type in io.PeerConnection uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.io.PeerConnection.InitializeConnection→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRates
- Direction
- io.PeerConnection uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break io.PeerConnection, while a change to io.PeerConnection can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: io.PeerConnection uses a module listed above it, which is the healthy direction.
23→22 io.PeerConnection uses router.Router✕
- Connections
- 1 pair of types, where a type in io.PeerConnection uses a type in router.Router.
- The types involved
fr.acinq.eclair.io.PeerConnection.DelayedRebroadcast→fr.acinq.eclair.router.Router.Rebroadcast
- Direction
- io.PeerConnection uses router.Router, so a change to router.Router can break io.PeerConnection, while a change to io.PeerConnection can't break router.Router.
- Position
- Below the diagonal: io.PeerConnection uses a module listed above it, which is the healthy direction.
23→25 io.PeerConnection uses io.Peer part of a loop✕
- Connections
- 3 pairs of types, where a type in io.PeerConnection uses a type in io.Peer.
- The types involved
fr.acinq.eclair.io.PeerConnection.ConnectedData→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.io.PeerConnection.ConnectionReady→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.io.PeerConnection.InitializingData→fr.acinq.eclair.io.Peer.Init
- Direction
- io.PeerConnection uses io.Peer, so a change to io.Peer can break io.PeerConnection, while a change to io.PeerConnection can't break io.Peer.
- 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→26 io.PeerConnection uses wire.protocol part of a loop✕
- Connections
- 7 pairs of types, where a type in io.PeerConnection uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.io.PeerConnection.ConnectedData→fr.acinq.eclair.wire.protocol.GossipTimestampFilterfr.acinq.eclair.io.PeerConnection.ConnectionReady→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.PeerConnection.ExpectedPong→fr.acinq.eclair.wire.protocol.Pingfr.acinq.eclair.io.PeerConnection.PendingAuth→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.PeerConnection.PendingCommitSigBatch→fr.acinq.eclair.wire.protocol.CommitSigfr.acinq.eclair.io.PeerConnection.PingTimeout→fr.acinq.eclair.wire.protocol.Pingfr.acinq.eclair.io.PeerConnection.SyncMessage→fr.acinq.eclair.wire.protocol.RoutingMessage
- Direction
- io.PeerConnection uses wire.protocol, so a change to wire.protocol can break io.PeerConnection, while a change to io.PeerConnection can't break wire.protocol.
- 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→36 io.PeerConnection uses fr.acinq.eclair part of a loop✕
- Connections
- 3 pairs of types, where a type in io.PeerConnection uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.io.PeerConnection.ExpectedPong→fr.acinq.eclair.TimestampMillifr.acinq.eclair.io.PeerConnection.InitializeConnection→fr.acinq.eclair.Featuresfr.acinq.eclair.io.PeerConnection.InitializeConnection→fr.acinq.eclair.InitFeature
- Direction
- io.PeerConnection uses fr.acinq.eclair, so a change to fr.acinq.eclair can break io.PeerConnection, while a change to io.PeerConnection can't break fr.acinq.eclair.
- 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→1 io uses blockchain✕
- Connections
- 1 pair of types, where a type in io uses a type in blockchain.
- The types involved
fr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.blockchain.OnChainAddressCache
- Direction
- io uses blockchain, so a change to blockchain can break io, while a change to io can't break blockchain.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→4 io uses crypto.TransportHandler✕
- Connections
- 1 pair of types, where a type in io uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.io.Peer→fr.acinq.eclair.crypto.TransportHandler.State
- Direction
- io uses crypto.TransportHandler, so a change to crypto.TransportHandler can break io, while a change to io can't break crypto.TransportHandler.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→5 io uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in io uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.io.PeerReadyManager→fr.acinq.eclair.io.PeerReadyManager.Registered
- Direction
- io uses io.PeerReadyManager, so a change to io.PeerReadyManager can break io, while a change to io can't break io.PeerReadyManager.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→8 io uses crypto.keymanager✕
- Connections
- 1 pair of types, where a type in io uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.io.Peer→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- io uses crypto.keymanager, so a change to crypto.keymanager can break io, while a change to io can't break crypto.keymanager.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→9 io uses io.PeerReadyNotifier✕
- Connections
- 1 pair of types, where a type in io uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.io.PeerReadyNotifier→fr.acinq.eclair.io.PeerReadyNotifier.Result
- Direction
- io uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break io, while a change to io can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→22 io uses router.Router✕
- Connections
- 4 pairs of types, where a type in io uses a type in router.Router.
- The types involved
fr.acinq.eclair.io.MessageRelay→fr.acinq.eclair.router.Router.GetNodeIdfr.acinq.eclair.io.PeerConnection→fr.acinq.eclair.router.Router.Stashfr.acinq.eclair.io.PendingChannelsRateLimiter→fr.acinq.eclair.router.Router.GetNodefr.acinq.eclair.io.Switchboard→fr.acinq.eclair.router.Router.Stash
- Direction
- io uses router.Router, so a change to router.Router can break io, while a change to io can't break router.Router.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→23 io uses io.PeerConnection✕
- Connections
- 8 pairs of types, where a type in io uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.io.IncomingConnectionsTracker→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.MessageRelay→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.Peer→fr.acinq.eclair.io.PeerConnection.ConnectionReadyfr.acinq.eclair.io.PeerChannelsCollector→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.PeerReadyManager→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.PeerReadyNotifier→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.io.PendingChannelsRateLimiter→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- io uses io.PeerConnection, so a change to io.PeerConnection can break io, while a change to io can't break io.PeerConnection.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
24→25 io uses io.Peer part of a loop✕
- Connections
- 4 pairs of types, where a type in io uses a type in io.Peer.
- The types involved
fr.acinq.eclair.io.ConnectionInfo→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.io.IncomingConnectionsTracker→fr.acinq.eclair.io.Peer.Disconnectfr.acinq.eclair.io.Peer→fr.acinq.eclair.io.Peer.ChannelIdfr.acinq.eclair.io.Peer→fr.acinq.eclair.io.Peer.PeerStorage
- Direction
- io uses io.Peer, so a change to io.Peer can break io, while a change to io can't break io.Peer.
- 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→26 io uses wire.protocol part of a loop✕
- Connections
- 5 pairs of types, where a type in io uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.io.ConnectionInfo→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.NodeURI→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.Peer→fr.acinq.eclair.wire.protocol.LightningMessagefr.acinq.eclair.io.ReconnectionTask→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.UnknownMessageReceived→fr.acinq.eclair.wire.protocol.UnknownMessage
- Direction
- io uses wire.protocol, so a change to wire.protocol can break io, while a change to io can't break wire.protocol.
- 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→32 io uses channel part of a loop✕
- Connections
- 5 pairs of types, where a type in io uses a type in channel.
- The types involved
fr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.channel.LocalChannelParamsfr.acinq.eclair.io.PeerReadyManager→fr.acinq.eclair.channel.Registerfr.acinq.eclair.io.PeerReadyNotifier→fr.acinq.eclair.channel.ChannelStatefr.acinq.eclair.io.PendingChannelsRateLimiter→fr.acinq.eclair.channel.PersistentChannelDatafr.acinq.eclair.io.Switchboard→fr.acinq.eclair.channel.PersistentChannelDataWithKeys
- Direction
- io uses channel, so a change to channel can break io, while a change to io can't break channel.
- 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 io uses balance.BalanceActor part of a loop✕
- Connections
- 7 pairs of types, where a type in io uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.io.IncomingConnectionsTracker→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.MessageRelay→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerChannelsCollector→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyManager→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PeerReadyNotifier→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.PendingChannelsRateLimiter→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- io uses balance.BalanceActor, so a change to balance.BalanceActor can break io, while a change to io can't break balance.BalanceActor.
- 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→36 io uses fr.acinq.eclair part of a loop✕
- Connections
- 14 pairs of types, where a type in io uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.io.IncomingConnectionsTracker→fr.acinq.eclair.NodeParamsfr.acinq.eclair.io.MessageRelay→fr.acinq.eclair.NodeParamsfr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.Featuresfr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.OpenChannelInterceptor→fr.acinq.eclair.NodeParamsfr.acinq.eclair.io.Peer→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.io.Peer→fr.acinq.eclair.Featuresfr.acinq.eclair.io.Peer→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.Peer→fr.acinq.eclair.NodeParamsfr.acinq.eclair.io.PeerConnection→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.io.PeerReadyNotifier→fr.acinq.eclair.BlockHeightfr.acinq.eclair.io.PendingChannelsRateLimiter→fr.acinq.eclair.NodeParamsfr.acinq.eclair.io.ReconnectionTask→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.io.Server→fr.acinq.eclair.TimestampMilli
- Direction
- io uses fr.acinq.eclair, so a change to fr.acinq.eclair can break io, while a change to io can't break fr.acinq.eclair.
- 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 io.Peer uses blockchain✕
- Connections
- 1 pair of types, where a type in io.Peer uses a type in blockchain.
- The types involved
fr.acinq.eclair.io.Peer.SimpleChannelFactory→fr.acinq.eclair.blockchain.OnChainChannelFunder
- Direction
- io.Peer uses blockchain, so a change to blockchain can break io.Peer, while a change to io.Peer can't break blockchain.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→2 io.Peer uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in io.Peer uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.io.Peer.ProposeOnTheFlyFunding→fr.acinq.eclair.channel.Upstream.Hot
- Direction
- io.Peer uses channel.Upstream, so a change to channel.Upstream can break io.Peer, while a change to io.Peer can't break channel.Upstream.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→4 io.Peer uses crypto.TransportHandler✕
- Connections
- 8 pairs of types, where a type in io.Peer uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.io.Peer.CONNECTED→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.Peer.DISCONNECTED→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.Peer.DisconnectedData→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.Peer.INSTANTIATING→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.Peer.Nothing→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.io.Peer.PeerInfo→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.io.Peer.Transition→fr.acinq.eclair.crypto.TransportHandler.Data
- Direction
- io.Peer uses crypto.TransportHandler, so a change to crypto.TransportHandler can break io.Peer, while a change to io.Peer can't break crypto.TransportHandler.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→7 io.Peer uses crypto.Sphinx✕
- Connections
- 1 pair of types, where a type in io.Peer uses a type in crypto.Sphinx.
- The types involved
fr.acinq.eclair.io.Peer.ProposeOnTheFlyFunding→fr.acinq.eclair.crypto.Sphinx.SharedSecret
- Direction
- io.Peer uses crypto.Sphinx, so a change to crypto.Sphinx can break io.Peer, while a change to io.Peer can't break crypto.Sphinx.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→8 io.Peer uses crypto.keymanager✕
- Connections
- 2 pairs of types, where a type in io.Peer uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.io.Peer.ChannelFactory→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.io.Peer.SimpleChannelFactory→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- io.Peer uses crypto.keymanager, so a change to crypto.keymanager can break io.Peer, while a change to io.Peer can't break crypto.keymanager.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→9 io.Peer uses io.PeerReadyNotifier✕
- Connections
- 1 pair of types, where a type in io.Peer uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.io.PeerReadyNotifier.Timeout
- Direction
- io.Peer uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break io.Peer, while a change to io.Peer can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→12 io.Peer uses io.MessageRelay✕
- Connections
- 1 pair of types, where a type in io.Peer uses a type in io.MessageRelay.
- The types involved
fr.acinq.eclair.io.Peer.RelayOnionMessage→fr.acinq.eclair.io.MessageRelay.Status
- Direction
- io.Peer uses io.MessageRelay, so a change to io.MessageRelay can break io.Peer, while a change to io.Peer can't break io.MessageRelay.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→15 io.Peer uses wire.protocol.LiquidityAds✕
- Connections
- 3 pairs of types, where a type in io.Peer uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.io.Peer.LiquidityPurchaseSigned→fr.acinq.eclair.wire.protocol.LiquidityAds.Purchasefr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.io.Peer.SpawnChannelNonInitiator→fr.acinq.eclair.wire.protocol.LiquidityAds.AddFunding
- Direction
- io.Peer uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break io.Peer, while a change to io.Peer can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→24 io.Peer uses io✕
- Connections
- 2 pairs of types, where a type in io.Peer uses a type in io.
- The types involved
fr.acinq.eclair.io.Peer.Connect→fr.acinq.eclair.io.NodeURIfr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.io.ConnectionInfo
- Direction
- io.Peer uses io, so a change to io can break io.Peer, while a change to io.Peer can't break io.
- Position
- Below the diagonal: io.Peer uses a module listed above it, which is the healthy direction.
25→26 io.Peer uses wire.protocol part of a loop✕
- Connections
- 10 pairs of types, where a type in io.Peer uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.io.Peer.Connect→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.wire.protocol.RecommendedFeeratesfr.acinq.eclair.io.Peer.OutgoingMessage→fr.acinq.eclair.wire.protocol.LightningMessagefr.acinq.eclair.io.Peer.PeerInfo→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.io.Peer.PeerRoutingMessage→fr.acinq.eclair.wire.protocol.RoutingMessagefr.acinq.eclair.io.Peer.ProposeOnTheFlyFunding→fr.acinq.eclair.wire.protocol.OnionRoutingPacketfr.acinq.eclair.io.Peer.RelayOnionMessage→fr.acinq.eclair.wire.protocol.OnionMessagefr.acinq.eclair.io.Peer.RelayUnknownMessage→fr.acinq.eclair.wire.protocol.UnknownMessagefr.acinq.eclair.io.Peer.SpawnChannelNonInitiator→fr.acinq.eclair.wire.protocol.OpenDualFundedChannel
- Direction
- io.Peer uses wire.protocol, so a change to wire.protocol can break io.Peer, while a change to io.Peer can't break wire.protocol.
- 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→31 io.Peer uses blockchain.fee part of a loop✕
- Connections
- 2 pairs of types, where a type in io.Peer uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- io.Peer uses blockchain.fee, so a change to blockchain.fee can break io.Peer, while a change to io.Peer can't break blockchain.fee.
- 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 io.Peer uses channel part of a loop✕
- Connections
- 10 pairs of types, where a type in io.Peer uses a type in channel.
- The types involved
fr.acinq.eclair.io.Peer.ChannelInfo→fr.acinq.eclair.channel.ChannelStatefr.acinq.eclair.io.Peer.Init→fr.acinq.eclair.channel.PersistentChannelDataWithKeysfr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.channel.SupportedChannelTypefr.acinq.eclair.io.Peer.SpawnChannelInitiator→fr.acinq.eclair.channel.ChannelConfigfr.acinq.eclair.io.Peer.SpawnChannelInitiator→fr.acinq.eclair.channel.LocalChannelParamsfr.acinq.eclair.io.Peer.SpawnChannelInitiator→fr.acinq.eclair.channel.SupportedChannelTypefr.acinq.eclair.io.Peer.SpawnChannelNonInitiator→fr.acinq.eclair.channel.ChannelConfigfr.acinq.eclair.io.Peer.SpawnChannelNonInitiator→fr.acinq.eclair.channel.LocalChannelParamsfr.acinq.eclair.io.Peer.SpawnChannelNonInitiator→fr.acinq.eclair.channel.SupportedChannelType
- Direction
- io.Peer uses channel, so a change to channel can break io.Peer, while a change to io.Peer can't break channel.
- 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 io.Peer uses balance.BalanceActor part of a loop✕
- Connections
- 2 pairs of types, where a type in io.Peer uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.io.Peer.ChannelInfo→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.io.Peer.SimpleChannelFactory→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- io.Peer uses balance.BalanceActor, so a change to balance.BalanceActor can break io.Peer, while a change to io.Peer can't break balance.BalanceActor.
- 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→36 io.Peer uses fr.acinq.eclair part of a loop✕
- Connections
- 11 pairs of types, where a type in io.Peer uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.Featuresfr.acinq.eclair.io.Peer.ConnectedData→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.Peer.LastRemoteFeatures→fr.acinq.eclair.Featuresfr.acinq.eclair.io.Peer.LastRemoteFeatures→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.Peer.LiquidityPurchaseSigned→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.io.Peer.OpenChannel→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.io.Peer.PeerInfo→fr.acinq.eclair.Featuresfr.acinq.eclair.io.Peer.PeerInfo→fr.acinq.eclair.InitFeaturefr.acinq.eclair.io.Peer.ProposeOnTheFlyFunding→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.io.Peer.ProposeOnTheFlyFunding→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.io.Peer.SimpleChannelFactory→fr.acinq.eclair.NodeParams
- Direction
- io.Peer uses fr.acinq.eclair, so a change to fr.acinq.eclair can break io.Peer, while a change to io.Peer can't break fr.acinq.eclair.
- 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→3 wire.protocol uses crypto.Sphinx.RouteBlinding✕
- Connections
- 2 pairs of types, where a type in wire.protocol uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedHopfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- wire.protocol uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break wire.protocol, while a change to wire.protocol can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→5 wire.protocol uses io.PeerReadyManager✕
- Connections
- 6 pairs of types, where a type in wire.protocol uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.wire.protocol.CancelOnTheFlyFunding→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.wire.protocol.CommitSig→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.wire.protocol.EncodedShortChannelIds→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.wire.protocol.NodeAnnouncement→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.wire.protocol.TlvCodecs→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- wire.protocol uses io.PeerReadyManager, so a change to io.PeerReadyManager can break wire.protocol, while a change to wire.protocol can't break io.PeerReadyManager.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→6 wire.protocol uses payment.relay.Relayer✕
- Connections
- 1 pair of types, where a type in wire.protocol uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.payment.relay.Relayer.RelayFees
- Direction
- wire.protocol uses payment.relay.Relayer, so a change to payment.relay.Relayer can break wire.protocol, while a change to wire.protocol can't break payment.relay.Relayer.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→10 wire.protocol uses wire.protocol.OfferTypes✕
- Connections
- 36 pairs of types, where a type in wire.protocol uses a type in wire.protocol.OfferTypes. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceAccountablefr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceAmountfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceBlindedPayfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceCreatedAtfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceErrorTlvfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceFallbacksfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceNodeIdfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoicePathsfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoicePaymentHashfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRelativeExpiryfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestAmountfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestChainfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestFeaturesfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestMetadatafr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestPayerIdfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestPayerNotefr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestQuantityfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceRequestTlvfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.InvoiceTlvfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferAbsoluteExpiryfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferAmountfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferChainsfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferCurrencyfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferDescriptionfr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.wire.protocol.OfferTypes.OfferFeatures
- Direction
- wire.protocol uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break wire.protocol, while a change to wire.protocol can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→13 wire.protocol uses transactions.Transactions✕
- Connections
- 4 pairs of types, where a type in wire.protocol uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.wire.protocol.CommitSig→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.wire.protocol.FundingCreated→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.wire.protocol.FundingSigned→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.wire.protocol.TxAddInput→fr.acinq.eclair.transactions.Transactions.InputInfo
- Direction
- wire.protocol uses transactions.Transactions, so a change to transactions.Transactions can break wire.protocol, while a change to wire.protocol can't break transactions.Transactions.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→14 wire.protocol uses payment✕
- Connections
- 2 pairs of types, where a type in wire.protocol uses a type in payment.
- The types involved
fr.acinq.eclair.wire.protocol.OfferCodecs→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.wire.protocol.PaymentOnionCodecs→fr.acinq.eclair.payment.PaymentBlindedRoute
- Direction
- wire.protocol uses payment, so a change to payment can break wire.protocol, while a change to wire.protocol can't break payment.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→15 wire.protocol uses wire.protocol.LiquidityAds✕
- Connections
- 15 pairs of types, where a type in wire.protocol uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.wire.protocol.AcceptDualFundedChannel→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundfr.acinq.eclair.wire.protocol.Init→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRatesfr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.PaymentDetailsfr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.Purchasefr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundfr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundPurchasefr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRatesfr.acinq.eclair.wire.protocol.NodeAnnouncement→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundRatesfr.acinq.eclair.wire.protocol.OpenDualFundedChannel→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.wire.protocol.SpliceAck→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundfr.acinq.eclair.wire.protocol.SpliceInit→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.wire.protocol.TxAckRbf→fr.acinq.eclair.wire.protocol.LiquidityAds.WillFundfr.acinq.eclair.wire.protocol.TxInitRbf→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.wire.protocol.UpdateAddHtlc→fr.acinq.eclair.wire.protocol.LiquidityAds.FundingFee
- Direction
- wire.protocol uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break wire.protocol, while a change to wire.protocol can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→25 wire.protocol uses io.Peer✕
- Connections
- 2 pairs of types, where a type in wire.protocol uses a type in io.Peer.
- The types involved
fr.acinq.eclair.wire.protocol.LightningMessageCodecs→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.wire.protocol.LightningMessageCodecs→fr.acinq.eclair.io.Peer.OpenChannel
- Direction
- wire.protocol uses io.Peer, so a change to io.Peer can break wire.protocol, while a change to wire.protocol can't break io.Peer.
- Position
- Below the diagonal: wire.protocol uses a module listed above it, which is the healthy direction.
26→31 wire.protocol uses blockchain.fee part of a loop✕
- Connections
- 9 pairs of types, where a type in wire.protocol uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.ExperimentalSpliceInit→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.OpenChannel→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.OpenDualFundedChannel→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.RecommendedFeerates→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.SpliceInit→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.TxInitRbf→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.wire.protocol.UpdateFee→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- wire.protocol uses blockchain.fee, so a change to blockchain.fee can break wire.protocol, while a change to wire.protocol can't break blockchain.fee.
- 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 wire.protocol uses channel part of a loop✕
- Connections
- 10 pairs of types, where a type in wire.protocol uses a type in channel.
- The types involved
fr.acinq.eclair.wire.protocol.ChannelDisabled→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.wire.protocol.CommitSig→fr.acinq.eclair.channel.ChannelSpendSignaturefr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.channel.ShortIdAliasesfr.acinq.eclair.wire.protocol.FundingCreated→fr.acinq.eclair.channel.ChannelSpendSignaturefr.acinq.eclair.wire.protocol.FundingSigned→fr.acinq.eclair.channel.ChannelSpendSignaturefr.acinq.eclair.wire.protocol.LiquidityAds→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.wire.protocol.OpenChannel→fr.acinq.eclair.channel.ChannelFlagsfr.acinq.eclair.wire.protocol.OpenDualFundedChannel→fr.acinq.eclair.channel.ChannelFlags
- Direction
- wire.protocol uses channel, so a change to channel can break wire.protocol, while a change to wire.protocol can't break channel.
- 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→36 wire.protocol uses fr.acinq.eclair part of a loop✕
- Connections
- 72 pairs of types, where a type in wire.protocol uses a type in fr.acinq.eclair. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.wire.protocol.AcceptChannel→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.wire.protocol.AcceptChannel→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.AcceptChannel→fr.acinq.eclair.UInt64fr.acinq.eclair.wire.protocol.AcceptDualFundedChannel→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.wire.protocol.AcceptDualFundedChannel→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.AcceptDualFundedChannel→fr.acinq.eclair.UInt64fr.acinq.eclair.wire.protocol.AmountBelowMinimum→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.AnnouncementSignatures→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.wire.protocol.ChannelAnnouncement→fr.acinq.eclair.Featurefr.acinq.eclair.wire.protocol.ChannelAnnouncement→fr.acinq.eclair.Featuresfr.acinq.eclair.wire.protocol.ChannelAnnouncement→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.wire.protocol.ChannelReady→fr.acinq.eclair.Aliasfr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.wire.protocol.ChannelUpdate→fr.acinq.eclair.TimestampSecondfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.Aliasfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.BlockHeightfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.Featurefr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.Featuresfr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.InitFeaturefr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.wire.protocol.CommonCodecs→fr.acinq.eclair.RealShortChannelId
- Direction
- wire.protocol uses fr.acinq.eclair, so a change to fr.acinq.eclair can break wire.protocol, while a change to wire.protocol can't break fr.acinq.eclair.
- 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→8 transactions uses crypto.keymanager✕
- Connections
- 3 pairs of types, where a type in transactions uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.crypto.keymanager.CommitmentPublicKeysfr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.crypto.keymanager.CommitmentPublicKeys
- Direction
- transactions uses crypto.keymanager, so a change to crypto.keymanager can break transactions, while a change to transactions can't break crypto.keymanager.
- Position
- Below the diagonal: transactions uses a module listed above it, which is the healthy direction.
27→13 transactions uses transactions.Transactions✕
- Connections
- 11 pairs of types, where a type in transactions uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.transactions.CommitmentSpec→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.ClosingTxsfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.CommitTxfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.ForceCloseTransactionfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.InputInfofr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.RedeemInfofr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.SimpleClosingTxFeefr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.TxGenerationSkippedfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.transactions.Transactions.UnsignedHtlcTx
- Direction
- transactions uses transactions.Transactions, so a change to transactions.Transactions can break transactions, while a change to transactions can't break transactions.Transactions.
- Position
- Below the diagonal: transactions uses a module listed above it, which is the healthy direction.
27→26 transactions uses wire.protocol✕
- Connections
- 3 pairs of types, where a type in transactions uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.transactions.DirectedHtlc→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.transactions.IncomingHtlc→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.transactions.OutgoingHtlc→fr.acinq.eclair.wire.protocol.UpdateAddHtlc
- Direction
- transactions uses wire.protocol, so a change to wire.protocol can break transactions, while a change to transactions can't break wire.protocol.
- Position
- Below the diagonal: transactions uses a module listed above it, which is the healthy direction.
27→31 transactions uses blockchain.fee part of a loop✕
- Connections
- 2 pairs of types, where a type in transactions uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.transactions.CommitmentSpec→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- transactions uses blockchain.fee, so a change to blockchain.fee can break transactions, while a change to transactions can't break blockchain.fee.
- 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→36 transactions uses fr.acinq.eclair part of a loop✕
- Connections
- 6 pairs of types, where a type in transactions uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.transactions.CommitmentSpec→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.BlockHeightfr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.transactions.Scripts→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.transactions.Transactions→fr.acinq.eclair.MilliSatoshi
- Direction
- transactions uses fr.acinq.eclair, so a change to fr.acinq.eclair can break transactions, while a change to transactions can't break fr.acinq.eclair.
- 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→8 channel.fund.InteractiveTxSigningSession uses crypto.keymanager✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- channel.fund.InteractiveTxSigningSession uses crypto.keymanager, so a change to crypto.keymanager can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break crypto.keymanager.
- Position
- Below the diagonal: channel.fund.InteractiveTxSigningSession uses a module listed above it, which is the healthy direction.
28→13 channel.fund.InteractiveTxSigningSession uses transactions.Transactions✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.transactions.Transactions.InputInfo
- Direction
- channel.fund.InteractiveTxSigningSession uses transactions.Transactions, so a change to transactions.Transactions can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break transactions.Transactions.
- Position
- Below the diagonal: channel.fund.InteractiveTxSigningSession uses a module listed above it, which is the healthy direction.
28→15 channel.fund.InteractiveTxSigningSession uses wire.protocol.LiquidityAds✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.wire.protocol.LiquidityAds.PurchaseBasicInfo
- Direction
- channel.fund.InteractiveTxSigningSession uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: channel.fund.InteractiveTxSigningSession uses a module listed above it, which is the healthy direction.
28→26 channel.fund.InteractiveTxSigningSession uses wire.protocol✕
- Connections
- 3 pairs of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.SendingSigs→fr.acinq.eclair.wire.protocol.TxSignaturesfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.wire.protocol.CommitSigfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.wire.protocol.TxSignatures
- Direction
- channel.fund.InteractiveTxSigningSession uses wire.protocol, so a change to wire.protocol can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break wire.protocol.
- Position
- Below the diagonal: channel.fund.InteractiveTxSigningSession uses a module listed above it, which is the healthy direction.
28→27 channel.fund.InteractiveTxSigningSession uses transactions✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in transactions.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.UnsignedLocalCommit→fr.acinq.eclair.transactions.CommitmentSpec
- Direction
- channel.fund.InteractiveTxSigningSession uses transactions, so a change to transactions can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break transactions.
- Position
- Below the diagonal: channel.fund.InteractiveTxSigningSession uses a module listed above it, which is the healthy direction.
28→29 channel.fund.InteractiveTxSigningSession uses channel.fund.InteractiveTxBuilder part of a loop✕
- Connections
- 2 pairs of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in channel.fund.InteractiveTxBuilder.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParamsfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.PartiallySignedSharedTransaction
- Direction
- channel.fund.InteractiveTxSigningSession uses channel.fund.InteractiveTxBuilder, so a change to channel.fund.InteractiveTxBuilder can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break channel.fund.InteractiveTxBuilder.
- 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 channel.fund.InteractiveTxSigningSession uses channel part of a loop✕
- Connections
- 7 pairs of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in channel.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.SendingSigs→fr.acinq.eclair.channel.Commitmentfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.ChannelParamsfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.CommitParamsfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.LocalCommitfr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.channel.RemoteCommit
- Direction
- channel.fund.InteractiveTxSigningSession uses channel, so a change to channel can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break channel.
- 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→36 channel.fund.InteractiveTxSigningSession uses fr.acinq.eclair part of a loop✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxSigningSession uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs→fr.acinq.eclair.BlockHeight
- Direction
- channel.fund.InteractiveTxSigningSession uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel.fund.InteractiveTxSigningSession, while a change to channel.fund.InteractiveTxSigningSession can't break fr.acinq.eclair.
- 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→2 channel.fund.InteractiveTxBuilder uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxBuilder uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedTransaction→fr.acinq.eclair.channel.Upstream.Local
- Direction
- channel.fund.InteractiveTxBuilder uses channel.Upstream, so a change to channel.Upstream can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break channel.Upstream.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→5 channel.fund.InteractiveTxBuilder uses io.PeerReadyManager✕
- Connections
- 2 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParams→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedTransaction→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- channel.fund.InteractiveTxBuilder uses io.PeerReadyManager, so a change to io.PeerReadyManager can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break io.PeerReadyManager.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→8 channel.fund.InteractiveTxBuilder uses crypto.keymanager✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxBuilder uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedFundingInput→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- channel.fund.InteractiveTxBuilder uses crypto.keymanager, so a change to crypto.keymanager can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break crypto.keymanager.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→13 channel.fund.InteractiveTxBuilder uses transactions.Transactions✕
- Connections
- 3 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParams→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedFundingInput→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedFundingInput→fr.acinq.eclair.transactions.Transactions.InputInfo
- Direction
- channel.fund.InteractiveTxBuilder uses transactions.Transactions, so a change to transactions.Transactions can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break transactions.Transactions.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→15 channel.fund.InteractiveTxBuilder uses wire.protocol.LiquidityAds✕
- Connections
- 2 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParams→fr.acinq.eclair.wire.protocol.LiquidityAds.Purchasefr.acinq.eclair.channel.fund.InteractiveTxBuilder.Succeeded→fr.acinq.eclair.wire.protocol.LiquidityAds.Purchase
- Direction
- channel.fund.InteractiveTxBuilder uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→26 channel.fund.InteractiveTxBuilder uses wire.protocol✕
- Connections
- 7 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.FullySignedSharedTransaction→fr.acinq.eclair.wire.protocol.TxSignaturesfr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxSession→fr.acinq.eclair.wire.protocol.TxCompletefr.acinq.eclair.channel.fund.InteractiveTxBuilder.PartiallySignedSharedTransaction→fr.acinq.eclair.wire.protocol.TxSignaturesfr.acinq.eclair.channel.fund.InteractiveTxBuilder.ReceiveMessage→fr.acinq.eclair.wire.protocol.InteractiveTxConstructionMessagefr.acinq.eclair.channel.fund.InteractiveTxBuilder.SendMessage→fr.acinq.eclair.wire.protocol.LightningMessagefr.acinq.eclair.channel.fund.InteractiveTxBuilder.SignedSharedTransaction→fr.acinq.eclair.wire.protocol.TxSignaturesfr.acinq.eclair.channel.fund.InteractiveTxBuilder.Succeeded→fr.acinq.eclair.wire.protocol.CommitSig
- Direction
- channel.fund.InteractiveTxBuilder uses wire.protocol, so a change to wire.protocol can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break wire.protocol.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→27 channel.fund.InteractiveTxBuilder uses transactions✕
- Connections
- 5 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in transactions.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTx→fr.acinq.eclair.transactions.DirectedHtlcfr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTxRbf→fr.acinq.eclair.transactions.DirectedHtlcfr.acinq.eclair.channel.fund.InteractiveTxBuilder.Purpose→fr.acinq.eclair.transactions.DirectedHtlcfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTx→fr.acinq.eclair.transactions.DirectedHtlcfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTxRbf→fr.acinq.eclair.transactions.DirectedHtlc
- Direction
- channel.fund.InteractiveTxBuilder uses transactions, so a change to transactions can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break transactions.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→28 channel.fund.InteractiveTxBuilder uses channel.fund.InteractiveTxSigningSession✕
- Connections
- 1 pair of types, where a type in channel.fund.InteractiveTxBuilder uses a type in channel.fund.InteractiveTxSigningSession.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.Succeeded→fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs
- Direction
- channel.fund.InteractiveTxBuilder uses channel.fund.InteractiveTxSigningSession, so a change to channel.fund.InteractiveTxSigningSession can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break channel.fund.InteractiveTxSigningSession.
- Position
- Below the diagonal: channel.fund.InteractiveTxBuilder uses a module listed above it, which is the healthy direction.
29→31 channel.fund.InteractiveTxBuilder uses blockchain.fee part of a loop✕
- Connections
- 7 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.FullySignedSharedTransaction→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTx→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTxRbf→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParams→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.Purpose→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTx→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTxRbf→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- channel.fund.InteractiveTxBuilder uses blockchain.fee, so a change to blockchain.fee can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break blockchain.fee.
- 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→32 channel.fund.InteractiveTxBuilder uses channel part of a loop✕
- Connections
- 10 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in channel.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.Failed→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTxRbf→fr.acinq.eclair.channel.Commitmentfr.acinq.eclair.channel.fund.InteractiveTxBuilder.LocalFailure→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.channel.fund.InteractiveTxBuilder.RemoteFailure→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedFundingInput→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedFundingInput→fr.acinq.eclair.channel.ChannelSpendSignaturefr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTx→fr.acinq.eclair.channel.Commitmentfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTx→fr.acinq.eclair.channel.CommitmentChangesfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTxRbf→fr.acinq.eclair.channel.Commitmentfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTxRbf→fr.acinq.eclair.channel.CommitmentChanges
- Direction
- channel.fund.InteractiveTxBuilder uses channel, so a change to channel can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break channel.
- 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 channel.fund.InteractiveTxBuilder uses balance.BalanceActor part of a loop✕
- Connections
- 8 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.Abort→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundTransactionResult→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.ReceiveMessage→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.SignTransactionResult→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.Start→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.UtxosUnlocked→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.ValidateSharedTx→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.fund.InteractiveTxBuilder.WalletFailure→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- channel.fund.InteractiveTxBuilder uses balance.BalanceActor, so a change to balance.BalanceActor can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break balance.BalanceActor.
- 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→36 channel.fund.InteractiveTxBuilder uses fr.acinq.eclair part of a loop✕
- Connections
- 9 pairs of types, where a type in channel.fund.InteractiveTxBuilder uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTx→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.FundingTxRbf→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.Input→fr.acinq.eclair.UInt64fr.acinq.eclair.channel.fund.InteractiveTxBuilder.InteractiveTxParams→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.Output→fr.acinq.eclair.UInt64fr.acinq.eclair.channel.fund.InteractiveTxBuilder.Purpose→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedTransaction→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTx→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.fund.InteractiveTxBuilder.SpliceTxRbf→fr.acinq.eclair.MilliSatoshi
- Direction
- channel.fund.InteractiveTxBuilder uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel.fund.InteractiveTxBuilder, while a change to channel.fund.InteractiveTxBuilder can't break fr.acinq.eclair.
- 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 blockchain.bitcoind.rpc uses blockchain✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in blockchain.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.blockchain.OnChainWallet
- Direction
- blockchain.bitcoind.rpc uses blockchain, so a change to blockchain can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break blockchain.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→5 blockchain.bitcoind.rpc uses io.PeerReadyManager✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- blockchain.bitcoind.rpc uses io.PeerReadyManager, so a change to io.PeerReadyManager can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break io.PeerReadyManager.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→8 blockchain.bitcoind.rpc uses crypto.keymanager✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.crypto.keymanager.OnChainKeyManager
- Direction
- blockchain.bitcoind.rpc uses crypto.keymanager, so a change to crypto.keymanager can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break crypto.keymanager.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→9 blockchain.bitcoind.rpc uses io.PeerReadyNotifier✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BatchingBitcoinJsonRPCClient→fr.acinq.eclair.io.PeerReadyNotifier.Timeout
- Direction
- blockchain.bitcoind.rpc uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→26 blockchain.bitcoind.rpc uses wire.protocol✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.wire.protocol.ChannelAnnouncement
- Direction
- blockchain.bitcoind.rpc uses wire.protocol, so a change to wire.protocol can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break wire.protocol.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→29 blockchain.bitcoind.rpc uses channel.fund.InteractiveTxBuilder✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in channel.fund.InteractiveTxBuilder.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BasicBitcoinJsonRPCClient→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.Response
- Direction
- blockchain.bitcoind.rpc uses channel.fund.InteractiveTxBuilder, so a change to channel.fund.InteractiveTxBuilder can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break channel.fund.InteractiveTxBuilder.
- Position
- Below the diagonal: blockchain.bitcoind.rpc uses a module listed above it, which is the healthy direction.
30→31 blockchain.bitcoind.rpc uses blockchain.fee part of a loop✕
- Connections
- 2 pairs of types, where a type in blockchain.bitcoind.rpc uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.blockchain.fee.FeeratePerKBfr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- blockchain.bitcoind.rpc uses blockchain.fee, so a change to blockchain.fee can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break blockchain.fee.
- 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→36 blockchain.bitcoind.rpc uses fr.acinq.eclair part of a loop✕
- Connections
- 1 pair of types, where a type in blockchain.bitcoind.rpc uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient→fr.acinq.eclair.BlockHeight
- Direction
- blockchain.bitcoind.rpc uses fr.acinq.eclair, so a change to fr.acinq.eclair can break blockchain.bitcoind.rpc, while a change to blockchain.bitcoind.rpc can't break fr.acinq.eclair.
- 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→13 blockchain.fee uses transactions.Transactions✕
- Connections
- 1 pair of types, where a type in blockchain.fee uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.blockchain.fee.OnChainFeeConf→fr.acinq.eclair.transactions.Transactions.CommitmentFormat
- Direction
- blockchain.fee uses transactions.Transactions, so a change to transactions.Transactions can break blockchain.fee, while a change to blockchain.fee can't break transactions.Transactions.
- Position
- Below the diagonal: blockchain.fee uses a module listed above it, which is the healthy direction.
31→30 blockchain.fee uses blockchain.bitcoind.rpc✕
- Connections
- 1 pair of types, where a type in blockchain.fee uses a type in blockchain.bitcoind.rpc.
- The types involved
fr.acinq.eclair.blockchain.fee.BitcoinCoreFeeProvider→fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinJsonRPCClient
- Direction
- blockchain.fee uses blockchain.bitcoind.rpc, so a change to blockchain.bitcoind.rpc can break blockchain.fee, while a change to blockchain.fee can't break blockchain.bitcoind.rpc.
- Position
- Below the diagonal: blockchain.fee uses a module listed above it, which is the healthy direction.
32→2 channel uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in channel uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.channel.CMD_ADD_HTLC→fr.acinq.eclair.channel.Upstream.Hot
- Direction
- channel uses channel.Upstream, so a change to channel.Upstream can break channel, while a change to channel can't break channel.Upstream.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→5 channel uses io.PeerReadyManager✕
- Connections
- 8 pairs of types, where a type in channel uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.channel.CMD_SPLICE→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.DATA_CLOSING→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.DATA_NEGOTIATING→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.DATA_NEGOTIATING_SIMPLE→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.DustExposure→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.LocalChanges→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.LocalCommit→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.channel.RemoteChanges→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- channel uses io.PeerReadyManager, so a change to io.PeerReadyManager can break channel, while a change to channel can't break io.PeerReadyManager.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→6 channel uses payment.relay.Relayer✕
- Connections
- 1 pair of types, where a type in channel uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.channel.Helpers→fr.acinq.eclair.payment.relay.Relayer.RelayFees
- Direction
- channel uses payment.relay.Relayer, so a change to payment.relay.Relayer can break channel, while a change to channel can't break payment.relay.Relayer.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→8 channel uses crypto.keymanager✕
- Connections
- 10 pairs of types, where a type in channel uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.channel.Commitment→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.channel.FullCommitment→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.channel.FullCommitment→fr.acinq.eclair.crypto.keymanager.LocalCommitmentKeysfr.acinq.eclair.channel.FullCommitment→fr.acinq.eclair.crypto.keymanager.RemoteCommitmentKeysfr.acinq.eclair.channel.Helpers→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.channel.PersistentChannelDataWithKeys→fr.acinq.eclair.crypto.keymanager.ChannelKeysfr.acinq.eclair.channel.RemoteCommit→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- channel uses crypto.keymanager, so a change to crypto.keymanager can break channel, while a change to channel can't break crypto.keymanager.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→11 channel uses db✕
- Connections
- 1 pair of types, where a type in channel uses a type in db.
- The types involved
fr.acinq.eclair.channel.InvalidLiquidityAdsPaymentType→fr.acinq.eclair.db.PaymentType
- Direction
- channel uses db, so a change to db can break channel, while a change to channel can't break db.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→13 channel uses transactions.Transactions✕
- Connections
- 17 pairs of types, where a type in channel uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.channel.ClosingTxProposed→fr.acinq.eclair.transactions.Transactions.ClosingTxfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.transactions.Transactions.InputInfofr.acinq.eclair.channel.DATA_CLOSING→fr.acinq.eclair.transactions.Transactions.ClosingTxfr.acinq.eclair.channel.DATA_NEGOTIATING→fr.acinq.eclair.transactions.Transactions.ClosingTxfr.acinq.eclair.channel.DATA_NEGOTIATING_SIMPLE→fr.acinq.eclair.transactions.Transactions.ClosingTxfr.acinq.eclair.channel.DATA_NEGOTIATING_SIMPLE→fr.acinq.eclair.transactions.Transactions.ClosingTxsfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_CREATED→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_INTERNAL→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_SIGNED→fr.acinq.eclair.transactions.Transactions.CommitTxfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_SIGNED→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.DustExposure→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.FullCommitment→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.FullCommitment→fr.acinq.eclair.transactions.Transactions.InputInfofr.acinq.eclair.channel.RemoteCommit→fr.acinq.eclair.transactions.Transactions.CommitmentFormatfr.acinq.eclair.channel.RemoteCommit→fr.acinq.eclair.transactions.Transactions.InputInfofr.acinq.eclair.channel.SupportedChannelType→fr.acinq.eclair.transactions.Transactions.CommitmentFormat
- Direction
- channel uses transactions.Transactions, so a change to transactions.Transactions can break channel, while a change to channel can't break transactions.Transactions.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→15 channel uses wire.protocol.LiquidityAds✕
- Connections
- 10 pairs of types, where a type in channel uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.channel.CMD_ADD_HTLC→fr.acinq.eclair.wire.protocol.LiquidityAds.FundingFeefr.acinq.eclair.channel.CMD_BUMP_FUNDING_FEE→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.channel.CMD_SPLICE→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.LiquidityAds.PurchaseBasicInfofr.acinq.eclair.channel.Helpers→fr.acinq.eclair.wire.protocol.LiquidityAds.AddFundingfr.acinq.eclair.channel.INPUT_INIT_CHANNEL_INITIATOR→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFundingfr.acinq.eclair.channel.INPUT_INIT_CHANNEL_NON_INITIATOR→fr.acinq.eclair.wire.protocol.LiquidityAds.AddFundingfr.acinq.eclair.channel.LiquidityPurchase→fr.acinq.eclair.wire.protocol.LiquidityAds.Feesfr.acinq.eclair.channel.LocalFundingStatus→fr.acinq.eclair.wire.protocol.LiquidityAds.PurchaseBasicInfofr.acinq.eclair.channel.TransactionPublished→fr.acinq.eclair.wire.protocol.LiquidityAds.PurchaseBasicInfo
- Direction
- channel uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break channel, while a change to channel can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→25 channel uses io.Peer✕
- Connections
- 12 pairs of types, where a type in channel uses a type in io.Peer.
- The types involved
fr.acinq.eclair.channel.ChannelParams→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.channel.DATA_WAIT_FOR_ACCEPT_CHANNEL→fr.acinq.eclair.io.Peer.OpenChannelfr.acinq.eclair.channel.DATA_WAIT_FOR_DUAL_FUNDING_CREATED→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_INTERNAL→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_SIGNED→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.channel.Helpers→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.channel.Helpers→fr.acinq.eclair.io.Peer.OpenChannelfr.acinq.eclair.channel.INPUT_INIT_CHANNEL_INITIATOR→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.channel.INPUT_INIT_CHANNEL_INITIATOR→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.channel.INPUT_INIT_CHANNEL_NON_INITIATOR→fr.acinq.eclair.io.Peer.Initfr.acinq.eclair.channel.INPUT_RECONNECTED→fr.acinq.eclair.io.Peer.Init
- Direction
- channel uses io.Peer, so a change to io.Peer can break channel, while a change to channel can't break io.Peer.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→26 channel uses wire.protocol✕
- Connections
- 55 pairs of types, where a type in channel uses a type in wire.protocol. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.channel.AnnouncedCommitment→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.channel.AvailableBalanceChanged→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.channel.CMD_ADD_HTLC→fr.acinq.eclair.wire.protocol.OnionRoutingPacketfr.acinq.eclair.channel.CMD_FAIL_HTLC→fr.acinq.eclair.wire.protocol.FailureReasonfr.acinq.eclair.channel.CannotExtractSharedSecret→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.channel.ChannelUpdateParametersChanged→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.channel.ClosingTxProposed→fr.acinq.eclair.wire.protocol.ClosingSignedfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.wire.protocol.AnnouncementSignaturesfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.wire.protocol.CommitSigfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.channel.CommitmentChanges→fr.acinq.eclair.wire.protocol.UpdateMessagefr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.CommitSigsfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.RevokeAndAckfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.TxSignaturesfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.UpdateAddHtlcfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.UpdateFailHtlcfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.UpdateFailMalformedHtlcfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.UpdateFeefr.acinq.eclair.channel.Commitments→fr.acinq.eclair.wire.protocol.UpdateFulfillHtlcfr.acinq.eclair.channel.DATA_NEGOTIATING→fr.acinq.eclair.wire.protocol.Shutdownfr.acinq.eclair.channel.DATA_NORMAL→fr.acinq.eclair.wire.protocol.ChannelAnnouncementfr.acinq.eclair.channel.DATA_NORMAL→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.channel.DATA_NORMAL→fr.acinq.eclair.wire.protocol.Shutdownfr.acinq.eclair.channel.DATA_SHUTDOWN→fr.acinq.eclair.wire.protocol.Shutdownfr.acinq.eclair.channel.DATA_WAIT_FOR_ACCEPT_DUAL_FUNDED_CHANNEL→fr.acinq.eclair.wire.protocol.OpenDualFundedChannel
- Direction
- channel uses wire.protocol, so a change to wire.protocol can break channel, while a change to channel can't break wire.protocol.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→27 channel uses transactions✕
- Connections
- 5 pairs of types, where a type in channel uses a type in transactions.
- The types involved
fr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_SIGNED→fr.acinq.eclair.transactions.CommitmentSpecfr.acinq.eclair.channel.DustExposure→fr.acinq.eclair.transactions.CommitmentSpecfr.acinq.eclair.channel.DustExposure→fr.acinq.eclair.transactions.DirectedHtlcfr.acinq.eclair.channel.LocalCommit→fr.acinq.eclair.transactions.CommitmentSpecfr.acinq.eclair.channel.RemoteCommit→fr.acinq.eclair.transactions.CommitmentSpec
- Direction
- channel uses transactions, so a change to transactions can break channel, while a change to channel can't break transactions.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→28 channel uses channel.fund.InteractiveTxSigningSession✕
- Connections
- 1 pair of types, where a type in channel uses a type in channel.fund.InteractiveTxSigningSession.
- The types involved
fr.acinq.eclair.channel.DATA_WAIT_FOR_DUAL_FUNDING_SIGNED→fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs
- Direction
- channel uses channel.fund.InteractiveTxSigningSession, so a change to channel.fund.InteractiveTxSigningSession can break channel, while a change to channel can't break channel.fund.InteractiveTxSigningSession.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→31 channel uses blockchain.fee✕
- Connections
- 26 pairs of types, where a type in channel uses a type in blockchain.fee. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.channel.CMD_BUMP_FORCE_CLOSE_FEE→fr.acinq.eclair.blockchain.fee.ConfirmationTargetfr.acinq.eclair.channel.CMD_BUMP_FUNDING_FEE→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.CMD_FORCECLOSE→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.CMD_UPDATE_FEE→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.ChannelCreated→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.ClosingFeerates→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.blockchain.fee.FeeratesPerKwfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.blockchain.fee.OnChainFeeConffr.acinq.eclair.channel.Commitments→fr.acinq.eclair.blockchain.fee.FeeratesPerKwfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.blockchain.fee.OnChainFeeConffr.acinq.eclair.channel.DATA_CLOSING→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.DATA_NEGOTIATING_SIMPLE→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_CREATED→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.DATA_WAIT_FOR_FUNDING_INTERNAL→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.DustExposure→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.FeerateTooDifferent→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.FeerateTooSmall→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.FundingFeerateTooLow→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.Helpers→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.INPUT_INIT_CHANNEL_INITIATOR→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.InvalidFundingFeerate→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.InvalidRbfFeerate→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.InvalidRbfFeerateTooHigh→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.channel.InvalidSpliceFeerate→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- channel uses blockchain.fee, so a change to blockchain.fee can break channel, while a change to channel can't break blockchain.fee.
- Position
- Below the diagonal: channel uses a module listed above it, which is the healthy direction.
32→33 channel uses balance.BalanceActor part of a loop✕
- Connections
- 8 pairs of types, where a type in channel uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.channel.CMD_BUMP_FORCE_CLOSE_FEE→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.CMD_GET_CHANNEL_INFO→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.ChannelFundingCommand→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.DATA_WAIT_FOR_DUAL_FUNDING_CREATED→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.ForbiddenCommandDuringQuiescenceNegotiation→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.ForbiddenCommandWhenQuiescent→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.HasOptionalReplyToCommand→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.HasReplyToCommand→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- channel uses balance.BalanceActor, so a change to balance.BalanceActor can break channel, while a change to channel can't break balance.BalanceActor.
- 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.
32→36 channel uses fr.acinq.eclair part of a loop✕
- Connections
- 99 pairs of types, where a type in channel uses a type in fr.acinq.eclair. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.channel.AnnouncedCommitment→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.channel.CMD_ADD_HTLC→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.channel.CMD_ADD_HTLC→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.CMD_SPLICE→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.CMD_UPDATE_RELAY_FEE→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.ChannelFeatures→fr.acinq.eclair.PermanentChannelFeaturefr.acinq.eclair.channel.ChannelFundingConfirmed→fr.acinq.eclair.BlockHeightfr.acinq.eclair.channel.ChannelReserveNotMet→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.ChannelTypes→fr.acinq.eclair.Featuresfr.acinq.eclair.channel.ChannelTypes→fr.acinq.eclair.InitFeaturefr.acinq.eclair.channel.CommitParams→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.channel.CommitParams→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.CommitParams→fr.acinq.eclair.UInt64fr.acinq.eclair.channel.Commitment→fr.acinq.eclair.BlockHeightfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.channel.Commitment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.Commitment→fr.acinq.eclair.NodeParamsfr.acinq.eclair.channel.Commitment→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.BlockHeightfr.acinq.eclair.channel.Commitments→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.channel.Commitments→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.Commitments→fr.acinq.eclair.RealShortChannelIdfr.acinq.eclair.channel.DATA_CLOSED→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.channel.DATA_CLOSING→fr.acinq.eclair.BlockHeightfr.acinq.eclair.channel.DATA_WAIT_FOR_DUAL_FUNDING_CONFIRMED→fr.acinq.eclair.BlockHeight
- Direction
- channel uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel, while a change to channel can't break fr.acinq.eclair.
- 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.
33→32 balance.BalanceActor uses channel✕
- Connections
- 1 pair of types, where a type in balance.BalanceActor uses a type in channel.
- The types involved
fr.acinq.eclair.balance.BalanceActor.GetGlobalBalance→fr.acinq.eclair.channel.PersistentChannelData
- Direction
- balance.BalanceActor uses channel, so a change to channel can break balance.BalanceActor, while a change to balance.BalanceActor can't break channel.
- Position
- Below the diagonal: balance.BalanceActor uses a module listed above it, which is the healthy direction.
34→2 payment.send.PaymentInitiator uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in payment.send.PaymentInitiator uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentConfig→fr.acinq.eclair.channel.Upstream.Hot
- Direction
- payment.send.PaymentInitiator uses channel.Upstream, so a change to channel.Upstream can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break channel.Upstream.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→14 payment.send.PaymentInitiator uses payment✕
- Connections
- 5 pairs of types, where a type in payment.send.PaymentInitiator uses a type in payment.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentConfig→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToNode→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToRoute→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.payment.send.PaymentInitiator.SendRequestedPayment→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.payment.send.PaymentInitiator.SendTrampolinePayment→fr.acinq.eclair.payment.Invoice
- Direction
- payment.send.PaymentInitiator uses payment, so a change to payment can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break payment.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→17 payment.send.PaymentInitiator uses message.OnionMessages✕
- Connections
- 1 pair of types, where a type in payment.send.PaymentInitiator uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentConfig→fr.acinq.eclair.message.OnionMessages.Recipient
- Direction
- payment.send.PaymentInitiator uses message.OnionMessages, so a change to message.OnionMessages can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break message.OnionMessages.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→22 payment.send.PaymentInitiator uses router.Router✕
- Connections
- 5 pairs of types, where a type in payment.send.PaymentInitiator uses a type in router.Router.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentConfig→fr.acinq.eclair.router.Router.PaymentContextfr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToNode→fr.acinq.eclair.router.Router.RouteParamsfr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToRoute→fr.acinq.eclair.router.Router.PredefinedRoutefr.acinq.eclair.payment.send.PaymentInitiator.SendSpontaneousPayment→fr.acinq.eclair.router.Router.RouteParamsfr.acinq.eclair.payment.send.PaymentInitiator.SendTrampolinePayment→fr.acinq.eclair.router.Router.RouteParams
- Direction
- payment.send.PaymentInitiator uses router.Router, so a change to router.Router can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break router.Router.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→26 payment.send.PaymentInitiator uses wire.protocol✕
- Connections
- 2 pairs of types, where a type in payment.send.PaymentInitiator uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToNode→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.payment.send.PaymentInitiator.SendSpontaneousPayment→fr.acinq.eclair.wire.protocol.GenericTlv
- Direction
- payment.send.PaymentInitiator uses wire.protocol, so a change to wire.protocol can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break wire.protocol.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→33 payment.send.PaymentInitiator uses balance.BalanceActor✕
- Connections
- 2 pairs of types, where a type in payment.send.PaymentInitiator uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SimplePaymentFactory→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.send.PaymentInitiator.TrampolinePaymentFactory→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.send.PaymentInitiator uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break balance.BalanceActor.
- Position
- Below the diagonal: payment.send.PaymentInitiator uses a module listed above it, which is the healthy direction.
34→35 payment.send.PaymentInitiator uses payment.send part of a loop✕
- Connections
- 2 pairs of types, where a type in payment.send.PaymentInitiator uses a type in payment.send.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.GetPayment→fr.acinq.eclair.payment.send.PaymentIdentifierfr.acinq.eclair.payment.send.PaymentInitiator.NoPendingPayment→fr.acinq.eclair.payment.send.PaymentIdentifier
- Direction
- payment.send.PaymentInitiator uses payment.send, so a change to payment.send can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break payment.send.
- 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.
34→36 payment.send.PaymentInitiator uses fr.acinq.eclair part of a loop✕
- Connections
- 9 pairs of types, where a type in payment.send.PaymentInitiator uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentConfig→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToNode→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToRoute→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.PaymentInitiator.SendRequestedPayment→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.PaymentInitiator.SendRequestedPayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.PaymentInitiator.SendRequestedPayment→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.send.PaymentInitiator.SendSpontaneousPayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.PaymentInitiator.SendTrampolinePayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.PaymentInitiator.SimplePaymentFactory→fr.acinq.eclair.NodeParams
- Direction
- payment.send.PaymentInitiator uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.send.PaymentInitiator, while a change to payment.send.PaymentInitiator can't break fr.acinq.eclair.
- 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.
35→3 payment.send uses crypto.Sphinx.RouteBlinding✕
- Connections
- 1 pair of types, where a type in payment.send uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedHop
- Direction
- payment.send uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break payment.send, while a change to payment.send can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→4 payment.send uses crypto.TransportHandler✕
- Connections
- 4 pairs of types, where a type in payment.send uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.payment.send.Autoprobe→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.payment.send.MultiPartPaymentLifecycle→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.crypto.TransportHandler.Datafr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.crypto.TransportHandler.State
- Direction
- payment.send uses crypto.TransportHandler, so a change to crypto.TransportHandler can break payment.send, while a change to payment.send can't break crypto.TransportHandler.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→11 payment.send uses db✕
- Connections
- 1 pair of types, where a type in payment.send uses a type in db.
- The types involved
fr.acinq.eclair.payment.send.TrampolinePayment→fr.acinq.eclair.db.OutgoingPayment
- Direction
- payment.send uses db, so a change to db can break payment.send, while a change to payment.send can't break db.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→14 payment.send uses payment✕
- Connections
- 5 pairs of types, where a type in payment.send uses a type in payment.
- The types involved
fr.acinq.eclair.payment.send.MultiPartPaymentLifecycle→fr.acinq.eclair.payment.PaymentEventfr.acinq.eclair.payment.send.MultiPartPaymentLifecycle→fr.acinq.eclair.payment.PaymentFailedfr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.payment.PaymentFailedfr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.payment.PaymentFailurefr.acinq.eclair.payment.send.TrampolinePayment→fr.acinq.eclair.payment.Invoice
- Direction
- payment.send uses payment, so a change to payment can break payment.send, while a change to payment.send can't break payment.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→17 payment.send uses message.OnionMessages✕
- Connections
- 4 pairs of types, where a type in payment.send uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.message.OnionMessages.Recipientfr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.message.OnionMessages.Recipientfr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.message.OnionMessages.Recipientfr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.message.OnionMessages.Recipient
- Direction
- payment.send uses message.OnionMessages, so a change to message.OnionMessages can break payment.send, while a change to payment.send can't break message.OnionMessages.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→20 payment.send uses payment.offer.OfferManager.InvoiceRequestActor✕
- Connections
- 4 pairs of types, where a type in payment.send uses a type in payment.offer.OfferManager.InvoiceRequestActor.
- The types involved
fr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.payment.send.Recipient→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Routefr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route
- Direction
- payment.send uses payment.offer.OfferManager.InvoiceRequestActor, so a change to payment.offer.OfferManager.InvoiceRequestActor can break payment.send, while a change to payment.send can't break payment.offer.OfferManager.InvoiceRequestActor.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→23 payment.send uses io.PeerConnection✕
- Connections
- 3 pairs of types, where a type in payment.send uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.payment.send.BlindedPathsResolver→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.send.OfferPayment→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.send.TrampolinePaymentLifecycle→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- payment.send uses io.PeerConnection, so a change to io.PeerConnection can break payment.send, while a change to payment.send can't break io.PeerConnection.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→25 payment.send uses io.Peer✕
- Connections
- 1 pair of types, where a type in payment.send uses a type in io.Peer.
- The types involved
fr.acinq.eclair.payment.send.TrampolinePaymentLifecycle→fr.acinq.eclair.io.Peer.GetPeerChannels
- Direction
- payment.send uses io.Peer, so a change to io.Peer can break payment.send, while a change to payment.send can't break io.Peer.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→26 payment.send uses wire.protocol✕
- Connections
- 6 pairs of types, where a type in payment.send uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.wire.protocol.GenericTlvfr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.wire.protocol.OnionRoutingPacketfr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.wire.protocol.Updatefr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.wire.protocol.UpdateFailHtlcfr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.wire.protocol.GenericTlv
- Direction
- payment.send uses wire.protocol, so a change to wire.protocol can break payment.send, while a change to payment.send can't break wire.protocol.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→33 payment.send uses balance.BalanceActor✕
- Connections
- 3 pairs of types, where a type in payment.send uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.send.BlindedPathsResolver→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.send.OfferPayment→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.send.TrampolinePaymentLifecycle→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.send uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.send, while a change to payment.send can't break balance.BalanceActor.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→34 payment.send uses payment.send.PaymentInitiator✕
- Connections
- 1 pair of types, where a type in payment.send uses a type in payment.send.PaymentInitiator.
- The types involved
fr.acinq.eclair.payment.send.PaymentInitiator→fr.acinq.eclair.payment.send.PaymentInitiator.PendingPayment
- Direction
- payment.send uses payment.send.PaymentInitiator, so a change to payment.send.PaymentInitiator can break payment.send, while a change to payment.send can't break payment.send.PaymentInitiator.
- Position
- Below the diagonal: payment.send uses a module listed above it, which is the healthy direction.
35→36 payment.send uses fr.acinq.eclair part of a loop✕
- Connections
- 24 pairs of types, where a type in payment.send uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.send.BlindedPathsResolver→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.send.BlindedRecipient→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.send.ClearRecipient→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.MultiPartPaymentLifecycle→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.payment.send.MultiPartPaymentLifecycle→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.send.OfferPayment→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.send.PaymentLifecycle→fr.acinq.eclair.FSMDiagnosticActorLoggingfr.acinq.eclair.payment.send.Recipient→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.Recipient→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.send.Recipient→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.send.Recipient→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.InvoiceFeaturefr.acinq.eclair.payment.send.SpontaneousRecipient→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.TrampolinePayment→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.send.TrampolinePayment→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.send.TrampolinePaymentLifecycle→fr.acinq.eclair.NodeParams
- Direction
- payment.send uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.send, while a change to payment.send can't break fr.acinq.eclair.
- 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.
36→1 fr.acinq.eclair uses blockchain✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in blockchain.
- The types involved
fr.acinq.eclair.Kit→fr.acinq.eclair.blockchain.OnChainWallet
- Direction
- fr.acinq.eclair uses blockchain, so a change to blockchain can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break blockchain.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→2 fr.acinq.eclair uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.CustomCommitmentsPlugin→fr.acinq.eclair.channel.Upstream.Cold
- Direction
- fr.acinq.eclair uses channel.Upstream, so a change to channel.Upstream can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break channel.Upstream.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→3 fr.acinq.eclair uses crypto.Sphinx.RouteBlinding✕
- Connections
- 2 pairs of types, where a type in fr.acinq.eclair uses a type in crypto.Sphinx.RouteBlinding.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoutefr.acinq.eclair.EclairImpl→fr.acinq.eclair.crypto.Sphinx.RouteBlinding.BlindedRoute
- Direction
- fr.acinq.eclair uses crypto.Sphinx.RouteBlinding, so a change to crypto.Sphinx.RouteBlinding can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break crypto.Sphinx.RouteBlinding.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→5 fr.acinq.eclair uses io.PeerReadyManager✕
- Connections
- 5 pairs of types, where a type in fr.acinq.eclair uses a type in io.PeerReadyManager.
- The types involved
fr.acinq.eclair.BitcoinDefaultWalletException→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.BitcoinWalletNotLoadedException→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.Eclair→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.EclairImpl→fr.acinq.eclair.io.PeerReadyManager.Listfr.acinq.eclair.NodeParams→fr.acinq.eclair.io.PeerReadyManager.List
- Direction
- fr.acinq.eclair uses io.PeerReadyManager, so a change to io.PeerReadyManager can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break io.PeerReadyManager.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→6 fr.acinq.eclair uses payment.relay.Relayer✕
- Connections
- 3 pairs of types, where a type in fr.acinq.eclair uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.payment.relay.Relayer.ChannelBalancefr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.relay.Relayer.ChannelBalancefr.acinq.eclair.NodeParams→fr.acinq.eclair.payment.relay.Relayer.RelayParams
- Direction
- fr.acinq.eclair uses payment.relay.Relayer, so a change to payment.relay.Relayer can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.relay.Relayer.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→8 fr.acinq.eclair uses crypto.keymanager✕
- Connections
- 3 pairs of types, where a type in fr.acinq.eclair uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.NodeParams→fr.acinq.eclair.crypto.keymanager.ChannelKeyManagerfr.acinq.eclair.NodeParams→fr.acinq.eclair.crypto.keymanager.NodeKeyManagerfr.acinq.eclair.NodeParams→fr.acinq.eclair.crypto.keymanager.OnChainKeyManager
- Direction
- fr.acinq.eclair uses crypto.keymanager, so a change to crypto.keymanager can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break crypto.keymanager.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→9 fr.acinq.eclair uses io.PeerReadyNotifier✕
- Connections
- 5 pairs of types, where a type in fr.acinq.eclair uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.io.PeerReadyNotifier.Timeoutfr.acinq.eclair.EclairImpl→fr.acinq.eclair.io.PeerReadyNotifier.Timeoutfr.acinq.eclair.FrontSetup→fr.acinq.eclair.io.PeerReadyNotifier.Timeoutfr.acinq.eclair.NodeParams→fr.acinq.eclair.io.PeerReadyNotifier.WakeUpConfigfr.acinq.eclair.Setup→fr.acinq.eclair.io.PeerReadyNotifier.Timeout
- Direction
- fr.acinq.eclair uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→10 fr.acinq.eclair uses wire.protocol.OfferTypes✕
- Connections
- 2 pairs of types, where a type in fr.acinq.eclair uses a type in wire.protocol.OfferTypes.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.wire.protocol.OfferTypes.Offerfr.acinq.eclair.EclairImpl→fr.acinq.eclair.wire.protocol.OfferTypes.Offer
- Direction
- fr.acinq.eclair uses wire.protocol.OfferTypes, so a change to wire.protocol.OfferTypes can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break wire.protocol.OfferTypes.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→11 fr.acinq.eclair uses db✕
- Connections
- 7 pairs of types, where a type in fr.acinq.eclair uses a type in db.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.Eclair→fr.acinq.eclair.db.OfferDatafr.acinq.eclair.Eclair→fr.acinq.eclair.db.OutgoingPaymentfr.acinq.eclair.EclairImpl→fr.acinq.eclair.db.IncomingPaymentfr.acinq.eclair.EclairImpl→fr.acinq.eclair.db.OfferDatafr.acinq.eclair.EclairImpl→fr.acinq.eclair.db.OutgoingPaymentfr.acinq.eclair.NodeParams→fr.acinq.eclair.db.Databases
- Direction
- fr.acinq.eclair uses db, so a change to db can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break db.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→14 fr.acinq.eclair uses payment✕
- Connections
- 7 pairs of types, where a type in fr.acinq.eclair uses a type in payment.
- The types involved
fr.acinq.eclair.AuditResponse→fr.acinq.eclair.payment.PaymentRelayedfr.acinq.eclair.Eclair→fr.acinq.eclair.payment.Bolt11Invoicefr.acinq.eclair.Eclair→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.Eclair→fr.acinq.eclair.payment.PaymentEventfr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.Bolt11Invoicefr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.Invoicefr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.PaymentEvent
- Direction
- fr.acinq.eclair uses payment, so a change to payment can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→15 fr.acinq.eclair uses wire.protocol.LiquidityAds✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.AcceptOpenChannel→fr.acinq.eclair.wire.protocol.LiquidityAds.AddFunding
- Direction
- fr.acinq.eclair uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→17 fr.acinq.eclair uses message.OnionMessages✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in message.OnionMessages.
- The types involved
fr.acinq.eclair.NodeParams→fr.acinq.eclair.message.OnionMessages.OnionMessageConfig
- Direction
- fr.acinq.eclair uses message.OnionMessages, so a change to message.OnionMessages can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break message.OnionMessages.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→18 fr.acinq.eclair uses payment.offer.OfferManager✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in payment.offer.OfferManager.
- The types involved
fr.acinq.eclair.Kit→fr.acinq.eclair.payment.offer.OfferManager.HandlerCommand
- Direction
- fr.acinq.eclair uses payment.offer.OfferManager, so a change to payment.offer.OfferManager can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.offer.OfferManager.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→20 fr.acinq.eclair uses payment.offer.OfferManager.InvoiceRequestActor✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in payment.offer.OfferManager.InvoiceRequestActor.
- The types involved
fr.acinq.eclair.RouteProvider→fr.acinq.eclair.payment.offer.OfferManager.InvoiceRequestActor.Route
- Direction
- fr.acinq.eclair uses payment.offer.OfferManager.InvoiceRequestActor, so a change to payment.offer.OfferManager.InvoiceRequestActor can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.offer.OfferManager.InvoiceRequestActor.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→22 fr.acinq.eclair uses router.Router✕
- Connections
- 10 pairs of types, where a type in fr.acinq.eclair uses a type in router.Router.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.Eclair→fr.acinq.eclair.router.Router.PredefinedRoutefr.acinq.eclair.Eclair→fr.acinq.eclair.router.Router.PublicNodefr.acinq.eclair.Eclair→fr.acinq.eclair.router.Router.RouteResponsefr.acinq.eclair.EclairImpl→fr.acinq.eclair.router.Router.ChannelDescfr.acinq.eclair.EclairImpl→fr.acinq.eclair.router.Router.PredefinedRoutefr.acinq.eclair.EclairImpl→fr.acinq.eclair.router.Router.PublicNodefr.acinq.eclair.EclairImpl→fr.acinq.eclair.router.Router.RouteParamsfr.acinq.eclair.EclairImpl→fr.acinq.eclair.router.Router.RouteResponsefr.acinq.eclair.NodeParams→fr.acinq.eclair.router.Router.RouterConf
- Direction
- fr.acinq.eclair uses router.Router, so a change to router.Router can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break router.Router.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→23 fr.acinq.eclair uses io.PeerConnection✕
- Connections
- 2 pairs of types, where a type in fr.acinq.eclair uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.NodeParams→fr.acinq.eclair.io.PeerConnection.Conffr.acinq.eclair.NotificationsLogger→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- fr.acinq.eclair uses io.PeerConnection, so a change to io.PeerConnection can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break io.PeerConnection.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→24 fr.acinq.eclair uses io✕
- Connections
- 2 pairs of types, where a type in fr.acinq.eclair uses a type in io.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.io.NodeURIfr.acinq.eclair.EclairImpl→fr.acinq.eclair.io.NodeURI
- Direction
- fr.acinq.eclair uses io, so a change to io can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break io.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→25 fr.acinq.eclair uses io.Peer✕
- Connections
- 4 pairs of types, where a type in fr.acinq.eclair uses a type in io.Peer.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.Eclair→fr.acinq.eclair.io.Peer.PeerInfofr.acinq.eclair.EclairImpl→fr.acinq.eclair.io.Peer.OpenChannelResponsefr.acinq.eclair.EclairImpl→fr.acinq.eclair.io.Peer.PeerInfo
- Direction
- fr.acinq.eclair uses io.Peer, so a change to io.Peer can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break io.Peer.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→26 fr.acinq.eclair uses wire.protocol✕
- Connections
- 11 pairs of types, where a type in fr.acinq.eclair uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.Eclair→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.EclairImpl→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.EclairImpl→fr.acinq.eclair.wire.protocol.NodeAnnouncementfr.acinq.eclair.GetInfoResponse→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.NodeParams→fr.acinq.eclair.wire.protocol.Colorfr.acinq.eclair.NodeParams→fr.acinq.eclair.wire.protocol.NodeAddressfr.acinq.eclair.NodeParams→fr.acinq.eclair.wire.protocol.RecommendedFeeratesfr.acinq.eclair.SendOnionMessageResponsePayload→fr.acinq.eclair.wire.protocol.OnionMessagePayloadTlvfr.acinq.eclair.SendOnionMessageResponsePayload→fr.acinq.eclair.wire.protocol.TlvStreamfr.acinq.eclair.Setup→fr.acinq.eclair.wire.protocol.NodeAddress
- Direction
- fr.acinq.eclair uses wire.protocol, so a change to wire.protocol can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break wire.protocol.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→31 fr.acinq.eclair uses blockchain.fee✕
- Connections
- 10 pairs of types, where a type in fr.acinq.eclair uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.blockchain.fee.ConfirmationTargetfr.acinq.eclair.Eclair→fr.acinq.eclair.blockchain.fee.FeeratePerBytefr.acinq.eclair.Eclair→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.EclairImpl→fr.acinq.eclair.blockchain.fee.ConfirmationTargetfr.acinq.eclair.EclairImpl→fr.acinq.eclair.blockchain.fee.FeeratePerBytefr.acinq.eclair.EclairImpl→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.NodeParams→fr.acinq.eclair.blockchain.fee.FeeratePerKwfr.acinq.eclair.NodeParams→fr.acinq.eclair.blockchain.fee.FeeratesPerKwfr.acinq.eclair.NodeParams→fr.acinq.eclair.blockchain.fee.OnChainFeeConffr.acinq.eclair.SpendFromChannelAddress→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- fr.acinq.eclair uses blockchain.fee, so a change to blockchain.fee can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break blockchain.fee.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→32 fr.acinq.eclair uses channel✕
- Connections
- 26 pairs of types, where a type in fr.acinq.eclair uses a type in channel. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
fr.acinq.eclair.DBChecker→fr.acinq.eclair.channel.PersistentChannelDataWithKeysfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_BUMP_FORCE_CLOSE_FEEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_BUMP_FUNDING_FEEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_CLOSEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_FORCECLOSEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_GET_CHANNEL_INFOfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_SPLICEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CMD_UPDATE_RELAY_FEEfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.ChannelSpendSignaturefr.acinq.eclair.Eclair→fr.acinq.eclair.channel.ClosingFeeratesfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.CommandResponsefr.acinq.eclair.Eclair→fr.acinq.eclair.channel.DATA_CLOSEDfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.RES_GET_CHANNEL_INFOfr.acinq.eclair.Eclair→fr.acinq.eclair.channel.SupportedChannelTypefr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_BUMP_FORCE_CLOSE_FEEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_BUMP_FUNDING_FEEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_CLOSEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_FORCECLOSEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_SPLICEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CMD_UPDATE_RELAY_FEEfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.ClosingFeeratesfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.CommandResponsefr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.DATA_CLOSEDfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.RES_GET_CHANNEL_INFOfr.acinq.eclair.EclairImpl→fr.acinq.eclair.channel.SupportedChannelType
- Direction
- fr.acinq.eclair uses channel, so a change to channel can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break channel.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→33 fr.acinq.eclair uses balance.BalanceActor✕
- Connections
- 1 pair of types, where a type in fr.acinq.eclair uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.Kit→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- fr.acinq.eclair uses balance.BalanceActor, so a change to balance.BalanceActor can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break balance.BalanceActor.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→34 fr.acinq.eclair uses payment.send.PaymentInitiator✕
- Connections
- 3 pairs of types, where a type in fr.acinq.eclair uses a type in payment.send.PaymentInitiator.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToRouteResponsefr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToNodefr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.send.PaymentInitiator.SendPaymentToRouteResponse
- Direction
- fr.acinq.eclair uses payment.send.PaymentInitiator, so a change to payment.send.PaymentInitiator can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.send.PaymentInitiator.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
36→35 fr.acinq.eclair uses payment.send✕
- Connections
- 2 pairs of types, where a type in fr.acinq.eclair uses a type in payment.send.
- The types involved
fr.acinq.eclair.Eclair→fr.acinq.eclair.payment.send.PaymentIdentifierfr.acinq.eclair.EclairImpl→fr.acinq.eclair.payment.send.PaymentIdentifier
- Direction
- fr.acinq.eclair uses payment.send, so a change to payment.send can break fr.acinq.eclair, while a change to fr.acinq.eclair can't break payment.send.
- Position
- Below the diagonal: fr.acinq.eclair uses a module listed above it, which is the healthy direction.
37→13 channel.publish.TxPublisher uses transactions.Transactions✕
- Connections
- 1 pair of types, where a type in channel.publish.TxPublisher uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.PublishReplaceableTx→fr.acinq.eclair.transactions.Transactions.ForceCloseTransaction
- Direction
- channel.publish.TxPublisher uses transactions.Transactions, so a change to transactions.Transactions can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break transactions.Transactions.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
37→30 channel.publish.TxPublisher uses blockchain.bitcoind.rpc✕
- Connections
- 1 pair of types, where a type in channel.publish.TxPublisher uses a type in blockchain.bitcoind.rpc.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.SimpleChildFactory→fr.acinq.eclair.blockchain.bitcoind.rpc.BitcoinCoreClient
- Direction
- channel.publish.TxPublisher uses blockchain.bitcoind.rpc, so a change to blockchain.bitcoind.rpc can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break blockchain.bitcoind.rpc.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
37→31 channel.publish.TxPublisher uses blockchain.fee✕
- Connections
- 2 pairs of types, where a type in channel.publish.TxPublisher uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.PublishReplaceableTx→fr.acinq.eclair.blockchain.fee.ConfirmationTargetfr.acinq.eclair.channel.publish.TxPublisher.ReplaceableAttempt→fr.acinq.eclair.blockchain.fee.ConfirmationTarget
- Direction
- channel.publish.TxPublisher uses blockchain.fee, so a change to blockchain.fee can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break blockchain.fee.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
37→32 channel.publish.TxPublisher uses channel✕
- Connections
- 1 pair of types, where a type in channel.publish.TxPublisher uses a type in channel.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.PublishReplaceableTx→fr.acinq.eclair.channel.FullCommitment
- Direction
- channel.publish.TxPublisher uses channel, so a change to channel can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break channel.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
37→33 channel.publish.TxPublisher uses balance.BalanceActor✕
- Connections
- 8 pairs of types, where a type in channel.publish.TxPublisher uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.ChildFactory→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.FinalAttempt→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.PublishTx→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.PublishTxResult→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.ReplaceableAttempt→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.SetChannelId→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.SimpleChildFactory→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.channel.publish.TxPublisher.WrappedCurrentBlockHeight→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- channel.publish.TxPublisher uses balance.BalanceActor, so a change to balance.BalanceActor can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break balance.BalanceActor.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
37→36 channel.publish.TxPublisher uses fr.acinq.eclair✕
- Connections
- 2 pairs of types, where a type in channel.publish.TxPublisher uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.channel.publish.TxPublisher.SimpleChildFactory→fr.acinq.eclair.NodeParamsfr.acinq.eclair.channel.publish.TxPublisher.WrappedCurrentBlockHeight→fr.acinq.eclair.BlockHeight
- Direction
- channel.publish.TxPublisher uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel.publish.TxPublisher, while a change to channel.publish.TxPublisher can't break fr.acinq.eclair.
- Position
- Below the diagonal: channel.publish.TxPublisher uses a module listed above it, which is the healthy direction.
38→9 payment.relay.NodeRelay uses io.PeerReadyNotifier✕
- Connections
- 1 pair of types, where a type in payment.relay.NodeRelay uses a type in io.PeerReadyNotifier.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.WrappedPeerReadyResult→fr.acinq.eclair.io.PeerReadyNotifier.Result
- Direction
- payment.relay.NodeRelay uses io.PeerReadyNotifier, so a change to io.PeerReadyNotifier can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break io.PeerReadyNotifier.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
38→14 payment.relay.NodeRelay uses payment✕
- Connections
- 1 pair of types, where a type in payment.relay.NodeRelay uses a type in payment.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.WrappedPaymentFailed→fr.acinq.eclair.payment.PaymentFailed
- Direction
- payment.relay.NodeRelay uses payment, so a change to payment can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break payment.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
38→25 payment.relay.NodeRelay uses io.Peer✕
- Connections
- 1 pair of types, where a type in payment.relay.NodeRelay uses a type in io.Peer.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.WrappedOnTheFlyFundingResponse→fr.acinq.eclair.io.Peer.ProposeOnTheFlyFundingResponse
- Direction
- payment.relay.NodeRelay uses io.Peer, so a change to io.Peer can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break io.Peer.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
38→33 payment.relay.NodeRelay uses balance.BalanceActor✕
- Connections
- 14 pairs of types, where a type in payment.relay.NodeRelay uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.OutgoingPaymentFactory→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.Relay→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.SimpleOutgoingPaymentFactory→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.Stop→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedMultiPartExtraPaymentReceived→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedMultiPartPaymentFailed→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedMultiPartPaymentSucceeded→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedOnTheFlyFundingResponse→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedPaymentFailed→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedPaymentSent→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedPeerInfo→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedPeerReadyResult→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedPreimageReceived→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay.WrappedResolvedPaths→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.relay.NodeRelay uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break balance.BalanceActor.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
38→34 payment.relay.NodeRelay uses payment.send.PaymentInitiator✕
- Connections
- 1 pair of types, where a type in payment.relay.NodeRelay uses a type in payment.send.PaymentInitiator.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.SimpleOutgoingPaymentFactory→fr.acinq.eclair.payment.send.PaymentInitiator.SimplePaymentFactory
- Direction
- payment.relay.NodeRelay uses payment.send.PaymentInitiator, so a change to payment.send.PaymentInitiator can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break payment.send.PaymentInitiator.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
38→36 payment.relay.NodeRelay uses fr.acinq.eclair✕
- Connections
- 3 pairs of types, where a type in payment.relay.NodeRelay uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay.SimpleOutgoingPaymentFactory→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.relay.NodeRelay.WrappedPeerInfo→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.relay.NodeRelay.WrappedPeerInfo→fr.acinq.eclair.InitFeature
- Direction
- payment.relay.NodeRelay uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.relay.NodeRelay, while a change to payment.relay.NodeRelay can't break fr.acinq.eclair.
- Position
- Below the diagonal: payment.relay.NodeRelay uses a module listed above it, which is the healthy direction.
39→1 channel.fsm uses blockchain✕
- Connections
- 2 pairs of types, where a type in channel.fsm uses a type in blockchain.
- The types involved
fr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.blockchain.OnChainChannelFunderfr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.blockchain.CurrentBlockHeight
- Direction
- channel.fsm uses blockchain, so a change to blockchain can break channel.fsm, while a change to channel.fsm can't break blockchain.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→4 channel.fsm uses crypto.TransportHandler✕
- Connections
- 2 pairs of types, where a type in channel.fsm uses a type in crypto.TransportHandler.
- The types involved
fr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.crypto.TransportHandler.Statefr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.crypto.TransportHandler.State
- Direction
- channel.fsm uses crypto.TransportHandler, so a change to crypto.TransportHandler can break channel.fsm, while a change to channel.fsm can't break crypto.TransportHandler.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→8 channel.fsm uses crypto.keymanager✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in crypto.keymanager.
- The types involved
fr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.crypto.keymanager.ChannelKeys
- Direction
- channel.fsm uses crypto.keymanager, so a change to crypto.keymanager can break channel.fsm, while a change to channel.fsm can't break crypto.keymanager.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→13 channel.fsm uses transactions.Transactions✕
- Connections
- 2 pairs of types, where a type in channel.fsm uses a type in transactions.Transactions.
- The types involved
fr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.transactions.Transactions.ClosingTxfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.transactions.Transactions.InputInfo
- Direction
- channel.fsm uses transactions.Transactions, so a change to transactions.Transactions can break channel.fsm, while a change to channel.fsm can't break transactions.Transactions.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→25 channel.fsm uses io.Peer✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in io.Peer.
- The types involved
fr.acinq.eclair.channel.fsm.SingleFundingHandlers→fr.acinq.eclair.io.Peer.OpenChannelResponse
- Direction
- channel.fsm uses io.Peer, so a change to io.Peer can break channel.fsm, while a change to channel.fsm can't break io.Peer.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→26 channel.fsm uses wire.protocol✕
- Connections
- 6 pairs of types, where a type in channel.fsm uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.wire.protocol.AnnouncementSignaturesfr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.wire.protocol.ChannelReadyfr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.wire.protocol.LightningMessagefr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.wire.protocol.Shutdownfr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.wire.protocol.ChannelReadyfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.wire.protocol.ChannelReestablish
- Direction
- channel.fsm uses wire.protocol, so a change to wire.protocol can break channel.fsm, while a change to channel.fsm can't break wire.protocol.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→28 channel.fsm uses channel.fund.InteractiveTxSigningSession✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in channel.fund.InteractiveTxSigningSession.
- The types involved
fr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.channel.fund.InteractiveTxSigningSession.WaitingForSigs
- Direction
- channel.fsm uses channel.fund.InteractiveTxSigningSession, so a change to channel.fund.InteractiveTxSigningSession can break channel.fsm, while a change to channel.fsm can't break channel.fund.InteractiveTxSigningSession.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→29 channel.fsm uses channel.fund.InteractiveTxBuilder✕
- Connections
- 2 pairs of types, where a type in channel.fsm uses a type in channel.fund.InteractiveTxBuilder.
- The types involved
fr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SharedTransactionfr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.channel.fund.InteractiveTxBuilder.SignedSharedTransaction
- Direction
- channel.fsm uses channel.fund.InteractiveTxBuilder, so a change to channel.fund.InteractiveTxBuilder can break channel.fsm, while a change to channel.fsm can't break channel.fund.InteractiveTxBuilder.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→31 channel.fsm uses blockchain.fee✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- channel.fsm uses blockchain.fee, so a change to blockchain.fee can break channel.fsm, while a change to channel.fsm can't break blockchain.fee.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→32 channel.fsm uses channel✕
- Connections
- 23 pairs of types, where a type in channel.fsm uses a type in channel.
- The types involved
fr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.channel.SupportedChannelTypefr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.channel.ChannelDataWithCommitmentsfr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.channel.Commitmentfr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.channel.DATA_NORMALfr.acinq.eclair.channel.fsm.CommonFundingHandlers→fr.acinq.eclair.channel.ShortIdAliasesfr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.channel.ChannelDataWithCommitmentsfr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.channel.ChannelStatefr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.channel.CloseStatusfr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.channel.Commitmentsfr.acinq.eclair.channel.fsm.CommonHandlers→fr.acinq.eclair.channel.PersistentChannelDatafr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.channel.DATA_WAIT_FOR_DUAL_FUNDING_CONFIRMEDfr.acinq.eclair.channel.fsm.DualFundingHandlers→fr.acinq.eclair.channel.DualFundingStatusfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.ChannelDataWithCommitmentsfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.ChannelStatefr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.CloseCommandfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.DATA_CLOSINGfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.DATA_NEGOTIATINGfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.FullCommitmentfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.LocalCommitPublishedfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.RemoteCommitPublishedfr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.RevokedCommitPublishedfr.acinq.eclair.channel.fsm.SingleFundingHandlers→fr.acinq.eclair.channel.PersistentChannelData
- Direction
- channel.fsm uses channel, so a change to channel can break channel.fsm, while a change to channel.fsm can't break channel.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→33 channel.fsm uses balance.BalanceActor✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- channel.fsm uses balance.BalanceActor, so a change to balance.BalanceActor can break channel.fsm, while a change to channel.fsm can't break balance.BalanceActor.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→36 channel.fsm uses fr.acinq.eclair✕
- Connections
- 3 pairs of types, where a type in channel.fsm uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.CltvExpiryDeltafr.acinq.eclair.channel.fsm.Channel→fr.acinq.eclair.NodeParamsfr.acinq.eclair.channel.fsm.SingleFundingHandlers→fr.acinq.eclair.BlockHeight
- Direction
- channel.fsm uses fr.acinq.eclair, so a change to fr.acinq.eclair can break channel.fsm, while a change to channel.fsm can't break fr.acinq.eclair.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
39→37 channel.fsm uses channel.publish.TxPublisher✕
- Connections
- 1 pair of types, where a type in channel.fsm uses a type in channel.publish.TxPublisher.
- The types involved
fr.acinq.eclair.channel.fsm.ErrorHandlers→fr.acinq.eclair.channel.publish.TxPublisher.PublishTx
- Direction
- channel.fsm uses channel.publish.TxPublisher, so a change to channel.publish.TxPublisher can break channel.fsm, while a change to channel.fsm can't break channel.publish.TxPublisher.
- Position
- Below the diagonal: channel.fsm uses a module listed above it, which is the healthy direction.
40→2 payment.relay uses channel.Upstream✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in channel.Upstream.
- The types involved
fr.acinq.eclair.payment.relay.PostRestartHtlcCleaner→fr.acinq.eclair.channel.Upstream.Cold
- Direction
- payment.relay uses channel.Upstream, so a change to channel.Upstream can break payment.relay, while a change to payment.relay can't break channel.Upstream.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→6 payment.relay uses payment.relay.Relayer✕
- Connections
- 2 pairs of types, where a type in payment.relay uses a type in payment.relay.Relayer.
- The types involved
fr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.payment.relay.Relayer.OutgoingChannelfr.acinq.eclair.payment.relay.ChannelRelayer→fr.acinq.eclair.payment.relay.Relayer.OutgoingChannel
- Direction
- payment.relay uses payment.relay.Relayer, so a change to payment.relay.Relayer can break payment.relay, while a change to payment.relay can't break payment.relay.Relayer.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→14 payment.relay uses payment✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in payment.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.payment.PaymentFailure
- Direction
- payment.relay uses payment, so a change to payment can break payment.relay, while a change to payment.relay can't break payment.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→15 payment.relay uses wire.protocol.LiquidityAds✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in wire.protocol.LiquidityAds.
- The types involved
fr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.wire.protocol.LiquidityAds.RequestFunding
- Direction
- payment.relay uses wire.protocol.LiquidityAds, so a change to wire.protocol.LiquidityAds can break payment.relay, while a change to payment.relay can't break wire.protocol.LiquidityAds.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→22 payment.relay uses router.Router✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in router.Router.
- The types involved
fr.acinq.eclair.payment.relay.PostRestartHtlcCleaner→fr.acinq.eclair.router.Router.Stash
- Direction
- payment.relay uses router.Router, so a change to router.Router can break payment.relay, while a change to payment.relay can't break router.Router.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→23 payment.relay uses io.PeerConnection✕
- Connections
- 5 pairs of types, where a type in payment.relay uses a type in io.PeerConnection.
- The types involved
fr.acinq.eclair.payment.relay.AsyncPaymentTriggerer→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.relay.ChannelRelayer→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.io.PeerConnection.Behaviorfr.acinq.eclair.payment.relay.NodeRelayer→fr.acinq.eclair.io.PeerConnection.Behavior
- Direction
- payment.relay uses io.PeerConnection, so a change to io.PeerConnection can break payment.relay, while a change to payment.relay can't break io.PeerConnection.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→25 payment.relay uses io.Peer✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in io.Peer.
- The types involved
fr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.io.Peer.OpenChannel
- Direction
- payment.relay uses io.Peer, so a change to io.Peer can break payment.relay, while a change to payment.relay can't break io.Peer.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→26 payment.relay uses wire.protocol✕
- Connections
- 6 pairs of types, where a type in payment.relay uses a type in wire.protocol.
- The types involved
fr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.wire.protocol.ChannelUpdatefr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.wire.protocol.FailureMessagefr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.wire.protocol.FailureMessagefr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.wire.protocol.OpenDualFundedChannelfr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.wire.protocol.SpliceInitfr.acinq.eclair.payment.relay.PostRestartHtlcCleaner→fr.acinq.eclair.wire.protocol.UpdateAddHtlc
- Direction
- payment.relay uses wire.protocol, so a change to wire.protocol can break payment.relay, while a change to payment.relay can't break wire.protocol.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→31 payment.relay uses blockchain.fee✕
- Connections
- 1 pair of types, where a type in payment.relay uses a type in blockchain.fee.
- The types involved
fr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.blockchain.fee.FeeratePerKw
- Direction
- payment.relay uses blockchain.fee, so a change to blockchain.fee can break payment.relay, while a change to payment.relay can't break blockchain.fee.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→32 payment.relay uses channel✕
- Connections
- 3 pairs of types, where a type in payment.relay uses a type in channel.
- The types involved
fr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.channel.CMD_FAIL_HTLCfr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.channel.ChannelExceptionfr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.channel.Commitments
- Direction
- payment.relay uses channel, so a change to channel can break payment.relay, while a change to payment.relay can't break channel.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→33 payment.relay uses balance.BalanceActor✕
- Connections
- 5 pairs of types, where a type in payment.relay uses a type in balance.BalanceActor.
- The types involved
fr.acinq.eclair.payment.relay.AsyncPaymentTriggerer→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.ChannelRelayer→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.balance.BalanceActor.Commandfr.acinq.eclair.payment.relay.NodeRelayer→fr.acinq.eclair.balance.BalanceActor.Command
- Direction
- payment.relay uses balance.BalanceActor, so a change to balance.BalanceActor can break payment.relay, while a change to payment.relay can't break balance.BalanceActor.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→36 payment.relay uses fr.acinq.eclair✕
- Connections
- 11 pairs of types, where a type in payment.relay uses a type in fr.acinq.eclair.
- The types involved
fr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.relay.ChannelRelay→fr.acinq.eclair.TimestampMillifr.acinq.eclair.payment.relay.ChannelRelayer→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.relay.ChannelRelayer→fr.acinq.eclair.ShortChannelIdfr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.CltvExpiryfr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.Featuresfr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.InitFeaturefr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.MilliSatoshifr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.relay.NodeRelayer→fr.acinq.eclair.NodeParamsfr.acinq.eclair.payment.relay.OnTheFlyFunding→fr.acinq.eclair.MilliSatoshi
- Direction
- payment.relay uses fr.acinq.eclair, so a change to fr.acinq.eclair can break payment.relay, while a change to payment.relay can't break fr.acinq.eclair.
- Position
- Below the diagonal: payment.relay uses a module listed above it, which is the healthy direction.
40→38 payment.relay uses payment.relay.NodeRelay✕
- Connections
- 2 pairs of types, where a type in payment.relay uses a type in payment.relay.NodeRelay.
- The types involved
fr.acinq.eclair.payment.relay.NodeRelay→fr.acinq.eclair.payment.relay.NodeRelay.OutgoingPaymentFactoryfr.acinq.eclair.payment.relay.NodeRelayer→fr.acinq.eclair.payment.relay.NodeRelay.OutgoingPaymentFactory
- Direction
- payment.relay uses payment.relay.NodeRelay, so a change to payment.relay.NodeRelay can break payment.relay, while a change to payment.relay can't break payment.relay.NodeRelay.
- Position
- Below the diagonal: payment.relay 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 30 | High / Critical |
| A05:2025 — Injection | 24 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
First, integrate automated security scanning into the CI pipeline to prevent regressions from reaching production. Second, document recovery time and point objectives alongside a tested restore procedure to ensure true disaster readiness. Third, maintain a changelog to track release contents and create architecture decision records to capture significant design choices and their consequences.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +7.5 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.3 pts | Low | ADR Quality |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +3.8 pts | Medium | DR & Backup |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED (2). | +1.0 pts | Low | Static Analysis (SAST) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.8 pts | Medium | Architecture documentation |
| 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.8 pts | Medium | Web-Security Posture |
| 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. | +1.7 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala | 4.4 | Mixed | Change Coupling: Boundary-crossing change coupling: Eclair.scala ↔ FormParamExtractors.scala |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala | 5.5 | Mixed | Cyclomatic Complexity: InteractiveTxBuilder.validateTx (cyclomatic 43) |
| eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala | 5.5 | Mixed | Cyclomatic Complexity: Helpers.validateParamsSingleFundedFundee (cyclomatic 25) |
| eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerScorer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/io/PeerConnection.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/Features.scala | 6.6 | Mixed | Explicit Debt: TodoComment |
| eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentEvents.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
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
Watchdog 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. 66 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 66 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, 337 of 355 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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 READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`scoverage`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog 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) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — Watchdog 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. Not scored — 5 Maven/Gradle manifest(s) were read, stating a version for 30 dependency(ies) and leaving 33 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 (REDACTED), 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 — Watchdog 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 — Watchdog 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog 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) — 2 | 3 | # Let's fetch eclair dependencies, so that Docker can cache them -------------------- ERROR: failed to solve: eclipse-temurin:21-jdk-noble: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jdk-noble: failed to do request: Head "https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/21-jdk-noble": Forbidden; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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.
- C3 Audit Trail — not measured this run — Watchdog 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. 'com.zaxxer.hikari' is imported (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — Watchdog 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. 'com.zaxxer.hikari' is imported (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — Watchdog 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. 'com.zaxxer.hikari' is imported (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret 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").
- 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.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
39 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ZmqWatcher.watching at 58. A further 5 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 LogCategory.apply at 33 — 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: eclair-core/src/main/scala/fr/acinq/eclair/Logs.scala (LogCategory.apply at 33), eclair-core/src/main/scala/fr/acinq/eclair/io/PeerReadyNotifier.scala (PeerReadyNotifier.isChannelReady at 27), eclair-core/src/main/scala/fr/acinq/eclair/balance/CheckBalance.scala (OffChainBalance.addChannelBalance at 25), eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/OnTheFlyFunding.scala (OnTheFlyFunding.validate at 16), eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerStatsTracker.scala (PeerStatsTracker.listening at 16). 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 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ZmqWatcher.watching (cyclomatic 58), InteractiveTxBuilder.validateTx (cyclomatic 43), MultiPartHandler.handle (cyclomatic 39). — 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 6 together lifts Cyclomatic Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
56 method(s) exceeded the cognitive complexity threshold of 15; the worst was Setup.bootstrap at 158.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with Setup.bootstrap (cognitive 158), Validation.handleChannelUpdate (cognitive 62). — 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 2 together lifts Cognitive Complexity from 5.5 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
18 god class(es) detected.
What to do
- Resolve the 16 FileTooLong finding(s) in God Classes — start with Channel.scala, Transactions.scala, Helpers.scala. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with BitcoinCoreClient.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with Eclair.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
80 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 15 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Commitments.scala (2), ErrorHandlers.scala (2), PgAuditDb.scala (2). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 13 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with PgAuditDb.scala (4), Transactions.scala (3), PgPaymentsDb.scala. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with PgAuditDb.scala (5), ReplaceableTxPrePublisher.scala, LocalOnChainKeyManager.scala. — One of this dimension's main actionable groups (12 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
4 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (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).
D6 · Cohesion (LCOM4)
3 of 49 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with Channel.scala, Peer.scala, TorProtocolHandler.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
2482 test methods: 2351 unit, 131 integration, 0 BDD, 0 e2e. The Scala suite contributes 2482 test case(s) across 163 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala (11×27=297); eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala (6×43=258); eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala (4×34=136)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with NodeParams.scala, InteractiveTxBuilder.scala, PaymentLifecycle.scala. — One of this dimension's main actionable groups (7 warning-level).
D16 · Bus Factor
21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala. Counted over 195 of the 258 production source files in this repository: 62 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
25 deducted task-comment markers across 57964 LoC (0.0/KLoC) → score 9.9. 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 25 TodoComment finding(s) in Explicit Debt — start with Channel.scala (5), Features.scala (4), PeerConnection.scala (2). — One of this dimension's main actionable groups (25 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 19 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Maven) 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 21 high, 3 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `eclair-front/src/main/resources/eclair-front.sh` (line 126), `eclair-node/src/main/resources/eclair-node.sh` (line 126), `mvnw` (lines 222–226, lines 278–282) — 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.
What to do
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
23 finding(s): 1 critical, 14 high, 7 medium, 1 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
21 of 196 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is eclair-core/src/main/scala/fr/acinq/eclair/crypto/Noise.scala. Counted over 196 of the 258 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 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Noise.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 20 Orphaned file finding(s) in Knowledge Freshness — start with BalanceEstimate.scala, BlindedPathsResolver.scala, PendingChannelsRateLimiter.scala. — One of this dimension's main actionable groups (20 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: Eclair.scala↔FormParamExtractors.scala 71%; OnChainFeeConf.scala↔Channel.scala 65%; Eclair.scala↔Channel.scala 64%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with Eclair.scala (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 7 Change coupling finding(s) in Change Coupling — start with OnChainFeeConf.scala, REDACTED, Channel.scala. — One of this dimension's main actionable groups (7 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 34 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
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Eclair` declares 64 abstract members: `connect`, `disconnect`, `open`, `rbfOpen`, `spliceIn`, `spliceOut`, `rbfSplice`, `close`, `forceClose`, `forceCloseResetFundingIndex`, `bumpForceCloseFee`, `updateRelayFee`, `channelsInfo`, `channelInfo`, `closedChannels`, `peers`, `node`, `nodes`, `receive`, `createOffer`, `disableOffer`, `listOffers`, `newAddress`, `receivedInfo`, `receivedPayments`, `send`, `sendBlocking`, `sendWithPreimage`, `sentInfo`, `sendOnChain`, `cpfpBumpFees`, `findRoute`, `findRouteBetween`, `sendToRoute`, `audit`, `relayStats`, `relayStats`, `getInvoice`, `pendingInvoices`, `allInvoices`, and 24 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. Those 64 declarations carry 63 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 63 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:91
- `AuditDb` declares 18 abstract members under just 9 distinct name(s): `add`, `add`, `add`, `add`, `add`, `add`, `addChannelUpdate`, `addPathFindingExperimentMetrics`, `listPublished`, `listPublished`, `listConfirmed`, `listConfirmed`, `listConfirmed`, `listChannelEvents`, `listChannelEvents`, `listSent`, `listReceived`, `listRelayed`. 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. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 9 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — eclair-core/src/main/scala/fr/acinq/eclair/db/AuditDb.scala:29
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
- Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — eclair-core/src/test/scala/fr/acinq/eclair/balance/CheckBalanceSpec.scala:289, eclair-core/src/test/scala/fr/acinq/eclair/integration/PerformanceIntegrationSpec.scala:42, eclair-core/src/test/scala/fr/acinq/eclair/router/AnnouncementsBatchValidationSpec.scala:46, …
What to do
- 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)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 4 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
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 3248 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.
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
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.
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: eclair-node/src/main/scala/fr/acinq/eclair/Boot.scala:86 — `newServerAt`.
- 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: eclair-node/src/main/scala/fr/acinq/eclair/Boot.scala:86 — `newServerAt`.
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
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 197 is called with an argument built by `d.graphWithBalances.graph.getEdgesBetween(r.source, targetNodeId).map(e => "…" e.desc.shortChannelId e.balance_opt e....` (line 197), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/router/RouteCalculation.scala:197
- `debug` at line 91 is called with an argument built by `d.ignore.channels.map(_.shortChannelId).mkString("…")` (line 91), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:91
- `debug` at line 86 is called with an argument built by `nextChannels.keys.mkString("…")` (line 86), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/ChannelRelayer.scala:86
- `debug` at line 105 is called with an argument built by `mappings.keys.mkString("…")` (line 105), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/ChannelRelayer.scala:105
- `debug` at line 191 is called with an argument built by `(intermediateNodes : + targetNodeId).mkString("…")` (line 191), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/message/Postman.scala:191
- `debug` at line 114 is called with an argument built by `localChanges.proposed.map(msg2String(_)).mkString("…")` (line 114), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:114
- `debug` at line 115 is called with an argument built by `remoteChanges.proposed.map(msg2String(_)).mkString("…")` (line 115), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:115
- `debug` at line 333 is called with an argument built by `toUnlock.mkString("…")` (line 333), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxFunder.scala:333
- `debug` at line 402 is called with an argument built by `toUnlock.mkString("…")` (line 402), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:402
- `debug` at line 446 is called with an argument built by `toUnlock.mkString("…")` (line 446), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:446
- `debug` at line 127 is called with an argument built by `remainingParentTxs.keySet.mkString("…")` (line 127), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxTimeLocksMonitor.scala:127
- `debug` at line 1139 is called with an argument built by `toUnlock.map(o => "…" o.txid o.index).mkString("…")` (line 1139), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:1139
- `debug` at line 396 is called with an argument built by `toUnlock1.map(o => "…" o.txid o.index).mkString("…")` (line 396), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala:396
- `debug` at line 68 is called with an argument built by `batch.groupBy(_.request.method)` (line 68), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BatchingClient.scala:68
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn` at line 90 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. — eclair-core/src/main/scala/fr/acinq/eclair/blockchain/watchdogs/HeadersOverDns.scala:90
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 258 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.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Adequate — gated by D29, D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.zaxxer.hikari' (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'com.zaxxer.hikari' (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.zaxxer.hikari' (eclair-core/src/main/scala/fr/acinq/eclair/db/Databases.scala:22) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 48 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to 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
- AX8 Test isolation — no test/production split to check
- 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) — 2 | 3 | # Let's fetch eclair dependencies, so that Docker can cache them -------------------- ERROR: failed to solve: eclipse-temurin:21-jdk-noble: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jdk-noble: failed to do request: Head "https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/21-jdk-noble": Forbidden; 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.
- D10 Test Quality — ~72492 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 — no .scala test runner
- D12 Dependency Hygiene — Not scored — 5 Maven/Gradle manifest(s) were read, stating a version for 30 dependency(ies) and leaving 33 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 30 declared JVM dependency coordinate(s) were read from its 5 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 9 of them (HTTP 403 Forbidden from https://repo1.maven.org/maven2/org/scalatest/scalatest_${scala.version.short}/3.2.16/scalatest_${scala.version.short}-3.2.16.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Scala not measured.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic 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) — 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1544 value object(s); 49 domain event(s); its domain events are published by services or handlers — no domain entity raises 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
- 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Scala code has 65,178 production line(s), 6 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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
- 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.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 41 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: Eclair.scala ↔ FormParamExtractors.scala eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:1
- Boundary-crossing change coupling: Eclair.scala ↔ Channel.scala eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:1
- REDACTED
- REDACTED
- Orphaned knowledge eclair-core/src/main/scala/fr/acinq/eclair/crypto/Noise.scala:1
Serious — 255 finding(s)
- TodoComment eclair-core/src/test/scala/fr/acinq/eclair/wire/protocol/LightningMessageCodecsSpec.scala:163
- TodoComment eclair-core/src/test/scala/fr/acinq/eclair/router/ChannelRouterIntegrationSpec.scala:203
- TodoComment eclair-core/src/test/scala/fr/acinq/eclair/integration/basic/zeroconf/ZeroConfAliasIntegrationSpec.scala:213
- TodoComment eclair-core/src/test/scala/fr/acinq/eclair/channel/states/e/NormalSplicesStateSpec.scala:2214
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/Features.scala:428
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/Features.scala:439
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/Features.scala:445
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/Features.scala:465
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/wire/protocol/ChannelTlv.scala:351
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/wire/protocol/FailureMessage.scala:164
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerScorer.scala:657
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/payment/Bolt11Invoice.scala:515
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentEvents.scala:270
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/io/PeerConnection.scala:516
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/io/PeerConnection.scala:523
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgUtils.scala:250
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:38
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:266
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:432
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:466
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:2364
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala:398
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:2618
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala:321
- TodoComment eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:373
- FileTooLong: fsm/Channel.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala
- FileTooLong: transactions/Transactions.scala eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala
- FileTooLong: channel/Helpers.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala
- FileTooLong: fund/InteractiveTxBuilder.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala
- FileTooLong: io/Peer.scala eclair-core/src/main/scala/fr/acinq/eclair/io/Peer.scala
- FileTooLong: channel/Commitments.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala
- FileTooLong: fsm/ChannelOpenDualFunded.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ChannelOpenDualFunded.scala
- FileTooLong: protocol/LightningMessageTypes.scala eclair-core/src/main/scala/fr/acinq/eclair/wire/protocol/LightningMessageTypes.scala
- FileTooLong: json/JsonSerializers.scala eclair-core/src/main/scala/fr/acinq/eclair/json/JsonSerializers.scala
- FileTooLong: router/Router.scala eclair-core/src/main/scala/fr/acinq/eclair/router/Router.scala
- FileTooLong: io/PeerConnection.scala eclair-core/src/main/scala/fr/acinq/eclair/io/PeerConnection.scala
- FileTooLong: eclair/Eclair.scala eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala
- FileTooLong: eclair/NodeParams.scala eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala
- FileTooLong: channel/ChannelData.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/ChannelData.scala
- FileTooLong: rpc/BitcoinCoreClient.scala eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala
- FileTooLong: pg/PgAuditDb.scala eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:613
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:1068
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala:296
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:292
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:347
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPeersDb.scala:163
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPeersDb.scala:177
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqlitePaymentsDb.scala:272
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqlitePeersDb.scala:90
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/router/BalanceEstimate.scala:285
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:419
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:749
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala:91
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteLiquidityDb.scala:217
- Duplicated block (5 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentPacket.scala:134
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:321
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:331
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:343
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:639
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:147
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteAuditDb.scala:427
- Duplicated block (6 lines × 2) REDACTED:74
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqlitePaymentsDb.scala:380
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala:673
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala:754
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala:1176
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:405
- Duplicated block (6 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/wire/protocol/OfferTypes.scala:286
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala:105
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/crypto/keymanager/LocalOnChainKeyManager.scala:157
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:443
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:574
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:608
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:616
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqlitePaymentsDb.scala:362
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala:960
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:318
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:517
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:382
- Duplicated block (7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgNetworkDb.scala:216
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala:296
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:820
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:191
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:102
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:112
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala:214
- Hotspot: eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala:263
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: OnChainFeeConf.scala ↔ Channel.scala eclair-core/src/main/scala/fr/acinq/eclair/blockchain/fee/OnChainFeeConf.scala:1
- Change coupling: REDACTED ↔ REDACTED REDACTED:1
- Change coupling: Channel.scala ↔ Scripts.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:1
- Change coupling: ChannelOpenDualFunded.scala ↔ ChannelOpenSingleFunded.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ChannelOpenDualFunded.scala:1
- Change coupling: Helpers.scala ↔ ChannelKeyManager.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:1
- Change coupling: Commitments.scala ↔ ChannelKeyManager.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:1
- Change coupling: InteractiveTxBuilder.scala ↔ ChannelTlv.scala eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:1
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:399
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/crypto/ChaCha20Poly1305.scala:56
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:252
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:269
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:630
- Duplicated block (8 lines × 2) REDACTED:156
- Duplicated block (8 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/payment/Bolt12Invoice.scala:141
- Duplicated block (10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgLiquidityDb.scala:165
- Duplicated block (10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:377
- Duplicated block (10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteAuditDb.scala:416
- Duplicated block (10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteAuditDb.scala:507
- Duplicated block (10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteLiquidityDb.scala:149
- Duplicated block (9 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:414
- Duplicated block (9 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:527
- Duplicated block (9 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:550
- Duplicated block (9 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:357
- Duplicated block (9 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:285
- Duplicated block (11 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:431
- Duplicated block (11 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:532
- Duplicated block (11 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgLiquidityDb.scala:117
- Duplicated block (11 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Scripts.scala:198
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:587
- Duplicated block (14 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgLiquidityDb.scala:192
- Duplicated block (14 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteAuditDb.scala:465
- Low cohesion: Channel (LCOM4 8) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:228
- Low cohesion: Peer (LCOM4 4) eclair-core/src/main/scala/fr/acinq/eclair/io/Peer.scala:62
- Low cohesion: TorProtocolHandler (LCOM4 4) eclair-core/src/main/scala/fr/acinq/eclair/tor/TorProtocolHandler.scala:49
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) REDACTED:183
- Duplicated block (17 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:191
- Duplicated block (15 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:486
- Duplicated block (15 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:231
- Duplicated block (12 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:646
- Duplicated block (12 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgLiquidityDb.scala:77
- ZmqWatcher.watching (cyclomatic 58) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala:222
- InteractiveTxBuilder.validateTx (cyclomatic 43) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:820
- MultiPartHandler.handle (cyclomatic 39) eclair-core/src/main/scala/fr/acinq/eclair/payment/receive/MultiPartHandler.scala:76
- PaymentLifecycle.handleRemoteFail (cyclomatic 34) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:191
- Validation.handleChannelUpdate (cyclomatic 33) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:375
- Setup.bootstrap (cyclomatic 31) eclair-core/src/main/scala/fr/acinq/eclair/Setup.scala:228
- IncomingPaymentPacket.decrypt (cyclomatic 29) eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentPacket.scala:125
- NodeParams.makeNodeParams (cyclomatic 27) eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala:296
- PaymentInitiator.main (cyclomatic 26) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentInitiator.scala:45
- PaymentLifecycle.myStop (cyclomatic 26) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:386
- Helpers.validateParamsSingleFundedFundee (cyclomatic 25) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:102
- Register.main (cyclomatic 25) eclair-core/src/main/scala/fr/acinq/eclair/channel/Register.scala:42
- TxPublisher.run (cyclomatic 25) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala:214
- DbEventHandler.receive (cyclomatic 25) eclair-core/src/main/scala/fr/acinq/eclair/db/DbEventHandler.scala:60
- RouteCalculation.finalizeRoute (cyclomatic 24) eclair-core/src/main/scala/fr/acinq/eclair/router/RouteCalculation.scala:51
- PeerScorer.fundChannelsIfNeeded (cyclomatic 23) eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerScorer.scala:573
- MutualClose.signSimpleClosingTx (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:865
- InteractiveTxFunder.filterInputs (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala:263
- ReplaceableTxPrePublisher.checkLocalCommitAnchorPreconditions (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala:99
- ReplaceableTxPublisher.wait (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:244
- Switchboard.normal (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/io/Switchboard.scala:87
- PostRestartHtlcCleaner.getHtlcsRelayedOut (cyclomatic 22) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:417
- PaymentLifecycle.handleUpdate (cyclomatic 20) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:326
- Syncing.checkSync (cyclomatic 19) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:499
- InteractiveTxBuilder.receive (cyclomatic 19) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:661
- InteractiveTxSigningSession.addRemoteSigs (cyclomatic 19) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:1195
- DustExposure.reduceForDustExposure (cyclomatic 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/DustExposure.scala:96
- Helpers.validateParamsDualFundedNonInitiator (cyclomatic 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:166
- MempoolTxMonitor.waitForConfirmation (cyclomatic 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/MempoolTxMonitor.scala:137
- Graph.dijkstraShortestPath (cyclomatic 18) eclair-core/src/main/scala/fr/acinq/eclair/router/Graph.scala:299
- ErrorHandlers.handleLocalError (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala:70
- InteractiveTxBuilder.receiveInput (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:602
- ReplaceableTxPrePublisher.check2ndStageTxPreconditions (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala:236
- PostRestartHtlcCleaner.main (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:112
- Sync.handleReplyChannelRange (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/router/Sync.scala:100
- Validation.handleChannelValidationResponse (cyclomatic 17) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:82
- ReplaceableTxFunder.signWalletInputs (cyclomatic 16) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxFunder.scala:266
- Relayer.receive (cyclomatic 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/Relayer.scala:65
- MultiPartPaymentLifecycle.myStop (cyclomatic 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:225
- Setup.bootstrap (cognitive 158) eclair-core/src/main/scala/fr/acinq/eclair/Setup.scala:228
- Validation.handleChannelUpdate (cognitive 62) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:375
- MultiPartHandler.handle (cognitive 52) eclair-core/src/main/scala/fr/acinq/eclair/payment/receive/MultiPartHandler.scala:76
- BitcoinCoreFeeProvider.getFeerates (cognitive 50) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/fee/BitcoinCoreFeeProvider.scala:49
- ZmqWatcher.watching (cognitive 47) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala:222
- InteractiveTxBuilder.validateTx (cognitive 46) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:820
- PaymentLifecycle.handleRemoteFail (cognitive 46) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:191
- IncomingPaymentPacket.decrypt (cognitive 43) eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentPacket.scala:125
- PaymentLifecycle.myStop (cognitive 39) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:386
- PeerScorer.fundChannelsIfNeeded (cognitive 38) eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerScorer.scala:573
- FrontSetup.bootstrap (cognitive 36) eclair-front/src/main/scala/fr/acinq/eclair/FrontSetup.scala:90
- MutualClose.signSimpleClosingTx (cognitive 35) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:865
- InteractiveTxFunder.filterInputs (cognitive 35) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala:263
- Sync.handleReplyChannelRange (cognitive 35) eclair-core/src/main/scala/fr/acinq/eclair/router/Sync.scala:100
- ReplaceableTxPublisher.wait (cognitive 34) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:244
- PaymentInitiator.main (cognitive 33) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentInitiator.scala:45
- Graph.dijkstraShortestPath (cognitive 33) eclair-core/src/main/scala/fr/acinq/eclair/router/Graph.scala:299
- RouteCalculation.finalizeRoute (cognitive 33) eclair-core/src/main/scala/fr/acinq/eclair/router/RouteCalculation.scala:51
- TxPublisher.run (cognitive 30) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxPublisher.scala:214
- PostRestartHtlcCleaner.handleDownstreamFulfill (cognitive 29) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:181
- PostRestartHtlcCleaner.handleDownstreamFailure (cognitive 29) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:250
- Channel.resumeSpliceSigningSessionIfNeeded (cognitive 28) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:3683
- PostRestartHtlcCleaner.main (cognitive 27) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/PostRestartHtlcCleaner.scala:112
- ReplaceableTxFunder.bump (cognitive 26) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxFunder.scala:167
- NodeParams.makeNodeParams (cognitive 25) eclair-core/src/main/scala/fr/acinq/eclair/NodeParams.scala:296
- MultiPartPaymentLifecycle.myStop (cognitive 25) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:225
- PaymentLifecycle.handleUpdate (cognitive 25) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/PaymentLifecycle.scala:326
- InteractiveTxBuilder.receive (cognitive 24) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:661
- PeerScorer.updateRelayFeesIfNeeded (cognitive 24) eclair-core/src/main/scala/fr/acinq/eclair/profit/PeerScorer.scala:427
- Graph.yenKshortestPaths (cognitive 24) eclair-core/src/main/scala/fr/acinq/eclair/router/Graph.scala:204
- BitcoinCoreClient.cpfp (cognitive 23) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:402
- Helpers.validateParamsSingleFundedFundee (cognitive 23) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:102
- BitcoinCoreClient.validate (cognitive 22) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:778
- Channel.handleNewBlock (cognitive 22) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/Channel.scala:3614
- Register.main (cognitive 21) eclair-core/src/main/scala/fr/acinq/eclair/channel/Register.scala:42
- ZmqWatcher.checkSpent (cognitive 20) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/ZmqWatcher.scala:430
- ReplaceableTxFunder.signWalletInputs (cognitive 20) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxFunder.scala:266
- Validation.handleChannelValidationResponse (cognitive 20) eclair-core/src/main/scala/fr/acinq/eclair/router/Validation.scala:82
- BitcoinCoreClient.signPsbt (cognitive 19) eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:486
- InteractiveTxSigningSession.addRemoteSigs (cognitive 19) eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:1195
- Sync.split (cognitive 19) eclair-core/src/main/scala/fr/acinq/eclair/router/Sync.scala:477
- BalanceActor.apply (cognitive 18) eclair-core/src/main/scala/fr/acinq/eclair/balance/BalanceActor.scala:70
- Commitment.canSendAdd (cognitive 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:487
- ReplaceableTxPrePublisher.checkLocalCommitAnchorPreconditions (cognitive 18) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala:99
- Helpers.validateParamsDualFundedNonInitiator (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:166
- MutualClose.receiveSimpleClosingSig (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala:941
- ErrorHandlers.handleLocalError (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ErrorHandlers.scala:70
- DbEventHandler.receive (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/db/DbEventHandler.scala:60
- Switchboard.normal (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/io/Switchboard.scala:87
- PaymentFailure.updateIgnored (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/payment/PaymentEvents.scala:244
- Transactions.isWitnessStandard (cognitive 17) eclair-core/src/main/scala/fr/acinq/eclair/transactions/Transactions.scala:59
- MainAndHtlcBalance.addRevokedClose (cognitive 16) eclair-core/src/main/scala/fr/acinq/eclair/balance/CheckBalance.scala:115
- Relayer.receive (cognitive 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/Relayer.scala:65
- BlindedPathsResolver.resolveBlindedPaths (cognitive 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/BlindedPathsResolver.scala:79
- PartHandler.waitForSettlement (cognitive 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/TrampolinePaymentLifecycle.scala:121
- TrampolinePaymentLifecycle.waitForSettlement (cognitive 16) eclair-core/src/main/scala/fr/acinq/eclair/payment/send/TrampolinePaymentLifecycle.scala:225
- TooManyMethods: BitcoinCoreClient eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BitcoinCoreClient.scala:54
- ClassTooLong: EclairImpl eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:223
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (26 shared lines) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:626
- Edited copy of a member (15 corresponding lines) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:343
- Edited copy of a member (16 corresponding lines) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/MempoolTxMonitor.scala:97
- Members sharing a duplicated core (6 members, 50+ identical tokens) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:464
- Duplicated block (27 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPrePublisher.scala:132
- Duplicated block (23 lines × 2) REDACTED:270
- Duplicated block (15–17 lines × 2) REDACTED:92
- Duplicated block (16 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/MempoolTxMonitor.scala:120
- Duplicated block (12–14 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgNetworkDb.scala:251
- Duplicated block (9–10 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:348
- Duplicated block (7–8 lines × 6) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:468
- Duplicated block (8 lines × 4) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:428
- Duplicated block (6–7 lines × 2) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgPaymentsDb.scala:260
- Duplicated block (6 lines × 4) eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgAuditDb.scala:531
- Coverage collected but not gated
Minor — 59 finding(s)
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/router/BalanceEstimate.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/send/BlindedPathsResolver.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/io/PendingChannelsRateLimiter.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/wire/protocol/OfferCodecs.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/Bolt12Invoice.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/send/OfferPayment.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/reputation/Reputation.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/router/BlindedRouteCreation.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/AsyncPaymentTriggerer.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/offer/OfferCreator.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/offer/OfferPaymentMetadata.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/reputation/ReputationRecorder.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgOffersDb.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/db/sqlite/SqliteOffersDb.scala:1
- Orphaned file eclair-node/src/main/scala/fr/acinq/eclair/api/handlers/WebSocket.scala:1
- Orphaned file eclair-node/src/main/scala/fr/acinq/eclair/api/handlers/Invoice.scala:1
- Orphaned file eclair-node/src/main/scala/fr/acinq/eclair/api/handlers/Message.scala:1
- Orphaned file eclair-node/src/main/scala/fr/acinq/eclair/api/handlers/Node.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/payment/receive/InvoicePurger.scala:1
- Orphaned file eclair-core/src/main/scala/fr/acinq/eclair/crypto/keymanager/LocalNodeKeyManager.scala:1
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/router/RouteCalculation.scala:197
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/payment/send/MultiPartPaymentLifecycle.scala:91
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/ChannelRelayer.scala:86
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/payment/relay/ChannelRelayer.scala:105
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/message/Postman.scala:191
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:114
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/Commitments.scala:115
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxFunder.scala:333
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:402
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/ReplaceableTxPublisher.scala:446
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/publish/TxTimeLocksMonitor.scala:127
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxBuilder.scala:1139
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/channel/fund/InteractiveTxFunder.scala:396
- Diagnostic log message is built whether or not it is wanted eclair-core/src/main/scala/fr/acinq/eclair/blockchain/bitcoind/rpc/BatchingClient.scala:68
- Disabled test eclair-core/src/test/scala/fr/acinq/eclair/balance/CheckBalanceSpec.scala:289
- Disabled test eclair-core/src/test/scala/fr/acinq/eclair/integration/PerformanceIntegrationSpec.scala:42
- Disabled test eclair-core/src/test/scala/fr/acinq/eclair/router/AnnouncementsBatchValidationSpec.scala:46
- Disabled test eclair-core/src/test/scala/fr/acinq/eclair/tor/TorProtocolHandlerSpec.scala:53
- Fat interface: Eclair (64 abstract members) eclair-core/src/main/scala/fr/acinq/eclair/Eclair.scala:91
- Fat interface: AuditDb (18 abstract members) eclair-core/src/main/scala/fr/acinq/eclair/db/AuditDb.scala:29
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST
- No release approval gate
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Duplicated predicate eclair-core/src/main/scala/fr/acinq/eclair/db/pg/PgNetworkDb.scala:88
- Interpolated log message defeats structured logging eclair-core/src/main/scala/fr/acinq/eclair/blockchain/watchdogs/HeadersOverDns.scala:90
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-004ec6e9bc4641fcb794ae9b8a968a5a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-004ec6e9bc4641fcb794ae9b8a968a5a/tree.json --exit-code 0 --source . | 0 | 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/watchdog-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 . | 24 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 23 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |