-
Notifications
You must be signed in to change notification settings - Fork 37
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backend/Utxo: support native segwit #211
Conversation
8e19812
to
fd88ef4
Compare
One last thing, can we do this in a soft-launch fashion? put a setting in Config.fs that is for now as =false, so geewallet behaves in same way as before. Then whenever we set it to =true, this new behaviour starts happening (so maybe we set it as true in lightning branch). |
Done |
1a3be72
to
265b103
Compare
Title's scope should be Backend/Utxo:, not just Backend. |
e93a7d2
to
7754684
Compare
|
@aarani after you finish with the
|
Just to make sure you understand the above, take in account that I want the build to publish 2 snaps: one for the stable channel and one for the beta one. |
d17f7b6
to
02b80aa
Compare
.github/workflows/CI.yml
Outdated
@@ -576,6 +576,7 @@ jobs: | |||
- name: Upload snap package to Snap Store | |||
env: | |||
SNAPCRAFT_LOGIN: ${{ secrets.SNAPCRAFT_LOGIN }} | |||
OVERRIDE_SNAP_VERSION: 0.7.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aarani harcoding a version number? are you serious????
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Mersho ^
7c9b030
to
f344e9e
Compare
@Mersho what value is the 2nd commit adding in this PR? Why is it separated from the 3rd commit? |
And why the scope of the last commit is completely wrong?????? |
1eca859
to
3995f62
Compare
Previously, native segwit was not widly supported so it was necessary to do segwit over P2SH, these days native segwit is supported by most wallets and with it's lower fee is the recommended choice. Lightning protocol is even dropping support for using P2SH shutdown scripts [1]. This commit adds support for native segwit (P2WPKH) while keeping the support for spending funds in users's old P2SH wallets. [1] lightning/bolts@8f2104e
This commit aims to create beta snap packages to allow testing experimental features like native segwit. This commit also updates Fsdk inside our scripts because the `GatherOrGetDefaultPrefix` function in the previous version did not allow additional arguments beside --prefix. A flag called --auto was also added for bypassing the "press any key" in bump.fsx. Co-authored-by: Mehrshad <[email protected]>
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This fixes the following crash when trying to broadcast a signed transaction from your cold-storage device: ``` unknown origin account at GWallet.Backend.UtxoCoin.Account.GetSignedTransactionDetails[T](String rawTransaction, Currency currency) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs:line 728 at GWallet.Backend.Account.GetSignedTransactionDetails[T](SignedTransaction`1 signedTransaction) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Backend/Account.fs:line 793 at Program.BroadcastPayment() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 82 at Program.PerformOperation(UInt32 numActiveAccounts, UInt32 numHotAccounts) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 398 at Program.ProgramMainLoop[a]() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 481 at Program.NormalStartWithNoParameters() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 493 ``` This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
This fixes the following crash when trying to broadcast a signed transaction from your cold-storage device: ``` unknown origin account at GWallet.Backend.UtxoCoin.Account.GetSignedTransactionDetails[T](String rawTransaction, Currency currency) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs:line 728 at GWallet.Backend.Account.GetSignedTransactionDetails[T](SignedTransaction`1 signedTransaction) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Backend/Account.fs:line 793 at Program.BroadcastPayment() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 82 at Program.PerformOperation(UInt32 numActiveAccounts, UInt32 numHotAccounts) in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 398 at Program.ProgramMainLoop[a]() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 481 at Program.NormalStartWithNoParameters() in /Users/knocte/Documents/Code/geewalletMASTERclean/src/GWallet.Frontend.Console/Program.fs:line 493 ``` This change also reduces a bit of primitive obsession (i.e. string vs BitcoinAddress) to make the code less "stringly-typed" lol. This should have been done in [1] but was an oversight on my part when reviewing. [1] #211
No description provided.