Skip to content

Conversation

@samricotta
Copy link

No description provided.

@samricotta samricotta changed the base branch from main to adding-remote July 9, 2025 10:18
pos := 1

err := rpcClient.WalletPassphrase("pass", 60)
//Add password in here for remote/dynamically
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you don't plan to fix in this PR, add a TODO

@samricotta samricotta marked this pull request as ready for review July 24, 2025 10:19
@samricotta samricotta requested a review from filippos47 August 15, 2025 11:54
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment @cursor review or bugbot run to trigger another review on this PR

harness/app.go Outdated
go printStatsForever(ctx, tm, stopChan, cfg)

covenantSender, err := NewSenderWithBabylonClient(ctx, "covenant", tm.Config.Babylon0.RPCAddr, tm.Config.Babylon0.GRPCAddr)
covenantSender, err := NewSenderWithBabylonClient(ctx, "covenant", tm.Config.Babylon0.RPCAddr, tm.Config.Babylon0.GRPCAddr, tm.Config.Babylon0.ChainID, "test")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Incorrect Parameter Order in Client Configuration

It looks like the NewSenderWithBabylonClient calls are passing chainId and grpcaddr in the wrong order. This swap means clients are getting configured with incorrect network details, which could lead to connection issues across the harness.

Additional Locations (4)
Fix in Cursor Fix in Web


if err != nil {
return err
log.Fatalf("send error: %v", err)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: FundSenders Errors Cause Program Termination

The FundSenders function now uses log.Fatalf for transaction send errors, which terminates the program instead of returning the error. This breaks the function's error handling contract, preventing callers from gracefully recovering from transaction failures.

Fix in Cursor Fix in Web

install-dependencies-command: |
sudo apt-get update
sudo apt-get install -y libzmq3-dev
go-version: '1.23'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the space add?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah think this is my auto linting working its magic

stakerPk,
unbondingTime,
params.UnbondingFeeSat,
100_010,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we want to use this magic number and not from params?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This I actually calculated a month or so ago but when building the slashing tx from staking tx, the program would complain that the params.UnbondingFeeSat was too high. This was the exact number needed for it to succeed

babylonTag = []byte{1, 2, 3, 4} //nolint:unused
eventuallyWaitTimeOut = 40 * time.Second
eventuallyPollTime = 1 * time.Second
eventuallyWaitTimeOut = 1800 * time.Second // 30 minutes for CI
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we suddenly need increase from 40s to 30min? We didn't change the logic for sandbox e2e

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree needs to be removed

Makefile Outdated

test-e2e:
go test -mod=readonly -failfast -timeout=15m -v $(PACKAGES_E2E) -count=1
go test -mod=readonly -failfast -timeout=35m -v $(PACKAGES_E2E) -count=1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there must be something wrong if out e2e needs 35min to finish

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree needs to be removed

Copy link
Member

@Lazar955 Lazar955 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are ready to open PR from adding-remote to main?

"sed -i -e 's/iavl-disable-fastnode = true/iavl-disable-fastnode = %s/' /home/node1/babylond/config/app.toml && "+
`sed -i -e 's/timeout_commit = "5s"/timeout_commit = "2s"/' /home/node1/babylond/config/config.toml &&`+
"babylond start --home=/home/node1/babylond --rpc.pprof_laddr=0.0.0.0:6060",
"export BABYLON_BLS_PASSWORD=password && babylond start --home=/home/node1/babylond --rpc.pprof_laddr=0.0.0.0:6060",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we set BABYLON_BLS_PASSWORD twice?

var stakers []*BTCStaker
for i := 0; i < numStakers; i++ {
stakerSender, err := NewSenderWithBabylonClient(ctx, fmt.Sprintf("staker-%d", i), tm.Config.Babylon1.RPCAddr, tm.Config.Babylon1.GRPCAddr)
stakerSender, err := NewSenderWithBabylonClient(ctx, fmt.Sprintf("staker-%d", i), tm.Config.Babylon1.RPCAddr, tm.Config.Babylon0.ChainID, tm.Config.Babylon1.GRPCAddr, "test")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's have a const for "test" backend keyring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants