Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

MWEB Light Client #8

Open
wants to merge 38 commits into
base: master
Choose a base branch
from
Open

MWEB Light Client #8

wants to merge 38 commits into from

Conversation

hectorchu
Copy link

Change Description

Description of change / link to associated issue.

Steps to Test

Steps for reviewers to follow to test the change.

Pull Request Checklist

Testing

  • Your PR passes all CI checks.
  • Tests covering the positive and negative (error paths) are included.
  • Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

馃摑 Please see our Contribution Guidelines for further guidance.

@@ -6371,21 +6371,6 @@ func (r *rpcServer) GetNetworkInfo(ctx context.Context,
func (r *rpcServer) StopDaemon(_ context.Context,
_ *lnrpc.StopRequest) (*lnrpc.StopResponse, error) {

// Before we even consider a shutdown, are we currently in recovery
Copy link
Member

@losh11 losh11 Mar 16, 2024

Choose a reason for hiding this comment

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

@hectorchu Is it a good idea to disable this check? The comment mentions that without this, the rescan wouldn't continue unless explictly started that way. Differing behaviour needs to be documented (@losh11).

Copy link
Author

Choose a reason for hiding this comment

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

It says you just need to remember to unlock the wallet next time with the recovery window option, which we do do. So its not an issue to allow a shutdown.

losh11

This comment was marked as resolved.

@@ -1359,6 +1359,10 @@ func minedTransactionsToDetails(
}
txDetail.Value = balanceDelta

if tx.Broadcast != nil {
Copy link
Member

Choose a reason for hiding this comment

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

@hectorchu in which case is the incorrect rawtx given?

Copy link
Author

Choose a reason for hiding this comment

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

For MWEB txns. Because after we've broadcast it we modify the MsgTx to add 'in the clear' MWEB inputs and outputs to the MsgTx, from the MsgTx.Mweb data. So the serialized tx changes. We save the original broadcast serialization in a separate field.

losh11

This comment was marked as resolved.

losh11

This comment was marked as resolved.

losh11

This comment was marked as resolved.

losh11

This comment was marked as resolved.

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.

None yet

2 participants