Skip to content

Commit b77145d

Browse files
authored
docs: Fix redundant keyring note (ethereum-optimism#242)
1 parent 14514b6 commit b77145d

File tree

2 files changed

+1
-6
lines changed

2 files changed

+1
-6
lines changed

README.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -91,11 +91,6 @@ trusting third parties. Instructions on how to set up a full Babylon node
9191
can be found in
9292
[the Babylon documentation](https://docs.babylonchain.io/docs/user-guides/btc-staking-testnet/setup-node).
9393

94-
The finality provider requires a Babylon keyring with loaded funds to be attached to it
95-
in order to be able to send transactions to Babylon.
96-
To setup such a keyring, follow the instructions in
97-
[the Babylon documentation](https://docs.babylonchain.io/docs/user-guides/btc-staking-testnet/getting-funds).
98-
9994
### 3.2. Setting up the EOTS Manager
10095

10196
After a node and a keyring have been set up,

finality-provider/service/fp_instance.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ func (fp *FinalityProviderInstance) Start() error {
104104
return fmt.Errorf("failed to bootstrap the finality-provider %s: %w", fp.GetBtcPkHex(), err)
105105
}
106106

107-
fp.logger.Info("the finality-provider %s has been bootstrapped",
107+
fp.logger.Info("the finality-provider has been bootstrapped",
108108
zap.String("pk", fp.GetBtcPkHex()), zap.Uint64("height", startHeight))
109109

110110
poller := NewChainPoller(fp.logger, fp.cfg.PollerConfig, fp.cc)

0 commit comments

Comments
 (0)