Show Posts
|
Pages: [1] 2 »
|
I have failed to reproduce the issue on my own. This has something to do with the state of your wallets. I'm going to need more data to figure out what's going. For starters, delete the .lmdb files in your datadir. They will reconstructed on the next run. See if that helps with the C++ signer.
Woot! Thanks, removing them, and with C++ signer, it worked. Still have those 4 confirmed txs which Armory thinks aren't confirmed (and offers to bump fee). I'll append tomorrow this one gets similarly stuck.
|
|
|
It looks like the Python signer is failing to populate the pubkey list of the unsigned tx object when it comes to imports. I'll investigate. For now, set yourself in expert user mode and try to manually pick the C++ signer at spend time, see if that fixes your issue.
(ERROR) TxFrames.py:925 - Problem sending transaction! Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx cppsigner.signTx() File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx return _CppBlockUtils.PythonSigner_signTx(self) RuntimeError: failed signature (ERROR) Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx cppsigner.signTx() File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx return _CppBlockUtils.PythonSigner_signTx(self) RuntimeError: failed signature Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx cppsigner.signTx() File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx return _CppBlockUtils.PythonSigner_signTx(self) RuntimeError: failed signature
|
|
|
What's vanity about it? Did you import a private key?
Edit:
Did you update your signer? Are you using mismatched versions between signer and online?
Yes, 1RustyRX2oai4EYYDpQGWvEL62BBGqN9T didn't occur naturally Hmm, it's the armory_0.96.3.99-gcc5.4_amd64.deb so I assume it's all included. I'm not doing offline signing. I don't need to reboot or anything? Happy to hand you whatever you need via GPG email, if it helps. Thanks, Rusty.
|
|
|
Yeah you want .2 or RC1
Didn't work. Moved the bug to RC1 thread.
|
|
|
Same problem with my save and restored 1RustyR vanity wallet:
(ERROR) TxFrames.py:925 - Problem sending transaction! Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx signerType=signer) File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature raise SignatureError('No PubKey that matches this privKey') SignatureError: No PubKey that matches this privKey (ERROR) Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx signerType=signer) File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature raise SignatureError('No PubKey that matches this privKey') SignatureError: No PubKey that matches this privKey
Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx signerType=signer) File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature DetSign, signerType=signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature raise SignatureError('No PubKey that matches this privKey') armoryengine.ArmoryUtils.SignatureError: No PubKey that matches this privKey
|
|
|
What version are you using? 0.96.3 has some signer issues.
Yep. Will try downgrading... 0.96.1 has same problem, different error: (ERROR) TxFrames.py:834 - Problem sending transaction! Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 828, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2682, in signUnsignedTx ustx.createAndInsertSignatureForInput(idx, addrObj.binPrivKey32_Plain) File "/usr/lib/armory/armoryengine/Transaction.py", line 2646, in createAndInsertSignatureForInput ustxi.createAndInsertSignature(self.pytxObj, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1398, in createAndInsertSignature derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1355, in createTxSignature raise SignatureError('No PubKey that matches this privKey') SignatureError: No PubKey that matches this privKey (ERROR) Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 828, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2682, in signUnsignedTx ustx.createAndInsertSignatureForInput(idx, addrObj.binPrivKey32_Plain) File "/usr/lib/armory/armoryengine/Transaction.py", line 2646, in createAndInsertSignatureForInput ustxi.createAndInsertSignature(self.pytxObj, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1398, in createAndInsertSignature derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1355, in createTxSignature raise SignatureError('No PubKey that matches this privKey') SignatureError: No PubKey that matches this privKey Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 828, in createTxAndBroadcast ustxSigned = self.wlt.signUnsignedTx(ustx) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2682, in signUnsignedTx ustx.createAndInsertSignatureForInput(idx, addrObj.binPrivKey32_Plain) File "/usr/lib/armory/armoryengine/Transaction.py", line 2646, in createAndInsertSignatureForInput ustxi.createAndInsertSignature(self.pytxObj, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1398, in createAndInsertSignature derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign) File "/usr/lib/armory/armoryengine/Transaction.py", line 1355, in createTxSignature raise SignatureError('No PubKey that matches this privKey') armoryengine.ArmoryUtils.SignatureError: No PubKey that matches this privKey
|
|
|
What version are you using? 0.96.3 has some signer issues.
Yep. Will try downgrading...
|
|
|
Hmm, my vanity-address wallet problems continue I selected a single UTXO and tried to send MAX with manully-set 135 sat/byte feerate: Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 871, in createTxAndBroadcast finalTx = ustxSigned.getSignedPyTx(signer=self.signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 2635, in getSignedPyTx raise SignatureError('Invalid signature while preparing final tx') armoryengine.ArmoryUtils.SignatureError: Invalid signature while preparing final tx (ERROR) Transaction.py:1488 - Signature in USTXI is not valid (ERROR) Transaction.py:2634 - Attempted to prepare final tx, but not all sigs available (ERROR) TxFrames.py:876 - Problem sending transaction! Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 871, in createTxAndBroadcast finalTx = ustxSigned.getSignedPyTx(signer=self.signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 2635, in getSignedPyTx raise SignatureError('Invalid signature while preparing final tx') SignatureError: Invalid signature while preparing final tx (ERROR) Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 871, in createTxAndBroadcast finalTx = ustxSigned.getSignedPyTx(signer=self.signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 2635, in getSignedPyTx raise SignatureError('Invalid signature while preparing final tx') SignatureError: Invalid signature while preparing final tx Traceback (most recent call last): File "/usr/lib/armory/ui/TxFrames.py", line 871, in createTxAndBroadcast finalTx = ustxSigned.getSignedPyTx(signer=self.signerType) File "/usr/lib/armory/armoryengine/Transaction.py", line 2635, in getSignedPyTx raise SignatureError('Invalid signature while preparing final tx') armoryengine.ArmoryUtils.SignatureError: Invalid signature while preparing final tx It then (I think it was after this) started scanning. After an hour or so, same error. This was the encrypted wallet I removed then restored, trying to get it to see that those "Right click to RBF" txs had actually gone through.
|
|
|
- I get a flashed-up-then-gone dialog on startup. Finally caught it on video, it's "Mirroring Wallets". Is this something I should be able to click on?
To allow for the use of segwit and compressed key in p2sh scripts, I developed a whole new wallet code. This stuff is in C++ and operates as companion code to the python stuff. The goal was to no disrupt the existing, time tested code, while providing new features for those willing to run new code. This flashing dialog is for the operation the mirrors the python wallet containers into their new, C++ implemented counterparts. These wallets are WO only, as they only need the data necessary to register the scripts with the DB and construct unsigned transactions. And no, there's nothing to click on, it is just there for report progress on the mirroring, and closes on its own. I figured I'd rather let people see something progress than silently mirror wallets, which can take up to a couple minutes on large wallets. You will see that dialog every run because you use an imported address, and the mirroring code goes through every import each run, since there is no deterministic way to verify the mirrored wallet is still in sync with the python counterpart. I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick). - Bump fee via right-click fails (see error below). This is my imported vanity addr 1RustyR...
Yep, I borked that when I fixed comments resolution in the main ledger. - You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):
And apparently I borked that too... fml. Thanks for the reports, will go over that stuff .4 Well, my tx didn't need bumping in the end. But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning? And trying to do a Wallet Consistency check gave a backtrace and an empty Perform Wallet Consistency Check with both buttons greyed out: (ERROR) ArmoryUtils.py:3192 - Error in pybkgdthread: 'unicode' object has no attribute 'walletPath' Traceback (most recent call last): File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3190, in run self.output = self.func() File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3127, in funcPartial return thefunc(*args, **kwargs) File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1848, in ParseWallet Progress=Progress) File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc return func(*args, **kwargs) File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1695, in FixWallet frt = fixer.ProcessWallet(wltPath, wlt, Passphrase, mode, Progress=Progress) File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc return func(*args, **kwargs) File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 400, in ProcessWallet WalletPath = Wallet.walletPath AttributeError: 'unicode' object has no attribute 'walletPath' Thanks! Rusty.
|
|
|
0.96.3 gcc 5.7 ubuntu deb. Three issues I've found (was on 0.93.3). - I get a flashed-up-then-gone dialog on startup. Finally caught it on video, it's "Mirroring Wallets". Is this something I should be able to click on? - Bump fee via right-click fails (see error below). This is my imported vanity addr 1RustyR... (ERROR) Traceback (most recent call last): File "/usr/bin/../lib/armory/ArmoryQt.py", line 3409, in showContextMenuLedger self.bumpFee(wltID, txHash) File "/usr/bin/../lib/armory/ArmoryQt.py", line 5913, in bumpFee addrComment = wlt.getCommentForAddress(h160) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 1818, in getCommentForAddress hashList = self.cppWallet.getScriptHashVectorForIndex(assetIndex) File "/usr/lib/armory/CppBlockUtils.py", line 4083, in getScriptHashVectorForIndex return _CppBlockUtils.WalletContainer_getScriptHashVectorForIndex(self, arg2) RuntimeError: invalid asset index
Traceback (most recent call last): File "/usr/bin/../lib/armory/ArmoryQt.py", line 3409, in showContextMenuLedger self.bumpFee(wltID, txHash) File "/usr/bin/../lib/armory/ArmoryQt.py", line 5913, in bumpFee addrComment = wlt.getCommentForAddress(h160) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 1818, in getCommentForAddress hashList = self.cppWallet.getScriptHashVectorForIndex(assetIndex) File "/usr/lib/armory/CppBlockUtils.py", line 4083, in getScriptHashVectorForIndex return _CppBlockUtils.WalletContainer_getScriptHashVectorForIndex(self, arg2) RuntimeError: invalid asset index
- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect): (ERROR) Traceback (most recent call last): File "/usr/lib/armory/ui/WalletFrames.py", line 289, in doRBF RBFDlg(self, self.main, wlt) File "/usr/lib/armory/ui/CoinControlUI.py", line 140, in __init__ self.rbfTreeModel = RBFTreeModel(self, wlt) File "/usr/lib/armory/ui/TreeViewGUI.py", line 998, in __init__ self.treeStruct = TreeStructure_RBF(self.wlt) File "/usr/lib/armory/ui/TreeViewGUI.py", line 708, in __init__ self.setup() File "/usr/lib/armory/ui/TreeViewGUI.py", line 714, in setup rbfList = self.wallet.getRBFTxOutList() File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 59, in inner return func(*args, **kwargs) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 512, in getRBFTxOutList utxos = self.cppWallet.getRBFTxOutList() File "/usr/lib/armory/CppBlockUtils.py", line 4005, in getRBFTxOutList return _CppBlockUtils.WalletContainer_getRBFTxOutList(self) DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7fafaba49600> >
Traceback (most recent call last): File "/usr/lib/armory/ui/WalletFrames.py", line 289, in doRBF RBFDlg(self, self.main, wlt) File "/usr/lib/armory/ui/CoinControlUI.py", line 140, in __init__ self.rbfTreeModel = RBFTreeModel(self, wlt) File "/usr/lib/armory/ui/TreeViewGUI.py", line 998, in __init__ self.treeStruct = TreeStructure_RBF(self.wlt) File "/usr/lib/armory/ui/TreeViewGUI.py", line 708, in __init__ self.setup() File "/usr/lib/armory/ui/TreeViewGUI.py", line 714, in setup rbfList = self.wallet.getRBFTxOutList() File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 59, in inner return func(*args, **kwargs) File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 512, in getRBFTxOutList utxos = self.cppWallet.getRBFTxOutList() File "/usr/lib/armory/CppBlockUtils.py", line 4005, in getRBFTxOutList return _CppBlockUtils.WalletContainer_getRBFTxOutList(self) <class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7fafaba49600> >
Hope that helps track something! Meanwhile I'll wait for my 2sat/byte TX Thanks! Rusty.
|
|
|
It doubles the total opening time, which may or may not be a problem. But outsourcability is so nice it's probably worth it!
About the opening time: could you clarify why there's an extra delay? I'm imagining that Alice would post her anchor tx and Bob would post his payment tx to Alice within seconds of each other. Bob is protected by a timeout, and Alice is protected because her tx is only paying herself at first. They wait until both txs are confirmed, then Bob can reveal his secret. Is this actually slower than your original method? Good point! And I've corrected my ml post, http://lists.linuxfoundation.org/pipermail/lightning-dev/2015-July/000069.htmlThanks! Rusty.
|
|
|
Maybe you should take a break from implementing stuff until this innovation-storm settles down I thought I did!
|
|
|
I like it! The atomic swap to inside the channel seems like a useful rebalancing technique in general (though asking me late Saturday night it's possible I missed something!). It's possibly more general than the thoughts I had for upgrading/changing anchors, but that requires more pondering. It doubles the total opening time, which may or may not be a problem. But outsourcability is so nice it's probably worth it! Now please go back in time and post this last week, before I implement dual-anchors
|
|
|
Hi everyone, just tagged alpha-01 of pettycoin, see http://pettycoin.org for faq and details. From the webpage: Pettycoin is an experimental open source project to create a public, scalable off-bitcoin network for small bitcoin transactions. It currently only runs on a test network. Cheers, Rusty Russell
|
|
|
Move this to the coin announcements sub-forum.
It's not an altcoin, hence I put it here. However, I'll post there too... Thanks! Rusty.
|
|
|
Hi everyone, just tagged alpha-01 of pettycoin, see http://pettycoin.org for faq and details. From the webpage: Pettycoin is an experimental open source project to create a public, scalable off-bitcoin network for small bitcoin transactions. It currently only runs on a test network. Cheers, Rusty Russell
|
|
|
Donated from my vanity address. I bought ~10 bitcoins in 2011 to support what I see as a promising open source project, and have been trickling them out since then to help the bitcoin economy.
But this helps the bitcoin project much more directly than me buying another pair of shoes!
Inspirational work, Jeff!
|
|
|
If you search the topic in baidu of the last week's price rise, and you search in Chinese, most posts and reports ascribe it to the recent adoption of bitcoin payment method by a web service of Baidu (jiasule.baidu.com).
BTW, do you have a bitcoin address we can tip to? Cheers, Rusty.
|
|
|
OK, Alex agrees, you get the 0.8BTC! Nice work! But you didn't put a Bitcoin address anywhere I can see it? Please fix CatalinWNC gets the 0.2 runner-up prize. Please post at BTC address too. Thanks, Rusty & Alex.
|
|
|
|